Selling & payments

Keep selling offline

An online-loaded POS can queue supported sales on the same device during an outage.

WHERE TO FIND IT

POS → connection indicator

Step by step

Open POS while online at the start of the day to refresh products and prices.
During an outage, watch the connection indicator and use cash for offline sales.
Reconnect on the same device and wait until the pending-sale count reaches zero.
For failed syncs, read the reason and ask a manager to correct it before Retry.

Load POS online so its catalog and prices are available on that device. The connectivity indicator distinguishes online, offline and pending or failed synchronisation; check the pending count before closing.
Offline records stay in that browser on that device. Do not sign out, clear site data, reinstall the browser or move to another device while sales are pending. Keep the device available until it reconnects.
Use payment methods that can be safely confirmed. Bank confirmations, online balances and connected services still need their own connectivity; do not assume an offline POS verifies them.

Open the till’s pending or failed queue and inspect the reason. Reconnect with the same user and device; wait for the server response before trying again.
A manager can review rejected sales in the back-office sync log. Fix stock, batch, customer-credit or access problems, then retry through the supported action. Never recreate a queued sale just to hide its error.
Confirm the queue reaches zero and the sale appears once in Sales history. Check any remaining failed entries individually before ending the shift.

A recovered sale remains attributed to the cashier who originally recorded it, even if a manager retries it from the Sync log.
If the store enforces shifts and that cashier’s shift has closed, resolve the displayed shift requirement for the original cashier before retrying. Do not change cashier identity or create a replacement sale to bypass the rejected record.
Retry after correcting the cause; dismiss only a confirmed duplicate or unwanted queue item with the proper permission. Keep browser data while any unsynchronised records remain.

Cached product catalog: Load online first, then browse and sell from the device copy.
Offline cash checkout: Scan items, take cash and print using compatible local hardware.
Automatic reconnect sync: Queue sales locally and upload them when connectivity returns.
Connection & queue status: See connection health and how many sales await sync.
Failed-sale recovery: Review errors and retry queued sales after correcting the cause.
Back-office sync log: Review successful, failed and conflicting offline submissions.
Duplicate-safe retries: Replay saved sales without creating another copy of the transaction.
Resolve sync exceptions: Dismiss audited exceptions and restore them for review when needed.