Restaurant and Cafe Wi-Fi: Keeping Ordering, Till and Guest Wi-Fi Separate Without Slowing Each Other Down
| Retail and F&B Networks
A restaurant cannot run on one Wi-Fi network. Ordering, till, kitchen tickets, guest Wi-Fi and CCTV all share one network — until it fails and the whole shop stops. Segmentation, till priority, peak-hour handling and acceptance.
Introduction: When a Restaurant's Network Stops, the Whole Shop Stops
A restaurant or cafe network is no longer just guest Wi-Fi. Ordering systems, tills, payments, kitchen tickets, stock, food-delivery tablets, staff communication, CCTV, music and guest Wi-Fi all need the network. At a busy lunch service, dozens of guests connect at once while ordering and payment need instant responses — if the network slows or drops, the impact is immediate: orders cannot be placed, payments cannot be taken, the kitchen gets no tickets, and guests complain.
Doing a restaurant network well means knowing which traffic matters most and which traffic can wait. Till and ordering are production traffic and must not compete with guests watching video; guest Wi-Fi is a service and must never reach the till system. This guide starts with segmentation, then covers till priority, ordering devices, kitchen tickets, peak hours and outdoor seating, and an acceptance checklist.
Segmentation: Till, Ordering, Kitchen, Guest and CCTV Each Go Their Own Way
A restaurant network needs at least five segments. Without segmentation, guests' phones can reach the till system, CCTV traffic drags down ordering, and a problem in any one area affects the whole network.
| Segment | What Lives There | How It Should Be Isolated |
|---|---|---|
| Till segment | Till machines, payment terminals, receipt printers | Reaches only payment and designated services; guests and visitor devices cannot reach it |
| Ordering segment | Ordering tablets, staff ordering phones, handheld ordering devices | Reaches only the ordering system and kitchen tickets; cannot reach the sensitive parts of the till segment |
| Kitchen segment | Kitchen ticket printers, kitchen display screens | Receives tickets from the ordering system only; guests and other segments cannot reach it |
| Guest segment | Guests' phones, tablets, laptops | Internet only; cannot reach till, ordering, kitchen or CCTV; guests isolated from each other |
| CCTV segment | In-shop cameras, recording system | Reaches only the recording system; does not compete with ordering and till traffic for the same network resources |
Segmentation must be implemented with real settings and tested in practice: from the guest segment, try to reach the till system and confirm you cannot; from the ordering segment, try to reach systems you should not reach and confirm you cannot. A settings screen that looks segmented is not proof that isolation actually works. For till-network reliability, see our retail till-network reliability guide; for office segmentation thinking, see our office network page.
Till Priority: Till and Ordering Must Not Compete With Guests Watching Video
The priority order for a restaurant network should be stated clearly: till and ordering first, kitchen tickets second, staff communication third, guest Wi-Fi last. This order is not about disrespecting guests — it is because a stopped till stops the whole shop, while slower guest Wi-Fi is only a worse experience. Practical steps include:
- Cable the till. Fixed till machines should be wired, not Wi-Fi-only. Wired connections are generally more stable than wireless, and the difference shows most at peak times.
- Reserve capacity for ordering devices. Count ordering tablets and handheld devices in advance and plan coverage around ordering positions — do not discover on opening day that one corner cannot place orders.
- Put reasonable limits on guest Wi-Fi. The guest segment should have sensible traffic arrangements so that one device cannot take all the bandwidth. Limits are not there to hassle guests — they protect till and ordering.
- Test peak hours in advance. Do not wait for lunch service to learn the network cannot cope. Before opening, simulate peak hours: many devices connected at once, ordering and paying at the same time, and check that till and ordering still work.
Ordering Devices: Tablets, Handhelds and QR-Code Ordering
In-Shop Ordering Tablets and Handheld Devices
In-shop ordering devices keep moving: from a table to the kitchen door, from the entrance to the till. As devices move, Wi-Fi roaming must be smooth — not a dropout at every step. AP placement must follow the routes staff walk, not just the seating area. Charging, spare devices and loss handling for ordering devices also need planning in advance: a dead battery or a lost device should not stop the whole shop.
QR-Code Ordering and Food-Delivery Tablets
QR-code ordering and food-delivery tablets are now common in restaurants. QR ordering needs guests to scan a code and have the ordering page open smoothly; delivery tablets need to receive orders and notifications. These tablets belong on the ordering segment or a separate segment — not mixed with guest Wi-Fi. The notification sound, placement and charging of delivery tablets all need thought too — do not discover a missed order only because a tablet ran out of battery or was muted.
Kitchen Tickets: A Kitchen That Gets No Tickets Is Worse Than a Slow Till
Kitchen tickets are the most easily overlooked link in a restaurant network. The till takes the money, the ordering system places the order, but the kitchen gets no ticket — guests wait with nothing to eat, and complaints follow. Kitchen environments are unfriendly to networks: high heat, grease, moisture, metal equipment and thick walls all affect signal and equipment life. Kitchen ticket devices should suit the kitchen environment, sit away from the hottest and dampest spots, and have their coverage tested in practice — never assume a dining-room AP will reach the kitchen. Kitchen tickets also need a fallback: if the network drops, how do ordering and tickets continue, and do staff know the process? Do not wait for an outage to think about it.
Guest Wi-Fi: Convenient Without Harming the Till
Guest Wi-Fi is a service, but it must not come at the till's expense. Practical steps:
- Keep login simple. Guests do not want to fill in a long form before getting online. The simpler the login, the fewer complaints and the less staff time spent helping.
- Change and display the password regularly. The guest Wi-Fi password should be changed regularly and displayed clearly — not hidden behind the till where nobody sees it, and not left unchanged indefinitely.
- Isolate guests from each other. One guest's device should not be able to reach another guest's device. That is basic protection.
- Never run the till on guest Wi-Fi. Till, ordering and kitchen tickets must never run on the guest segment. Staff should not connect a till to guest Wi-Fi for convenience.
For guest-network login and isolation practice, see our guest Wi-Fi login-page guide, adjusted for restaurant needs.
Outdoor Seating, Queuing Areas and Multiple Branches
Restaurants with outdoor seating or queuing areas need separate outdoor coverage thinking: ordering at outdoor tables, Wi-Fi for queuing guests, and buzzer or queue calling at the door all need coverage. Outdoor coverage should use equipment suited to outdoor use, with protection and installation requirements confirmed against the equipment specifications — never put an indoor AP straight outside. Multi-branch restaurants also need to think about management across branches: whether network settings are consistent across branches, who maintains them, and how incidents are reported. For multi-branch networking, see our multi-branch / multi-location network guide; for overall enterprise Wi-Fi planning, see our Wi-Fi solutions page.
Outage Handling: What Happens When the Till Network Drops
- The till needs a fallback. When the network drops, how does the till work, can cash still be taken, what happens to payments, and do staff know the process? It should be written down and drilled in advance, not improvised during an outage.
- Backup must be tested. Having a backup connection does not equal having a backup — cut the main link and confirm the backup genuinely takes over and the till and ordering genuinely keep working.
- Name who notifies and who fixes. During an outage, who calls the provider, who notifies branches, and who decides whether to switch to fallback — all agreed in advance. For IT support arrangements, see our SME IT support page.
- Reconcile after the outage. Transactions, orders and kitchen tickets from the outage period must be reconciled after recovery — do not assume the system reconciles everything automatically.
Acceptance Checklist
| Acceptance Item | How to Test |
|---|---|
| Segmentation | Guest device tries till, ordering, kitchen and CCTV and cannot reach them; ordering device tries systems it should not reach and cannot reach them |
| Till | Fixed till confirmed wired; payments still work under a peak-hour simulation |
| Ordering | Staff walk the whole floor placing orders, confirming every position can order and roaming does not drop |
| Kitchen tickets | Test ticket delivery in the kitchen, confirming tickets arrive at busy times; simulate an outage and confirm the fallback works |
| Guest Wi-Fi | Test the guest flow end to end: login, video, guest-to-guest isolation |
| Backup | Cut the main link and confirm the backup takes over and the till keeps working |
Common Misunderstandings
- Can one Wi-Fi network do everything? No. Till, ordering, kitchen, guest and CCTV mixed together means a problem anywhere affects the whole shop.
- Should guest Wi-Fi be as fast as possible with no limits? No. Without limits, one device can take all the bandwidth and drag down till and ordering.
- Can the till just use guest Wi-Fi? No. The till should run on its own segment, preferably wired — not connected to the guest network for convenience.
- Does installing APs equal full coverage? No. Kitchen, outdoor seating and corner positions must each be tested one by one, not assumed.
- Does having a backup mean outages never stop the shop? No. A backup counts only if its switch-over has been tested; an untested backup may not take over when the outage happens.
Staff Training: The Network Is Only as Good as the People Using It
Even the best-planned restaurant network fails if staff do not know how it works. New staff should be shown which network each device uses, where the passwords are kept, and what to do when ordering or payment stalls. A one-page sheet at the till — which segment each device uses, who to call when the network drops, and the fallback steps — saves more service than any single piece of equipment. Rehearse the outage drill when new staff join, not only when the network is installed, so the fallback is familiar before it is ever needed.
Conclusion: Segment, Prioritise the Till, Test in Practice
Doing a restaurant network well comes down to three sentences: segmentation must be tested, not just set on a settings screen; till and ordering come first and must not compete with guest traffic; peak hours and outages must be drilled in advance, not discovered at lunch service. Our team surveys the site first, then recommends a solution for your actual shop.