Which EDIFACT messages are most commonly used in logistics?

The most widely used message types are ORDERS (purchase order), DESADV (dispatch advice), INVOIC (invoice), and IFTMIN (transport instruction). In the warehouse environment, DESADV plays a central role, as it supplies the WMS with incoming goods information in advance and reduces manual data capture.

Can EDIFACT be replaced by APIs?

APIs offer significantly more flexible and real-time-capable integration, but require all partners to provide the corresponding interfaces. In many industries – particularly in retail and among large industrial companies – EDIFACT remains the required standard. In practice, both approaches often coexist.

How much effort is involved in implementing EDIFACT with a new trading partner?

The effort involved depends heavily on the partner, their implementation guidelines, and your own system landscape. In practice, mapping, testing, and sign-off per partner represent a significant portion of any project. Many companies therefore use EDI service providers who maintain standard mappings for common partners.

What happens if an EDIFACT message contains errors?

Faulty messages are either rejected and acknowledged with a CONTRL acknowledgement message, or they end up in an error queue, depending on the system. Without active monitoring, faulty messages can go unnoticed and lead to gaps in goods receipt or invoicing.

← Back to glossary

EDIFACT

Also: UN/EDIFACT, EDI EDIFACT, Electronic Data Interchange For Administration Commerce and Transport, EDIFACT-Standard, EDIFACT Nachricht, EDIFACT Format

AI-generated

In brief

EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport) is an internationally standardized UN standard for the structured electronic exchange of business documents between companies.

Key facts

EDIFACT is a UN standard for the cross-industry, machine-readable exchange of business documents such as purchase orders, dispatch advices, and invoices.
Each message type carries a standardized identifier, e.g. ORDERS, DESADV, or INVOIC, which is interpreted consistently worldwide.
National subsets and partner-specific implementation guidelines require a dedicated mapping for each trading partner.
Error and exception handling is an often-underestimated operational overhead when using EDIFACT.
EDIFACT increasingly complements or competes with API-based integration approaches in modern architectures, but remains the de facto standard in many industries.

What is EDIFACT?

EDIFACT stands for Electronic Data Interchange For Administration, Commerce and Transport and was developed by the United Nations as a cross-industry EDI standard. It defines a uniform syntax and a library of standardized message types – known as Message Types – which allow companies to exchange purchase orders, dispatch advices, invoices, warehouse movements, and many other business documents in a fully automated, machine-readable format. Unlike proprietary formats, EDIFACT is vendor-independent and globally applicable, making it particularly attractive for international supply chains.

How does EDIFACT work in practice?

An EDIFACT message consists of hierarchically structured segments: interchange headers, functional groups, individual messages, and their data segments. Each message type carries a six-character identifier – for example, ORDERS for purchase orders, DESADV for dispatch advices, or INVOIC for invoices. A mapping layer, typically within the EDI converter or middleware system in use, translates the internal data structures of the ERP or WMS into the EDIFACT format and vice versa.

In intralogistics, EDIFACT is particularly relevant at the interfaces between suppliers, freight carriers, and the warehouse itself. Typical scenarios include:

Automatic receipt of dispatch advices (DESADV) that supply the warehouse management system with goods receipt information in advance
Transmission of order data (ORDERS) directly from the ERP to suppliers without manual data entry
Electronic invoicing (INVOIC) to accelerate posting processes
Status messages on goods movements between logistics service providers

Transmission takes place via communication channels such as AS2, SFTP, or Value Added Networks (VANs). Many companies use an EDI service provider or an Integration Platform as a Service (iPaaS) to outsource mapping and operations.

What matters when selecting and implementing EDIFACT?

A critical success factor is the maintenance of mappings: every trading partner interprets the EDIFACT standard slightly differently, as national subsets and industry-specific implementation guidelines exist. This means that a separate mapping must be created and tested for each new partner – an effort that is often underestimated.

In addition, you should ensure robust error and exception handling. Faulty or undeliverable messages must be detected, logged, and escalated – manual interventions without transparent monitoring can lead to hidden data errors in the supply chain. Whether a dedicated middleware solution, a cloud-based EDI service provider, or an integrated ERP module is the better choice depends on the number of partners, message volume, and internal IT capacity – there is no universally correct answer here.

Frequently asked questions

EDI (Electronic Data Interchange) is the umbrella term for the electronic exchange of data between systems. EDIFACT is a specific EDI standard, standardized by the United Nations, with a defined syntax and message library. Other EDI standards exist, such as ANSI X12 (predominantly used in North America), but in Europe and international trade, EDIFACT is dominant.

Related terms

API
An API (Application Programming Interface) is a defined interface through which two software systems can exchange data in an automated and standardized way. In intralogistics, it connects systems such as WMS, ERP, or TMS with one another and with external services.
Artikelstammdaten
Item master data refers to the permanently valid base data of an item – such as dimensions, weight, packaging units, hazardous goods classification, and best-before date relevance. It forms the foundation for all logistical, procurement-related, and system-driven processes along the supply chain.
Auftragsabwicklung
Order fulfillment refers to the complete process from receiving a customer order through to its successful delivery and invoicing. It encompasses all operational and administrative steps required to fulfill an order on time and without errors.
Avisierung
Pre-advice refers to the advance notification of a delivery by the supplier to the recipient before the goods arrive. It enables the warehouse to plan staffing, dock capacity, and put-away processes in a timely manner.
Beschaffungslogistik
Procurement logistics encompasses all logistical processes that manage the flow of materials from suppliers through to handover at the warehouse or production facility. It connects purchasing, transportation, and goods receipt into a seamless inbound process.
DESADV
DESADV (Dispatch Advice) is a standardized EDI message in EDIFACT format that electronically announces an upcoming delivery. It transmits structured information on packaging units, items, quantities, and identifiers such as the SSCC to the goods recipient.

Matching categories

Enable delivery notification Integrating Systems & Interfaces Connect ERP, WMS & TMS Managing carrier & service provider integrations Improve Data Quality & Master Data Automating document processes