Why does a restaurant POS need to work offline?

Short answer: because a cloud-only POS stops the moment the connection does — and connections drop during exactly the hours you can least afford it. A POS that stores orders on the device keeps billing, printing and sending kitchen tickets through an outage, then syncs everything once you are back online. Nothing is lost and nobody waits.

What actually breaks when the internet drops?

It is easy to assume the worst case is “reports are delayed”. In a cloud-only system it is considerably worse, because every action needs the server:

• Billing stops — no new bill can be generated or printed
• Kitchen tickets stop — orders no longer reach the kitchen screen or printer
• Card and UPI records stop reconciling against the order
• Table status freezes — nobody can see what is occupied or paid
• Staff fall back to handwritten bills, re-keyed later with mistakes

The cost is rarely the lost minutes. It is the queue at the counter, the table that walks out, and the hour spent that night reconciling paper slips against a system that has no record of them.

Why this matters more in India

Broadband here is generally good and getting better, but outages are still a normal part of the week rather than a rare event — power cuts that take the router down, a provider fault, or a monsoon afternoon that knocks the line out. A café does not get to choose when that happens, and it is disproportionately likely to land during a lunch or dinner rush simply because that is when you are trading hardest.

A system that assumes a permanent connection is designing for conditions that do not exist.

“Offline mode” does not always mean offline

This is where a lot of buyers get caught. The phrase gets used for two very different things:

Only the second one keeps a restaurant open. If a vendor says “offline”, it is worth finding out which of these they mean.

How to test it in two minutes

Do not take the claim on trust, and do not settle for a slide about it. During the demo, ask them to:

• Disconnect the internet — actually unplug it, not just switch tabs
• Take a fresh order with two or three items
• Generate and print the bill
• Send a ticket to the kitchen screen or printer
• Reconnect, and show the sale appearing in reports

Any vendor with genuine offline support can do all five without preparation. It is the single most revealing question you can ask in a POS demo.

How Synexlabs handles it

Offline billing runs through the Windows desktop app, installed on the counter PC. Being clear about that matters: the browser version needs a connection like any web app, so if uninterrupted billing is the reason you are buying, the desktop app is the part that delivers it.

With it installed, orders, bills and kitchen tickets all continue during an outage, stored locally on the machine. When the connection returns they upload automatically — no re-typing, no reconciliation, and reports and stock end up exactly as they would have been. Invoice numbering and GST calculation happen on the device, so bills issued mid-outage are sequenced and taxed the same as any other.

Frequently asked questions