RFID Container Tracking Through LDB: Shipment Exception and Proof-of-Movement File
By Ravi Sisodia · Reviewed by CA Divyanshu Sengar · Updated 5 October 2026
2-minute summary
- RFID events give LDB a physical-movement evidence layer across ports, rail, toll and logistics nodes.
- For an exception investigation, the strongest use is a timestamp sequence showing where the container was observed and where the next expected event failed to appear.
- RFID evidence should be paired with gate slips, FASTag/rail/carrier data and custody documents when the dispute turns on possession or responsibility.
Current position
Control and evidence map
| # | Control / evidence requirement | |
|---|---|---|
| 1 | Preserve the raw event timestamp, location/node and event label rather than only a dashboard screenshot. | |
| 2 | Check for duplicate reads, missing reads and impossible sequence jumps before relying on the trail. | |
| 3 | Join RFID events to vehicle/FNR/carrier records where available. | |
| 4 | Identify the custody handover document corresponding to each critical movement event. | |
| 5 | Escalate unexplained gaps using a standard exception code and owner. | |
Worked example
A container has an RFID exit read at a port but no expected inland toll/rail event for an extended period. The logistics team should verify whether the container changed vehicle or mode and obtain the corresponding handover record before declaring it “stuck”.
Common mistakes
- Equating an RFID read with contractual acceptance by the next party.
- Ignoring a changed container or vehicle number.
- Using a screenshot that hides event details or timezone.
- Not documenting how a missing event was investigated.
Frequently asked questions
What technology does LDB use?
The official release identifies RFID, IoT, Big Data and Cloud technologies.
Is every physical movement captured?
Coverage is extensive, but operational gaps or identifier changes can occur and should be investigated.
Can RFID events prove custody?
They can support the timeline, but custody usually also depends on contractual/operational handover records.
What should an exception file contain?
Event trail, corroborating records, identified gap, owner and resolution evidence.
Official sources
- Press Information Bureau / Ministry of Commerce & Industry - Logistics Data Bank Tracks 10 Crore EXIM Containers, Provides Visibility across Logistics Chain (PIB PRID 2299348; 2026-08-14)
- NICDC Logistics Data Services Limited - Logistics Data Bank 2.0 portal, coverage and analytics (Current portal; current)
- NICDC Logistics Data Services Limited - LDB 2.0 Portal User Guide (LDB2.0 Manual; 2025-11)
Disclaimer
Educational and professional reference only; confirm the current law, rates and the facts of your case before relying on this page.