Guide · Networks, Firewalls & Wi-Fi

Why the Wi-Fi drops in the warehouse and not in the front office

The front office has never had a Wi-Fi complaint. The warehouse, on the same controller with the same access points, drops scanners in the back aisles, freezes the picking screen for five seconds at a time, and gets worse every November. Nothing is wrong with the equipment. The building is a different radio environment, and it was designed for the office.

Published 8 September 2026 · From the enterprise IT practice in Houston, Texas. Business hours, US Central; an engineer replies within one business day.

A different building

An office is drywall, ceilings nine feet up, and laptops that sit still. A warehouse is thirty-foot ceilings, aisles of steel racking that block and reflect radio, inventory whose height changes with the season, and scanners that move at forklift speed through a dozen coverage cells in a minute. The access points that cover an office from the ceiling cannot see down a racked aisle from the roof, and a scanner that changes cells every few seconds is doing the hardest thing a wireless client can do, which is roam.

The complaint arrives as 'the Wi-Fi drops', but the scanner rarely loses signal. It holds on to an access point it has left behind, or the picking application's session times out during a hand-off that took two seconds too long. Those are design problems, and they have known fixes.

The five causes, in the order we find them

  1. Access points mounted at the roof over the aisles, with racking between them and the scanner; the fix is lower mounting on the racking or the columns, or directional antennas aimed down the aisles
  2. Old scanners that only speak 2.4 GHz, and the network still allowing the slowest legacy data rates, which lets a distant scanner cling to a far access point at a crawl; raise the minimum rate, put the scanners that can on 5 GHz, and retire the ones that cannot
  3. Sticky roaming: transmit power turned up to fill the gaps, which makes every scanner hear a distant access point loudly enough to stay on it; turn power down, add access points, and turn on the fast-roaming standards only after checking the scanners support them
  4. Too few access points for the device count, so a shift change or a receiving wave saturates one radio while the next sits idle
  5. Interference from the building: microwave ovens in the break room, the neighbour's network on the same channel, wireless cameras, and in some plants the motors and welders on the floor

Inventory changes the radio

A survey done in July when the racks are half empty describes a different building from the one in November. Radio that passed through an empty bay is absorbed by a full one, especially by paper, liquids, and anything dense. Design for full racks, survey at both ends of the year if you can, and expect the fourth quarter to be the test.

What a survey actually produces

Two things. A predictive design, from the floor plan and the racking layout, that says where the access points go and how many. Then a validation walk with the scanner model you actually use, not a laptop, because scanners have weaker radios and their own roaming habits. The output is a heat map at scanner height, a list of access points with their locations and names on a drawing, and the channel and power plan. Label the access points so the drawing stays true.

A survey is also what settles the argument between the WMS vendor, who says it is the network, and the network provider, who says it is the application. The heat map and the roam log say which.

The network behind the radio

  • Scanners on their own VLAN, separated from the office, the cameras, and the guest network, with the WMS reachable and nothing else
  • A DHCP scope sized for every scanner, tablet, and printer on the floor with room to spare, and a lease long enough that a scanner does not renew mid-shift
  • Switch ports with enough power budget for the access points, and current firmware on the controller
  • The application's session timeout raised to cover a normal roam, after the roam has been fixed, not instead of fixing it
  • Label printers on the floor on a cable where there is one, because a printer roaming is a printer offline

The fixes that are not

  • A consumer range extender in the back corner, which doubles the airtime every packet costs
  • A second network name for the warehouse on the same access points
  • Transmit power set to maximum, which makes the sticky-client problem worse in every aisle
  • Replacing the scanners before surveying the building, which produces newer scanners with the same complaint

The survey and the redesign are the network, firewall, and Wi-Fi work on our Enterprise IT services page, and the floor it lands on is described on the 3PL and warehouse software page; the label printer case study is what the printers on the same floor needed.

Where this sits on the IT page

One row of our Enterprise IT services page does this work: Networks, Firewalls & Wi-Fi. The page covers the eight layers together, on-site across Greater Houston and remote across Texas, and starts every engagement with an inventory of what you have.

More guides

Other tickets this page gets

Printers, Scanners & Peripherals

Why a network printer keeps going offline in the office, and the four settings that fix it

Usually addressing, not hardware: a reserved address, a standard TCP/IP port, one driver from one place, and power settings that leave the network interface awake.

Read the guide →
Servers, Virtualization & Backup

Windows Server 2012 R2 gets its last updates on October 13, 2026 and 2016 on January 12, 2027: the per-server decision

Two deadlines four months apart, and a decision that is made one server at a time: in place, rebuilt beside the old one, or retired with the share that moved.

Read the guide →
Active Directory & Entra ID

Your only IT person quit. What to lock down in the first 48 hours

Nothing needs rebuilding today. The order of work for two days: the accounts that own everything, the leaver's own access, what would break next, and what to write down.

Read the guide →
Get in touch

Send a floor plan, or a photo of the racking.

How many scanners, which model, and where the access points are today. You get back what a survey would cover, whether the existing access points can be reused, and what the WMS timeout should be set to once the roaming is fixed.

Prefer to talk?

Call 832-598-8234 or email msco@stoneagesoftware.com. Houston, Texas — serving Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro.

What happens next

We read your message, an engineer replies with questions or a straight answer, and if it's worth a call we book one. No drip campaign, no handoff to sales.

No obligation — we reply within one business day. This form sends your details to Stone Age Software LLC so we can respond to you. See our privacy policy for how we handle them. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.