X12 transaction guide · Transportation
EDI 211 Motor Carrier Bill of Lading
The X12 document shippers, or the party contracting the carrier, use to give a motor carrier a legal bill of lading for a shipment.
- Sent by
- Shipper or party contracting the carrier
- Received by
- Motor carrier
- Standard
- ANSI ASC X12
- EDIFACT equivalent
- IFTMIN
What is an EDI 211?
The EDI 211 Motor Carrier Bill of Lading is the ANSI X12 transaction set shippers, or other parties responsible for contracting with a motor carrier, use to provide a legal bill of lading for a shipment. It carries the shipment's parties, references, commodities, weights and handling requirements.
The 211 is specifically the bill of lading. The standard notes it is not meant for load tenders, pickup manifests or appointment scheduling, which have their own transaction sets such as the 204 load tender and 215 pickup manifest.
How to read this diagram: the top row shows who sends the 211, 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 211 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.
When it is used
- Sending bills of lading electronically to LTL carriers
- Replacing paper bills of lading at pickup
- Providing commodity and hazardous materials details
Where it fits in the document flow
Structure
Mandatory segments in the 211 (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
- BOL
- B2A
- N1
- AT1
- AT2
- LX
- G61
- LH1
- SE
Practical example
The 211 in practice
A parts supplier ships several LTL orders a day. When each shipment is ready, its shipping system sends the carrier a 211 with the shipper, consignee, piece count, weight, freight class and reference numbers. The driver picks up without re-keying paperwork, and later 214 status messages and the 210 freight invoice reference the same bill of lading number.
Implementation
Implementation considerations for the 211
- Use the bill of lading number consistently, because status messages and freight invoices depend on it.
- Send accurate weights and freight classes to avoid reweigh and reclassification charges.
- Check each carrier's requirements, as not all carriers accept the 211.
How ECOM helps
Automate the 211 with ECOM
Industry
Trucking and Transportation
Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.
Industry
Manufacturing
Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.
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
- 216Motor Carrier Shipment Pickup Notification
- 213Motor Carrier Shipment Status Inquiry
- 106Motor Carrier Rate Proposal
- 108Response to a Motor Carrier Rate Proposal
- 107Request for Motor Carrier Rate Proposal
- 212Motor Carrier Delivery Trailer Manifest
- 215Motor Carrier Pickup Manifest
- 227Trailer Usage Report
- 404Rail Carrier Shipment Information
- 240Motor Carrier Package Status
- 422Equipment Order
- 352Customs Carrier General Order Status
Need help with the EDI 211?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.
