Five practical takeaways
- A WMS rollout can make existing network weaknesses much more visible because scanners, terminals and other operational devices become more dependent on reliable connectivity.
- Handheld scanners, printers and forklift-mounted terminals behave differently on Wi-Fi and should be checked as separate device types.
- Roaming across aisles, loading areas and operational zones matters just as much as basic coverage for mobile WMS devices.
- Switching, cabling, uplink capacity and PoE can constrain a WMS rollout even where wireless coverage appears good.
- Testing representative workflows before go-live gives the distribution centre a better chance of finding network problems before they affect a whole shift.
Summary
A WMS can only work reliably if the network underneath it is reliable too.
When failed scans, delayed updates or dropped sessions appear during a rollout, it is easy for the WMS itself to take the blame. In practice, the underlying cause may be an existing coverage gap, poor roaming behaviour, an unsuitable client device or a constraint elsewhere in the network.
Our approach at UK Netcom is to check those conditions before go-live. A WMS project should not begin with the assumption that an existing warehouse network is either good enough or needs replacing. It should begin by proving what the network can support.
Introduction
In our design work, we see new operational systems expose network problems that were already there but had not previously caused enough disruption to attract attention.
A WMS rollout is a good example.
It may bring handheld scanners, vehicle-mounted terminals, mobile printers and live dashboards into workflows where reliable connectivity becomes part of the movement of stock itself.
That does not necessarily mean the WMS generates huge amounts of bandwidth. The bigger issue is often that connectivity becomes more operationally important and less tolerant of interruption.
This article sets out what we would check on the network side before that change goes live.
Why does a WMS rollout change what the network needs to support?
Some warehouse networks were originally designed around lower device concurrency or more intermittent workflows.
A WMS can change that pattern. More users may depend on handheld devices throughout a shift. Forklift terminals may stay connected as vehicles move between aisles. Scans may need to reach the application promptly before the next part of a process can continue.
That makes reliability, roaming and application continuity more important than headline speed.
Our article on how enterprise Wi-Fi supports business-critical applications looks at the same principle more broadly. Good coverage is useful, but the network still has to support the application and device behaviour behind the workflow.
Before a WMS goes live, we would want to understand:
- Which devices will use it;
- Where those devices will move;
- Where a lost connection causes operational delay;
- How many devices may be active at peak periods;
- Whether goods-in, dispatch, loading bays or yards are included;
- What happens to a transaction if connectivity briefly drops.
That gives us a clear picture of what the network actually needs to support.
What should be checked on the wireless side before rollout?
Does coverage exist everywhere the WMS will actually be used?
The obvious place to start is coverage, but the test area should follow the workflow rather than simply the floor plan.
That may include:
- Goods-in;
- Storage aisles;
- Pick faces;
- Packing areas;
- Mezzanines;
- Dispatch;
- Loading bays;
- Chilled or specialist storage;
- Outdoor or transitional areas.
Warehouses can be difficult RF environments because high racking, stock materials, aisle geometry and mounting height all influence how signal behaves.
The environment can change too. An empty aisle may behave differently once the racking is filled, particularly where stock materials absorb or reflect RF energy.
We therefore want to know whether the network works where the device is actually used, including at scanner or terminal height, rather than simply whether coverage exists somewhere in the space.
Our guide to designing Wi-Fi across offices, warehouses and outdoor areas explains why different operational zones cannot always be treated as one identical RF environment.
How well do scanners and terminals roam between access points?
Roaming matters because warehouse devices move.
A handheld scanner may travel through several cells during one picking route. A forklift-mounted terminal can move quickly between aisles and operational zones.
If a device stays attached to an access point for too long, or transitions badly between cells, the user may see delays or dropped application sessions even though there is technically Wi-Fi coverage.
Features within the current IEEE 802.11 wireless LAN standard, including mechanisms associated with 802.11k, 802.11v and 802.11r, can assist roaming where the WLAN and client support them.
They do not remove the need for proper RF design.
The client device still plays a major role in deciding when to roam, so we would look at both the infrastructure and the actual scanner or terminal being deployed.
What device activity should the network be tested against?
The better question is not whether every device can associate with Wi-Fi. It is whether those devices can keep working reliably throughout a real shift.
We may want to understand what happens when:
- Several pickers work in the same aisle;
- A shift change increases concurrent logins;
- Scanners roam while transactions are active;
- Printers and terminals operate at the same time;
- Dashboards and operational systems share the infrastructure.
The WMS itself may use relatively small transactions, but those transactions can still be business-critical.
What should be checked on the wired side before rollout?
Good Wi-Fi coverage does not mean the whole network path is healthy.
Switching, uplinks, cabling and power all sit behind the access points. If one of those areas is constrained, improving the wireless design alone may not solve the problem.
Before rollout, we would normally check:
- Whether AP-facing switch ports provide the required speed;
- Available switch and uplink capacity;
- PoE capability and overall power headroom;
- Cabling condition and suitability;
- Resilience around critical network paths;
- How business-critical systems are separated from unrelated traffic.
This is part of why our UK Netcom Wi-Fi site surveys and consultancy look at the existing infrastructure as well as RF behaviour. A wireless design only makes sense if the network underneath it can support the result.
Does network segmentation need reviewing?
A WMS is a business-critical application, so network architecture and access controls should be considered alongside performance.
The UK’s National Cyber Security Centre explains in its network security fundamentals guidance that segmentation can help control traffic flow and access between different parts of a network.
For a distribution centre, that may mean making deliberate decisions about how WMS devices, corporate systems, guest access, operational equipment and management interfaces are separated.
Segmentation does not make Wi-Fi faster by itself. Its purpose here is to control access and help limit the impact of unrelated or compromised systems.
What network-adjacent devices does a WMS rollout typically add or stress?
Different device types deserve separate consideration because they do not all behave like a modern laptop.
| Device type | Typical network behaviour | What we would check |
| Handheld barcode scanners | Short transactional activity while moving between locations | Coverage at carrying height, roaming behaviour and client compatibility |
| Forklift-mounted terminals | Persistent application sessions while vehicles move through aisles and zones | Coverage and roaming along real vehicle routes |
| Networked label printers | Intermittent but operationally important traffic from fixed positions | Reliable connectivity at printer locations and correct network access |
| Supervisor tablets | Persistent application or dashboard sessions | Coverage, roaming where applicable and realistic concurrent activity |
The device model matters.
Rugged scanners may support different bands, roaming features or antenna characteristics from laptops and smartphones. A network that looks healthy when tested with an engineer’s laptop can behave differently with the devices employees actually use.
This distinction matters in warehouse environments. UK Netcom does not just want to prove that a device can connect. We want to understand whether the devices the warehouse depends on can complete their real workflows reliably.
How should the warehouse environment itself be considered?
Warehouse Wi-Fi is rarely static.
Stock levels change. Pallets move. Racking may be reconfigured. Temporary staging areas appear during busy periods. Loading doors open and close, and mobile equipment moves through the RF environment.
That is why a pre-WMS review should consider the operational site, not just a drawing.
We would pay particular attention to:
- High or dense racking;
- Changing stock profiles;
- Narrow aisles;
- High-bay mounting;
- Mezzanines;
- Vehicle routes;
- Loading areas;
- Indoor-to-outdoor transitions.
These details help explain why two apparently similar warehouses can need different wireless designs.
How should WMS performance be validated before go-live?
This is where we stop relying on assumptions and test the network properly.
Where possible, we would validate the network using representative devices and workflows.
That might mean walking a real picking route with the scanner model that will be deployed, driving a representative forklift route, checking fixed printers and testing transitions between goods-in, storage, packing and dispatch.
The aim is to answer practical questions:
- Does the device stay usable throughout the route?
- Does it roam where expected?
- Are application sessions maintained?
- Are there repeatable weak points?
- Does performance change when several devices are active together?
A coverage map on its own cannot prove application continuity.
Post-change validation is important in our UK Netcom work because it turns “the design should work” into evidence that the network actually supports the intended operation.
How should business disruption risk be managed during cutover?
Where network changes are being made alongside the WMS rollout, changing everything across the entire distribution centre at once can make troubleshooting harder.
Where operationally practical, we would favour a controlled approach:
- Define the network changes required before cutover.
- Pilot them in a limited or representative area.
- Test the real devices and workflows.
- Record what success looks like.
- Keep a rollback plan for changes that affect live operations.
- Extend the change once the result has been validated.
Not every site needs the same cutover plan, but network changes should still be tested before they affect the whole operation.
The precise approach will depend on the site, WMS and operational constraints.
Conclusion
A WMS can appear to fail because of network problems the warehouse team never sees directly.
Coverage, roaming behaviour, client-device capability, switching, cabling and PoE can all affect what looks to the user like a simple WMS transaction.
The better approach is to check those conditions before go-live.
Our UK Netcom approach is to understand the workflow, test the devices and routes that matter, identify the underlying constraints and validate the result before assuming either the software or hardware needs changing.
Distribution centres preparing for a WMS rollout can speak with our Wi-Fi design team about a network readiness review before the go-live date is committed.
FAQs
Can an existing Wi-Fi network support a new WMS without changes?
Sometimes. It depends on the existing RF design, device population, client behaviour, wired infrastructure and how the WMS will actually be used. We would check those conditions rather than assume the network either needs replacing or will automatically cope.
Is roaming really that important for a WMS rollout?
Yes, where scanners or forklift-mounted terminals move regularly between access points. Poor roaming can interrupt application use even when general Wi-Fi coverage appears adequate.
Should the wired network be checked even if Wi-Fi coverage looks fine?
Yes. Switch ports, uplinks, cabling and PoE can still constrain an access point or the network path behind it. Good RF coverage does not prove that the whole connection is healthy.
Does a WMS need a high-bandwidth Wi-Fi network?
Not necessarily. Many WMS transactions are relatively small. Reliability, application response, roaming and consistent connectivity may matter more than maximum throughput.
How much disruption should a WMS-related network change cause?
There is no universal answer. Where operationally practical, network changes should be tested in a controlled area, validated with real workflows and backed by a rollback plan before wider deployment.