When to use this: understanding (and explaining to staff) what happens when the whole shop loses internet with 3 counters billing.
How it behaves
-
Each session runs independently — its own local data, its own upload queue. No session blocks another.
-
Bill numbers stay unique — each session bills on its own numbered series, identified by a terminal letter inside the bill number (
AH1A-2627-000001— store code, terminal A, financial year, sequence). session A and session B therefore cannot produce the same number, even with nobody online to co-ordinate them. Staff see nothing different on the receipt: the number printed offline is the permanent one. -
Reconnection merges everything — all queues upload; sales, stock movements and registers consolidate. Stock counts reflect all session' sales once synced.
Set expectations
- Each device must already be bound to its counter before the connection drops. Assigning or switching a counter needs the server, so it is unavailable offline — a device that is already billing on counter B simply carries on.
- During the outage each counter sees its own unsynced sales only; the combined picture (dashboard, stock) completes after everyone syncs.
- A return can only be raised on the counter that billed it while you are offline; the other counters' bills come back into reach when the shop reconnects.
- Long outage? Just leave the BitMed windows open and on screen — the queues hold regardless, but a hidden or minimised tab is throttled by the browser and drains more slowly once the connection returns.