Industry problems

How do warehouses and yards handle dead zones?

Warehouses and yards handle dead zones in two ways. They add coverage, with more Wi-Fi or a private cellular network such as CBRS in the United States, and they make devices tolerate gaps by keeping scans and task updates on the device until they can reach the warehouse system. Standards such as GS1 EPCIS help, because an event records when and where it happened separately from when a system received it.

TL;DR

More Wi-Fi or private CBRS can shrink dead zones, but radios fail, so devices must also tolerate gaps. Scans with a GS1 identifier and EPCIS event time, held in a durable outbox, survive a dead zone intact. Two devices can still act on the same thing while apart, so use operation IDs and let the system of record decide conflicts.

Learning objectives

After reading this article you will be able to:

  • Explain how extra Wi-Fi and private CBRS networks add coverage in warehouses and yards
  • Describe how GS1 identifiers and EPCIS event times let scans survive a dead zone
  • Identify the conflicts that arise when two devices act on the same thing apart

Warehouse and yard dead zones

A warehouse network is local infrastructure, so anywhere the site’s own radios do not reach is a dead zone for the devices that depend on them. Handheld scanners, vehicle terminals and phones reach the warehouse management system through access points or radios the site installs. A yard is the same problem at a larger scale: trailers, gatehouses and parking rows spread across open ground, sometimes far from the building.

Gaps will always exist, so what matters is 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.

Extra Wi-Fi and private CBRS coverage

The direct way to remove dead zones 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. Wi-Fi vs private 5G vs a device mesh compares the options on spectrum, devices, cost per shift and what fails when each one goes down.

Dead-zone scans with GS1 and EPCIS

Making scans tolerate a dead zone starts with the data, and two GS1 standards help a scan keep its identifier and its true time through the gap.

  • 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 eventTime is when the capturing application says the event occurred, while recordTime is 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.

Conflicts between devices working apart

Problems appear when two devices act on the same thing while apart. Holding data locally keeps it safe, but the device is working from what it last knew:

  • 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.

Frequently asked questions

Does a private CBRS network work without the internet?

Under the rules the FCC adopted in 2015, CBRS radios must register with and be authorised by a Spectrum Access System before they first transmit, and must follow its instructions on power and frequency. Planning a private network therefore includes planning how its radios stay in contact with that system.

Can a handheld scan barcodes with no connection?

Yes. A GS1 barcode carries the identifier itself, so the scan can be captured and stored on the device. What the device cannot do offline is look up information about that item unless it already holds a local copy.

What is the difference between eventTime and recordTime in EPCIS?

eventTime is when the capturing application says the event occurred, while recordTime is 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.

What is an SSCC?

The GS1 General Specifications define the Serial Shipping Container Code as the identifier for an individual logistic unit, unique worldwide. Because it is printed in the barcode, a handheld can capture a scan with no connection at all.

How quickly must a CBRS radio obey the Spectrum Access System?

Under the rules the FCC adopted in 2015, a radio must change frequency, change power or stop transmitting within 60 seconds when instructed. It must also register with the system before its first transmission.

Can a handheld in a dead zone pass its scans to another device?

Yes, with device-to-device software. A handheld can pass its retained records to a nearby device, such as a vehicle terminal or another handheld, which carries them toward coverage, while the warehouse system remains the record.

Sources

Build it with Offline Protocol

The backend delivery guide describes how to retain readings and workflow events on devices, optionally pass them to a local collector, and deliver them to an existing system of record with explicit acceptance at each step.

Read the backend delivery guide