Offline POS: Keep Selling During Load-Shedding and Internet Cuts

If you run a retail counter in Pakistan, you already know the two interruptions that can freeze a sale at the worst possible moment: load-shedding and a patchy internet connection. A cloud-only point-of-sale system is only as reliable as the link between your shop and the server. When that link drops — a tripped feeder, a fibre cut, a weak mobile signal in a back-of-shop corner — a purely online POS simply stops working, and a customer is left standing at the counter while the screen spins.

POS Line is built offline-first precisely because these interruptions are a normal part of trading here, not a rare emergency. The goal is simple: a power flicker or a few minutes without internet should never mean a lost sale, a confused cashier, or a queue of frustrated customers. Your counter keeps running on the device in front of the cashier, and the system catches up with the cloud automatically once the connection returns.

POS Line runs in the browser and keeps a working copy of what the cashier needs right on the device. When the internet drops, the POS does not error out — it switches to a local mode and continues to accept sales.

Behind the scenes, each completed sale is written to a local queue stored in the browser using IndexedDB — a small on-device database. This means the sale is saved to the physical device immediately, before it ever needs to reach the server. The queue holds every transaction made while offline, in order, waiting for the connection to come back.

• No spinner of death: the cashier doesn't wait on the network to finish a sale.
• Saved locally first: each sale is persisted to the device the moment it's rung up.
• Held in a queue: offline sales line up safely until POS Line can sync them to the cloud.

Because the data lives on the device, a brief power flicker that reloads the page does not wipe your pending sales — they remain queued, ready to sync.

Offline mode is meant to keep the core checkout flow moving so the line keeps clearing. While the connection is down, a cashier can still:

• Ring up a sale — add items to the cart and complete the transaction at the counter.
• Take payment and close out the sale, with each transaction stored locally in the queue.
• Keep serving the next customer without waiting for the network to recover.

The important honest point is this: offline mode is designed to keep checkout running, not to replace every cloud-dependent action. Features that genuinely need a live connection — for example, anything that has to reach an external service in real time — will resume as soon as you're back online. The design priority is that the till keeps taking money so you never turn a paying customer away during an outage.

You don't have to remember to do anything special when the internet comes back. As soon as POS Line detects a connection again, it begins syncing the queued sales to the cloud automatically, in the background, while the cashier keeps working.

1. Connection returns — power and internet are restored at the shop.
2. Queue drains — POS Line pushes each locally-stored sale up to the server.
3. Records reconcile — your dashboard, reports, and stock catch up to reflect every offline transaction.

The result is that nothing made during the outage is lost. Sales taken in the dark are exactly the sales that show up in your records once the lights are back on.

The biggest fear with any offline-then-sync system is a sale being posted twice — a duplicate order, or worse, a double charge — if a network hiccup makes the device unsure whether the server already received a transaction.

POS Line handles this with idempotent reconciliation. In plain terms, each queued sale carries an identity that the server recognises. If the same sale reaches the server more than once — say the connection drops mid-sync and the device retries — the server recognises it as one already recorded and does not create a second copy. Each real sale lands exactly once.

This is what makes the sync safe to run automatically. The system can retry as aggressively as it needs to over a flaky connection, confident that nothing is lost and nothing is double-posted.

It's worth being clear about how this works so you can plan around it. Offline mode keeps your counter selling, but the queued sales live on that one device until it reconnects. A few practical points:

• The device must come back online to sync. Until it does, those offline sales exist only on that device's local queue — they won't yet appear in your cloud dashboard or on another terminal.
• Keep the device powered. Pair your POS device with the same UPS or battery backup you use to keep trading through load-shedding, so it stays on and can sync the moment internet returns.
• Let it finish syncing. When you're back online, give the device a moment on a stable connection so the queue can fully drain before you close up for the day.

Used this way, POS Line turns the two most common interruptions in Pakistani retail — load-shedding and a dropped internet line — from a reason to stop selling into a non-event your cashiers barely notice.