Where dead zones come from
A warehouse network is local infrastructure. Handheld scanners, vehicle terminals and phones reach the warehouse management system through access points or radios the site installs, and anywhere those radios do not reach is a dead zone for the devices that depend on them. A yard is the same problem at a larger scale: trailers, gatehouses and parking rows spread across open ground, sometimes far from the building.
The question is not whether gaps exist but what happens to work done inside them. A pick, a putaway or a trailer check made in a dead zone has to be recorded somewhere, and later it has to reach the system of record without being lost, duplicated or given the wrong time.
There are two broad responses. One is to shrink the gaps with more coverage. The other is to make devices and data tolerate them. The two can be combined.
Adding coverage
The direct answer is more radio. Extra Wi-Fi access points fill gaps inside the building. For larger areas, such as yards, a private cellular network is another option.
In the United States, the Citizens Broadband Radio Service (CBRS) opened the 3550-3700 MHz band to shared commercial use, and the FCC’s order names private wireless broadband networks for industrial processes among its intended uses. That 2015 order set up three tiers: incumbent users, such as federal radar systems, have the highest priority; Priority Access licensees come next; and General Authorized Access users can operate throughout the band but receive no interference protection from other CBRS users. A Spectrum Access System authorises radios by location and frequency. Under those rules, a radio must register with the system before its first transmission and must change frequency, change power or stop transmitting within 60 seconds when instructed.
More coverage is more infrastructure. Each radio, controller and core network is a component that can fail, and a private network still has to be designed around the places devices go.
Making records survive the gap
The second response starts with the data. Two GS1 standards help.
- Identifiers in the label. The GS1 General Specifications define the Serial Shipping Container Code (SSCC) as the identifier for an individual logistic unit, unique worldwide. Because the identifier is printed in the barcode, a handheld can capture a scan with no connection at all.
- Events with their own time. The GS1 EPCIS standard lets different applications create and share visibility event data. Each event describes what, when, where, why and how. Its
eventTimeis when the capturing application says the event occurred, whilerecordTimeis when a repository recorded it, a bookkeeping field that says nothing about the real-world event. A scan held on a device until it reaches coverage keeps its true time when it finally arrives.
On the device, the pattern is an offline-first app. Android’s guidance describes the local data source as the app’s source of truth. For data that matters, it recommends lazy writes: save locally first, then queue the change to send at the earliest opportunity. A durable outbox holds those changes, and a background job drains it with exponential backoff once the network returns.
What the gap still breaks
Holding data locally keeps it safe, but the device is working from what it last knew. Problems appear when two devices act on the same thing while apart:
- Two pickers are sent to the same location because the reassignment never reached one of them.
- A pallet is moved twice, once by each of two devices that did not see the other’s scan.
- A trailer is marked ready in the yard while the building’s system still shows it loading.
Some conflicts can be merged; others need an authority, such as the warehouse management system, to decide. Each record needs an operation ID so a retried upload is applied once, and the app should distinguish a message being delivered from being accepted and committed by the system of record.
Device-to-device software adds a third option between “covered” and “not covered”. A handheld in a dead zone can pass its retained records to a nearby device, such as a vehicle terminal or another handheld, which carries them toward coverage. This is store and forward applied to a site. The warehouse system remains the record; the local exchange only moves data closer to it.