The logistics and transportation industry processes some of the highest volumes of EDI transactions of any sector. Every shipment that moves by truck, rail, ocean, or air generates a chain of electronic documents between shippers, carriers, freight forwarders, customs brokers, and consignees. EDI provides the standardized language that allows these diverse parties to communicate shipment details, tracking updates, and financial settlements without manual intervention.
Transportation EDI uses both ANSI X12 (dominant in North America) and UN/EDIFACT (dominant internationally). The X12 transportation transaction sets fall in the 100-299 range, while EDIFACT provides messages like IFTMIN (transport instruction), IFTSTA (transport status), and CUSCAR (customs cargo report). International shipping also relies on EDIFACT for customs declarations through messages defined by the World Customs Organization.
Key EDI Documents in Transportation
Bill of Lading (EDIFACT IFTMBC / X12 211)
The bill of lading is the foundational document in freight transportation. It serves simultaneously as a receipt of goods, a contract of carriage, and in ocean shipping, a document of title. The electronic bill of lading transmitted via EDI contains shipper and consignee information, commodity descriptions, weight and dimensions, routing instructions, and freight classification codes. Motor carriers use the X12 211 to receive load tenders from shippers.
Shipment Status (EDIFACT IFTSTA / X12 214)
Real-time shipment tracking depends on EDI status messages. Carriers transmit 214 transactions at each milestone: pickup, departure from origin terminal, arrival at intermediate stops, customs clearance, and final delivery. Each status update includes date, time, location, and event codes. Shippers and 3PLs aggregate these updates to provide end-to-end visibility dashboards for their customers.
Freight Invoice (EDIFACT INVOIC / X12 210)
After delivery, carriers submit electronic freight invoices detailing accessorial charges, fuel surcharges, linehaul rates, and applicable tariff references. The X12 210 freight invoice enables automated three-way matching against the original tender and proof of delivery, significantly reducing the invoice dispute cycle that plagues manual freight payment processes.
Customs Declarations (EDIFACT CUSDEC / CUSCAR)
International trade requires electronic customs declarations to be submitted before goods cross borders. The EDIFACT CUSDEC message carries import and export declaration data including Harmonized System commodity codes, country of origin, declared values, and applicable trade preference programs. Many customs authorities now require advance electronic filing, such as the EU's Import Control System (ICS2) and the US Customs and Border Protection's Automated Commercial Environment (ACE).
Ocean, Air, and Rail EDI
Each transport mode has its own EDI conventions. Ocean carriers use EDIFACT messages like BAPLIE (bayplan) to communicate container stowage positions and COPARN for container release orders. Airlines exchange cargo data through IATA Cargo-IMP messages and the newer Cargo-XML standard. Railroads in North America use the X12 404 (rail waybill) and 418 (rail advance interchange) transactions, coordinated through Railinc, the industry's shared data network.
Third-Party Logistics and EDI
Third-party logistics providers (3PLs) are among the most EDI-intensive organizations, often maintaining hundreds of trading partner connections. A 3PL must receive orders from clients, transmit pickup instructions to carriers, relay tracking updates back to clients, and reconcile invoices from multiple carriers. The X12 940 (warehouse shipping order) and 945 (warehouse shipping advice) transactions are central to 3PL warehouse operations, while the 990 (response to load tender) enables automated carrier selection and dispatch.
Related Resources
Transportation EDI connects closely with Retail and Manufacturing supply chains. For information on secure transmission methods used in logistics, see our guides on Value Added Networks and AS2 Protocol. Visit our Mapping & Translation page to understand how logistics companies handle the complexity of multiple EDI formats across trading partners.