EDI in logistics

EDI and EDIFACT in Logistics: Definition, How It Works, Messages, and Standards

EDI (Electronic Data Interchange) is the automatic exchange of commercial and logistics documents between the computer systems of two companies, in a standardized format, without the need for re-entry. EDIFACT is the UN’s international standard that defines this format: the syntax (ISO 9735) and hundreds of message types such as the purchase order (ORDERS), the shipping notice (DESADV), the transport instruction (IFTMIN), and the transport status (IFTSTA). In logistics, EDI connects shippers, carriers, freight forwarders, warehouses, ports, and customs authorities. Several standards have been developed based on this, specific to different sectors: GS1 EANCOM for retail, INOVERT for French road transport, and ODETTE for the automotive industry.

This article explains how an EDI exchange works, how to read an EDIFACT message, what types of messages are exchanged, which standards to use depending on your industry, and what EDI does not address.

What is EDI?

EDI (Electronic Data Interchange) is a machine-to-machine data exchange method: a company’s software (ERP, TMS, WMS) generates a structured document, transmits it to its partner’s software, which automatically processes it. No one reads or re-enters the document.

For this to work, both partners must speak the same language. That is the role of EDI standards: they define the list of messages, the order of the information, and the codes to be used. Both parties then specify their choices in a message implementation guide, since a standard allows for many options.

How Does an EDI Exchange Work?

  1. Extraction: The source system (ERP, TMS) generates the data for a document, such as a shipping order.
  2. Translation: EDI translation software converts this data into the agreed-upon format (EDIFACT, INOVERT, X12, etc.).
  3. Transmission: The file is sent using a secure protocol: AS2, SFTP, OFTP2 (widely used in the automotive industry), X.400, or via a value-added network (VAN) operated by a service provider.
  4. Validation and acknowledgment: The recipient checks the syntax and sends an acknowledgment (in EDIFACT, CONTRL for syntax, APERAK for application processing).
  5. Integration: The data is fed into the recipient's system, which can then respond (confirmation, status, invoice).

What EDI Brings to Logistics

  • Eliminate the need to re-enter data and the errors that come with it (weight, part numbers, addresses).
  • Speed: A shipping order or delivery status is received within minutes, rather than having to go through an email, a PDF, and then manual data entry.
  • Traceability: Each message is time-stamped, acknowledged, and can be archived.
  • Visibility: Status updates (picked up, in transit, delivered) are automatically reported to the shipper.
  • Scalability: The same system can process ten or ten thousand shipments per day.

Be cautious about quantified benefits. The figures circulating come mainly from vendors: EDI Basics (OpenText) claims a reduction of “at least 35%” in transaction costs, based on a customer case study, and cites a 30- to 40% reduction in erroneous transactions without providing a source. No recent independent study supports generalizing these figures. The actual benefit depends primarily on the number of connected partners and the proportion of documents that are still not processed via EDI.

What is EDIFACT?

UN/EDIFACT (United Nations Electronic Data Interchange for Administration, Commerce, and Transport) is the international EDI standard published by the United Nations Economic Commission for Europe (UNECE) and maintained by UN/CEFACT (Center for the Facilitation of Trade and Electronic Transactions).

His points of reference:

  • ISO 9735 standardized syntax, approved in 1987.
  • More than 200 standard messages covering multiple sectors: orders, invoices, shipping notices, transportation, customs, insurance, and finance.
  • Versioned repertoires named by year and version, such as D.96A, D.01B, or D.22B. Both partners must agree on which repertoire to use. D.96A remains one of the most widely used, despite its age.
  • A parent standard: Many industry-specific standards (EANCOM, INOVERT, ODETTE) are subsets or adaptations of EDIFACT.

EDIFACT is the dominant standard in Europe and in international transportation, particularly in the maritime and customs sectors. In North America, the ANSI X12 standard has become the norm.

The Structure of an EDIFACT Message

An EDIFACT file is a sequence of segments, each identified by a three-letter code and ending with an apostrophe. The segments are nested like envelopes:

SegmentRole
UNA (optional)Defines the separator characters used in the file
UNB … UNZTransaction details: sender, recipient, date, control number
UNG … ONE (optional)Functional group: a collection of messages of the same type
UNH … UNTMessage header and footer: message type (IFTMIN, INVOIC…) and directory (D.96A…)
Data segmentsContent: parts (NAD), dates (DTM), references (RFF), goods (GID), quantities (QTY), etc.

The default separators are + between data elements, : between components, ' at the end of a segment, and ? as the escape character. A simplified example of the beginning of a transport status:

UNB+UNOC:3+SHIPPER+CARRIER+261108:1400+0001'
UNH+1+IFTSTA:D:96A:UN'
...
UNT+12+1'
UNZ+1+0001'

For information on converting these files to XML format and the specifics of the D.96A directory, see our article “Understanding EDIFACT and Its XML Conversion.”

‍

Key EDIFACT Messages in Transportation and Logistics

MessageRoleWho usually sends it?
ORDERSOrderBuyer → Supplier
DESADVShipping Notice (equivalent to a delivery slip)Supplier or shipper → recipient
RECADVReceipt confirmation, including any discrepancies notedRecipient → Sender
IFTMINShipping Instruction (Shipping Order)Shipper or freight forwarder → carrier
IFTMBF / IFTMBCTransportation Reservation Request and Confirmation (Booking)Freight forwarder ↔ shipping line
IFTSTAShipping status (picked up, in transit, delivered, etc.)Carrier → Shipper
IFCSUMBill of Lading or Cargo SummaryCarrier, freight forwarder
COPARN / CODECOContainer Movement Notifications, Terminal Inbound and Outbound MovementsShipowner ↔ terminal
BAPLIEShip's loading plan (bay plan)Shipowner ↔ terminal
CUSCAR / CUSDECCustoms Manifest / Customs DeclarationCarrier or declarant → customs
INVOICInvoiceSupplier, carrier → customer
CONTRL / APERAKSyntax/Application AcknowledgmentRecipient → Sender

Sources: UN/EDIFACT (UNECE) directories; EDI Basics.

The various EDI standards: EDIFACT, GS1, INOVERT, ODETTE, ETEBAC

Each industry has adapted EDI to its specific needs. Here are the standards most commonly used in logistics in France.

EDIFACT

The international reference standard, described above. It serves as the basis for the other standards on this list and remains the most widely used in international transportation, particularly in maritime and customs contexts. This is the standard you will encounter when dealing with a shipping line, a port terminal, or a customs system.

GS1

GS1 is the international organization known for its identification codes: GTIN for products (the barcode), GLN for locations and companies, and SSCC for logistics units (pallets, packages). On the EDI front, GS1 publishes EANCOM, a ready-to-use subset of UN/EDIFACT that eliminates the need for each pair of partners to reinterpret the standard. EANCOM is the industry standard for mass retail and for data flows between manufacturers, retailers, and logistics providers. GS1 also offers an XML version of its messages.

INOVERT

INOVERT (INternational OVERland Transport) is the EDI standard for French overland transport, promoted by the GTF association, which was founded in 1987 by three carriers: Calberson, Danzas, and Mory. Its messages are based on the EDIFACT syntax and data set; they were validated by the EDIFACT Board as early as 1988. Version 4.0 was released in 2012, and the GTF has since added XML and JSON formats.

Key INOVERT messages: DISPOR (transport order), SCONTR (communications between subcontractors), REPORT (status and proof of delivery), AARNOT (notice of arrival), PICKUP (pickup request), TRAINV (transport invoice), INOSAV (after-sales service).

ODETTE

ODETTE

Odette (Organization for Data Exchange by Tele-Transmission in Europe) was founded in 1984 by European automakers to reduce paper usage between automakers and suppliers. It publishes messages and recommendations for the automotive supply chain and lent its name to the OFTP2 transfer protocol, which is widely used in the industry. Now known as Odette International, the organization also covers XML, JSON, RFID, and APIs. In France, its work is carried out by Galia.

ETEBAC

‍

ETEBAC (Electronic Exchange Between Banks and Customers) is not a logistics messaging standard but a French protocol for transferring files between banks and their customers: transfer and direct debit submissions, and account statements. It was based on the X.25 network, which France Télécom discontinued in the early 2010s. ETEBAC has been replaced by EBICS, an Internet-based protocol that the CFONB (French Committee for Banking Organization and Standardization) adopted in collaboration with German banks, in a joint Franco-German version published in 2010. If you still see “ETEBAC” mentioned in a set of specifications, it actually refers to EBICS.

ANSI X12

The U.S. standard, managed by ASC X12. In North America, it serves the same purpose as EDIFACT does in Europe, with its own transaction numbers (850 for the purchase order, 856 for the shipping notice, 214 for the shipping status, and 810 for the invoice). You’ll encounter it when dealing with North American customers, carriers, or platforms.

Which EDI standard is best for which use case?

StandardSectorScopeWhat You Need to Know
UN/EDIFACTAll sectors, international transportation, maritime, customsWorldwide (especially Europe)Master standard, versioned directories (D.96A is widely used)
GS1 EANCOMRetail, Consumer GoodsWorld ChampionshipA subset of EDIFACT, including the GTIN, GLN, and SSCC codes
INOVERTRoad Transport and Courier ServicesFranceGTF standard, based on EDIFACT version 4.0, in XML and JSON formats
ODETTEAutomotiveEuropeIndustry-Specific Messages and the OFTP2 Protocol
ANSI X12All sectorsNorth AmericaThe U.S. equivalent of EDIFACT
ETEBACBankFranceBanking Protocol Replaced by EBICS

EDI or API: What's the Difference?

EDI exchanges complete documents (such as an order or an invoice) in batches, according to a common standard. An API allows two applications to query each other in real time about specific data (such as the status of a shipment or a rate). The two complement each other: many carriers continue to use EDI for orders and invoicing, and add APIs for tracking and booking.

CriteriaEDIAPI
Exchange UnitA complete document, often in batchesA query and a response regarding a piece of data
DeadlineFrom a few minutes to a few hoursReal Time
FormatStandards (EDIFACT, INOVERT, X12, etc.)Typically JSON; each provider has its own schema
Connecting a PartnerProject scoping and testing, often lasting several weeksFaster if the API is documented
Typical UseOrders, shipping orders, invoices, customsTracking, Pricing, Booking, Visibility

For a detailed comparison with web services, read " API, EDI, Web Service: What Are the Differences?".

‍

Do you want to be more productive?

Book a demo
Book a demo

EDI, Cargo-XML, eBL, eFTI: Other Standards for Digitalization in Transportation

EDIFACT is not the only data exchange standard in the transportation industry. Depending on the mode of transport, you may encounter:

EDI and Electronic Invoicing 2026

France's electronic invoicing reform took effect on September 1, 2026: all VAT-registered businesses must now be able to receive electronic invoices, and large companies and mid-sized companies must issue them. The requirement to issue electronic invoices will be extended to small and medium-sized enterprises (SMEs) and micro-enterprises on September 1, 2027.

Impact on EDI flows: An INVOIC invoice exchanged between two French companies must now be routed through an approved platform (PA, formerly PDP). The core formats are UBL, UN/CEFACT CII, and Factur-X; therefore, an existing EDIFACT message must be supported or converted by the chosen platform. Check this with your EDI service provider. For details, see “Electronic Invoicing 2026: Why Data Reliability Is Becoming Essential.”

How do you set up EDI?

  1. List the flows and partners: what documents (orders, shipping orders, status updates, invoices), with whom, and in what volume.
  2. Select the standard and version required by your partners (EDIFACT D.96A, INOVERT 4.0, EANCOM, etc.) and obtain their implementation guides.
  3. Select the transmission method: AS2, SFTP, OFTP2, or a value-added network.
  4. Choose the tool: an on-premises EDI translator, a cloud-based EDI platform, or a fully managed EDI service provided by a vendor.
  5. Map your data (ERP, TMS, WMS) to EDI messages.
  6. Test with each partner, message by message, and then go live.
  7. Monitor: rejections, missing acknowledgments, and changes to the implementation guides.

A simple integration with a cloud platform can be completed in a few weeks. A multi-partner project involving multiple standards takes several months.

What types of EDI solutions are there?

Solution TypeFor whomExamples
EDI and API Integration Platform (Cloud)Companies that want to manage their own workflowsLobster_data, Youredi
Managed EDI ServiceCompanies that prefer to outsource the connection and monitoringBusiness System Integrators (BSI)
TMS with built-in EDI connectorsShippers and carriers who want EDI integrated into their transportation softwareCargoson, Dashdoc
Documentary AI in the run-up to EDICompanies that still receive some of their documents as PDFs, scans, or via emailDocloop

This is a sample list; the items are not ranked.

The Limitation of EDI: Documents That Are Not Received via EDI

EDI only works if the other party is connected. However, in international shipping, a large portion of the information still arrives in the form of documents: commercial invoices in PDF format, packing lists, bills of lading, certificates of origin, and shipping instructions sent by email. Small suppliers, overseas agents, and one-time partners: connecting each of them via EDI is not cost-effective.

Another limitation: an EDI message can be perfectly valid syntactically but incorrect in substance. If the weight on the invoice does not match that on the packing list, the EDI message will carry the error all the way to the customs declaration.

That’s where Docloop comes in. The platform automatically extracts data from unstructured documents, structures it, and then verifies that the data is consistent across documents (weight, number of packages, descriptions, values, missing items) before sending it to your TMS, ERP, or EDI and API feeds. This is the principle of document reconciliation, which is also detailed in our article on discrepancies between invoices, packing lists, and bills of lading. To learn more: how to automate the processing of shipping documents and how to avoid data entry errors in logistics operations.

‍

FAQs
Q.
What is EDI and why is it important in 2025?

EDI (Electronic Data Interchange) is a system for the electronic exchange of standardized business documents between partners. By 2025, it has become indispensable because it automates processes, reduces errors by up to 40%, and speeds up transactions. Companies that do not use EDI lose competitiveness compared to those that have adopted it.

Q.
How much does it cost to set up an EDI system?

The cost varies depending on the size of the company and the complexity of its needs. Modern cloud solutions in 2025 offer flexible pricing. The initial investment quickly pays for itself thanks to the savings made. Processing costs can be reduced by up to 35% in the first year.

Q.
Is EDI compatible with all computer systems?

Yes, modern EDI solutions in 2025 are designed to be compatible with most systems. APIs facilitate integration with ERP, WMS, and other existing software. Standardized formats ensure interoperability between different platforms.

Q.
How long does it take to implement EDI?

The implementation time depends on the complexity of the project. A simple cloud solution can be up and running in a few weeks. More complex projects require 2 to 6 months. Support from experts significantly speeds up the process.

Q.
Is EDI secure for sensitive data?

Absolutely. EDI systems use advanced security protocols in 2025. Data encryption is systematic. Security certifications guarantee the protection of sensitive commercial information. GDPR compliance standards are met.

Q.
What is the difference between EDI and API?

EDI is a system for exchanging standardized documents between companies. APIs enable real-time communication between applications. In 2025, the two technologies are often combined to maximize efficiency. EDI manages business documents while APIs facilitate system integration.

Q.
How can we summarize it?

The digitization of logistics flows through logistics EDI represents an ongoing revolution in modern logistics. This system enables the electronic exchange and processing of standardized business documents between trading partners. It is an efficient and secure method of transmitting crucial information. Orders, invoices, shipping notices, and all commercial documents are processed automatically. In October 2025, software tools such as Docloop, BSI, Cargoson, and others continue to improve the efficiency and accuracy of EDI. Their contributions are manifold: - Complete automation of repetitive processes - Standardization of data according to international standards - Drastic reduction in operating costs - Almost total elimination of human error In logistics and within the supply chain, electronic data interchange is now widely used. The automation of communication and document processing is complete. The benefits are numerous and measurable. Operational efficiency is significantly improved. The visibility of goods flows is perfect. Coordination between supply chain players reaches optimal levels.To implement this information exchange effectively, specialized software is required. This software converts commercial documents into the appropriate electronic formats. Data validation is automatic. Security is guaranteed. Data exchange process management is continuously optimized. Companies that adopt EDI in 2025 are positioning themselves favorably for the future of digital logistics.