What Happens to Your POS When the Internet Drops — And How to Sell Through It

Every shop has a version of this afternoon. The lights are on, the card machine is fine, the queue is six people deep — and the till is a spinning circle. Someone finds a notepad. By closing time there are thirty handwritten sales waiting to be keyed in, two of them illegible, and nobody is entirely sure whether the third one was actually paid.

Offline mode is the part of a POS system nobody evaluates until the day they need it. Connection drops are not rare enough to plan around by hoping: routers reboot, a provider has a bad hour, a market stall runs on a phone hotspot behind a concrete wall. The real question is not whether your till will lose the internet. It is what the till does in the ten minutes afterwards.

An outage is a retail problem, not an IT problem

A twenty-minute outage rarely costs twenty minutes. What it costs shows up later, in three places:

• The re-keying. Paper sales have to be entered again after the event, from handwriting, under time pressure, by someone who was not necessarily the person who took them.

• The stock drift. Anything sold on paper is invisible to your stock figures until it is typed in, so your counts and your shelves quietly disagree for the rest of the day.

• The uncertainty. A sale written on a notepad has no payment status. Was that one paid by card? Was the card actually charged, or did the terminal decline while the queue moved on?

None of this is a networking failure. It is a business-continuity failure that happens to be triggered by a router.

What offline mode should actually mean

There are two bad answers to a dropped connection, and one good one.

The first bad answer is a till that simply stops. Nothing rings up, and the business reverts to paper — with all the re-keying, guesswork and drift above.

The second bad answer is worse: a till that accepts everything. If it takes a payment it cannot verify, or redeems a balance it cannot check, it has written a promise your books cannot honour. Those transactions do not come back to you as sales. They come back as reconciliation problems, days later, when the context is gone.

The good answer is narrower and more honest: keep selling whatever can be settled locally, refuse whatever genuinely requires a server, and queue the work so nothing has to be retyped when the connection returns.

What keeps working when the connection drops

In Winstia, a POS register that loses connectivity carries on ringing up sales. Cash works. Card works, keyed in the way most merchants already key an amount into the standalone bank terminal beside the till. The cart, the tax calculation and the receipt all behave normally, and the completed sale is written to a queue held on the device itself rather than to a notepad.

Stock is adjusted locally at the same moment. If someone refreshes the screen mid-outage, the catalogue shows what is genuinely left on the shelf instead of the count from before the outage began — which matters more than it sounds, because a stale figure during a busy hour is how you promise a customer the last one of something you have already sold. (More on why that gap costs money: real-time inventory management.)

What offline mode should refuse — and why that is the point

Some things cannot be honestly completed without a server. Winstia stops rather than guesses:

• Online and gateway payments. A payment link or a card reader needs the processor to confirm the charge. Offline there is nothing to confirm, so there is nothing to record.

• Gift cards. The remaining balance is enforced on the server. A sale queued against a gift card could reach the front of the queue after that card has already been drained elsewhere.

• Store-credit sales. If a customer's credit balance cannot be checked, extending credit creates money owed by nobody. This one fails closed by design: the screen asks for another tender instead.

• Loyalty redemption and promotions. Both are validated server-side, so no discount is handed out that the accounts cannot later account for.

Each refusal appears as a plain message with a way forward, not a dead end. In practice an outage narrows your tenders to cash and keyed card — which is exactly what the notepad gave you, minus the notepad.

Warm the offline cache before you need it

Here is the habit worth building, because it is the one thing an outage cannot do for you: a register can only sell offline from a product catalogue it already holds.

The POS toolbar has a Cache for Offline control that pulls your products, categories and tax configuration onto the device in advance, then shows a tick and how long ago it was warmed. If the copy has aged out, it says so and offers a refresh rather than quietly presenting itself as ready. A cached price list from four days ago is not readiness, and a badge that pretends otherwise is worse than no badge at all.

Make it part of opening the register. It takes seconds, and it is the difference between an outage you trade through and one you write down.

What happens when the connection comes back

Reconnection should be the boring part. Queued sales sync on their own, and each one is cleared from the queue only after the server confirms it — so a sale can be retried safely, but it cannot be posted twice. You get a confirmation of how many went through.

From that point they are ordinary sales. They appear in your reports, your stock movements, your customer ledgers and your double-entry accounts exactly as though the connection had never dropped. There is no separate offline ledger to reconcile afterwards, which is the whole point: the outage should leave a gap in your afternoon, not in your books.

A five-minute offline readiness routine

1. Warm the offline cache when you open the register, and check for the tick before the first customer.

2. Make sure every person on the till knows that cash and keyed card are the offline tenders — learned before a queue is watching, not during one.

3. Agree in advance what to say to a customer who wants to pay by gift card or store credit during an outage. A prepared sentence beats an improvised one.

4. When the connection returns, glance at the sync confirmation before you carry on.

5. Close the register normally at the end of the day, counting cash, card and digital.

Offline is a design decision, not a checkbox

Most POS systems list offline mode as a feature. Far fewer will tell you which transactions they refuse offline, and that is the answer that actually matters — because a system that accepts everything is not more capable than one that refuses honestly. It is just deferring the problem to your month-end.

So when you are comparing systems, ask three questions: what can I still sell, what will it stop me doing, and where do those sales go when the connection returns? (Our full guide to choosing a POS system covers what else to ask.) An outage will always be an inconvenience. It should not also be an evening of re-keying, or a week of wondering which numbers to trust.

Winstia runs your POS, inventory, invoicing and double-entry accounts in one system, so an offline sale lands everywhere it should the moment it syncs. See how it works or book a demo.