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 324 Vessel Stow Plan (Ocean)

The X12 document that carries information on where equipment and cargo are stowed on a vessel.

Sent by
Ocean carrier, vessel operator or terminal
Received by
Terminal operator, carrier or vessel planner
Standard
ANSI ASC X12
EDIFACT equivalent
BAPLIE

What is an EDI 324?

The EDI 324 Vessel Stow Plan (Ocean) is the ANSI X12 transaction set that provides information on the stowage of equipment and cargo on a vessel. It identifies each container or cargo unit and its position on board, along with the details needed for handling, such as weight and hazardous cargo.

Terminals use the stow plan to plan discharge and loading at the next port, and vessel planners use it to check stability and segregation. Internationally, the EDIFACT BAPLIE message is more common for this purpose.

How the EDI 324 worksDiagram of the EDI 324 Vessel Stow Plan (Ocean). Ocean carrier, vessel operator or terminal sends it to terminal operator, carrier or vessel planner. 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: V1 (Vessel Identification), the required R4 loop with R4 (Port or Terminal) and the required N7 loop with N7 (Equipment Details) and V4 (Cargo Location Reference). 0 optional loops are listed by their first segment.How the EDI 324 worksVessel Stow Plan (Ocean): who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 324SENDEROcean carrier, vesseloperator or terminalRECEIVERTerminal operator,carrier or vesselplanner997 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 324ST … SEHEADINGV1Vessel IdentificationRequired loop R4 · repeats up to 20R4Port or TerminalRequired loop N7 · repeats up to 9,999N7Equipment DetailsV4Cargo Location ReferenceBlue 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 324. Your trading partner's implementation guide adds its own requirements.
How the EDI 324 worksDiagram of the EDI 324 Vessel Stow Plan (Ocean). Ocean carrier, vessel operator or terminal sends it to terminal operator, carrier or vessel planner. 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: V1 (Vessel Identification), the required R4 loop with R4 (Port or Terminal) and the required N7 loop with N7 (Equipment Details) and V4 (Cargo Location Reference). 0 optional loops are listed by their first segment.How the EDI 324 worksVessel Stow Plan (Ocean): who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 324SENDEROcean carrier,vessel operatoror terminalRECEIVERTerminaloperator, carrieror vesselplanner997 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 324 (ST … SE)HEADINGV1Vessel IdentificationRequired loop R4 · repeats up to20R4Port or TerminalRequired loop N7 · repeats up to9,999N7Equipment DetailsV4Cargo Location ReferenceBlue 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 324. Your trading partner'simplementation guide adds its own requirements.

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

  • Sending the stow plan to the next port of call
  • Planning discharge and loading operations
  • Sharing positions of hazardous or reefer containers

Where it fits in the document flow

This document 324 Vessel Stow Plan (Ocean)
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 324 (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
  • V1
  • R4
  • N7
  • V4
  • SE

Practical example

The 324 in practice

After loading in Savannah, a vessel operator sends the terminal at the next port a 324 listing every container on board with its stowage position, weight, port of discharge and any hazardous cargo or reefer settings. The terminal's planners build the discharge sequence before the vessel arrives.

Implementation

Implementation considerations for the 324

  • Confirm whether partners expect the X12 324 or the EDIFACT BAPLIE.
  • Validate container numbers and weights, which affect vessel safety.
  • Send the plan in time for the next port to prepare operations.
  • Include hazardous cargo details required for segregation.

How ECOM helps

Automate the 324 with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

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

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

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

Request a Demo Contact us