Working offline & sync
Where: POS — everything, all the time Who: all POS users
The POS is designed for exactly this: keep selling when the internet dies. Everything needed to run a sale lives on the device itself.
What works offline — fully
- Browsing and searching the catalog (including product & collection images — they're cached on the device)
- Signing in cashiers by PIN
- Creating orders, holding/resuming, checkout, printing
- Stock display from the last sync
What pauses offline
Nothing stops — but outbound data queues: sales, stock movements and any local changes wait on the device and upload the moment the connection returns. Inbound updates (new products, price changes, new cashiers, new collections) arrive at the next successful sync.
The sync cycle
While online, the terminal syncs about once a minute:
- Push — queued local changes upload
- Pull — anything new on the server comes down
- Images — new product/collection images download in the background
Reading the sync indicator
The status area shows pending changes (queued uploads — should trend toward zero) and the last sync time. "Last sync: 3 minutes ago" = healthy; "2 days ago" = the till has been offline — sales are safe, but it's running on older data.
Good to know
- Long offline periods are fine — nothing is lost; the queue just gets longer.
- If the till is online but Last sync isn't moving, the device may have been revoked — check its status in the dashboard.
- A manager can force a sync cycle from the terminal's settings instead of waiting for the next automatic one.