DCSA Track & Trace is the Digital Container Shipping Association standard that normalises carrier shipment events into one shape: transport events and equipment events, locations identified by UN/LOCODE, and every event classified as planned, estimated, or actual, so tracking reads the same across carriers.
Before the standard, each line published events in its own vocabulary and structure, and integrating five carriers meant five dialects. DCSA, founded by the major container lines in 2019, published Track & Trace interface standards so an API consumer sees one model: consistent event types, consistent location coding, consistent time classifiers.
The classifier triple is the quietly powerful part: an estimated arrival and an actual arrival are different assertions, and the standard forces that honesty into the data. Adoption varies by carrier and endpoint, so real-world integrations still blend standard and legacy feeds.
TrackingMCP aligns its event model to DCSA semantics: events carry UN/LOCODE locations and planned-estimated-actual classifiers, and carrier dialects are mapped into that shape in tracking. The alignment is documented on the DCSA trust page, and the same normalised stream feeds the API and MCP tools.
DCSA Track & Trace is the Digital Container Shipping Association standard that normalises carrier shipment events into one shape: transport events and equipment events, locations identified by UN/LOCODE, and every event classified as planned, estimated, or actual, so tracking reads the same across carriers.
Member carriers have committed to the standards and expose them in varying degrees; coverage and endpoint quality differ by line. Aggregators bridge the gaps by normalising non-standard feeds into the same model.
Transport events describe the means of transport, a vessel arriving or departing; equipment events describe the container itself, loaded, discharged, gated in or out. A shipment’s story interleaves both.
How TrackingMCP aligns to DCSA →
Container tracking API & MCP →
More in Tracking data & standards: EDI 315 status message · Browse all 106 terms →