Offline restaurant POS: what happens when the internet drops (2026)

A restaurant POS can handle an internet outage in three ways. A cloud-only POS stops. An offline edition runs on the shop PC and keeps selling, with each till keeping its own sales. An offline-first system works offline and syncs later, which gives one set of numbers but is harder to build. Choose by asking what must keep working, how many tills or branches you have, and who looks after backups.

What breaks when the internet drops

A cloud POS is simple to run and easy to report from, but it has one hard failure: no internet means no POS. No orders, no kitchen tickets, no closing bills. On a busy counter that is the failure a restaurant feels most, and the one a vendor's demo rarely shows.

The honest question for any vendor is not "do you work offline?" but "what exactly works offline, and what do I lose?"

Three designs compared

What must keep working offline

For the counter to carry on, these need to work with no connection:

• Taking orders for dine-in, takeaway and delivery.
• The kitchen display or printed tickets.
• Cash and shift handling, including opening a shift, counting the drawer and closing it.
• Receipts and closing bills.
• Stock deduction and reports for that till.

What an offline POS cannot do

Be clear about the limits before you buy:

• Online orders. Orders from WhatsApp, delivery apps or a guest's phone need the internet. If you take them, see our guide to WhatsApp ordering for restaurants.
• Card and wallet payments usually need a connection. Ask the vendor and your bank what happens when the line is down.
• Combined reporting. In an offline edition, two computers each keep their own sales. If you need one report across branches, you need sync or a cloud system.

How we built an offline edition

We built an offline restaurant POS for a fast-food restaurant in Pakistan as a self-contained Windows bundle: a cloud edition and an offline edition shipped from one codebase, with the same till, kitchen display, cash shifts, stock and reports. The offline folder carries its own runtime and database, and nothing is installed into Windows, so deleting the folder removes the software completely. Backing up is closing the POS and copying the folder.

We chose not to build sync for that edition. Anything that writes in two places needs a rule for which change wins, and that is the part nobody wants to discover late on a live till. The full story, including the bugs, is in our case study of how we built an offline restaurant POS.

Test the money logic

Offline or not, test how the POS treats payment methods. In one of our early builds the drawer logic matched the word "cash" in a payment method's name, which also matched JazzCash, a mobile wallet. Wallet money never enters the drawer, so the till expected more cash than it held and would have declared a cashier short. Ask the vendor to run a bill split between cash and a wallet and show you the drawer reconciliation.

Questions to ask before you buy

1. 1What works offline and what does not?
2. 2Where is the data stored, and how is it backed up?
3. 3Do two tills or branches get one set of numbers, and how?
4. 4How are card and wallet payments handled when the connection is down?
5. 5Does the drawer reconcile correctly with a split cash and wallet bill?
6. 6Who owns the data, and what happens when we leave?

Our POS systems page explains what we build, and our restaurant POS guide for Pakistan walks through 12 features with real screens. Tell us how many tills you run and how reliable your internet is and we will tell you which design we would choose.

*Screens are from our restaurant POS, shown with a demonstration menu and sales.*