Electronic Data Interchange (EDI) is still the backbone of digital communication in logistics, retail, and supply chain management. Among the most widely used standards is EDIFACT, which allows companies to exchange structured business documents automatically.

But for many developers and integration teams, EDIFACT can feel abstract. What does a real EDIFACT workflow actually look like?

In this article, we walk through a realistic EDIFACT integration example from order creation to shipment processing and invoicing.

Typical EDIFACT Workflow in Logistics

A typical logistics workflow includes several message types exchanged between partners.

Example participants:

• Retailer (buyer)
• Logistics provider / warehouse
• Supplier / manufacturer

Typical message flow:

ORDERS  → purchase order
ORDRSP  → order response
DESADV  → dispatch advice
IFTSTA  → shipment status
INVOIC  → invoice

These messages ensure that all systems in the supply chain remain synchronized.

Step 1 — Sending an Order (ORDERS)

The process usually begins with a purchase order.

A retailer sends an ORDERS message to a supplier or logistics provider.

Example EDIFACT message:

UNH+1+ORDERS:D:96A:UN'
BGM+220+PO20260312+9'
DTM+137:20260312:102'
NAD+BY+5412345000013::9'
NAD+SU+4012345500004::9'
LIN+1++8712345001234:EN'
QTY+21:100'
UNS+S'
CNT+2:1'
UNT+9+1'

Important segments:

SegmentMeaningUNHMessage headerBGMBeginning of message (order number)DTMDate/timeNADParties (buyer/supplier)LINLine itemQTYQuantity

Once the message is generated, it is transmitted via an EDI communication channel.

Step 2 — Transmission via EDI Protocol

EDIFACT messages are usually transmitted using specialized communication protocols.

Common transport methods include:

• AS2
• SFTP
• OFTP / OFTP2
• VAN networks

Typical flow:

ERP System
     ↓
EDI Mapping Engine
     ↓
Communication Protocol (AS2 / SFTP)
     ↓
Partner EDI Gateway

The receiving partner validates the message structure and imports the data into their system.

Step 3 — Order Response (ORDRSP)

After receiving the order, the supplier may send an ORDRSP message to confirm or modify it.

Example:

UNH+2+ORDRSP:D:96A:UN'
BGM+231+PO20260312+29'
DTM+137:20260312:102'
LIN+1++8712345001234:EN'
QTY+113:100'
UNT+6+2'

Possible responses include:

• order confirmation
• partial confirmation
• quantity changes
• delivery date adjustments

Step 4 — Dispatch Notification (DESADV)

Once goods are shipped, the supplier sends a Dispatch Advice (DESADV).

This informs the receiver about:

• shipped items
• quantities
• packaging units
• pallet structure

Example:

UNH+3+DESADV:D:96A:UN'
BGM+351+SHIP12345+9'
DTM+137:20260313:102'
NAD+SU+4012345500004::9'
CPS+1'
PAC+10'
LIN+1++8712345001234:EN'
QTY+12:100'
UNT+8+3'

The DESADV message is critical for warehouse preparation and goods receiving.

Step 5 — Shipment Status Updates (IFTSTA)

Logistics providers often send IFTSTA messages to provide shipment tracking updates.

Example status messages include:

• goods picked up
• shipment in transit
• delivery completed

Example:

UNH+4+IFTSTA:D:96A:UN'
BGM+34+STATUS123'
DTM+137:20260313:102'
STS+1+DELIVERED'
UNT+5+4'

These updates allow partners to track shipments automatically.

Step 6 — Invoice (INVOIC)

Finally, the supplier sends an INVOIC message.

Example:

UNH+5+INVOIC:D:96A:UN'
BGM+380+INV20260314+9'
DTM+137:20260314:102'
NAD+BY+5412345000013::9'
NAD+SU+4012345500004::9'
MOA+77:1500'
UNT+6+5'

The receiving ERP system processes the invoice automatically.

What Happens Inside an Integration Platform

In reality, EDIFACT messages are rarely processed directly by ERP systems.

Instead, an EDI integration layer handles the transformation.

Typical architecture:

Partner EDIFACT
      ↓
EDI Gateway
      ↓
EDI Mapping Engine
      ↓
Canonical Data Model
      ↓
ERP / WMS / TMS

The mapping engine translates EDIFACT segments into structured internal data.

Example mapping:

EDIFACT SegmentInternal FieldBGMorderNumberNAD+BYbuyerLINproductQTYquantity

This allows internal systems to remain independent of EDIFACT structures.

Common Challenges in EDIFACT Integrations

Even though the workflow seems straightforward, real-world integrations often face challenges.

Typical issues include:

• different EDIFACT versions (D.96A, D.99B, D.01B)
• partner-specific mapping rules
• missing segments
• incorrect qualifiers
• communication errors

Integration teams often maintain custom mappings per partner.

Modern Approach: Hybrid API + EDI Architecture

Today many companies combine EDIFACT with modern APIs.

Example architecture:

API Gateway
     ↓
Integration Platform
     ↓
EDI Mapping
     ↓
ERP / WMS / TMS

This allows:

• legacy EDI partners to continue using EDIFACT
• modern partners to integrate via APIs
• real-time integrations

Conclusion

EDIFACT integrations remain a critical part of logistics and supply chain communication.

A typical workflow includes:

1. ORDERS (purchase order)
2. ORDRSP (order confirmation)
3. DESADV (dispatch advice)
4. IFTSTA (shipment status)
5. INVOIC (invoice)

Although the technology is decades old, it still powers a large portion of global trade.

Companies that implement modern integration layers and API gateways can significantly simplify EDIFACT workflows while maintaining compatibility with existing partners.

About Hemutis

Hemutis helps companies design and implement reliable integration architectures for logistics and supply chain systems. From EDIFACT mappings to modern API platforms, we support organizations in building scalable digital infrastructure.