X12 317 — Delivery / Pickup Order
The 317 transmits a delivery or pickup order between a freight forwarder, carrier, and terminal to authorize the movement of cargo.
Purpose
The 317 documents a structured instruction to authorize the pickup or delivery of a container, parcel, or lot: authorized carrier, source terminal, destination terminal, time window, special instructions.
It is used between freight forwarders and carriers to formalize authorization; it also serves as a manifest for the terminal that verifies the carrier identity at gate. Acknowledged by 997. Followed by a 214 (Status) once executed.
Envelope structure
The 317 travels within the three X12 envelope levels (ISA/IEA,
GS/GE with functional group DP, and ST/SE).
Didactic example in release 004010:
ISA*00* *00* *ZZ*FORWARDER *ZZ*TERMINALCO *260514*1500*U*00401*000000317*0*P*>~
GS*DP*FORWARDER*TERMINALCO*20260514*1500*1*X*004010~
ST*317*0001~
B1*FORWARDER*DP-2026-0042*20260514*A~
N1*SH*ACME FORWARDER*92*FWD-001~
N1*CA*DRAYAGE COMPANY*92*SCAC-DCMP~
N1*TR*TERMINAL OPERATOR*92*USLAX-PIER-100~
N7*MSCU*4501230*22G1~
N9*BM*BL-2026-LAX-0098~
DTM*002*20260521~
SE*10*0001~
GE*1*1~
IEA*1*000000317~ Common segments
- Header —
ST,B1(action A=Add). - Parties —
N1*SH(Forwarder),N1*CA(authorized Carrier),N1*TR(Terminal). - Container —
N7(Equipment),N9*BM(BL reference). - Timing —
DTM*002(planned date),DTM*077(cut-off). - Summary —
SE.
Common pitfalls
- Carrier authorization: the terminal validates the carrier at gate using
N1*CASCAC; an unlisted carrier is refused even if the cargo is physically present. - Window vs cut-off: a 317 must indicate the pickup window; arriving out of window triggers an appointment rebook and potentially a dry-run charge.
- Single use: a 317 for a container can only be executed once; a second pickup attempt on the same 317 must be cancelled first, otherwise the terminal refuses.
Related transactions
Documentation
The code 317 and the name Delivery / Pickup Order are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.