POS integrations
Every store’s POS, one head-office view
Head office should not need a login for every till. Stores360 connects to the point-of-sale in each location and reads sales into one dashboard.
In short
Stores360 connects to the point-of-sale system in each of your locations and reads sales into one dashboard for head office. Clover and Toast are read live through their APIs on a schedule you set per location. Mixed estates — some stores on Clover, some on Toast — are shown side by side on the same ranking.
Every POS we read
Supported means a live connection you can add today. Planned means it is not built yet, and we will not pretend otherwise.
Clover
SupportedSupported — live API and webhooks
Clover REST API on a schedule, plus Clover webhooks for change events.
Clover multi-location reporting
Toast
SupportedSupported — live API and webhooks
Toast REST API on a schedule, plus Toast webhooks for change events.
Toast multi-location reporting
Square
PlannedPlanned — tell us if you run Square
Not yet connected. Tell us which locations run Square and we will tell you when it is.
Tell us you run SquareRunning something else?
Tell us which POS you run and how many locations. We will say honestly whether we can read it, and when.
Tell us your POSHow a connection works
Each location holds its own connection to its own POS account: a merchant ID for Clover, a restaurant GUID for Toast, plus the credential that provider issues. Head office adds them all from one Stores360 account. Nothing is installed at the store and nothing changes at the till.
Every connection runs on its own schedule — hourly, daily at a set time, or several times a day — in the location's own timezone, and can be synced by hand at any time. Provider webhooks are received, verified by signature, and recorded against the connection. A failed run leaves a durable record with the reason, shown on the location, rather than a quietly stale number.
What each provider can retrieve is declared per provider, not discovered later. Clover exposes nineteen datasets; Toast exposes seven. Both pages say exactly which, and which it cannot.
Frequently asked questions
Do I need a new POS?
No. Stores360 reads from the POS each location already has. Nothing is installed on the device and nothing changes at the till. If a location runs a POS we do not read yet, tell us which one on the request-access form.
How often is POS data refreshed?
On the schedule you set per location — hourly, daily at a set time, or several times a day — in the location’s own timezone, plus a manual sync whenever you want one.
Can stores on different POS systems be compared?
Yes. Every connection normalises into the same curated sales records, so a Clover location and a Toast restaurant appear on the same dashboard and the same ranking.
What does head office see that the POS dashboard does not?
Every location on one page; comparisons between locations; royalties calculated from the synced sales; brand-standard audits with photo evidence; announcements that record receipt; and an immutable audit log. A POS dashboard shows one account’s sales.
Is a store-level login required?
No. Head office connects every location from one account. Franchisees can be given their own role-scoped login to see their own location, but the connection does not depend on it.
Which POS systems are supported today?
Clover and Toast, both through their live APIs with webhooks. Square is planned. Anything else: tell us which POS you run and how many locations, and we will say honestly whether and when.
For the wider comparison, see Stores360 versus POS-native multi-store reporting.
Every till, one screen
From $87 per store, per month, with no per-user fees. The connection is included; there is no per-integration charge.