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 352 Customs Carrier General Order Status

The X12 document carriers and terminals use to tell customs or consignees the status of cargo in, or about to go into, general order.

Sent by
Carrier, terminal operator, port authority or service center
Received by
Customs authority or consignee
Standard
ANSI ASC X12

What is an EDI 352?

The EDI 352 Customs Carrier General Order Status is the ANSI X12 transaction set carriers, terminal operators, port authorities and service centers use to give customs or consignees bill of lading status information for cargo in, or about to go into, general order, along with entry and release information.

In the United States, imported cargo that is not entered within the time allowed is sent to a general order warehouse, where storage costs accrue and the goods can eventually be sold. Reporting general order status helps consignees act before that happens.

How the EDI 352 worksDiagram of the EDI 352 Customs Carrier General Order Status. Carrier, terminal operator, port authority or service center sends it to customs authority 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: M10 (Manifest Identifying Information) and the required P4 loop with P4 (Port Information) and the required M14 loop with M14 (General Order Status Information). 0 optional loops are listed by their first segment.How the EDI 352 worksCustoms Carrier General Order Status: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 352SENDERCarrier, terminaloperator, port authorityor service centerRECEIVERCustoms authority orconsignee997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AVGS … GETransaction set 352ST … SEHEADINGM10Manifest Identifying InformationRequired loop P4 · repeats up to 20P4Port InformationRequired loop M14 · repeats up to 9,999M14General Order Status InformationBlue 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 352. Your trading partner's implementation guide adds its own requirements.
How the EDI 352 worksDiagram of the EDI 352 Customs Carrier General Order Status. Carrier, terminal operator, port authority or service center sends it to customs authority 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: M10 (Manifest Identifying Information) and the required P4 loop with P4 (Port Information) and the required M14 loop with M14 (General Order Status Information). 0 optional loops are listed by their first segment.How the EDI 352 worksCustoms Carrier General Order Status: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 352SENDERCarrier, terminaloperator, portauthority orservice centerRECEIVERCustomsauthority orconsignee997 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 AV (GS … GE)Transaction set 352 (ST … SE)HEADINGM10Manifest IdentifyingInformationRequired loop P4 · repeats up to20P4Port InformationRequired loop M14 · repeatsup to 9,999M14General Order StatusInformationBlue 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 352. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting cargo approaching general order status
  • Reporting cargo moved to a general order warehouse
  • Updating entry and release information for such cargo

Where it fits in the document flow

This document 352 Customs Carrier General Order Status
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 352 (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
  • M10
  • P4
  • M14
  • SE

Practical example

The 352 in practice

A container has sat unentered at a port terminal for almost the allowed period. The carrier sends a 352 reporting the bill of lading as approaching general order, and the consignee's broker files the entry the same day. For another container that passes the deadline, a second 352 reports its move to a general order warehouse.

Implementation

Implementation considerations for the 352

  • Alert consignees and brokers early, before the general order deadline.
  • Keep bill of lading references consistent with the manifest (309).
  • Track storage costs and responsibilities once cargo is in general order.
  • Follow the customs authority's implementation guide.

How ECOM helps

Automate the 352 with ECOM

Industry

Trucking and Transportation

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

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

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

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

Request a Demo Contact us