Lost pallets to RFID dock-door EPCIS, reconciled with TMS; time-stamped, shared evidence

Overview

A consumer durables company kept losing track of pallets and returnable containers as they moved between plants, distribution centers, 3PLs, and retailers. Shortages triggered last-minute repacks, deposits and rental fees piled up, and disputes with pooling providers and carriers dragged on without good evidence. Intelligex deployed RFID at dock doors, associated assets to shipments at the moment of load/unload, and reconciled those events with carrier scans and Transportation Management System (TMS) milestones. Asset balances became visible by site and in transit, and disagreements with partners were resolved using shared, time-stamped data.

Client Profile

• Industry: Consumer durables manufacturing and distribution
• Company size (range): Multi-plant, multi-DC network with 3PL partners
• Stage: Established Warehouse Management System (WMS), TMS, and pooled/owned returnable transport items (RTIs)
• Department owner: Procurement, Supply Chain & Logistics
• Other stakeholders: Warehouse operations, Carrier management, Finance/AP, Packaging engineering, Customer service, 3PLs and pooling providers, IT applications

The Challenge

Pallets, crates, and other RTIs flowed across a complex network. Counts were done manually or inferred from bills of lading, barcode labels degraded in the field, and asset movements were recorded late or not at all. The WMS knew what inventory sat on the dock; the TMS knew which truck moved when; pooling providers operated portals with their own records. None of these sources tied a specific asset identifier to a specific shipment event reliably. When a shortage surfaced at a site or a fee appeared on a pooling invoice, teams chased email threads and spreadsheets to reconstruct what happened.

Replacing core systems was not feasible. Operations needed to keep current WMS and TMS flows, carriers ranged from API-capable to phone-and-paper, and 3PLs followed their own processes. The business wanted a practical way to see asset balances by site and partner, standardize identifiers, and use objective events to reconcile charges and shortages—without slowing dock throughput.

Why It Was Happening

Tracking depended on batch counts instead of asset-level events. Pallets and containers were treated as line items rather than uniquely identified assets, so counts drifted with repacks, transfers, and split shipments. Barcode scans were inconsistent at high-volume doors and in rough environments, and association to shipments was often manual. Carriers captured trailer events, not container-level movements, so TMS data did not settle asset disputes.

Data lived in silos. The WMS recorded picks and loads; the TMS had tenders and statuses; pooling providers maintained separate ledgers; 3PLs uploaded spreadsheets. Without a shared event model and a way to link assets to shipment IDs at the dock, balances diverged and no single team owned reconciliation. Disputes hinged on memory and partial documents rather than a common, time-stamped record.

The Solution

Intelligex implemented an RFID-based tracking and reconciliation layer that captured asset movements at dock doors and tied them to shipments. Passive UHF tags on pallets and returnable containers were read by fixed portals and handhelds; events were recorded in a lineage ledger aligned with the GS1 EPCIS event model; and a reconciliation engine matched those events against TMS milestones and carrier scans. Exceptions flowed to a human-in-the-loop queue with reason codes. The approach preserved existing WMS/TMS processes and created a shared source of truth for balances and settlements, grounded in GS1 EPC/RFID standards.

• Integrations: Bi-directional sync with WMS for load/unload tasks and door assignments; TMS for shipments, tenders, and status events (for example, Oracle Transportation Management or SAP Transportation Management); ERP for asset accounts, deposits, and rental fees; pooling provider APIs or file exchanges; EPCIS event store for asset movement history.
• RFID infrastructure: Dock door portals and handheld readers tuned for high-throughput reads; tag commissioning and encoding using EPCglobal UHF Class 1 Gen 2 conventions; rugged tag selection for pallets and containers.
• Asset registry: Canonical mapping of each Electronic Product Code (EPC) to asset type, ownership (pooled vs. owned), pooling provider, and lifecycle status.
• Association and event capture: Automated linkage of dock reads to shipment ID, trailer, door, and time window; inbound and outbound events recorded with read confidence and operator context.
• Reconciliation engine: Comparison of expected versus actual asset counts by shipment and site; matching against carrier scans and TMS milestones; generation of evidence bundles for disputes.
• Validations and guardrails: Filtering for duplicate and stray reads, anti-collision tuning, and read windows bound to door tasks; checks for mismatched ownership and incompatible asset types on loads.
• Exception workflow: Human-in-the-loop review for shortages, overages, and misreads; tasks to adjust balances, initiate partner claims, or update the asset registry; reason codes captured.
• Dashboards: Balances by site and partner, in-transit assets, chronic loss lanes, pooling fee reconciliation, and dispute aging.
• Permissions and audit: Role-based access for operations, procurement, carrier management, finance, and partners; immutable logs of reads, associations, adjustments, and approvals.

Implementation

• Discovery: Mapped asset flows across plants, DCs, 3PLs, and retailers; identified chronic loss routes and doors with the heaviest volume; inventoried pooling provider data and fee practices; surveyed RF environments and metal interference risks; documented WMS/TMS integration points.
• Design: Defined the EPC encoding scheme and asset registry model; laid out portal placement and read zones; designed the EPCIS event schema and association to shipments; established reconciliation rules, thresholds, and reason codes; aligned a shared glossary for statuses.
• Build: Installed readers and antennas; configured middleware for read filtering and association; implemented EPCIS storage; built connectors to WMS/TMS/ERP and pooling portals; created the exception console and dashboards.
• Testing/QA: Calibrated read rates and anti-collision settings with live traffic; piloted on select doors and lanes with parallel manual counts; validated reconciliation against TMS events and carrier scans; enforced human-in-the-loop reviews to tune thresholds and stray-read filters.
• Rollout: Started with one DC and a subset of carriers and 3PLs; kept manual BOL counts as a fallback; expanded by door bank and route as read performance stabilized; onboarded pooling provider data for automated fee checks once event quality proved reliable.
• Training/hand-off: Quick sessions for dock leads and yard teams on portal workflows and handheld exception scans; guidance for packaging on tag placement and commissioning; playbooks for finance to use evidence bundles in fee disputes; transitioned run-state to supply chain operations with IT support on call.

Results

Asset visibility became routine. Pallets and returnable containers were associated to shipments at the door, and movements were reconciled against carrier and TMS events without extra steps for operators. Site-level and in-transit balances were accessible in one place, so shortages were addressed before they impacted shipping, and pooling fee reviews relied on a common record rather than email debates.

Partner conversations changed tone. Disputes with carriers and pooling providers were supported by event timelines tied to shipment IDs and door activities. Finance and procurement resolved charges with shared evidence, and operations focused on improving chronic lanes highlighted by the dashboards. The network spent less time reconciling counts and more time moving product.

What Changed for the Team

• Before: Asset counts lived in spreadsheets and BOL notes; After: RFID events at dock doors updated balances automatically and tied assets to shipments.
• Before: Disputes depended on recollection; After: Evidence bundles showed time-stamped reads, shipment associations, and carrier events.
• Before: In-transit visibility was guesswork; After: An EPCIS-backed ledger showed where assets sat by site and partner.
• Before: Tag scans were manual and inconsistent; After: Fixed portals handled high-volume doors with handhelds for exceptions.
• Before: Pooling fees were reviewed ad hoc; After: Reconciliation checks compared provider invoices with captured events and ownership rules.

Key Takeaways

• Treat pallets and returnable containers as tracked assets, not consumables—assign unique identifiers and capture movements at the dock.
• Use standards such as GS1 EPC/RFID and GS1 EPCIS so events are portable across partners.
• Associate asset reads to shipment IDs at load/unload and reconcile against TMS milestones to resolve discrepancies quickly.
• Filter and govern read data—calibrate portals, suppress stray reads, and route exceptions through a human-in-the-loop workflow.
• Integrate with existing WMS, TMS, ERP, and pooling portals; layer event capture and reconciliation without changing core processes.
• Pilot by door and lane, keep manual counts as a fallback, and expand once read rates and reconciliation outcomes are stable.

FAQ

What tools did this integrate with?
The solution synchronized load/unload tasks and door assignments with the WMS, matched events and milestones with the TMS (for example, Oracle Transportation Management or SAP Transportation Management), and updated asset accounts and fee reconciliations in the ERP. Pooling provider data was ingested via API or file exchange. Asset movement history followed the GS1 EPCIS event model.

How did you handle quality control and governance?
We tuned portals for read zones and anti-collision, applied filters for duplicate and stray reads, and bound reads to door task windows. Events carried read confidence, operator, and association context. Exceptions moved through a human-in-the-loop queue with reason codes and approvals. Changes to thresholds, ownership rules, and reconciliation logic were versioned and audit-logged.

How did you roll this out without disruption?
We piloted at a single DC with a few doors and lanes, running RFID capture in parallel with manual counts. The legacy process remained in place while we calibrated read performance and reconciliation rules. As confidence grew, we expanded door coverage and enabled automated fee checks, keeping handheld scans for exceptions and maintaining a fallback to BOL counts during transition.

What RFID standards and tags were used?
Tags and readers followed EPCglobal UHF Class 1 Gen 2 conventions, aligned with GS1 EPC/RFID. Rugged passive UHF tags were selected for pallets and containers, and EPC encoding schemes ensured each asset was uniquely identifiable across sites and partners.

How were disputes with carriers and pooling providers handled?
When a charge or shortage surfaced, the reconciliation engine produced an evidence bundle showing dock reads tied to shipment IDs, carrier milestones from the TMS, and asset ownership data. Those bundles accompanied dispute submissions to carriers or pooling providers. Finance and procurement worked from the same facts, and partners could reference the same event model to close issues faster.