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 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.
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
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.
Trading partners
Integration guides that include the 300
How ECOM helps
Automate the 300 with ECOM
Industry
Transportation and Logistics
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.
Solution
Ocean Freight EDI and API Integration
Ocean carrier, terminal and customs integration for booking, shipping instructions, VGM, container tracking and freight invoices.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related transportation documents
- 301Confirmation (Ocean)
- 303Booking Cancellation (Ocean)
- 313Shipment Status Inquiry (Ocean)
- 323Vessel Schedule and Itinerary (Ocean)
- 361Carrier Interchange Agreement (Ocean)
- 304Shipping Instructions
- 310Freight Receipt and Invoice (Ocean)
- 215Motor Carrier Pickup Manifest
- 219Logistics Service Request
- 220Logistics Service Response
- 222Cartage Work Assignment
- 225Response to a Cartage Work Assignment
From the guide to go-live
Put this into practice with ECOM
Reading about EDI is the first step. When you are ready to meet a trading partner's requirements, an ECOM specialist can help.
-
EDI compliance help
Check documents against the partner's rules before they are sent, and find out why labels, ship notices or invoices are rejected or short-paid for EDI 300.
-
EDI implementation
Map, test and certify the documents for EDI 300, and connect them to your ERP, warehouse or order system.
-
Managed EDI
Have ECOM run the day-to-day EDI: monitoring, error handling and new trading partner setup.
Need help with the EDI 300?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.




























