Despatch Advice Message
UN/EDIFACT DESADV is the international equivalent of the X12 856 Advance Ship Notice, describing what was shipped and how it is packed.
In this guide
EDIFACT DESADV moves from Supplier to Buyer / Warehouse (Seller → Buyer) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How EDIFACT DESADV Works
Sender
Supplier
Receiver
Buyer / Warehouse
Direction
Seller → Buyer
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Logistics & Fulfillment
Sender — Supplier
EDI Transmission
DESADV
Despatch Advice Message
UN/EDIFACT D.96A / D.01B
Receiver — Buyer / Warehouse
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT DESADV workflow. Steps: Pick & Pack, Build Pack Hierarchy, Transmit Ahead of Shipment, Buyer Gateway, Scan-Based Receiving, Flag Discrepancies. Transmitted from Supplier to Buyer / Warehouse via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Enables automated, scan-based receiving by linking physical package identifiers (SSCC) to the electronic shipment record.
Sender
Supplier
Receiver
Buyer / Warehouse
Direction
Seller → Buyer
Standard / Version
UN/EDIFACT D.96A / D.01B
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BGM | Beginning of Message | Despatch advice document number. |
| CPS | Consignment Packing Sequence | Builds the pack/parcel hierarchy. |
| PAC | Package | Package type and identification. |
| GIN | Goods Identity Number | Carries the SSCC for a package. |
| LIN | Line Item | Items contained in a package. |
Interactive example
Click any segment below to see its business meaning.
UNH
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
UNH+1+DESADV:D:96A:UN'
BGM+351+ASN-55210+9'
DTM+11:20230920:102'
RFF+ON:PO-2024-88213'
NAD+DP+DC4WAREHOUSE::92'
CPS+1'
PAC+1++1AB'
GIN+BJ+00312345678901234567'
LIN+1++SKU-10293:BP'
QTY+12:100'
UNS+S'
UNT+11+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| WMS Shipment Record | carton.sscc | GIN/7402 (Identity Number) |
| WMS Shipment Record | carton.item.qty_shipped | QTY+12 (Quantity) |
Validation rules
- GIN SSCC values must be 18 digits and pass GS1 check-digit validation.
- RFF+ON must reference a valid, open ORDERS document.
- CPS hierarchical numbering must be sequential and internally consistent.
Common errors & troubleshooting
Receiving can't match cartons to the DESADV
Cause: SSCC was reassigned after the DESADV was transmitted due to a late repack.
Fix: Finalize and lock SSCC assignment before DESADV transmission, or send a corrective message if repacking is unavoidable.
Related articles
Frequently asked questions
It's typically required whenever the trading partner agreement calls for automated, scan-based receiving, which is standard for most large retail and automotive supply chains in EDIFACT markets.
Still have questions about DESADV?
Ask EDI AI →