Integration · Clover
Clover multi-location reporting for head office
Clover Dashboard shows one merchant at a time. Stores360 reads every Clover merchant in your estate through the Clover API and puts them on one screen, so head office sees revenue by store and by trading day without logging into each account.
In short
Stores360 reads orders, payments, items and employees from each Clover merchant through the Clover REST API and shows every location on one head-office dashboard: revenue by store and trading day, comparisons between locations, and royalty invoices calculated from those actual sales. Setup is a merchant ID and an API token per location; nothing changes at the till.
What we read from Clover
Exactly the datasets the connection retrieves — nothing listed here that the integration does not fetch.
Orders, with line items, payments and the employee
Each order is retrieved expanded, so the line items, the payments that settled it and the employee who rang it arrive in one read. This is the dataset the curated daily-sales figures are built from.
Payments, refunds and credits
Retrieved as their own collections so a refunded order is visible as a refund rather than as a quietly smaller total. Stored raw today; curated views are on the roadmap.
Items, categories, modifier groups, discounts and tax rates
The catalogue as Clover holds it, so a menu or product comparison across locations uses the same names each store actually sells under.
Employees, roles and shifts
Who was on the till and when. Employees are curated; roles and shifts are stored raw for now.
Merchant profile, address, opening hours, tenders, order types and cash events
The reference data a multi-location report needs to make sense of a location, retrieved once per run and kept in step.
What head office sees that Clover doesn't show
One view across every merchant
Clover Dashboard is one merchant, one login. A twelve-store operator on Clover has twelve dashboards. Stores360 shows all twelve, ranked, on one page, and a mixed estate with Toast locations appears on the same page.
Royalties from the same sales figure
Royalty invoices are calculated from the synced Clover orders, so the franchisor and the franchisee are looking at one number and the invoice shows the working.
Brand-standard audits with photo evidence
Clover records what was sold. It does not record whether the store was clean, signed correctly or staffed to standard. Audits run on a phone with photos and scores, tied to the same location record as the sales.
Announcements that record receipt
A head-office instruction sent through Stores360 records who received it and who acknowledged it — the thing a group email cannot prove.
An immutable audit log
Every consequential change — a royalty rate, an audit score, a connection edit — is written to a log that cannot be edited afterwards.
Connecting a location
One connection per Clover account. Head office can add every location from one Stores360 account; nothing is installed at the store.
Before you connect
- Access to Clover Dashboard for the location, with permission to view Business Information and create API tokens.
- The location’s merchant ID — one per location.
- 1
Find the merchant ID
In Clover Dashboard, open Account & Setup → Business Information. The merchant ID is the short alphanumeric code shown there; one merchant ID per location.
- 2
Create an API token
In Clover Dashboard, open Account & Setup → API Tokens and create a token with read permission for orders, payments, inventory, employees and merchant. Copy it once; Clover does not show it again.
- 3
Add the connection in Stores360
In Stores360, open the location, choose Add POS connection, select Clover, and enter the merchant ID, a display name and the API token. The token is used to open the connection and is never shown again.
- 4
Set the sync schedule
Choose hourly, daily at a set time, or several times a day, in the location’s own timezone. Daily at 02:00 local time is the default.
- 5
Run the first sync and check the figures
Use Sync now. Within a few minutes the location shows its last sync time and status, and its sales appear on the head-office dashboard. Compare one trading day against Clover Dashboard before you rely on it.
How often, and what happens when it fails
Scheduled retrieval
Each connection has its own schedule — hourly, once a day at a set time, or several set times a day — run in the location’s timezone. A manual sync can be triggered at any time from the location.
Webhooks
Clover change notifications are received, verified by signature, and recorded against the connection, so a sync failure or a merchant change is visible to an operator rather than discovered later.
Failure handling
A failed run leaves a durable failure record with the reason, shown on the location. A run that partly succeeds keeps what it retrieved and reports which datasets it did not.
Royalties from Clover sales
Royalty policies in Stores360 are applied to the curated sales the connection produces. A billing run takes each location's synced sales for the period, applies the policy, and issues a per-location invoice that shows the sales figure it was calculated from. The franchisor and the franchisee are looking at the same number, read from the same till.
How royalty billing works, step by step →Limits, stated up front
- Each Clover merchant is one connection. A location with two merchants (two tills on separate accounts) is two connections on the same location.
- Curated sales figures are derived from orders, items and employees today. The other datasets are retrieved and stored raw, and are not yet shown on the dashboard.
- Stores360 reads from Clover. It does not write to Clover: no menu pushes, no price changes, no refunds issued from head office.
Pricing
From $87 per store, per month, with no per-user fees. The Clover connection is included; there is no per-integration charge. Details on the pricing page.
The methods behind this
Written to be useful whether or not you ever buy anything from us.
How to connect a POS to head-office reporting
What a POS integration has to get right before head office should believe a single number it produces.
How to track sales across multiple store locations
One comparable number per store per day — including the details that quietly break most multi-site sales reports.
How to calculate and invoice franchise royalties
Turn the monthly royalty spreadsheet into a policy, a billing run and an invoice per location.
Frequently asked questions
Do I need a new POS to use Stores360 with Clover?
No. Stores360 reads from the Clover account each location already has, through the Clover API. Nothing is installed on the device and nothing changes at the till.
How often is Clover data refreshed?
On the schedule you set per location — hourly, daily at a set time, or several times a day — plus a manual sync whenever you want one. Clover webhooks are also received and recorded against the connection.
Can I compare Clover stores with stores on a different POS?
Yes. Every connection normalises into the same curated sales records, so a Clover location and a Toast location appear on the same dashboard and the same ranking.
What does head office see that Clover Dashboard does not?
Every merchant 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. Clover Dashboard shows one merchant’s sales.
Does each store need a Stores360 login?
No. Head office can connect 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.
What does Stores360 need from Clover?
The merchant ID and an API token with read permission. The token is used to open the connection and is stored in a secrets store, never in the connection record and never shown again.
Does Stores360 write anything back to Clover?
No. The integration is read-only. Prices, menus and refunds are managed in Clover as they are today.
See how this fits into manage 10+ locations from one dashboard and franchise management software for brands and their operators, or see every POS we read.
Running Clover in more than one location?
Tell us how many, and we will show you every one of them on a single screen. From $87 per store, per month.
Read-only. Nothing changes at the till.