Integration · Toast
Toast multi-location reporting for head office
Toast reports one restaurant at a time, and its multi-location views stop at sales. Stores360 reads every Toast restaurant in your group through the Toast API and puts them on one screen with the audits, royalties and records a franchise actually runs on.
In short
Stores360 reads orders, menus, employees, shifts and cash entries from each Toast restaurant through the Toast API and shows every location on one head-office dashboard: revenue by restaurant and trading day, comparisons between locations, and royalty invoices calculated from those actual sales. Setup is your Toast API client credentials and one restaurant GUID per location.
What we read from Toast
Exactly the datasets the connection retrieves — nothing listed here that the integration does not fetch.
Orders and checks
Orders are read for a rolling window each run, with their checks and payments attached, because Toast keeps payment on the check rather than as a separate collection. This is the dataset the curated daily-sales figures are built from.
Menus
The published menus for the restaurant, so item-level comparisons across locations use the names each restaurant actually sells under.
Employees and shifts
Who was working and when, from Toast’s labour endpoints. Employees are curated; shifts are stored raw.
Cash entries and dining options
Cash-management entries and the restaurant’s dining options (dine-in, takeout, delivery), retrieved and stored raw for later reporting.
Restaurant profile
The restaurant’s own record, retrieved each run so a location’s name and settings stay in step.
What head office sees that Toast doesn't show
One view across every restaurant
Toast’s reporting is per restaurant, with group views that cover sales. Stores360 shows every restaurant, ranked, on one page, and a mixed group with Clover locations appears on the same page.
Royalties from the same sales figure
Royalty invoices are calculated from the synced Toast orders, so the franchisor and the franchisee are looking at one number and the invoice shows the working.
Brand-standard audits with photo evidence
Toast records what was sold. It does not record whether the kitchen passed inspection, the signage was right or the opening checklist was done. 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.
An immutable audit log
Every consequential change is written to a log that cannot be edited afterwards — including changes to the Toast connection itself.
Connecting a location
One connection per Toast account. Head office can add every location from one Stores360 account; nothing is installed at the store.
Before you connect
- An active Toast employee account at the restaurant enabling API access.
- A Toast subscription at RMS Essentials or higher — standard API access is not available on lower tiers.
- The Manage Integrations permission on that employee account.
- 1
Get Toast API access
Toast issues API credentials — a client ID and client secret — through its partner and developer programme. One credential set can reach every restaurant in your group that has granted it access.
- 2
Find each restaurant’s GUID
In Toast Web, each restaurant has a GUID (a long hexadecimal identifier). You need one per location you want to connect.
- 3
Add the connection in Stores360
In Stores360, open the location, choose Add POS connection, select Toast, and enter the restaurant GUID, a display name and the client secret. Stores360 exchanges the credentials for a token itself; the secret is stored in a secrets store and 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 Toast’s own sales summary 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 restaurant’s timezone. Orders are read for a rolling window so a late-closing night is not split across two runs.
Webhooks
Toast notifications are received, verified by signature, and recorded against the connection.
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 Toast 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
- Toast has no separate payments, tenders, refunds, discounts, modifier-groups, tax-rates or customers collections to retrieve. Payments are read as part of each check; the rest are simply not available from Toast’s API and are not claimed.
- Orders are retrieved in pages with an upper bound per run. A very high-volume restaurant on a daily schedule may need an hourly one; the run reports when it reached the bound.
- Stores360 reads from Toast. It does not write to Toast: no menu pushes, no price changes, no voids issued from head office.
Pricing
From $87 per store, per month, with no per-user fees. The Toast 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 Toast?
No. Stores360 reads from the Toast restaurants you already run, through the Toast API. Nothing is installed on the terminals and nothing changes at the till.
How often is Toast 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. Toast webhooks are also received and recorded against the connection.
Can I compare Toast restaurants with locations on a different POS?
Yes. Every connection normalises into the same curated sales records, so a Toast restaurant and a Clover location appear on the same dashboard and the same ranking.
What does head office see that Toast does not show?
Every restaurant 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.
What does Stores360 need from Toast?
Toast API client credentials and the GUID of each restaurant. One credential set can cover every restaurant that has granted it access; the secret is stored in a secrets store, never in the connection record.
What does Toast not expose?
Separate payments, tenders, refunds, discounts, modifier groups, tax rates and customers are not retrievable from Toast’s API. Payments arrive attached to each check. Stores360 declares these limits per provider rather than leaving an empty report to discover later.
Does Stores360 write anything back to Toast?
No. The integration is read-only. Menus, prices and voids are managed in Toast 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 Toast 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.