Five practical takeaways
- Seasonal staffing can increase the number of devices active at once, particularly where extra scanners or terminals are issued for peak shifts.
- Shift changes can create short spikes in authentication and connection activity when devices reconnect, reauthenticate or are handed to a new team.
- Capacity planning should be based on realistic device concurrency by zone, not simply the total seasonal headcount.
- Higher order volumes do not automatically mean high bandwidth demand; reliable transactions, roaming and consistent response matter just as much.
- The best time to prove the network can support peak is before the warehouse reaches peak operating conditions.
Summary
Peak trading changes the way a warehouse network is used. More workers may be active in the same picking and packing areas, additional scanners may be issued, shifts may overlap and temporary staging areas can change how devices move around the building.
Our approach is to map expected devices and workflows by zone, then check whether the existing wireless and wired infrastructure has enough headroom.
The Office for National Statistics publishes regular UK temporary-worker data, but a warehouse capacity plan still needs to be based on the site’s own staffing, device and shift assumptions.
Introduction
In our UK Netcom design work, seasonal capacity planning is different from asking whether Wi-Fi works on an ordinary day.
A distribution centre may add temporary staff, issue more handheld scanners, extend operating hours or change picking routes to handle higher order volumes. Those changes can put more devices into the same operational areas and make small weaknesses more visible.
The important point is to plan against the peak operating condition rather than use the peak itself as the test.
What actually changes when seasonal staff join a warehouse?
More people on site is the obvious change, but headcount alone is not a useful Wi-Fi capacity figure.
What matters is how many additional wireless devices will be active, where they will be used and what those devices will be doing.
Twenty additional workers spread across a building may create very little extra pressure in one area. Twenty pickers using dedicated scanners across the same group of aisles can create a very different demand profile.
We would normally look at:
- Additional devices by operational zone;
- Device type and wireless capability;
- Expected concurrent activity;
- Movement between access points;
- Shift patterns and overlap;
- Temporary work areas created for peak.
Our guide to designing Wi-Fi across offices, warehouses and outdoor areas explains why warehouse capacity cannot be separated from the physical RF environment. High racking, stock, aisle geometry and loading areas all affect how the design behaves.
Why can shift changes create short spikes in demand?
A shift change does not automatically create a network problem.
However, where devices reconnect, reauthenticate, are powered up or are handed to a new team, many connection events can happen over a short period. A network that performs well once everybody is connected may therefore behave differently during that transition.
We would want to understand whether scanners remain logged in, whether users authenticate again and how much overlap exists between outgoing and incoming teams.
Steady mid-shift behaviour may not reveal a problem that only appears around changeover.
Does higher order volume mean the warehouse needs more Wi-Fi bandwidth?
Not necessarily.
Many scanner and WMS transactions are relatively small in data terms. The better question is whether those transactions continue to complete reliably while more devices are active and moving around the site.
We would look at airtime use by zone, retries, roaming behaviour and application response rather than relying on a headline bandwidth figure.
Our article on how enterprise Wi-Fi supports business-critical applications looks at this distinction in more detail. Business-critical wireless is about predictable performance, not simply the highest speed-test result.
How should seasonal Wi-Fi capacity be planned rather than assumed?
A good capacity plan starts with the busiest realistic operating condition.
| Planning question | Why it matters | What we would check |
| How many additional devices will be active in each zone? | Capacity pressure is local to the APs serving that area | Device count by picking, packing, goods-in and dispatch zone |
| Will shift patterns change? | Longer or overlapping shifts can extend busy periods | Peak concurrency and overlap between teams |
| What happens at shift change? | Reconnection and authentication may briefly concentrate demand | Behaviour during changeover, not just mid-shift |
| Are new device models being introduced? | Different clients can roam and behave differently | Band support, roaming behaviour and real-device testing |
| Will stock or layouts change for peak? | RF conditions can change even if AP positions stay the same | Racking, staging areas, pick faces and operational routes |
The aim is to model a credible busy period and leave enough headroom for normal variation.
That is more useful than designing around total site headcount because Wi-Fi demand is rarely spread evenly across a warehouse.
How can stock, racking and temporary staging affect peak Wi-Fi?
Peak season can change the RF environment as well as the number of users.
Racking may hold more stock. Temporary staging areas may appear around goods-in or dispatch. Pick faces may move, and busy routes through the warehouse can change.
Dense stock can absorb or reflect RF energy, while metal racking can shape how signal travels along aisles. We would not assume that an empty or lightly stocked warehouse represents the hardest operating condition.
This is one reason our Wi-Fi site surveys and consultancy look at device capacity, existing infrastructure, interference, building construction and application priorities together.
Coverage remains important, but it is only one part of the picture.
How should different seasonal devices be accounted for?
Temporary workers do not necessarily use different devices from permanent staff. Many sites simply issue more of the existing scanner estate.
But if different scanners, tablets or terminals are introduced for peak, they should be checked rather than assumed to behave like established hardware.
The current IEEE 802.11 wireless LAN standard provides the underlying WLAN framework, but real client behaviour still varies according to hardware, drivers, antenna design and supported features.
We would want to know whether a new device:
- Supports the intended frequency bands;
- Associates reliably;
- Roams cleanly between access points;
- Maintains the required application session;
- Performs consistently in the busiest operational areas.
Testing only with an engineer’s laptop can miss those differences. In warehouse environments, the scanner or terminal people actually use is the device that matters.
What else should be checked beyond the access points?
Peak Wi-Fi capacity is not solely an access-point question.
Switch ports, uplinks, PoE capacity and authentication infrastructure all sit behind the wireless layer. If one of those becomes constrained when more devices are active, the user may experience it as a Wi-Fi problem.
In our UK Netcom survey work, we therefore look at whether the wider infrastructure can support the proposed operating condition.
That can include:
- AP-facing switch-port capability;
- uplink utilisation and available headroom;
- PoE capacity where additional APs are proposed;
- authentication behaviour at busy periods;
- cabling and infrastructure issues affecting particular areas.
This does not mean every seasonal increase needs a wired-network upgrade. It means those dependencies should be checked before the wireless network is blamed.
Does peak capacity planning always require new hardware?
No. Existing access points and switching may be perfectly adequate if RF capacity, switch and uplink capability, PoE headroom, authentication services and client behaviour have been checked against the proposed peak load.
Sometimes configuration or RF optimisation is enough. In other cases, a particular zone genuinely needs additional capacity or a different wireless design.
We let the evidence determine that recommendation rather than starting with an access-point count.
That matters because adding another AP is not automatically a capacity fix. If the underlying problem is channel utilisation, cell design or client behaviour, another radio may not solve it.
How should warehouses prove capacity before peak arrives?
This is where a capacity estimate becomes useful operational evidence.
Where practical, we would validate representative peak conditions before the busiest period starts by:
- Testing with the scanner or terminal models that will actually be used.
- Walking real picking and replenishment routes.
- Checking busy zones with representative concurrent clients.
- Observing channel utilisation, retries and roaming behaviour.
- Testing shift-change authentication where relevant.
- Confirming application continuity during movement.
The aim is to test the conditions most likely to expose a capacity or roaming weakness before peak arrives.
We would not necessarily try to recreate every order or every worker expected during the busiest week. The objective is to reproduce enough of the expected device density, movement and application behaviour to determine whether the network has suitable headroom.
Is complaint history enough to judge the previous peak?
Not on its own.
A warehouse that received very few Wi-Fi complaints last year may have performed well, but complaint numbers do not measure capacity.
Support records are still useful. Repeated scanner disconnects, delayed transactions or trouble in a particular aisle can help identify where deeper testing is needed.
But measured network behaviour gives us a stronger baseline than assuming that few tickets mean plenty of spare capacity.
For UK Netcom, this distinction matters because seasonal planning should be based on what the network can demonstrate, not simply what users happened to report.
When should a warehouse review capacity again?
A full survey does not automatically need repeating every year.
We would review the assumptions whenever there is a meaningful change in:
- Peak device count;
- Shift structure;
- Scanner or terminal models;
- Warehouse layout;
- Racking or stock profile;
- Operational applications;
- Switching or wireless infrastructure.
If very little has changed and the previous peak was properly validated, a focused review may be enough.
The important thing is to know what the last design or survey was validated against. If that baseline no longer resembles the way the warehouse operates, it is worth checking again.
Conclusion
Seasonal staff and peak order volumes create a predictable change in the way a warehouse network is used.
The important figure is not simply seasonal headcount. It is the number and type of devices active in each zone, how those devices move, what happens during busy transitions and whether the RF environment changes as stock and workflows change.
For us, the aim is to validate the peak operating condition before the warehouse reaches it, rather than discover a capacity gap once demand is already at its highest.
Distribution centres preparing for their next peak can speak with our Wi-Fi design team about a seasonal capacity review based on the devices, zones and workflows that matter most.
FAQs
Do we need to survey the network every year before peak season?
Not necessarily. A full survey may not be required if the network, warehouse layout, device estate and peak operating model have not changed materially. We would revisit the assumptions when those conditions differ from the last validated period.
Is shift-change load really different from steady mid-shift demand?
It can be. Where devices reconnect, reauthenticate or are issued to incoming staff, a short concentration of connection activity can behave differently from the same devices already connected and working steadily.
Should seasonal workers use different devices from permanent staff?
Not necessarily. Using the same proven device estate can simplify planning. If different devices are introduced, their wireless capability and roaming behaviour should be tested before peak.
Does a lack of complaints during a previous peak prove the network coped well?
No. Support-ticket volume is useful operational information, but it is not the same as measured capacity. Validation data gives a more reliable view of whether the network had adequate headroom.
Does higher order volume automatically mean we need more access points?
No. Higher order volume may increase device activity, but the answer depends on where that activity occurs, existing airtime utilisation, client behaviour and RF design. More access points should only be recommended where the evidence shows they are needed.