EDI
EDI (Electronic Data Interchange) is the computer-to-computer exchange of business documents in a standard electronic format between organisations, replacing paper documents and manual re-keying. Instead of emailing or posting a purchase order or invoice, systems exchange it as a structured EDI message that both sides' software can process automatically.
EDI has been a backbone of B2B and supply-chain integration for decades, using agreed message standards — chiefly UN/EDIFACT (international) and ANSI X12 (North America) — for documents such as orders, invoices, dispatch advices, and a rich set of logistics messages (booking, bill of lading, container status, customs and manifest messages like COPRAR, CODECO, IFTMIN, CUSDEC and many more). Messages are transmitted between partners over VANs, AS2 or SFTP. EDI delivers speed, accuracy, lower cost and automation by removing manual handling. While newer APIs offer real-time exchange and are increasingly used alongside it, EDI remains deeply embedded in trade and logistics, mandated by many carriers, retailers and customs authorities. It is a foundational technology of supply-chain data exchange, and the many specific EDI message types are core vocabulary in freight and shipping systems.
EDI has quietly run global trade for decades — orders, invoices, bookings, bills of lading and customs messages flowing computer-to-computer without paper or re-keying. Mandated by carriers, retailers and customs, it is deeply embedded even as APIs rise alongside it. Its message standards and types are core vocabulary for anyone working with freight and shipping systems.
What standards does EDI use?
Chiefly UN/EDIFACT internationally and ANSI X12 in North America, defining the format of documents like orders, invoices and shipping messages.
How does EDI compare with APIs?
EDI exchanges standardised messages (often batched); APIs offer real-time, on-demand exchange. Both are used, often together, in modern logistics.