ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 213 — Motor Carrier Shipment Status Inquiry

The 213 is the inquiry sent to a motor carrier to know the status of one or more shipments. It calls for a 214 in response.

Purpose

The 213 asks where a shipment stands: approximate GPS location, last event (pickup, in transit, DC arrival…), updated ETA. It is a batch channel: for real-time use a modern tracking API is preferred. In mature EDI flows many shipper / carrier pairs do without it, because the carrier pushes a 214 on every significant event anyway.

Envelope structure

The 213 travels in a functional group IB (Inquiry Bill). Didactic example in release 004010 on a PRO-Number inquiry:

x12 example-213.x12 
ISA*00*          *00*          *ZZ*ACMESHIPPER   *ZZ*ACMECARRIER   *260514*0930*U*00401*000000213*0*P*>~
GS*IB*ACMESHIPPER*ACMECARRIER*20260514*0930*1*X*004010~
ST*213*0001~
B1*ACMECARRIER*PRO-7781*20260514*I~
N9*BM*BOL-2026-998~
N9*CN*ACME RETAIL DC 5~
SE*5*0001~
GE*1*1~
IEA*1*000000213~

The B1 (Beginning Segment) opens with: queried carrier SCAC, PRO Number, request date, function code (I = Inquiry). The N9 segments refine the BOL Number and consignee, letting the carrier locate the shipment even when the PRO is unknown.

Common segments

  • Header — ST, B1 (Beginning Segment), DTM.
  • Alternate identifiers — repeated N9 loop (BM = BOL, CN = Consignee Number, OO = Order, PR = Price Quote).
  • Parties — optional N1 loop to refine SH / CN.
  • Summary — SE.

Common pitfalls

  • Missing SCAC: without SCAC in B101, the inquiry is rejected: it is the primary identifier.
  • Ambiguous identifier: BOL or PO may not be unique on the carrier side; prefer the carrier PRO Number when known.
  • Request volume: some carriers cap 213s at a few thousand per day; beyond that, switch to an API or to push-based 214s.

Documentation

The code 213 and the name Motor Carrier Shipment Status Inquiry are public and listed on x12.org/products/transaction-sets.