Offline POS for restaurants: why the till must keep working without internet

Friday evening, a restaurant on Nizami Street. Twenty tables are taken, the grill is full of lülə kabab, a family of eight has just ordered dolma and dovğa. At 20:40 the router blinks red. The provider has a problem somewhere in the district, and nobody knows for how long.

What happens next depends on one technical detail most owners never ask about: where your POS actually lives. This article explains, in plain words, how an offline POS for restaurants works, how it differs from a cloud-only till, and what to check before you buy one.

What happens to a cloud-only POS during an outage

Many modern systems keep everything on a remote server, and the tablet and the till are just windows into it. When the internet drops, those windows go blank or freeze on the last screen. In practice the evening looks like this:

• waiters switch to notepads and run to the kitchen with handwritten orders;
• the cook gets half the orders on paper while the other half is stuck in the system, and dishes for one table come out twenty minutes apart;
• the cashier cannot close or print a check, so guests wait at the door or leave cash with a "put it through later";
• discounts and voids happen on someone's word, without a trace;
• when the connection returns, someone has to retype everything, and part of it never gets entered.

The next morning the cash in the drawer does not match the report, the stock write-off is wrong, and nobody can say which waiter served table 7. So one hour without internet throws off the numbers for the whole day. Guests notice it too: a family that waited twenty minutes for the bill will remember that longer than the taste of the dolma.

Some managers try to save the evening by sharing internet from their phone. Sometimes it works, but a phone battery, a weak mobile signal in a basement hall and a data limit are a shaky foundation for the whole restaurant's till.

Why you cannot avoid outages completely

You do not need statistics for this. A venue loses its connection for ordinary reasons: work on the provider's line, a cable damaged during roadworks, a router that froze and needs a restart, a power cut that takes the modem down with it, a cleaner who unplugged "that black box". In the regions, a strong wind can leave a whole street offline for an evening. None of this is anyone's fault, and none of it can be fully prevented. What you can choose is whether the restaurant keeps working while it happens.

A second provider or a mobile router as a backup channel helps, but it may run along the same street and depend on the same power line. Backup internet is useful, but a till that needs no internet at all is more reliable.

How a local hub and cloud sync work, in plain words

Think of the venue as a small office with its own post room. In a system like Dishment, the venue's main Windows computer runs a small local server called the hub. Waiter tablets, the till, the kitchen display and the printers talk to the hub over the venue's own Wi-Fi or cable network. That network does not need the internet. Nor does the hub need a server cabinet: it is a program on an ordinary Windows computer, for example the one at the cashier's desk.

So when the internet drops:

1. the waiter sends the order from the tablet to the hub;
2. the hub passes tickets to the kitchen display and the station printers;
3. the cashier closes the check and prints the receipt;
4. the hub keeps every order, payment and void until it can send them on.

When the connection returns, the hub sends everything to the cloud by itself. Reports in Back Office, the owner's dashboard and stock write-offs catch up. Nothing is lost, and nothing has to be retyped.

One caveat: the card terminal belongs to your bank and needs its own connection. Ask the bank for a terminal with a SIM card, so card payments go through even when your Wi-Fi is down; the till records the payment type either way.

What to check before you buy

A sales demo always runs on perfect Wi-Fi. Ask for a different one:

• Unplug the internet in front of you. Not the power, just the provider's cable. Then take an order, send it to the kitchen, close and print the check.
• Ask where the server lives. If the answer is "in the cloud" and nothing runs inside the venue, the system stops when the internet does.
• Ask what is not available offline. Some systems keep taking orders but cannot print or accept payments. Get that list in writing.
• Ask about a time limit. Can the venue work offline for a whole evening, or only for a few minutes?
• Ask how sync is shown. You should see whether everything has reached the cloud, not guess.
• Ask about two waiters on one check. Even offline, the system must stop two people from editing the same order at once.
• Check the hardware. What computer does the local server need, and what happens if it is switched off?

Prepare the local network in advance

A local hub only helps if the network inside the venue is in good shape. Most of this is a one-time job for whoever installs your equipment:

• Connect the hub computer to the router by cable, and the kitchen display too if you can. Tablets can stay on Wi-Fi.
• Give guests their own Wi-Fi network. A full hall of phones playing videos should not share a network with the waiters' tablets.
• Give network printers a fixed address, so they do not "disappear" after a router restart.
• Label the main computer "Do not switch off: the till runs here". Otherwise someone will turn off "the old PC in the corner" to save power.
• Check the Wi-Fi in every corner: the summer terrace, the second floor, the far hall. A dead zone stays dead with or without internet.

The outage drill: a checklist for managers

A fire drill feels boring until the day there is a fire. Run this one once a month, in a quiet hour, with the shift manager and one waiter:

1. Pull the provider's cable out of the router, but leave the router itself on.
2. Enter a test order on a waiter tablet, with a modifier and a comment.
3. Check that the ticket appears on the kitchen display and the station printer.
4. Close the check in cash and print it; void one item with a reason.
5. Make sure staff know the card terminal plan: does it have its own SIM card, or do you announce "cash only today"?
6. Check that the provider's support number and your contract number are taped next to the router.
7. Plug the cable back in and check in Back Office that the test order, payment and void have arrived.
8. Write down what went wrong and fix it before the weekend.

The drill takes about fifteen minutes, and during a real outage the team already knows what to do.

How Dishment handles it

Dishment was built with this scenario in mind. The hub runs on the venue's main Windows computer: when the internet drops, orders, kitchen tickets, payments and printing keep working, and when it is back, everything syncs to the cloud automatically. Waiters do not need new rules: the order still goes from the tablet to the hub, and the kitchen still sees it on screen. The kitchen display keeps showing tickets with timers, and the printers print Azerbaijani letters and Cyrillic correctly. With the Notifications module, the owner gets a Telegram message when the hub stops responding and when it is back. With the extended reports, the Live page shows which moment the numbers are from while the hub is offline, so you never look at stale figures without knowing it. Read more about offline mode, or book a demo and ask us to pull the cable.