Use the Bill of Lading when you need one shipment timeline across multiple containers or legs. Use a container number when you need unit-level gate and handling events. Use a booking number early, before the BL issues. Use a vessel or voyage only for schedule lookups and disruption scanning, not for shipment status.


Decision Tree

  • You need one view for all boxes on the same shipment → Use BL.
  • You are investigating a single box’s delay, gate move, or hold → Use container.
  • You are pre-carriage and the BL is not issued yet → Use booking, then switch to BL once available.
  • You are checking whether a service is late or re-routed → Use vessel or voyage for schedule context, then return to BL or container for status.

What Each Key Actually Shows

  • BL: shipment-level milestones and a unified timeline when containers split or transship.
  • Container: box-level gate in or out, load, discharge, yard moves, and inspections.
  • Booking: planned data and early activity. Coverage is limited after handover.
  • Vessel or voyage: schedule, ETA shifts, and general service updates. Not a shipment key.

Common Scenarios and the Right Key

  • Multiple containers under one contract split across two vessels → Start with BL for a single source of truth. Open container views only for exceptions.
  • Buyer requests one link for all boxes on a PO → Share the BL view.
  • Export gate cut confusion for a specific box → Container view first, then confirm the BL timeline.
  • Suspected service delay across many shipments → Check vessel or voyage for the service, then return to each shipment’s BL.

Troubleshooting

  • No record found: verify you are using the correct key. Remove spaces and copy from the original document or portal.
  • Recent issuance: allow short propagation time, then retry with the BL.
  • Transshipment blind spots: some partner legs appear later. Keep the BL as your anchor and check container detail only to validate a suspected roll or hold.

Connects To TRADLINX

TRADLINX standardizes shipment events across carriers at BL level, so operations, finance, and customers see one shared timeline. Pricing is at BL level, not per container, which keeps cost predictable when shipments include many boxes.


Last verified: 2025-11-06 • Volatility: Low

Leave a Reply

Trending

Discover more from Tradlinx Blogs

Subscribe now to keep reading and get access to the full archive.

Continue reading