Wireless problems we solve
Warehouse Scanners Disconnecting or Roaming Poorly
Scanner and AGV drops in distribution centres are usually roaming, cell-edge and racking-related RF problems rather than coverage shortfalls.
Engineer’s questionWhy do warehouse scanners lose connection while roaming?
1 — Direct answer
The short answer
Handheld scanners, vehicle-mount terminals and AGVs use conservative radios with low transmit power, small antennas and aggressive roaming thresholds. They fail long before a laptop does, in exactly the environments where RF is hardest: metal racking, changing inventory, long aisles and high ceilings.
Most warehouse disconnect cases come down to one of four things — a design built for coverage rather than roaming, asymmetric link budget between the AP and the scanner, roaming decisions the client makes too late, or authentication delays on every roam.
Treat it as a mobility problem, not a coverage problem. Measure at scanner height, with scanner-class transmit power in mind, along the routes the devices actually travel.
Likely causes, roughly in order of frequency
- Cell-edge design based on AP transmit power
- An AP at 17 dBm heard at −67 dBm may still be receiving the scanner's 10–13 dBm transmission at an unusable level. Asymmetry causes drops exactly where the heatmap looks acceptable.
- Sticky-client behaviour
- Scanner radios often hold an association until well below −80 dBm. Where cells are large, the device is already failing before it looks for a better AP.
- Racking and inventory changes
- A full rack of dense product is a very different RF environment than an empty one. Designs validated on an empty facility fail after go-live and after seasonal re-racks.
- Roaming and fast-transition configuration
- Missing or inconsistent 802.11r/k/v support, or full re-authentication on every roam, produces multi-second gaps that break session-based scanning applications.
- Coverage holes on travel routes
- Dock doors, freezer/cooler rooms, mezzanines, battery rooms and yard edges are frequently outside the designed coverage envelope.
- Application session timeouts
- Terminal-emulation and WMS sessions can drop from a roam gap of only a few hundred milliseconds, so a 'disconnect' may be an application event, not a de-authentication.
2 — Symptoms
Symptoms and what they usually mean
| Symptom | What it usually indicates |
|---|---|
| Drops occur in the same aisles or at the same turns | Location-specific RF or roaming boundary issue — highly diagnosable with an on-site survey. |
| Drops started after a re-rack or seasonal inventory change | The RF environment changed; the design did not. |
| Only certain device models are affected | Client radio capability, driver or roaming-threshold differences. |
| Sessions freeze then recover after several seconds | Roaming and re-authentication delay rather than a hard coverage loss. |
| Problems concentrated near dock doors or cold storage | Known hard-RF boundary areas that often need dedicated design treatment. |
3 — Do this first
Safe checks you can run yourself
These are non-disruptive checks a competent network engineer can complete with the controller or cloud dashboard already in place. Do them before changing configuration — they frequently identify the cause, and they always make an external investigation faster and cheaper.
- 1
Collect the device roaming logs
Most enterprise scanner platforms expose roam history, RSSI at roam and authentication timing. This is the highest-value data you already own.
- 2
Map the drop locations
Plot reported failures on the floor plan against AP placement and travel routes before assuming a global problem.
- 3
Review controller client-history and de-auth reasons
Distinguish de-authentication, idle timeout, authentication failure and clean roams.
- 4
Verify 802.11r/k/v support on both sides
Confirm what the WLAN advertises and what the scanner firmware actually supports — mismatches are common.
- 5
Check the SSID's security and RADIUS path
Full EAP re-authentication on every roam, or a distant RADIUS server, is a frequent and fixable cause.
- 6
Confirm minimum data rates and cell sizing
Very low basic rates enlarge cells and encourage clients to stay associated at unusable link quality.
4 — Watch out
Common mistakes and misleading indicators
“The heatmap shows −65 dBm everywhere”
Predicted coverage at AP transmit power does not represent what a 13 dBm scanner can deliver back to the AP.
“It must be the scanners, they are old”
Device age is real, but the design must accommodate the client population that is actually deployed.
“We added APs and it did not help”
Adding APs without adjusting channel plan, power and cell edges can increase CCI and worsen roaming.
“The controller shows no disconnects”
Application-layer session loss from roam gaps often leaves no controller event at all.
5 — Escalation point
When normal troubleshooting is no longer enough
- Drops are impacting shipping, receiving or picking productivity and cannot be reproduced on demand.
- You have device logs but no way to correlate them with RF conditions at those locations.
- The facility has been re-racked, expanded or re-purposed since the design was validated.
- AGVs, AMRs or vehicle-mount terminals are involved, where roaming continuity requirements are stricter than for handhelds.
- Multiple sites in the same network show the same behaviour and you need a reference design rather than per-site fixes.
6 — Professional investigation
What a professional wireless investigation should measure
- Active survey along travel routes
- Roaming behaviour, association history, retry rates and throughput measured along real picking and vehicle paths at device height.
- Passive survey at scanner class
- Coverage and SNR evaluated against the transmit power of the actual client devices, not the APs.
- Roaming and authentication analysis
- Packet captures of the roam exchange, including 802.11r fast transition, 802.11k neighbour reports and EAP timing.
- Spectrum analysis
- Identification of non-Wi-Fi sources common in industrial spaces: motors, chargers, wireless cameras, proprietary telemetry.
- Controller and RF profile review
- Channel plan, channel width, transmit power ranges, RRM behaviour, band steering, minimum data rates and roaming assist features.
- Physical design review
- AP placement, mounting height, antenna type and orientation relative to racking and aisle geometry.
7 — Relevant service
Which NetRobin service applies
Active Wireless Survey
An active survey measures the network as the client experiences it while moving — association, roaming, throughput and loss along the actual routes — which is the only reliable way to prove where and why mobile devices are dropping.
Often combined with
8 — Deliverables
What you should expect to receive
- Measured coverage, SNR and roaming behaviour along the travel routes surveyed
- Identified coverage and roaming boundary problems mapped to the floor plan
- Root-cause findings distinguishing RF, roaming, authentication and application factors
- AP placement, antenna and RF configuration recommendations
- Validation criteria for confirming the remediation worked
Direct answers
Frequently asked questions
- Why do warehouse scanners lose connection while roaming?
- Usually because the design was validated for coverage rather than mobility. Scanners transmit at lower power than APs, hold associations too long, and roam late. Combined with metal racking, changing inventory and full re-authentication on each roam, that produces drops at predictable locations.
- Should a warehouse survey be done with racking full or empty?
- Racking and inventory materially change RF. Where possible, survey under representative stocked conditions, and re-validate after significant re-racks, facility expansion or a change in stored materials.
- Does 802.11r fix scanner roaming problems?
- Fast transition removes re-authentication delay on roam, which helps when authentication is the bottleneck. It does not fix late roaming decisions, oversized cells or coverage gaps, and the client firmware must actually support the same mechanism.
10 — Next step
Request a Site Survey
Tell us the facility type, device models and where the drops occur — we will scope the right survey for it.