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 350 Customs Status Information

The X12 document customs uses to give carriers, terminals and service providers cargo release and hold information for shipments.

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

What is an EDI 350?

The EDI 350 Customs Status Information is the ANSI X12 transaction set the customs service uses to supply carriers, terminal operators, port authorities and service providers with cargo release and hold information for import shipments. It can also give exporters, their agents and carriers information about export shipments.

Terminals will not release a container that customs is holding, so the status in the 350 directly controls whether cargo can be picked up. Carriers and terminals pass the status on to consignees and truckers, who need it to plan pickups.

How the EDI 350 worksDiagram of the EDI 350 Customs Status Information. Customs authority sends it to carrier, terminal operator, port authority or service provider. It usually follows 309. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the . 2 optional loops are listed by their first segment.How the EDI 350 worksCustoms Status Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS309Customs ManifestEDI 350SENDERCustoms authorityRECEIVERCarrier, terminaloperator, port authorityor service provider997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AUGS … GETransaction set 350ST … SEHEADING+ 2 optional loops, starting with:P4BA1Blue 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 350. Your trading partner's implementation guide adds its own requirements.
How the EDI 350 worksDiagram of the EDI 350 Customs Status Information. Customs authority sends it to carrier, terminal operator, port authority or service provider. It usually follows 309. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the . 2 optional loops are listed by their first segment.How the EDI 350 worksCustoms Status Information: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS309Customs ManifestEDI 350SENDERCustomsauthorityRECEIVERCarrier, terminaloperator, portauthority orservice provider997 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 AU (GS … GE)Transaction set 350 (ST … SE)HEADING+ 2 optional loops, starting with:P4BA1Blue 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 350. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 350, 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 350 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 customs release of import cargo
  • Reporting holds, such as exam holds, on a shipment
  • Updating export shipment status

Where it fits in the document flow

Usually follows 309 Customs Manifest
This document 350 Customs Status Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 350 (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
  • P4
  • VID
  • X4
  • BA1
  • SE

Practical example

The 350 in practice

Customs reviews the manifest and the importer's entry for a container. It sends the carrier and the terminal a 350 placing the container on hold for an exam, and later another 350 releasing it. The terminal's gate system blocks pickup while the hold is active and allows it once the release arrives.

Implementation

Implementation considerations for the 350

  • Feed holds and releases straight into terminal and dispatch systems.
  • Match status messages to bills of lading and containers exactly.
  • Pass status on to consignees and brokers, who need to act on holds.
  • Follow the customs authority's implementation guide for status codes.

How ECOM helps

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

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

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

Request a Demo Contact us