EDI
EDI (Electronic Data Interchange) is the structured, computer-to-computer exchange of business documents — such as orders, invoices, and shipping notices — in a standardized electronic format.
What is EDI?
In logistics, EDI replaces the fax, the e-mailed spreadsheet and the re-keying that comes with them. A shipper's system sends a transport order straight into the carrier's system, the carrier sends status updates back, and the invoice follows the same route. Because both sides agree on the format in advance, nobody has to read or retype the document.
Two standards dominate. UN/EDIFACT is the international standard used across Europe, with messages such as IFTMIN (transport instruction), IFTSTA (status report), DESADV (despatch advice) and INVOIC (invoice). ANSI X12 is the North American equivalent: a carrier receives a 204 load tender, answers with a 990, reports progress with 214 status messages and bills with a 210 freight invoice.
In practice, the trading partners agree on a standard, a version and an implementation guide that says which segments and codes they use. They connect over a transfer channel such as AS2, SFTP or a value-added network (VAN), map the messages to and from their own systems, and test with sample files before going live. That mapping and testing is repeated for every new partner, which is why EDI onboarding often takes weeks.
Example: a retailer's ERP sends an IFTMIN for 12 pallets from its warehouse to a store. The carrier's TMS turns it into a transport order without anyone touching it, sends an IFTSTA when the goods are loaded and another at delivery, and issues an INVOIC once the proof of delivery is in. The retailer's system matches the invoice to the original order automatically.
Transportial connects partners through its integration framework. It exchanges JSON, XML and CSV over APIs, webhooks, FTP or SFTP and e-mail, and maps every incoming field to the OTM5 data model without code. EDIFACT messages are used with ferry and terminal partners, and generic EDIFACT or X12 order messages are mapped per partner. Customers without EDI can simply e-mail a PDF: AI extraction turns it into a transport order for review.
Frequently asked questions
Is EDI still used in transport?
Yes. Large shippers, retailers, ports and terminals still exchange orders, statuses and invoices by EDI, often over connections that have run for years. Newer integrations increasingly use REST APIs, and many companies run both side by side.
What is the difference between EDI and an API?
EDI exchanges complete business documents in a fixed standard, usually in batches over AS2, SFTP or a VAN. An API lets one system request or send data in real time, typically as JSON over HTTPS. EDI gives you a shared standard; an API gives you speed and flexibility, but each provider defines its own format unless both sides follow an open model such as OTM5.
Which EDI messages are used in road transport?
In EDIFACT: IFTMIN for transport instructions, IFTSTA for status reports, DESADV for despatch advice and INVOIC for invoices. In ANSI X12: 204 (load tender), 990 (response to a load tender), 214 (shipment status) and 210 (freight invoice).
Does Transportial support EDI?
Yes. The integration framework exchanges JSON, XML and CSV with any partner, uses EDIFACT with ferry and terminal partners such as P&O Ferries and DP World, and maps generic EDIFACT or X12 order messages per partner, alongside the REST API and the OTM5 open standard.
See EDI in a real TMS
Transportial puts these concepts to work in one operational platform — planning, tracking, documents, and finance.