Logistics IT fails differently from office IT. A dropped scanner stops a pick, a failed line stops declarations, and neither waits for business hours. Support for a freight or warehouse operation means Wi-Fi designed around racking, a second internet path, and cover that matches shift patterns rather than office ones.
When the scanner stops, the goods stop
The operation runs longer than the office does, and the cost of a stoppage is immediate and physical. A truck at a gate waiting on a declaration is a different kind of problem from a slow spreadsheet.
Three consequences follow. Coverage has to match the shift pattern rather than nine to six. The network has to carry equipment an office never has: handheld scanners, label printers, weighbridges and CCTV. And connectivity to customs and port systems is not a convenience but the thing the operation runs on.
- Support hours matched to shifts, with a route that reaches someone at night.
- Wi-Fi designed around racking and movement, not around desks.
- A second internet path, because declarations cannot wait for a repair.
- Operational devices on their own network, separate from office systems.
- Documentation that a night-shift supervisor can follow.
How should warehouse Wi-Fi be designed?
Not like an office. Handheld scanners are the demanding client: many are older radios, all of them move constantly, and each aisle of steel racking changes where the signal goes. Coverage planned from an empty floor plan will not survive a full warehouse.
The design answer is a survey walked with the actual scanners once racking is in place, access points mounted for the aisles rather than for tidiness, and settings tuned so a device hands over cleanly instead of clinging to a distant radio. Our guide to warehouse IT and Wi-Fi covers the detail.
What happens when the internet fails?
In an office it is an interruption. In a logistics operation it can stop declarations, tracking updates and the customer portal at once, so a second path is infrastructure rather than a luxury.
It needs designing rather than buying. A second line from a different provider, connected to a firewall with two WAN ports, switches over automatically. Both du and e& publish business options. The detail that catches sites out is that failover usually changes the public address, which can break a portal that recognises you by it, so the procedure is agreed before it is needed.
How do shift workers use shared devices safely?
Shared logins are the usual shortcut and the usual audit finding, because nothing that happens on the floor can be traced to a person. The workable pattern is individual accounts with fast sign-in on shared devices, so accountability survives without slowing the shift down.
Handhelds, label printers and fixed terminals should sit on an operational network separate from office systems, so a compromised device cannot reach finance or HR. Our multi-location IT support page covers running that consistently across sites.
What should be ready before a peak season?
Logistics runs to seasons, and the weeks when the operation is busiest are the worst possible time to discover a limit. The pattern is predictable enough to plan against.
Capacity is the first check: a network sized for a normal week may not hold when temporary staff arrive with extra handhelds and the racking is fuller than the survey assumed. The second is change control, which matters here for the same reason it matters in an exam hall: a firmware update installing itself during peak week is a self-inflicted outage, so a freeze is agreed in advance. The third is the human route, meaning the night supervisor knows who to call and has the number on the wall rather than in an email.
None of this is expensive. All of it is far cheaper agreed in a quiet month than improvised in a busy one.
- Check capacity against peak headcount and device count, not the average.
- Agree a change freeze covering firmware, configuration and cabling work.
- Confirm failover actually switches, by testing it rather than assuming.
- Post the out-of-hours support route where the night shift will see it.
- Hold spare handhelds and label printers, configured and charged.
What about sites in the free zones?
Many Dubai logistics operations sit in zones with their own connectivity arrangements and their own approvals for works, and Dubai South publishes what applies there.
The practical implications are lead times and access. Getting a line installed, or a contractor approved to run cable at height, takes longer in a zone than in a tower, so both are started earlier. Our IT for Dubai South logistics guide covers the pattern.
Scanning through the night shift
We cover the infrastructure the operation runs on: warehouse and office networks, Wi-Fi surveyed with your devices in place, failover internet, segmentation, Microsoft 365, backup and support with written response times. Engineers work on site across the UAE and the support line runs 24/7.
What we do not do is replace your warehouse management or customs software, which are specialist platforms; we make them reliable and coordinate with those vendors. A free site assessment covers the network, coverage and failover, and you keep the findings either way.
Frequently asked questions
Yes. The support line runs 24/7 and out-of-hours arrangements are written into the agreement rather than being best effort, because a logistics operation running shifts will eventually have a problem at two in the morning. What is covered and who is called is agreed in advance.
Usually because they hold on to a distant access point instead of handing over as the picker walks, or because racking blocks signal in ways an empty-floor plan never showed. A survey walked with the actual scanners, plus settings tuned for roaming, fixes most cases without new hardware.
If declarations, tracking or a customer portal stop when the line does, yes. A second line from a different provider on a firewall with two WAN ports switches over automatically. Plan for the public address changing on failover, because portals that recognise your site by it will notice.
They should not. Shared logins remove any trace of who did what, which becomes an audit finding and a security gap. Individual accounts with fast sign-in on shared devices keep the shift moving while preserving accountability.
Not as the vendor. Those are specialist platforms and we do not claim to replace them. We make the infrastructure they depend on reliable, handle identity and access, and coordinate with the vendor when an issue crosses between the platform and the network.
Written by Srinivasan Ramachandran, Founder, Listonics · Last reviewed September 27, 2026