How does a POS keep billing when the internet goes down?

Nothing dramatic — and that is the point. The POS notices the connection is gone, switches to offline mode, and the cashier keeps billing. Items still come from the product catalog the device already has, quantities and totals work normally, and the receipt printer keeps printing because it sits on the shop's own network, not the internet.

Sales taken during the cut are cash sales, saved safely on the device with a clearly marked provisional receipt — the printout says it is an offline sale, so a provisional slip can never be confused with a final tax bill. Even a bill that was opened before the cut can be settled during it; the system reconciles it cleanly with the original once the connection returns.

• Billing screen, cart, and receipt printing keep working
• Offline sales are cash sales, stored on the counter device
• Receipts are explicitly marked as provisional offline sales
• A bill opened before the cut can still be settled during it

Every offline sale is created with its own unique reference on the device. When the connection returns, the queue uploads — and if the upload is interrupted and retried, or the page reloads and submits the same queue again, the server recognises each reference and simply returns the sale it already recorded. However messy the reconnect, one sale ends up in the books exactly once.

Syncing is also automatic in both directions that matter: it fires the moment the POS comes back online, and it fires again whenever the POS is next opened — so sales queued before a device restart don't sit forgotten. The cashier never has to remember to press an upload button.

The server, always. When an offline sale syncs, the server re-prices every line from its own catalog and checks the arithmetic before accepting the sale as paid. The counter device is treated as a witness to what was sold, never as the authority on what it cost — which closes the door on tampered devices or stale price lists quietly corrupting your books.

Anything that doesn't add up — an item the server doesn't recognise, a discount beyond what that cashier is allowed, cash that doesn't match the recalculated total — is not silently accepted and not thrown away either. The customer already paid, so the sale is parked for a manager to review and resolve. Nothing is auto-approved that shouldn't be, and no genuine sale is ever lost.

A cloud POS in a browser tab has one honest limitation: the tab must stay open through the outage. If someone refreshes the page or restarts the PC while the internet is still down, a cloud page cannot reload from a dead connection — queued sales stay safe on the device, but billing waits until the line returns.

ERP Node's branded Windows desktop app removes that limitation. The app is installed on the counter PC and loads from the PC itself, so it opens from its desktop shortcut even with no internet at all — and inside it, the same offline billing and sync engine runs unchanged. For shops in areas with frequent cuts, the pairing of offline-first POS plus desktop app is the difference between 'usually fine' and 'never stops billing'.

Every vendor says 'works offline'. Ten minutes with the internet cable pulled out tells you whether it is true. Run this drill on a real counter with real products before you rely on any system — including ours.

• Pull the internet mid-bill: does the cart survive and can you finish the sale?
• Print the offline receipt: is it clearly marked provisional, so it can't pass as a final bill?
• Restart the device while offline: are the queued sales still there afterwards?
• Reconnect and watch the sync: does each sale appear exactly once in reports?
• Reconnect twice in a row (or reload during sync): still exactly once?
• Check a synced sale's prices: do they match the server's catalog, not the device's?