The dinner rush when the POS goes down is one of the most expensive 45-minute windows in any small business. The POS network that supports it is almost never the network that came with the internet service, and the gap between "works most of the time" and "never fails at 7 PM" is entirely about design.
01PCI segmentation is not optional.
PCI-DSS v4 requires strict network segmentation between systems that touch cardholder data and everything else. "Everything else" specifically includes guest Wi-Fi, back-of-house devices, manager laptops, and the streaming music system.
Practically: the POS, kitchen printers, POS server (if on-prem), and any payment terminals live on a dedicated VLAN with firewall rules that permit only explicit traffic. Guest Wi-Fi is fully isolated. Back-of-house gets its own network with separate ACLs.
02Why your dinner rush drops.
The usual culprit on a failing POS network: all traffic shares one flat network. Guest Wi-Fi saturates the uplink, the POS can't reach the payment processor, cards decline, the line backs up, servers comp the meals, and the owner wonders why "the internet is slow."
Properly-segmented networks survive this. The guest Wi-Fi can be completely saturated and the POS traffic still flows because it's prioritized, isolated, and doesn't share the contended bandwidth.
03Wireless for Toast, Square, and handhelds.
Modern POS platforms, Toast, Square, Revel, Lightspeed, ship with handheld wireless devices. Those handhelds want solid 5GHz coverage with low roaming latency across the entire venue, including the patio.
Design for capacity, not coverage. One AP with a strong signal that covers the whole restaurant fails the moment 30 guests show up with phones and the kitchen has 8 handhelds in motion. Three properly-placed APs with planned channels, co-channel avoidance, and seamless roaming handles the peak.
04Redundant internet, configured correctly.
Fiber primary, cellular failover, automatic cutover in under 30 seconds. Every modern restaurant network spec we write includes this. The cellular circuit is cheap; the downtime it prevents is very much not.
The failover needs to be tested. Actually-unplugged tested. The number of times we've discovered a "failover" that was never configured correctly is higher than we'd like to admit.
05The last five feet.
POS stations, kitchen printers, back-of-house devices, hardwired wherever possible. Wireless POS is convenient until it's not. Hardwired workstations save one full category of 7 PM panic.
Cat6A drops at every fixed location, PoE switches with enough budget for phones and APs, a properly-dressed rack, none of this is glamorous, all of it is what separates restaurants that never call about the network from restaurants that call weekly.
Fourteen restaurant clients across Naples, Bonita, and Fort Myers, Toast, Square, Aloha, and a few legacy Micros holdouts. Dual-WAN with LTE failover is non-negotiable; dinner-rush freeze is what we get called about, and it is almost always DNS or a saturated cable uplink. Pilot a fix for $1,800–$3,500 before anyone commits to a full swap.