After Wi-Fi 6E started being deployed in earnest through 2023-2024, Wi-Fi 7 (802.11be) has now reached the phase where enterprise vendors push it as the default for new customers. The question is whether the first step of that upgrade is worth the investment, and where the pitfalls are that leave so many projects short of what the marketing promised.
What makes Wi-Fi 7 different from Wi-Fi 6/6E
1. Multi-Link Operation (MLO)
The one capability that simply did not exist before — the AP and the client can use several frequency bands at once (2.4 + 5 + 6 GHz) instead of picking one. MLO has two important modes:
- Enhanced Multi-Link Single Radio (eMLSR) — switches band dynamically according to conditions
- Simultaneous Transmit/Receive (STR) — transmits and receives on different bands at the same time, raising aggregate throughput
2. 320 MHz channels in the 6 GHz band
Twice the width of Wi-Fi 6E (160 MHz), lifting theoretical peak throughput to roughly 46 Gbps. In practice most enterprises will still run 160 MHz, because it gives better spatial reuse wherever there are several APs.
3. 4096-QAM
Modulation 20% denser than the 1024-QAM of Wi-Fi 6 — but usable only on very high quality links (high SNR, short range).
Wi-Fi 7 is not merely "faster". It changes the paradigm from a single radio to aggregated radios.
The numbers from the Wireless Broadband Alliance Phase 2 trial
The WBA ran a field trial with AT&T, RUCKUS Networks and Intel in a real enterprise environment. The interesting results:
- Uplink throughput up by as much as 116% under interference, compared with Wi-Fi 6E
- Uplink latency down 66% for real-time traffic (video conferencing, IoT)
- MLO across 5 + 6 GHz on a single client delivered 2-5 Gbps in ideal conditions
- A 4x4 MIMO AP running 5 + 6 GHz simultaneously on 160 MHz channels pushed an aggregate 4-6 Gbps per AP under real load
These numbers matter because they show MLO is not a statistical trick: it genuinely helps the real-time workloads where Wi-Fi 6E had jitter problems.
Where enterprises usually get the deployment wrong
1. Buying Wi-Fi 7 APs when 80% of the client fleet is Wi-Fi 6
This is the mistake Cisco, Aruba, Juniper Mist and Ekahau all flagged through 2025-2026 — customers pay 30-50% more per AP, but the MLO benefit only applies to newer laptops with a Wi-Fi 7 chip (Intel BE200, Qualcomm FastConnect 7800). Survey the inventory before deploying: if the fleet is still entirely Wi-Fi 5/6, waiting another year or two is the better investment.
2. Configuring 320 MHz channels in a high-density area
On paper it looks appealing — 2x peak speed. But in dense AP areas (an office floor, a classroom) a channel that wide makes spatial reuse collapse and co-channel interference rise. The standard recommendation is 160 MHz in 6 GHz for consistency, keeping 320 MHz for point-to-point bridges or an isolated zone such as a large meeting room far away from other APs.
3. Forgetting 6 GHz regulation in Thailand
In Thailand the NBTC opened the 6 GHz band for Wi-Fi in 2024, but only as LPI (Low Power Indoor), not standard power. A Wi-Fi 7 AP deployed in Thailand is therefore capped at 24 dBm TX power, below the US/EU limit, so real behaviour differs from overseas case studies — the RF design has to place APs 15-20% closer together than usual.
4. Not upgrading switching and uplinks
Flagship Wi-Fi 7 APs such as the Cisco Catalyst 9136, Aruba CX 730 and Juniper AP47 can pull 5-9 Gbps each. If the uplink is still 1 GbE, the result is no better than Wi-Fi 6. Plan for mGig (2.5/5/10 GbE) on the access switch, plus PoE++ (802.3bt) for class 6 APs that draw 40W or more.
Who should move now
From experience designing medium and large networks in Thailand, the criteria that hold up:
- Move now: hospitals (medical IoT and telemedicine), university campuses (high-density classrooms), warehousing and manufacturing (real-time IoT sensors), studio and broadcast (latency-sensitive)
- Wait 6-12 months: SMB offices without heavy real-time traffic, retail chains where Wi-Fi 6 is already working well
- Wait 18-24 months: residential, and co-working spaces where users change laptops quickly — wait for AP prices to drop and for Wi-Fi 7 to be the default in MacBooks and iPhones
A 5-point checklist before signing a Wi-Fi 7 PO
- Survey what percentage of client devices in the fleet actually have a Wi-Fi 7 chip
- Check whether the access switches support mGig and PoE++
- Set a 6 GHz channel plan based on 160 MHz, except where 320 MHz has been verified as appropriate
- Configure a band-steering policy that keeps Wi-Fi 6 clients on 5 GHz while Wi-Fi 7 clients get MLO across 5 + 6 GHz
- Run a predictive survey (Ekahau, Hamina, iBwave) or on-site validation before rollout, rather than trusting the spec sheet
Wi-Fi 7 is not a future option — it is the baseline for 2027-2028. But deploying it at the wrong time costs more than waiting another 12 months.