Hospitality IT: guest Wi-Fi and payments
In hospitality every outage is visible to a guest. A payment terminal that hesitates, a reservation system that will not load, a guest network that drops halfway through a check-in: all of it happens in front of the customer.
Guest Wi-Fi belongs on its own segment with its own bandwidth limit, permanently separated from tills, payment terminals and back office systems. A guest streaming video should never be able to slow a transaction.
Plan capacity for a full venue, not an average evening. A restaurant at eighty per cent occupancy has three times the device count of a quiet Tuesday, and that is exactly the night the network has to hold.
Fix the connection redundancy before the season. A second path over 4G or 5G with automatic switchover costs little and prevents the failure that empties a terrace.
Guest and business traffic never share
This is the single most common fault we find in hospitality, and it is entirely preventable. A guest network sharing capacity and a network segment with the till system means one guest downloading something large can slow a payment, and a compromised guest device sits on the same network as the systems handling card transactions.
The fix is ordinary: a separate segment for guests, a bandwidth cap per device, no route to anything internal, and a captive portal if you want the marketing data. It takes an afternoon on properly managed equipment.
Plan for full, not average
| Venue | Typical device load when full | What to plan for |
|---|---|---|
| Restaurant, 80 covers | Around 100 to 150 guest devices plus staff | Density in the dining area, not the whole building |
| Hotel, 60 rooms | Two to three devices per occupied room | Per-floor capacity and roaming in corridors |
| Event space | Highly variable, often several hundred | Temporary capacity you can add for an event |
| Terrace or outdoor area | Seasonal, weather-dependent | Outdoor-rated units, planned coverage boundary |
Measuring matters here for the same reason it does in retail: a room full of people absorbs signal, and a venue measured empty tells you very little. The approach is under Wi-Fi analysis.
Payments need a path that survives
A payment terminal that cannot reach its provider is the fastest way to a visible problem. That means a second connection path with automatic switchover, and terminals on a segment that is not competing with anything else.
Also worth checking, because it is skipped often: what the staff are told to do when it happens. A printed card at the bar with the fallback procedure and a number that reaches a person is worth more than another switch.
The season sets the change window
Hospitality has the same rhythm as retail with a different calendar. For a beach venue the season is May to September; for a city hotel it is conferences and holidays; for a restaurant it is December and every Saturday.
We plan the work into the quiet weeks and freeze changes during the season, and where cover is needed it runs to opening hours rather than office hours. That includes evenings and weekends, which is when the sector actually operates.
The systems that have to talk to each other
A hospitality estate is rarely one system. There is a property management or reservation system, a point of sale, a payment provider, often a booking platform and sometimes a key card system. Each has its own supplier and its own idea of who is responsible when the link between two of them breaks.
That gap is where most of the frustration sits. Somebody has to own the chain rather than the components, which is the whole point of service governance: one party chasing the other suppliers instead of you doing it between services.
The guest network is part of the product
For a hotel in particular, the Wi-Fi appears in reviews. It is worth treating as a service you deliver rather than an amenity you provide: a portal that works on the first attempt, no daily re-authentication, and coverage in the rooms rather than in the corridor outside them.
Corridor-mounted access points produce a lovely heatmap and mediocre in-room coverage, because the wall by the door is usually the thickest part of the room. It is a common and expensive shortcut.
Questions we get about this
What venue and hotel managers ask.
Can guest Wi-Fi share a network with our till system?
No. A guest downloading something large can slow a payment, and a compromised guest device would sit on the same network as the systems handling card transactions. Guests belong on their own segment with a bandwidth cap and no route to anything internal.
Why does the Wi-Fi only fail when we are busy?
Because device count, not bandwidth, is what breaks it. A full restaurant carries three times the devices of a quiet evening, and if the network was planned on an average night it will hold until exactly the moment it matters.
What happens if the payment terminal loses connection?
With a second path over 4G or 5G and automatic switchover, nothing visible. Without one, you need a printed fallback procedure at the bar and a number that reaches a person. Most venues have neither, and discover that on a Saturday.
Do you support evenings and weekends?
Yes. Cover runs to your opening hours rather than office hours, with evenings and weekends staffed by our own people rather than covered by an on-call phone.
Where this lands in our work
The services behind this.
Want this looked at for your own sites?
Half an hour on a call is usually enough to tell you whether we are the right party for it, and we will say so if we are not.