What happens to your restaurant when the internet drops at rush hour?
“Our system works offline” hides a question: which part of it? The till alone is not enough if the kitchen screen and the waiters’ phones freeze.
In short: a good cloud restaurant system does not need the internet to run — only to sync. When the line drops, three things must carry on: taking orders on the floor, getting them to the kitchen, and payment and printing. What waits for the connection to return is only the upload to the cloud and remote reporting.
“Offline” is not one word
| Level | What keeps going in an outage | What that means in a restaurant |
|---|---|---|
| Nothing | The system is a web page; the line drops and it freezes | Pen and paper, then keying it all in later |
| The till only | The till device sells and prints | Floor and kitchen go back to paper; waiters queue at the till |
| The whole restaurant | Till, waiter devices and kitchen screens | The guest notices nothing |
The difference between levels two and three is a simple technical one: do the devices talk to each other through the cloud or through the venue’s network? If the waiter’s phone sends the order to a distant server so it can come back to a kitchen screen ten metres away, a dropped line cuts those ten metres.
How local pairing works
One device — the main POS — acts as a hub inside the restaurant. Waiter devices and kitchen screens connect to it through the local router. The order travels: waiter’s phone → router → main device → kitchen screen. None of that leaves for the internet. The main device is what uploads bills to the cloud when there is a connection, and queues them when there is not.
The router itself keeps working when the internet line is down: the internal network is one thing, the link to the outside another.
What is really postponed?
- Sales showing up in the web control panel and the manager app.
- Posting bills to accounting.
- QR orders from guests’ phones — those come over the internet by nature.
- Menu and price changes you made from somewhere else.
None of which the guest at the table can see.
A five-step plan
- Test now, not on the day: in a quiet hour, unplug the internet cable from the router (not the power). Take an order on a waiter’s phone, check it reached the kitchen, take payment and print.
- Protect power before internet: a power cut stops the router, and the internal network with it. A small UPS for the router and the main POS is a cheap investment.
- Printers on the local network: a printer driven from the cloud will stop. One on the venue’s network will not.
- Watch the sync indicator: the system should show clearly that bills are “waiting to sync”, and they should clear by themselves when the line returns.
- A backup line for receiving, not for running: a phone hotspot is enough to pass QR orders and syncing through a long outage — but your restaurant should not depend on it to operate.
In Sahl
In Sahl’s restaurant module, waiter devices and kitchen displays pair with the main POS over the venue’s network, so the whole restaurant carries on through an outage. The floor bar shows sync status and the number of connected devices, and bills upload automatically when the connection returns. For the wider picture on selling offline, read offline POS in Palestine, and on taking orders on a phone.
Frequently asked questions
Does a cloud restaurant system work without internet?
It depends how it is built. A good one runs locally and uses the internet only to sync. Ask specifically whether waiter devices and the kitchen screen carry on, or only the till.
Does the router work if the internet line is down?
Yes. The internal network between your devices keeps running as long as the router has power; only the link to the outside is lost.
What happens to bills issued during the outage?
They are queued on the main device and uploaded to the cloud automatically when the connection returns, with no manual entry.