Offline selling and sync
A shop cannot stop selling because the internet does. MyShopie POS keeps a local copy of the catalog on the tablet and queues completed sales when the connection drops, then replays them once it is back. Trading continues; what pauses is anything that needs a live answer from somewhere else.
Plans: Retail, Growth, Enterprise
Requires app: Point of Sale. Install Point of Sale from Settings → Apps before these screens appear.
What keeps working, and what does not
Section titled “What keeps working, and what does not”| Capability | Offline | Why |
|---|---|---|
| Searching and adding catalog items | Yes | The tablet holds a local catalog snapshot |
| Custom lines | Yes | Nothing to look up |
| Cash tenders and change | Yes | Arithmetic is local |
| Completing a sale | Yes | Queued and replayed on reconnect |
| Voids, price overrides, no-sales | Yes | Logged locally and replayed with the sale |
| Opening and closing a shift | Yes | Replayed with the rest of the queue |
| Card payment on a terminal | No | Authorisation has to reach the acquirer |
| Store credit | No | The balance is authoritative server-side |
| Loyalty balances and rewards | No | Same reason |
| Promotion code verification | No | A code is checked against live conditions |
| Refunds and exchanges | No | They need the original order and its refund history |
| Live stock levels | Snapshot only | The catalog is as of the last sync |
The split is consistent: anything the tablet can decide by itself works, and anything that depends on an authoritative answer elsewhere waits.
How the queue works
Section titled “How the queue works”-
A sale completes on the tablet. The cashier sees it as finished and the customer gets a receipt. The order is written to a local queue with its own client-side identifier.
-
The connection returns. The app replays the queue to the store.
-
Each queued item is applied once. The identifier makes replay idempotent — if the connection drops halfway through the replay and the app tries again, already-applied sales are recognised rather than duplicated.
-
Stock, orders and shift figures catch up. The sales appear in the Orders list, the shift’s expected cash reflects the cash tenders, and any overrides land in the override log with their original timestamps.
This is why the override log for a lane that has been offline fills in all at once: the entries carry the time the action happened, not the time it synced.
Running through an outage
Section titled “Running through an outage”-
Keep selling for cash. Tell staff explicitly that card is unavailable — the failure mode to avoid is a cashier assuming a terminal is broken and trying it repeatedly.
-
Do not promise stock you cannot see. Treat the quantity on screen as approximate for anything that moves quickly.
-
Hold refunds. Note the customer’s details and process the return once you are back online rather than paying out against a sale you cannot read.
-
Close the shift normally if the outage spans the end of trading. The close is queued like everything else. Count the drawer accurately; the reconciliation happens when the queue replays.
-
Check the sync afterwards. Open Dashboard → POS → Registers and confirm the register’s last-used time is current, then confirm the day’s orders are all present.
Spot a register that has stopped syncing
Section titled “Spot a register that has stopped syncing”The signal is in Dashboard → POS → Registers: the device panel’s Token last used at. A lane that is clearly trading but whose token was last used hours ago is selling into its queue. Causes, in rough order of likelihood:
- The tablet’s network dropped — venue Wi-Fi, an expired captive-portal session, a SIM out of data.
- The tablet is in a power-saving state that is suspending background work.
- The app has not been foregrounded since the connection returned. Opening the app prompts a replay.
If a tablet has been offline for an extended period, foreground the app on a known-good connection and leave it until the queue drains before you start a new shift on it.
Common problems
Section titled “Common problems”Orders from yesterday are missing from the dashboard. The tablet has not synced. Foreground the app on a working connection; the queue replays. Do not re-ring the sales by hand — they will duplicate when the queue finally drains.
A card tender was recorded but the terminal has no record of it. A card taken on a standalone terminal is captured by the cashier, so an offline sale can record a card tender that was never authorised. Reconcile card tenders against the acquirer’s statement after any outage.
Stock went negative on a line. It was oversold while one or more tablets were offline against a stale snapshot. Correct the stock, and treat it as a reason to shorten how long you trade disconnected.
A shift shows a huge variance after an outage. Check that the opening float and the close count both replayed, and that the cash movements during the outage were recorded on the tablet rather than on paper.
The same sale appears twice. Rare, and almost never the queue — replay is idempotent. Check whether a cashier re-rang a sale manually because they believed the first had been lost.
Will a dropped connection lose a sale? No. A completed sale is held on the tablet and replayed when the connection returns. Each queued sale carries its own identifier, so a replay that is interrupted and retried does not create a duplicate.
Can I take a card payment offline? No. A card authorisation has to reach the acquirer, so card tenders need connectivity at the moment of the sale. Cash completes offline.
Will the tablet sell stock it does not have? It can. The offline catalog is a snapshot, so stock levels drift while the tablet is offline and oversell is possible on fast-moving lines. This is the main reason to keep offline trading to the length of an outage rather than a way of working.
How do I tell whether a register is syncing? Open Dashboard → POS → Registers and look at Token last used in the device panel. A lane that is trading but whose last-used time is hours old is selling into its queue.
