Offline-First Mode

How it works

Every change is written to the device’s local database first. While offline it waits in the queue; once connected, the queue drains in order and the cloud confirms each item.

Nothing stops at the counter

Sales, shifts, stock movements, and settings changes all write to the local database first. A lost connection never blocks a transaction.

The offline queue

Every change — a sale, a shift event, a stock movement, a settings update — is appended to the outbound queue. When connectivity returns, the queue drains in order and the server acknowledges each item. Every item is tracked as pending, synced, or failed, so nothing disappears silently.

Checking the queue

The Offline Queue screen (manager) shows how many items are pending, synced, and failed, plus any conflicts, the last successful sync, and how old the oldest pending item is. Use Sync All to drain immediately, pull to refresh, or delete a stuck item. Items from the server that repeatedly fail to apply are quarantined and can be requeued once the cause is fixed.

Conflicts

Because each register works on its own local data and merges are order-based, conflicts are rare and resolve deterministically — the latest change wins for each record. Resolved conflicts surface as a count on the queue screen, so you know it happened.

Cloud sync and plans

Cloud sync moves the queue between registers and is part of paid plans. On a plan without sync, the offline queue keeps working exactly the same — sales are safe locally and drain the moment you upgrade. See Cloud Sync for what syncs and how to check its status.