When the Internet Dies Mid-Service: Restaurant POS and Delivery Tablets
Ask your POS supplier one question before signing: what happens when the internet drops during service? The answers vary enormously.
A restaurant runs three systems at once: the till taking orders, the kitchen receiving them, and delivery tablets doing both from outside. When the internet drops mid-service, what happens depends entirely on which point-of-sale system you bought, and most operators have never checked.
Key takeaways
- POS offline behaviour differs enormously between products; confirm yours before you need to know.
- Two internet lines with automatic failover cost less than one closed evening.
- Delivery tablets are business equipment and should not be on guest Wi-Fi.
- Kitchen screens want wired connections, because kitchens are hostile to wireless.
- Keep a paper printer as a fallback so an order still reaches the kitchen if a screen fails.
- The written manual fallback matters more than the technology; practise it before service.
The question to ask before you sign anything
What happens to this system when the internet goes down during service? Every point-of-sale supplier has an answer and they are not the same answer. Some systems hold a local cache, keep taking orders and card payments, and reconcile when the line comes back. Others are entirely cloud-dependent and stop, taking the diary and the payment terminal with them.
Neither design is wrong, but they demand completely different preparation. A system that keeps working offline needs a sensible reconciliation process and someone who understands it. A system that stops needs a second internet line and a paper fallback that the shift manager has actually rehearsed.
What causes trouble is not knowing which one you have. That is discovered, reliably, at the worst moment: a full restaurant, a queue at the till, and a manager phoning a supplier who does not answer at nine on a Friday evening.
There is a second question worth asking in the same conversation: what happens to card payments specifically. Order-taking and payment can behave differently in the same product, and a system that keeps taking orders offline while refusing all card payments has not really saved your evening. Ask about both, separately, and ask what the reconciliation looks like afterwards, because a queue of stored transactions that all have to be re-authorised the next morning is its own kind of problem.
Two lines, and why one is not enough
A single internet connection is the most common single point of failure in a Dubai restaurant. A street-level fault, building works, or a provider problem takes out orders, payments, kitchen screens and every delivery platform simultaneously, and none of that is within your control.
The engineering answer is two connections from different providers where possible, with a firewall that switches between them automatically and quickly enough that a card payment in progress survives. We size this against what du and e& can genuinely deliver to the specific unit, because availability differs considerably between buildings and a design based on an advertised package rather than a checked address tends to disappoint.
The cost comparison is usually decisive once written down. A second line is a modest monthly figure. One lost Friday evening service, in covers and in delivery orders that went to a competitor because your kitchen showed as closed, is a larger number.
One detail that catches people out is how the failover is configured. Two lines plugged into two separate routers is not failover; it is two networks, and somebody has to physically move cables while a queue waits. Proper failover means one firewall holding both connections and switching between them without anyone touching anything, which is a configuration job rather than extra hardware in most cases.
Kitchen screens belong on cable
A kitchen is one of the worst wireless environments in any building: stainless steel everywhere, extraction equipment generating interference, heat, and staff moving constantly. Wi-Fi works there until the room is busy, which is precisely when it must not fail.
So kitchen display screens should be wired wherever it is physically possible, and that decision has to be made while the ceilings are open rather than afterwards. Retrofitting a cable into a finished commercial kitchen is disproportionately expensive and sometimes not permitted at all.
The screens themselves need choosing for the environment rather than bought as office monitors. Heat, steam and grease shorten the life of consumer displays considerably, and the mounting has to survive being wiped down daily. Our structured cabling service covers the installation side, and it is far cheaper as part of a fit-out than as a correction.
Keeping a restaurant POS working offline in Dubai: the fallback that saves service
Whatever the technology, keep a thermal printer at the pass as a parallel path. If a kitchen screen fails, or the network between front of house and kitchen drops, a printed ticket still gets the order to the kitchen and service continues. It is inexpensive, it requires no training, and it is the difference between a degraded evening and a stopped one.
Beyond that, the fallback needs to be written down and practised. One page: how to take orders on paper, how to handle payment if the terminal is down, who to call, and how to enter the evening into the system afterwards. A procedure that exists only in the head of a manager who is on leave is not a procedure.
Practise it once, deliberately, on a quiet evening. Teams who have done that handle a real outage calmly. Teams who have only read about it do not, and the cost of the panic is usually larger than the cost of the fault.
Delivery tablets are business equipment
Most Dubai restaurants run several delivery platforms simultaneously, each with its own tablet at the pass. That row of tablets is typically the least managed technology in the building: consumer devices, on guest Wi-Fi, charging off a shared extension lead, with nobody responsible for them until one stops accepting orders.
Treating them as business equipment fixes almost all of it. Put them on a dedicated network separate from guest Wi-Fi so a customer streaming video cannot slow an order. Mount them properly with fixed power rather than a tangle of cables that gets knocked out. Measure wireless coverage at the pass rather than at the front door, because those are different places.
Then monitor them. A tablet that has dropped off the network should raise an alert, not be discovered when a platform calls about missed orders and a rating that has already fallen.
Should you integrate delivery into the POS?
Where your point-of-sale supports it, pushing aggregator orders directly into the till removes the re-typing, and with it the transposition errors that happen at the busiest moment of the evening. It also means your reporting includes delivery rather than sitting in three separate platform dashboards.
Whether it is worth the cost depends on volume and on how many platforms you run. A restaurant taking a handful of delivery orders a day will not notice. One running three platforms at dinner service, with a member of staff effectively employed to re-key orders, usually finds the integration pays for itself quickly.
The question to ask is what the integration actually does rather than whether it exists. Does it push the order into the kitchen automatically, does it handle modifiers and notes correctly, and what happens to an order that arrives while the integration is down? The last one is the question suppliers answer least clearly.
Separating the network properly
Separating the network is not exotic and it does not require expensive equipment. Most business-grade access points and switches support it out of the box, and the reason it is so often missing is simply that nobody configured it when the restaurant opened. It is one of the cheaper improvements available and it removes a whole class of intermittent fault.
There is a security dimension as well as a reliability one. A flat network where the guest Wi-Fi, the cameras and the till all share one space means a compromise of the least protected device reaches the most sensitive one. Cameras and cheap connected equipment are the usual entry point because they are rarely updated, and a card terminal should not be reachable from them under any circumstances.
- Tills and card terminals: their own segment, protected and not shared with anything public.
- Kitchen screens and the pass: wired, on a segment that cannot be affected by guest traffic.
- Delivery tablets: a dedicated wireless network, monitored, separate from guests.
- Back office: rotas, stock, supplier orders and payroll, backed up and kept apart from the POS.
- Guest Wi-Fi: isolated, with a bandwidth limit so it cannot slow payments.
- CCTV: its own segment, because cameras are a common route into flat networks.
Cloud kitchens have a narrower margin for error
A cloud kitchen has no dining room, which sounds simpler and in one way is: there is no guest Wi-Fi to separate and no front of house to consider. In another way it is considerably more exposed, because every order arrives through a platform over the internet and there is no walk-in trade to fall back on.
That makes connectivity existential rather than important. Two lines, monitored tablets and a tested fallback are not refinements for a cloud kitchen; they are the business. An hour offline is an hour with zero revenue and a visible drop in platform ranking that takes longer to recover than the outage lasted.
It also concentrates the risk on the tablets themselves. A single row of consumer devices on one network, charging from one extension lead, is the whole order pipeline. Redundancy there is cheap relative to what it protects.
What to do first
Ask your POS supplier the offline question and write the answer down. That single conversation determines everything else, and it costs nothing.
Then price a second internet line and compare it honestly against one lost evening. Then move the delivery tablets off guest Wi-Fi onto their own network and mount them properly. Then write the one-page manual fallback and practise it once.
A note on sequence, because operators frequently start at the wrong end. The instinct is to replace the point-of-sale system, which is the most disruptive and expensive option available and usually not the problem. In most restaurants we assess, the software is adequate and the connection, the network separation and the absence of a fallback are what actually cause the failures. Those are cheaper to fix and fixing them first tells you whether the software was ever the constraint.
None of that is a large project and most of it is configuration rather than purchase. If you would rather have it assessed during service than guessed at from a floor plan, that is what an assessment on our restaurant IT page covers, and a restaurant inside a hotel should also read the hotel side because the network boundary is usually the first thing to establish.
Frequently asked questions
Ask the supplier directly and get it in writing, then test it. Disconnecting the line deliberately on a quiet afternoon tells you more in five minutes than any documentation, and it shows your team what the failure actually looks like before it happens during service.
Compare it against one lost dinner service, including the delivery orders that went elsewhere while your kitchen showed as closed. For most restaurants that comparison settles it quickly. For a cloud kitchen with no walk-in trade, it is not really optional.
Almost always because they are consumer devices on guest Wi-Fi with coverage measured at the front of the restaurant rather than at the pass. Moving them to a dedicated network, mounting and powering them properly, and monitoring them resolves it in most kitchens.
You can, and it will work until the kitchen is busy. Stainless steel, extraction equipment and constant movement make kitchens a poor wireless environment, and the failures cluster at peak service. Wire them during the fit-out if there is any possibility of doing so.
One page: how to write orders, how to get them to the kitchen, what to do if the card terminal is down, who to phone, and how to enter the service into the system afterwards. Keep a copy at the pass and at the till, not in a folder in the office.
Yes. The helpdesk runs around the clock and engineers attend on site outside office hours, because restaurant problems happen in the evening and at weekends. Planned work is scheduled between services rather than during them.
Cabling to the pass and the kitchen, the comms position, and the internet line order. The first two are expensive to correct once surfaces are finished, and the internet line has the longest lead time of anything on the list, so it should be ordered before almost anything else.
Written by Srinivasan Ramachandran, Founder, Listonics · Published Sep 24, 2026 · Last reviewed October 11, 2026 · 2,039 words
