972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 317 Delivery/Pickup Order

The X12 document importers or their agents use to give marine terminal operators orders for the delivery or pickup of goods.

Sent by
Importer, customs broker or forwarder
Received by
Marine terminal operator
Standard
ANSI ASC X12

What is an EDI 317?

The EDI 317 Delivery/Pickup Order is the ANSI X12 transaction set importers or their agents use to give marine terminal operators orders for the delivery or pickup of goods. It tells the terminal which cargo to release, to which trucker or carrier, and when.

The delivery order is one of the release conditions at a terminal, alongside customs clearance and payment of carrier charges. Sending it electronically speeds up container pickup and reduces the risk of release to the wrong party.

How the EDI 317 worksDiagram of the EDI 317 Delivery/Pickup Order. Importer, customs broker or forwarder sends it to marine terminal operator. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required N1 loop with N1 (Party Identification), G62 (Date/Time), N9 (Extended Reference Information), TD5 (Carrier Details (Routing Sequence/Transit Time)) and the required L0 loop with L0 (Line Item - Quantity and Weight). 0 optional loops are listed by their first segment.How the EDI 317 worksDelivery/Pickup Order: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 317SENDERImporter, customsbroker or forwarderRECEIVERMarine terminaloperator997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SOGS … GETransaction set 317ST … SEHEADINGRequired loop N1 · repeats up to 10N1Party IdentificationG62Date/TimeN9Extended Reference InformationTD5Carrier Details (Routing Sequence/Transit Time)Required loop L0 · repeats up to 9,999L0Line Item - Quantity and WeightBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 317. Your trading partner's implementation guide adds its own requirements.
How the EDI 317 worksDiagram of the EDI 317 Delivery/Pickup Order. Importer, customs broker or forwarder sends it to marine terminal operator. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required N1 loop with N1 (Party Identification), G62 (Date/Time), N9 (Extended Reference Information), TD5 (Carrier Details (Routing Sequence/Transit Time)) and the required L0 loop with L0 (Line Item - Quantity and Weight). 0 optional loops are listed by their first segment.How the EDI 317 worksDelivery/Pickup Order: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 317SENDERImporter,customs brokeror forwarderRECEIVERMarine terminaloperator997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SO (GS … GE)Transaction set 317 (ST … SE)HEADINGRequired loop N1 · repeats up to10N1Party IdentificationG62Date/TimeN9Extended ReferenceInformationTD5Carrier Details (RoutingSequence/Transit Time)Required loop L0 · repeats up to9,999L0Line Item - Quantity andWeightBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 317. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 317, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 317 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Authorizing a trucker to pick up an import container
  • Ordering delivery of cargo from a terminal
  • Updating pickup arrangements at a terminal

Where it fits in the document flow

This document 317 Delivery/Pickup Order
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 317 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • N1
  • G62
  • N9
  • TD5
  • L0
  • SE

Practical example

The 317 in practice

After customs releases an import shipment, the importer's broker sends the terminal a 317 naming the trucking company that will collect two containers, with the bill of lading and container numbers and the planned pickup date. The terminal's gate system matches the trucker on arrival and releases the containers.

Implementation

Implementation considerations for the 317

  • Identify the authorized trucker exactly, to avoid gate rejections.
  • Send the order before the trucker arrives at the terminal.
  • Check customs and carrier holds, which can still block release.
  • Track free time, as delayed pickup leads to storage charges.

How ECOM helps

Automate the 317 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 317?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us