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 212 Motor Carrier Delivery Trailer Manifest

The X12 document a motor carrier uses to tell a consignee the contents of a trailer holding multiple shipments tendered for delivery.

Sent by
Motor carrier
Received by
Consignee or other interested party
Standard
ANSI ASC X12

What is an EDI 212?

The EDI 212 Motor Carrier Delivery Trailer Manifest is the ANSI X12 transaction set motor carriers use to give consignees and other interested parties the contents of a trailer that contains multiple shipments and has been tendered for delivery. It lists each shipment on the trailer with its references, piece counts and weights.

The 212 is for less-than-truckload and consolidated deliveries; it is not used for full truckload shipments. A consignee that receives many LTL shipments a day can use it to plan dock labor and match each shipment to its purchase order before the trailer is unloaded.

How the EDI 212 worksDiagram of the EDI 212 Motor Carrier Delivery Trailer Manifest. Motor carrier sends it to consignee or other interested party. 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: ATA (Beginning Segment for Motor Carrier Delivery Trailer Manifest), B2A (Set Purpose) and the required 0150 loop with AT7 (Shipment Status Details). 3 optional loops are listed by their first segment.How the EDI 212 worksMotor Carrier Delivery Trailer Manifest: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 212SENDERMotor carrierRECEIVERConsignee or otherinterested party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TMGS … GETransaction set 212ST … SEHEADINGATABeginning Segment for Motor Carrier DeliveryTrailer ManifestB2ASet PurposeRequired loop 0150 · repeats up to 1AT7Shipment Status Details+ 2 optional loops, starting with:N1MS2DETAIL+ 1 optional loop, starting with:LXBlue 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 212. Your trading partner's implementation guide adds its own requirements.
How the EDI 212 worksDiagram of the EDI 212 Motor Carrier Delivery Trailer Manifest. Motor carrier sends it to consignee or other interested party. 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: ATA (Beginning Segment for Motor Carrier Delivery Trailer Manifest), B2A (Set Purpose) and the required 0150 loop with AT7 (Shipment Status Details). 3 optional loops are listed by their first segment.How the EDI 212 worksMotor Carrier Delivery Trailer Manifest: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 212SENDERMotor carrierRECEIVERConsignee orother interestedparty997 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 TM (GS … GE)Transaction set 212 (ST … SE)HEADINGATABeginning Segment for MotorCarrier Delivery TrailerManifestB2ASet PurposeRequired loop 0150 · repeats upto 1AT7Shipment Status Details+ 2 optional loops, starting with:N1MS2DETAIL+ 1 optional loop, starting with:LXBlue 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 212. Your trading partner'simplementation guide adds its own requirements.

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

  • Notifying a consignee of the shipments on a delivery trailer
  • Planning receiving for consolidated LTL deliveries
  • Confirming which shipments arrive together

Where it fits in the document flow

This document 212 Motor Carrier Delivery Trailer Manifest
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 212 (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
  • ATA
  • B2A
  • N1
  • AT7
  • MS2
  • LX
  • OID
  • SE

Practical example

The 212 in practice

A university hospital's central warehouse receives a daily LTL trailer from its main carrier. Each morning the carrier sends a 212 listing the 35 shipments on the trailer, with shippers, pro numbers, purchase order references, pieces and weights. The receiving team pre-assigns dock doors and staff and flags urgent items for immediate delivery to wards.

Implementation

Implementation considerations for the 212

  • Use the manifest to pre-receive, but still confirm what is physically delivered.
  • Match pro numbers and purchase order references to expected inbound shipments.
  • Do not use the 212 for full truckload deliveries, which have their own documents.
  • Agree on timing, so the manifest arrives before the trailer.

How ECOM helps

Automate the 212 with ECOM

Industry

Trucking and Transportation

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

Industry

Healthcare

Secure B2B integration and file transfer for providers, suppliers, distributors and healthcare partners.

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

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

Request a Demo Contact us