ANSI X12 transaction set 211
Connect EDI 211 bill of lading with your ERP, TMS, WMS or finance workflow.
Tirnav helps teams implement EDI 211 with validated maps, system integration and exception monitoring. Map shipment records into the agreed bill-of-lading format and send the validated EDI 211 to the carrier.
Message overview
EDI 211 communicates a motor carrier bill of lading from the shipper or contracting party to the carrier.
Typical message flow
Related carrier messages
Implementation workflow
Confirm EDI 211 availability, the implementation guide and required X12 version with the partner.
Agree connectivity, identifiers, sample files and destination-system mappings.
Map shipment records into the agreed bill-of-lading format and send the validated EDI 211 to the carrier.
Validate required fields and partner business rules before processing.
Test duplicates, rejected messages and acknowledgement handling.
Launch with monitoring, exception routing and controlled reprocessing.
X12 reference
Segment requirements vary by trading partner and implementation guide. These are common examples, not a universal requirement list.
| Segment | Business meaning | Implementation notes |
|---|---|---|
| ISA / GS | Control headers | Identify the agreed interchange sender, receiver and functional group. |
| ST / SE | Transaction envelope | Identify transaction set 211 and validate its control reference and segment count. |
| BOL | Bill of lading | Identifies the bill of lading and communicates key shipment and transportation information. |
| N1 / N2 / N3 / N4 | Party and location | Identifies parties and locations such as shipper, consignee, carrier, bill-to and other shipment participants. |
| G62 | Date and time | Communicates pickup, delivery, shipment and other transportation-related dates and times. |
| L11 | Reference information | Carries purchase order, shipment, booking, bill of lading and other reference numbers. |
| S5 | Stop-off details | Identifies shipment stops and communicates stop sequence and related pickup or delivery information. |
| L5 | Commodity information | Identifies commodities being transported and provides descriptions and related shipment details. |
| L0 | Line-item details | Communicates quantities, packaging, weights and units of measure for the shipment. |
| L1 | Freight charges | Provides freight rates, charges, allowances and other transportation billing information when required. |
| L3 | Shipment totals | Provides shipment-level totals such as weight, quantity, volume and freight charges. |
| SE / GE / IEA | Control trailers | Close the transaction, functional group and interchange with control counts and matching references. |
Mapping and operations
Tirnav transforms the partner message into the format required by your ERP, WMS, OMS, 3PL or custom application while applying partner-specific business rules.
Exception handling
Detect rejected, malformed or incomplete messages.
Diagnose source data, mapping or business-rule failures.
Resolve the issue with the right owner and correction.
Reprocess safely while preserving transaction history.
Trading partners
Related transaction sets
EDI 211 is the ANSI X12 Motor Carrier Bill of Lading Transaction Set. It communicates shipment and bill-of-lading information between a shipper or other responsible party and a motor carrier.
An EDI 211 can include bill-of-lading references, shipper and consignee details, pickup and delivery locations, shipment dates, commodity information, quantities, weights and other transportation details required by the carrier.
FedEx Freight supports EDI-based bill-of-lading workflows. The applicable transaction, such as EDI 204 or EDI 211, depends on the specific carrier implementation and business process.
EDI 211 communicates motor carrier bill-of-lading information, while EDI 215 communicates a motor carrier pickup manifest. The appropriate transaction depends on the carrier's implementation requirements and transportation workflow.
Tirnav can map shipment and bill-of-lading data from your ERP, TMS, WMS or 3PL into the required EDI 211 format, validate the transaction and transmit it to the carrier.
Implementation typically requires the carrier's implementation guide, applicable X12 version, sample EDI files, connectivity requirements and destination-system field mappings. Testing validates the complete workflow before production.
Yes. Tirnav can integrate EDI 211 with 3PL systems so shipment and bill-of-lading information can flow automatically between the 3PL, your business systems and the carrier.
Tirnav validates EDI 211 transactions and identifies issues such as missing shipment information, invalid references or mapping errors. Failed transactions can be reviewed, corrected and reprocessed.
Explore our latest thoughts on technology and business.
Learn how automotive EDI helps Indian OEMs and suppliers automate forecasts, purchase orders, ASN, invoices, ERP integration and supplier collaboration.
A practical plan to convert UB-04 claim data into HIPAA-compliant X12 837I, submit to a clearinghouse or payer, and track 999/277CA acknowledgments - with realistic timeline and cost.
Confused about how to start with EDI? We break down the three paths: SaaS Fulfilment Portals (like SPS Commerce Web), Integrated EDI (ERP Automation), and building your own In-House system.
Skip the backlog. Connect directly with our architects to discuss your business goals, technical challenges, and digital transformation roadmap.