Cloud sync and store status
A connected store sends its business data to FMX EPOS Cloud, and Cloud sends selected changes back to the store. Cloud pages show what the store last sent, so check the times and status on each page before you rely on it.
Check sync on the till
Section titled “Check sync on the till”Signed in to the Back Office on the till:
- Open Back Office → System Settings → Cloud.
- Check Store and Catalogue. Changes to Upload means the catalogue was changed on the till and goes up with the next sync. Conflict with Version … needs a decision: select Compare in Menus.
- Check Last Sync.
- If the last sync failed, a Last Error line shows why.
Illustration, not a screenshot. The real screen can differ with the theme or version.
The store syncs once a minute unless its licence sets a different interval, shown under Syncs Every on the store’s Store Overview page in Cloud. A page can therefore be slightly behind even when everything is working.
Any till running on the Cloud licence can carry the sync, so syncing continues when one till is switched off. It does not have to be the Integration Host.
The Cloud connection and licence mode are set on Back Office → Licence, not on the Cloud tab.
Check status in Cloud
Section titled “Check status in Cloud”Every store page in Cloud starts with what the store last reported about its sync:
- a red Store sync problem notice when the till’s last sync failed, a published menu version was not applied or a Cloud change could not be carried out. It gives the time of the last complete sync and the reason. If it says Cloud changes not carried out, changes waiting for the store stay waiting until that problem is fixed;
- a blue notice while the store uploads its data again, with how many tables are done. Until it finishes, the pages may be incomplete.
Then open the Store Overview page and check:
- today’s Net Sales, Cash, Card and Open Orders;
- Running Tills: the tills that have run on the Cloud licence in the last 30 days, each Online or Offline;
- Tills and Platforms: each till’s last contact and version, and each platform as Polling, Polling Off or Failing. The card’s subtitle says when the store last reported and Last change received (when the store’s latest changes reached Cloud). A till showing write(s) waiting for the database is holding work it took while the restaurant database was unreachable, and sends it once the database is back;
- Menus: the catalogue versions and any conflict.
Tills and Platforms
As the store reported at 10:41.
- Front TillOnline
- Bar Till2 writes waiting for the databaseOffline
- Just EatPolling
Illustration, not a screenshot. The real screen can differ with the theme or version.
The top of the Online Ordering page shows whether the store is taking website and QR orders: Taking Orders, Not Taking Orders or Not Connected.
The Overview page under Workspace shows today’s figures for every store in one table, each by that store’s business day, with the last sync time. Released stores are not listed. A store with a failing sync shows Sync Problem, and one uploading its data again shows Uploading Data Again. Data not yet synced is not included.
If you manage more than one store, the list at the top of each store page opens the same page for another store. Return to Workspace goes back to the Stores page.
Initial history snapshot
Section titled “Initial history snapshot”After the first claim, the store can upload a snapshot of its earlier business history.
- Keep at least one till running on the Cloud licence.
- Keep its restaurant database and internet connections up.
- Follow the progress in the notice at the top of the store’s pages in Cloud, for example (12 of 24 tables done).
- Treat reports as incomplete until the notice has gone.
Later syncs carry new changes. You can keep trading during the upload, but reports cannot include records Cloud has not yet received. A CSV file exported during the upload has -incomplete in its name.
When a store that was disconnected connects again, it uploads its whole history again. For a large store this can take several minutes, and the store’s Cloud pages are incomplete until it has finished.
How Cloud changes reach the store
Section titled “How Cloud changes reach the store”Pages such as Staff, Sales Settings, Restaurant, Membership, Platform Mapping, Coupons, Online Ordering and the Sold Out tab of Menus send changes to the store.
- A Cloud user with permission saves the change.
- Cloud shows Waiting for the Store.
- The store picks the change up at its next sync.
- The store checks it against the same rules the till uses, then applies it.
- Cloud shows Applied at the Store. Cloud’s copy of the record updates with the next data sync.
- If the store’s checks reject the change, Cloud shows Refused by the store: and the reason.
Illustration, not a screenshot. The real screen can differ with the theme or version.
Some pages allow only one waiting change for the same area, so wait for its result before you submit another.
Read-only operational view
Section titled “Read-only operational view”The Live Status page shows the store’s latest report of open tables, kitchen screens, print problems, terminals and connected platforms. Use it to find where a problem is. It cannot control a till, a printer or a kitchen screen. See Live Status.
Fix printer, kitchen display, database or network problems at the restaurant, then wait for the next sync to update Cloud.
Recover a stalled sync
Section titled “Recover a stalled sync”- Check that the Cloud licence is valid and that Cloud Licensing shows In Use on the till’s Licence page. A store on offline licensing does not sync.
- Check that at least one till running on the Cloud licence is switched on. A till showing No Seat can still carry the sync.
- Check that the till can reach the restaurant database.
- Check that it can reach FMX EPOS Cloud and that the Windows clock is correct.
- Read the exact error on the till’s Cloud settings tab, and the Store sync problem notice in Cloud.
- Check whether a catalogue conflict or a refused change is waiting for someone to decide.
- If the till’s sign-in page says Update this till to EPOS … or later for cloud sync, install the current Till version on that till through your normal update process. If the sales screen shows Cloud sync stopped, read the till it names, for example Update EPOS on Bar Till for cloud sync., and update that till. The sales screen of every till shows the same notice, so the till to update may not be the one in front of you. A till below Cloud’s minimum version can still trade locally on a valid licence, but it cannot sync with Cloud. It hands the sync over, so an updated till that is running carries it on, and it tries again after 15 minutes or when it restarts.
- Fix the problem reported and let the next sync run.
- Check that Last Sync moves on and Last Error clears.
If a Cloud page says The cloud database did not answer. Try again., the fault is in Cloud itself. Wait a moment and repeat the action.
Do not release the store to clear an error: releasing closes the store’s Cloud record and stops its connected services. If the error persists, give support the store’s status, the terminal name, the time and the exact error shown. Never send passwords or connection strings.
What Cloud cannot confirm
Section titled “What Cloud cannot confirm”Cloud only reports what the store has synced. Even when every Cloud page looks healthy, it cannot prove that a receipt printed, that the kitchen saw a ticket, or that a card terminal completed its own transaction. Those devices and providers have their own status.