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 304 Shipping Instructions

The X12 document a shipper or forwarder sends to an ocean carrier with the information needed to prepare the bill of lading or sea waybill.

Sent by
Shipper or freight forwarder
Received by
Ocean carrier
Standard
ANSI ASC X12
EDIFACT equivalent
IFTMIN

What is an EDI 304?

The EDI 304 Shipping Instructions is the ANSI X12 transaction set that gives an ocean carrier all the information needed to prepare and distribute a contract of carriage, such as an ocean bill of lading or sea waybill. It covers the parties, the cargo and container details, references and how the documents should be issued.

Shipping instructions must be accurate and on time: they become the bill of lading, which customs authorities, banks and consignees rely on. Corrections after the bill of lading is issued can delay cargo and incur fees.

How the EDI 304 worksDiagram of the EDI 304 Shipping Instructions. Shipper or freight forwarder sends it to ocean carrier. It usually follows 301. It is usually followed by 310 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B2 (Beginning Segment for Shipment Information Transaction). 6 optional loops are listed by their first segment.How the EDI 304 worksShipping Instructions: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS301Confirmation (Ocean)EDI 304SENDERShipper or freightforwarderRECEIVEROcean carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY310Freight Receipt andInvoice (Ocean)997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SOGS … GETransaction set 304ST … SEHEADINGB2Beginning Segment forShipment InformationTransaction+ 4 optional loops, starting with:M1N1R4C8DETAIL+ 1 optional loop, starting with:LXSUMMARY+ 1 optional loop, starting with:L3Blue 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 304. Your trading partner's implementation guide adds its own requirements.
How the EDI 304 worksDiagram of the EDI 304 Shipping Instructions. Shipper or freight forwarder sends it to ocean carrier. It usually follows 301. It is usually followed by 310 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B2 (Beginning Segment for Shipment Information Transaction). 6 optional loops are listed by their first segment.How the EDI 304 worksShipping Instructions: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS301Confirmation (Ocean)EDI 304SENDERShipper orfreightforwarderRECEIVEROcean carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY310Freight Receipt and Invoice (Ocean)997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SO (GS … GE)Transaction set 304 (ST … SE)HEADINGB2Beginning Segment forShipment InformationTransaction+ 4 optional loops, starting with:M1N1R4C8DETAIL+ 1 optional loop, starting with:LXSUMMARY+ 1 optional loop, starting with:L3Blue 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 304. Your trading partner'simplementation guide adds its own requirements.

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

  • Giving a carrier the data for the bill of lading
  • Providing container, seal and cargo details after loading
  • Specifying consignee and notify parties

Where it fits in the document flow

Usually follows 301 Confirmation (Ocean)
This document 304 Shipping Instructions
Usually followed by 310 Freight Receipt and Invoice (Ocean)997 Functional Acknowledgment

Structure

Mandatory segments in the 304 (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
  • B2
  • M1
  • N1
  • R4
  • C8
  • LX
  • N7
  • L1
  • H1
  • LH1
  • PO4
  • L0
  • PAL
  • CTP
  • SAC
  • L9
  • L3
  • TDS
  • SE

Practical example

The 304 in practice

Once its four containers are loaded and sealed, the exporter's forwarder sends the carrier a 304 with each container and seal number, the cargo description, weights, the shipper, consignee and notify parties. The carrier prepares the bill of lading from it and sends a 310 for the forwarder to check before the original is released.

Implementation

Implementation considerations for the 304

  • Submit instructions before the carrier's documentation cut-off.
  • Validate container numbers, seals and weights against loading records.
  • Review the draft bill of lading (310) against the instructions before it is finalized.

How ECOM helps

Automate the 304 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

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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

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

Request a Demo Contact us