Why we shifted to Azure IoT Edge for disconnected warehouse analysis.

Not every distribution hub sits on fiber. Some of our largest deployments run in facilities where the internet connection drops for minutes at a time, every day.

Not every distribution hub sits on fiber. Some of our largest deployments run in facilities where the internet connection drops for minutes at a time, every day, without ever affecting the warehouse floor itself.

The Cost of Assuming Constant Connectivity

Our first-generation architecture streamed every scan event straight to the cloud. On a stable connection this worked well, but the moment a facility lost its uplink, we lost visibility into exactly the kind of exception events operators care about most.

A dropped connection during a receiving dock surge meant a gap in the audit trail right when discrepancies were most likely to occur.

Buffering and Syncing at the Edge

Azure IoT Edge modules now run directly on our rack-mounted hardware, buffering scan events, exception scores, and video-derived telemetry locally whenever the uplink is degraded or unavailable.

Once connectivity is restored, the module reconciles the buffered queue against our Azure Cosmos DB instance in order, so the dashboard timeline stays accurate even after an outage.

“We stopped designing for the network we wished every facility had, and started designing for the network most facilities actually have.”

The result is a platform that keeps counting, flagging, and logging inventory events on the warehouse floor, whether or not the rest of the building is online.