In brief
Hundreds of concurrent devices, separating common areas from shop networks, and campaign notices. What makes a mall installation different.
Guest Wi-Fi in a mall or large store is not a scaled-up café installation. Three separate issues appear: density, network separation, and who owns the common area.
Density
In a mall, the concurrent device count can vary threefold between a weekday and a weekend. Plan capacity against the weekend peak, not the average.
What density means technically:
- Concurrent session capacity becomes more critical than line speed. With five hundred devices connected at once, each does not need to be very fast; none should be left out.
- Access point density matters. Rather than covering a wide corridor with one powerful access point, more units at lower power work better in a crowd.
- Speed limits become mandatory. On an unlimited mall network, a few users take most of the line.
Network separation: the critical part
A mall does not have one network; it has at least three:
- The visitor network — guests in common areas.
- Shop networks — each tenant's card terminal, stock terminal and camera system.
- The mall's own operations network — management office, security, technical services, digital signage.
These have to be isolated from each other. A tenant's card terminal being visible from a device on the visitor network is not acceptable.
In practice the separation is done with VLANs. Visitor traffic passes through the hotspot appliance; shop and operations traffic does not.
If tenants have their own lines it gets easier: their traffic never touches your network. But if they use the line the mall provides, each tenant needs its own VLAN.
How often will a visitor sign in?
A mall visitor stays for a few hours and may lose the connection several times in that window — moving between sections, going down to the car park, in a lift.
Asking for a new code on every drop wears them out. Two settings fix it:
- Session length should not be short. Four to eight hours is reasonable for a mall.
- Device remembering should be on. A device reconnecting the same day passes without a code.
Notices and surveys
A mall portal has more marketing value than a café's, because the visitor came to shop anyway.
What works:
- A notice after sign-in. A campaign, an event, a newly opened shop. Shown after sign-in completes, not on the sign-in screen.
- A short survey. A single satisfaction question. Long surveys go unanswered.
- A redirect. Send them to the mall's own page or a campaign page after sign-in.
Overdone, it backfires: every step that lengthens the sign-in flow pushes visitors back to mobile data.
Car park and outdoor areas
Two areas are often skipped in mall installations:
- The car park. Coverage is usually weak and visitors want to connect there too. It needs its own access point plan.
- The food court. The busiest area; devices per table run above the mall average.
Setup order
- Inventory the networks: how many tenants, how many separate networks, which use your line.
- Plan the VLANs; separate visitor, tenant and operations networks.
- Route visitor traffic through the hotspot appliance.
- Size capacity against the weekend peak.
- Set speed limits and session length; turn on device remembering.
- Put notices and surveys after sign-in.
- Test the car park and food court separately.