If your Wi-Fi dies right when you need it most — 7pm Saturday, payment terminals throwing errors, the kitchen display freezing, the manager's iPad spinning — it's almost never a "the internet is bad" problem. It's a network design problem, and it's usually fixable for less money than you think.
Here's what's actually happening, and what to do about it.
Why dinner-rush Wi-Fi falls over
A typical restaurant network has three completely different jobs running on the same Wi-Fi:
- Mission-critical: POS terminals, payment processors, kitchen display systems, online-order tablets
- Operational: Manager iPads, scheduling apps, security cameras, music streaming
- Guest: Customer phones, the occasional laptop, and during dinner rush, sometimes 60+ devices that connect, fail, retry, fail, retry
If all three groups are sharing the same network and the same access point, what kills you isn't bandwidth — it's airtime contention. Wi-Fi is a polite protocol; one device transmits at a time. When you have 60 phones all trying to associate, the POS waits its turn behind them. By the time it gets a slot, the payment processor has timed out.
The fix: three networks, one router.
The fix is to split traffic onto three separate Wi-Fi networks (technically three "SSIDs" on different VLANs) so guest device chaos can't drown out your POS. Most consumer routers can't do this. Most prosumer-grade gear can. We typically deploy:
Network 1 — POS / payment
Wired where possible. Wireless only for tablets and handheld order-takers. Locked down — only known devices, fixed IP addresses, no guest access. Prioritized in the QoS settings so payment traffic gets airtime first.
Network 2 — Staff / operations
For manager iPads, scheduling apps, kitchen displays. Separated from POS so a compromised iPad doesn't pivot to the payment terminal. Different SSID name and password from guest.
Network 3 — Guest
Captive portal optional. Bandwidth-capped per device. Isolated — devices can't see each other or the internal networks. The guest network can be on fire and your POS won't notice.
Hardware that actually holds up
For most small restaurants we deploy Ubiquiti UniFi or TP-Link Omada gear — both are roughly $150–$300 per access point, support multiple SSIDs and VLANs, and don't require a yearly subscription. Avoid:
- Consumer Wi-Fi 6 routers from big-box stores. They're great for a 4-bedroom house, terrible for 60+ simultaneous devices.
- The mesh system your ISP is leasing you for $15/month. It's prioritized for streaming Netflix in a living room, not running a POS during a Saturday rush.
- "Just add another extender." Extenders make airtime contention worse, not better.
Payment terminal failover
Even the best network has a bad day. The single highest-impact protection is configuring your payment terminals (Square, Toast, Clover, Stripe) to failover to cellular data when Wi-Fi fails. Most modern terminals support this; many restaurants just never enabled it. Cost is usually a few dollars a month. Saves you from a 90-minute outage during the dinner rush.
Quick win: if you do nothing else this month, log into your payment terminal admin panel and turn on cellular failover. Five minutes. Saves at least one rush from disaster per year.
The site survey nobody does
Most restaurant Wi-Fi problems trace back to access-point placement. The router gets put wherever the cable came in — which is usually in a back office, behind a metal door, next to an ice machine. That's the worst possible spot.
A proper site survey takes about an hour. Walk the floor with a tool like Ekahai or NetSpot, map out signal strength, identify dead zones, find the spots where two access points are interfering with each other. Most kitchens need a separate ceiling-mount AP from the dining room because the prep wall blocks signal. Most patios need their own outdoor-rated AP.
Skip this and you're guessing. Do it once and you'll never put another AP in the wrong place.
What to ask your IT person (or us)
- "Are POS, staff, and guest on separate VLANs?"
- "Is QoS prioritizing payment traffic?"
- "Does our payment terminal failover to cellular?"
- "How many simultaneous devices can each access point handle, and how many do we have on the floor at peak?"
- "When was the last time someone walked the floor with a Wi-Fi survey tool?"
If they don't have answers to those five, you've found the problem.