Every shop that relies on a cloud-only point of sale eventually has the same bad afternoon: the internet drops, the screen spins, and a queue builds while staff write sales on paper. An offline-capable POS is designed so that afternoon never happens. This article explains how offline mode works in general terms, what its limits are, and how to set up your counter so an outage is a non-event.
Online-only, offline-capable and fully local
Point-of-sale systems fall roughly into three groups:
- Online-only. Every action is sent to a server as it happens. When the connection goes, so does the till.
- Offline-capable. The system normally talks to a server, but can keep recording sales on the device when the connection is lost, then send them when it returns.
- Fully local. Everything runs on one computer in the shop. It never needs the internet, but it is harder to reach from elsewhere and harder to back up off-site.
Offline-capable systems try to give you the best of both: central records you can see from anywhere, and a counter that keeps working through outages.
How offline mode works
When an offline-capable POS loses its connection, it switches to recording sales locally. In a browser-based system this usually means the sale is stored in the browser's own storage on that device. Each stored sale waits in a queue. The cashier carries on ringing up sales, taking cash and printing receipts as normal.
When the connection comes back, the device sends the queued sales to the server in order. The server records them, updates stock levels and includes them in reports. A well-built system marks each queued sale with a unique identifier so the same sale cannot be recorded twice, even if the connection flickers during upload.
What usually works offline
- Ringing up items that are already loaded on the device.
- Cash sales and printing receipts to a locally connected printer.
- Applying prices and discounts that were set before the outage.
What may not work offline
- Card payments. Card terminals need their own connection to the bank or payment provider. If the terminal uses the same internet line, it goes down too. Some terminals have mobile data as a backup; ask your provider.
- Live stock across locations. While a device is offline, other devices cannot see its sales, so stock counts elsewhere lag until it syncs.
- New products or price changes made on the server during the outage reach the device only after it reconnects.
- Online payments and anything that checks an outside service wait until the connection returns.
The risks and how to manage them
Offline mode moves responsibility to the device for a while, so treat that device with care during an outage:
- Do not clear the browser or close its data. Queued sales live in the browser's storage. Clearing site data, using a private window, or resetting the device before it syncs can lose those sales.
- Keep the device powered. A laptop or tablet with a charged battery rides through short power cuts. A desktop needs a UPS.
- Use one device per till. Do not switch a cashier to a different device mid-outage; the queue stays on the original device.
- Check the sync afterwards. When the connection returns, confirm that the queue has emptied and the day's report includes the offline sales.
Setting up your counter for outages
- Choose hardware with batteries. A laptop or tablet as the main till, and a receipt printer that connects by USB or directly to the device rather than through the internet.
- Keep a backup connection. A phone hotspot is fine as a backup; it should not be your only plan.
- Keep cash float ready. During an outage more customers may need to pay cash if card terminals are affected.
- Write a one-page outage routine. Who checks the connection, which device keeps selling, what to tell card customers, and who confirms the sync afterwards.
- Practise once. Turn off the Wi-Fi during a quiet hour, ring up a few test sales, turn it back on and confirm they synced. Ten minutes of practice prevents panic later.
Questions to ask any POS vendor
- Exactly which functions keep working offline, and which stop?
- Where are offline sales stored, and what would delete them?
- How does the system prevent duplicate sales after reconnecting?
- How do I see that the queue has synced?
- Can I test offline mode in the demo?
How CWPOS handles it
CWPOS runs in a browser on a laptop, tablet or phone. When the connection drops, sales are queued on the device and sync automatically when it reconnects. Offline queuing depends on the device and browser staying open and their local storage staying intact, so the precautions above apply. The best way to judge it is to try it: open the live demo, switch off your Wi-Fi during a sale and watch what happens. More background is on our offline POS page.
