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 313 Shipment Status Inquiry (Ocean)

The X12 document an authorized party uses to ask an ocean carrier for the status of a shipment.

Sent by
Shipper, consignee, forwarder or broker
Received by
Ocean carrier
Standard
ANSI ASC X12

What is an EDI 313?

The EDI 313 Shipment Status Inquiry (Ocean) is the ANSI X12 transaction set that provides the information an authorized party to an ocean shipment needs to ask the ocean carrier about the status of a shipment. It identifies the shipment by bill of lading, booking or container number.

The carrier answers with a 315 status details message. Many parties now subscribe to 315 events instead of asking, but the 313 remains useful for on-demand checks on specific containers. It is a simple request with few segments.

How the EDI 313 worksDiagram of the EDI 313 Shipment Status Inquiry (Ocean). Shipper, consignee, forwarder or broker sends it to ocean carrier. It usually starts the exchange. It is usually followed by 315 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B4 (Beginning Segment for Inquiry or Reply). 0 optional loops are listed by their first segment.How the EDI 313 worksShipment Status Inquiry (Ocean): who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 313SENDERShipper, consignee,forwarder or brokerRECEIVEROcean carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY315Status Details (Ocean)997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code QOGS … GETransaction set 313ST … SEHEADINGB4Beginning Segment for Inquiry or ReplyBlue 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 313. Your trading partner's implementation guide adds its own requirements.
How the EDI 313 worksDiagram of the EDI 313 Shipment Status Inquiry (Ocean). Shipper, consignee, forwarder or broker sends it to ocean carrier. It usually starts the exchange. It is usually followed by 315 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B4 (Beginning Segment for Inquiry or Reply). 0 optional loops are listed by their first segment.How the EDI 313 worksShipment Status Inquiry (Ocean): who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 313SENDERShipper,consignee,forwarder orbrokerRECEIVEROcean carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY315Status Details (Ocean)997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code QO (GS … GE)Transaction set 313 (ST … SE)HEADINGB4Beginning Segment for Inquiryor ReplyBlue 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 313. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 313, 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 313 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

  • Asking for the current status of a container
  • Checking a shipment when expected events are missing
  • Requesting status for specific bills of lading

Where it fits in the document flow

This document 313 Shipment Status Inquiry (Ocean)
Usually followed by 315 Status Details (Ocean)997 Functional Acknowledgment

Structure

Mandatory segments in the 313 (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
  • B4
  • SE

Practical example

The 313 in practice

A consignee notices that no discharge event has arrived for a container whose vessel docked two days ago. Its visibility system sends the carrier a 313 for that container number. The carrier replies with a 315 showing the container was discharged and is on hold for a customs exam, and the consignee alerts its broker.

Implementation

Implementation considerations for the 313

  • Identify shipments by the references the carrier indexes, such as container or bill of lading numbers.
  • Use inquiries for exceptions rather than polling every shipment.
  • Prefer event subscriptions (315) for routine tracking.
  • Confirm which parties the carrier authorizes to inquire.

How ECOM helps

Automate the 313 with ECOM

Industry

Trucking and Transportation

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

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Industry

3PL and Warehousing

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

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 313?

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

Request a Demo Contact us