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 325 Consolidation of Goods In Container

The X12 document a consolidator sends to the deconsolidator or consignee describing the goods loaded into a container.

Sent by
Consolidator
Received by
Deconsolidator or consignee
Standard
ANSI ASC X12

What is an EDI 325?

The EDI 325 Consolidation of Goods in Container is the ANSI X12 transaction set that provides information on the goods loaded into a container. A consolidator sends it to the deconsolidator or the consignee at destination.

Consolidators combine cargo from several shippers into one container, under a master bill of lading with separate house bills for each shipper. The 325 tells the destination party what is in the container and for whom, so it can plan devanning, customs clearance and onward delivery for each shipment.

How the EDI 325 worksDiagram of the EDI 325 Consolidation of Goods In Container. Consolidator sends it to deconsolidator or consignee. 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: B12 (Beginning Segment for Consolidation of Goods In Container), V1 (Vessel Identification) and R4 (Port or Terminal) and detail: the required MBL loop with MBL (Bill of Lading) and the required LIN loop with LIN (Item Identification), SN1 (Item Detail (Shipment)) and TD1 (Carrier Details (Quantity and Weight)). 2 optional loops are listed by their first segment.How the EDI 325 worksConsolidation of Goods In Container: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 325SENDERConsolidatorRECEIVERDeconsolidator orconsignee997 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 325ST … SEHEADINGB12Beginning Segment for Consolidation of Goods InContainerV1Vessel IdentificationR4Port or TerminalDETAILRequired loop MBL · repeats up to 999MBLBill of LadingRequired loop LIN · repeats up to 999LINItem IdentificationSN1Item Detail (Shipment)TD1Carrier Details (Quantity and Weight)+ 2 optional loops, starting with:N1H1Blue 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 325. Your trading partner's implementation guide adds its own requirements.
How the EDI 325 worksDiagram of the EDI 325 Consolidation of Goods In Container. Consolidator sends it to deconsolidator or consignee. 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: B12 (Beginning Segment for Consolidation of Goods In Container), V1 (Vessel Identification) and R4 (Port or Terminal) and detail: the required MBL loop with MBL (Bill of Lading) and the required LIN loop with LIN (Item Identification), SN1 (Item Detail (Shipment)) and TD1 (Carrier Details (Quantity and Weight)). 2 optional loops are listed by their first segment.How the EDI 325 worksConsolidation of Goods In Container: who sendsit, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 325SENDERConsolidatorRECEIVERDeconsolidatoror consignee997 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 325 (ST … SE)HEADINGB12Beginning Segment forConsolidation of Goods InContainerV1Vessel IdentificationR4Port or TerminalDETAILRequired loop MBL · repeats upto 999MBLBill of LadingRequired loop LIN · repeatsup to 999LINItem IdentificationSN1Item Detail (Shipment)TD1Carrier Details(Quantity and Weight)+ 2 optional loops, starting with:N1H1Blue 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 325. Your trading partner'simplementation guide adds its own requirements.

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

  • Describing the contents of a consolidated container
  • Preparing devanning and distribution at destination
  • Supporting customs clearance of consolidated cargo

Where it fits in the document flow

This document 325 Consolidation of Goods In Container
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 325 (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
  • B12
  • V1
  • R4
  • MBL
  • N1
  • LIN
  • SN1
  • TD1
  • H1
  • SE

Practical example

The 325 in practice

A consolidator in Shenzhen loads cargo for 12 importers into one 40-foot container. It sends its agent in Chicago a 325 with the container and master bill of lading, each house bill, the importer, the goods, piece counts and weights. The agent plans the devanning at its warehouse and prepares delivery orders for each importer.

Implementation

Implementation considerations for the 325

  • Link each house bill to the master bill and the container.
  • Send the data before the container arrives, to plan devanning and customs work.
  • Use consistent piece counts and weights with the house bills of lading.
  • Agree with the deconsolidator on references for each importer's shipment.

How ECOM helps

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

Logistics Automation

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

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

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

Request a Demo Contact us