RFID warehouse processing 16,800 barrels per hour at 99.7% dispatch accuracy
A flagship deployment that took dispatch errors from 8, 10% to under 0.3%: and turned a 5-hour shift-end reconciliation into a 20-minute exception review.
Outcomes
16,800
barrels / hour
Sustained throughput
90%
reduction
In dispatch errors
99.7%
accuracy
Outbound manifest match
< 9
months
Payback period
4×
faster
Shift-end reconciliation
The challenge
- Dispatch errors running at 8, 10% of outbound shipments, ~1 in 10 trucks left with a discrepancy.
- 5, 6 hours of daily shift-end reconciliation, two staff full-time.
- Returns sat unrecorded for 24, 48 hours before appearing in SAP.
- Zero visibility into which specific barrels were in which zone, FIFO dispatch impossible.
What we built
- Passive UHF RFID at every dock, intra-plant aisle and outbound gate.
- Forklift-mounted readers paired with rugged Samsung Galaxy XCover handhelds.
- Custom edge deduplication engine reducing 50+ raw reads per barrel into a single canonical movement event.
- Real-time SAP S/4HANA integration with IDoc-based goods-issue and goods-receipt postings, 15-minute reconciliation cadence.
- Operator UI in regional languages with one-click exception reporting.
The shop floor we walked into
Fourteen clipboards. That was the count on day one. Fourteen versions of the same inventory truth, each maintained by a different operator across the warehouse. The shift supervisor’s master register contradicted the forklift driver’s log, which contradicted the dispatch gate’s tally sheet. Nobody was lying, they were all working with data that was already stale by the time it was written down.
For a high-velocity paint manufacturing facility shipping thousands of barrels a day, the cost of that staleness was 8, 10% dispatch errors, 5, 6 hours of nightly reconciliation, and a customer-claims trend the COO refused to accept as the new normal.
What we built
A four-layer RFID stack designed to survive the realities of an Indian paint warehouse, oil, dust, metallic racking, forklift traffic and shift changes.
Why standard RFID would have failed
A naive deployment of off-the-shelf readers and middleware would have drowned SAP under tens of millions of raw read events within the first week. The breakthrough was the edge deduplication engine, reducing the firehose of reads into a settled stream of business-meaningful movements before anything hit the ERP.
What changed for operations
Within six months of go-live, dispatch errors fell by 90%. The two-person nightly reconciliation team was redeployed to value-adding work. Customer chargebacks dropped sharply. The COO got an answer to the question that had been bothering him for years: “Where, exactly, is barrel batch number X right now?”
Tech stack
- • Impinj fixed readers
- • Zebra forklift readers
- • Samsung Galaxy XCover7 handhelds
- • Custom edge dedup engine
- • SAP S/4HANA (IDoc/BAPI)
Timeline
14 weeks pilot to full warehouse rollout. 6-week hyper-care window.
Talk to the team
Want a reference call with this customer?
Under NDA, we facilitate direct conversations with selected reference clients.
Request a reference call