Warehousing and distribution RFID field guide
The WMS should receive business events, not an uncontrolled stream of tag observations. Define identity, location, task, aggregation, time window, confidence and exception rules in middleware before a receipt, move, pick or shipment is posted.
RFID can observe many tags repeatedly and out of order. WMS transactions require a bounded population, a business context and a decision about whether the observation is sufficient to change inventory.
01
Before comparing models, frequencies or read ranges, fix the process boundary, accountable owner and evidence the operation must produce. Record these decisions in the project scope.
02
RFID results depend on the item, environment, movement, device configuration and event logic together. Control risk through design constraints and exception handling rather than post-deployment interpretation.
03
Test matched, missing, extra, duplicate, wrong-location, split-pallet, canceled-task and offline scenarios. Verify inventory state, task state, middleware queue and physical stock reconcile after each case.
Use event IDs, business keys and state checks for idempotency. Keep the original observation available for audit while delivering a validated, versioned business event to WMS.
First turn the physical read into an explainable, traceable business event; then decide whether it satisfies the target workflow. Results that have not been validated at the target site should not be presented as a universal performance promise.
Review the responsibility boundaries across tags, devices, middleware and business systems together, and support acceptance with a written method, denominator and exception record.
Usually not. Middleware should filter and contextualize observations into the events the WMS contract expects.
The designated WMS or ERP normally remains the inventory system of record; RFID supplies validated evidence according to agreed rules.
Queue with source time and context, then revalidate against current task and inventory state before posting after reconnection.
Share WMS APIs, transaction rules, identifier hierarchy, device flows and exception cases. REAOX can define the event contract and integration test set.
