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 300 Reservation (Booking Request) (Ocean)

The X12 document a shipper or freight forwarder sends to an ocean carrier to reserve space, containers and equipment on a vessel.

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

What is an EDI 300?

The EDI 300 Reservation (Booking Request) (Ocean) is the ANSI X12 transaction set a shipper or forwarder uses to reserve space, containers and equipment for transport by ocean vessel. It describes the cargo, the number and type of containers, the ports and dates involved and the parties to the shipment.

The booking is the first step of an ocean shipment. The carrier replies with a 301 confirmation, after which the shipper sends shipping instructions (304) and the carrier later issues the bill of lading (310) and status events (315).

How the EDI 300 worksDiagram of the EDI 300 Reservation (Booking Request) (Ocean). Shipper or freight forwarder sends it to ocean carrier. It usually starts the exchange. It is usually followed by 301 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B1 (Beginning Segment for Booking or Pickup/Delivery), Y1 (Space Reservation Request), the required N1 loop with N1 (Party Identification) and the required R4 loop with R4 (Port or Terminal) and detail: the required LX loop with LX (Transaction Set Line Number). 3 optional loops are listed by their first segment.How the EDI 300 worksReservation (Booking Request) (Ocean): who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 300SENDERShipper or freightforwarderRECEIVEROcean carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY301Confirmation (Ocean)997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code ROGS … GETransaction set 300ST … SEHEADINGB1Beginning Segment for Booking or Pickup/DeliveryY1Space Reservation RequestRequired loop N1 · repeats up to 99N1Party IdentificationRequired loop R4 · repeats up to 20R4Port or Terminal+ 1 optional loop, starting with:Y2DETAILRequired loop LX · repeats up to 999LXTransaction Set Line Number+ 2 optional loops, starting with:H1LH1Blue 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 300. Your trading partner's implementation guide adds its own requirements.
How the EDI 300 worksDiagram of the EDI 300 Reservation (Booking Request) (Ocean). Shipper or freight forwarder sends it to ocean carrier. It usually starts the exchange. It is usually followed by 301 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B1 (Beginning Segment for Booking or Pickup/Delivery), Y1 (Space Reservation Request), the required N1 loop with N1 (Party Identification) and the required R4 loop with R4 (Port or Terminal) and detail: the required LX loop with LX (Transaction Set Line Number). 3 optional loops are listed by their first segment.How the EDI 300 worksReservation (Booking Request) (Ocean): whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 300SENDERShipper orfreightforwarderRECEIVEROcean carrier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY301Confirmation (Ocean)997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RO (GS … GE)Transaction set 300 (ST … SE)HEADINGB1Beginning Segment for Bookingor Pickup/DeliveryY1Space Reservation RequestRequired loop N1 · repeats up to99N1Party IdentificationRequired loop R4 · repeats up to20R4Port or Terminal+ 1 optional loop, starting with:Y2DETAILRequired loop LX · repeats up to999LXTransaction Set LineNumber+ 2 optional loops, starting with:H1LH1Blue 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 300. Your trading partner'simplementation guide adds its own requirements.

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

  • Booking container space on an ocean vessel
  • Requesting specific equipment, such as reefer containers
  • Booking recurring export shipments from a plant or DC

Where it fits in the document flow

This document 300 Reservation (Booking Request) (Ocean)
Usually followed by 301 Confirmation (Ocean)997 Functional Acknowledgment

Structure

Mandatory segments in the 300 (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
  • B1
  • Y1
  • Y2
  • N1
  • R4
  • LX
  • H1
  • LH1
  • SE

Practical example

The 300 in practice

A furniture exporter needs to ship four 40-foot containers from Savannah to Rotterdam next month. Its freight forwarder sends the ocean carrier a 300 booking request with the cargo description, container type and count, ports and preferred sailing. The carrier confirms space and equipment with a 301, and the exporter schedules container pickups for loading.

Implementation

Implementation considerations for the 300

  • Book early in peak seasons, and track each booking until it is confirmed by a 301.
  • Use container type codes and port identifiers the carrier recognizes.
  • Keep the booking number, because instructions, bills of lading and status events reference it.

How ECOM helps

Automate the 300 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 300?

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

Request a Demo Contact us