X12 163 — Transportation Appointment Schedule Information
Communication of loading/unloading appointment windows between carrier and facility. Dock-scheduling efficiency pivot.
Purpose
The 163 coordinates transport appointments between a carrier and a site (warehouse, retail DC, manufacturer plant). Several cases: appointment request, confirmation, modification, cancellation. Avoids detention/demurrage by synchronising arrivals with dock-handling capacity. Used massively by Walmart, Target, Amazon, and their suppliers.
Envelope structure
The 163 travels inside the three X12 envelope levels (ISA/IEA,
GS/GE with functional group TI, and ST/SE).
Didactic example in 004010:
ISA*00* *00* *ZZ*CARRIER01 *ZZ*RETAILDC *260516*2030*U*00401*000000163*0*P*>~
GS*TI*CARRIER01*RETAILDC*20260516*2030*1*X*004010~
ST*163*0001~
B6*RQ*APPT-001*20260516~
N1*CA*ACME TRUCKING*92*ACMETRK~
N1*ST*RETAIL DC DALLAS*92*RDCDAL~
BX*00*S*PP*PO-2026-001*XYZ*L*A~
DTM*002*20260520~
DTM*003*0900~
REF*PO*PO-2026-001~
SE*8*0001~
GE*1*1~
IEA*1*000000163~ Common segments
- Header —
ST,B6Beginning of Appointment Schedule. - Carrier —
N1*CA. - Facility —
N1*SForN1*ST. - Appointment detail —
BX,DTM*002appt date,DTM*003appt time. - Reference —
REF*POlinked PO. - Summary —
SE.
Common pitfalls
- Window too wide: "between 0900 and 1700" saturates the dock. Specify a 30-60 min slot.
- No referenced PO: the site does not know what to expect when the truck arrives.
- Modification without prior cancellation: two active appointments for the same truck saturate the calendar.
Related transactions
Documentation
The 163 code and the Transportation Appointment Schedule Information name are public and listed at x12.org/products/transaction-sets. The full loops/qualifiers/code-lists structure is distributed by DISA via proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.