For UK and European retail, DESADV is the message that decides how smoothly your delivery is received. The buyer's warehouse scans the SSCC on each pallet label, looks it up in your DESADV, and books the contents in without counting. When the label and the message disagree, the pallet gets counted by hand, and that is when queries, delays and deductions start.
This guide follows the GS1 EANCOM 2002 DESADV layout (directory D.01B). All four examples are live: they are parsed in your browser by the same engine as our EDIFACT inspector, with SSCC and GTIN check digits verified. If you know the X12 856, the concepts carry over directly; the 856 guide covers the HL hierarchy that CPS replaces.
What is an EDIFACT DESADV?
DESADV (despatch advice) is the UN/EDIFACT message a supplier sends to tell the buyer exactly what has been despatched: which orders, on which pallets or cartons, with which products and quantities. It relates to one seller and one buyer, one despatch point and one or more destinations.
GS1's principle for the message is that each unit delivered (pallet, carton) should be uniquely identified, and the DESADV describes what is in each one. When the goods arrive, the physical delivery and the electronic message can be cross-checked, and discrepancies show up immediately.
"Despatch" is the British and EDIFACT spelling. The message is the same thing US partners call an ASN.
When DESADV is sent in the order-to-cash flow
| Step | Message | Direction | Timing |
|---|---|---|---|
| 1 | ORDERS | Buyer to supplier | Order placed |
| 2 | ORDRSP | Supplier to buyer | Before picking, if required |
| 3 | DESADV | Supplier to buyer | At despatch, always before the goods arrive |
| 4 | RECADV | Buyer to supplier | After the delivery is booked in |
| 5 | INVOIC | Supplier to buyer | Quoting the DESADV number in RFF+DQ |
GS1 is explicit that the despatch advice should always be sent before the goods are physically delivered, so the receiving site can prepare. In practice, build it when the vehicle is loaded and the pallet labels are printed, not at the end of the day.
The CPS packing hierarchy
X12 describes packing with HL loops. DESADV does it with CPS (consignment packing sequence) groups. Each CPS has its own level number and, optionally, a parent number, which builds a tree:
CPS+1 Consignment (whole shipment)
├── CPS+2+1 Pallet 1, parent is level 1
│ └── LIN ... Products on pallet 1
└── CPS+3+1 Pallet 2, parent is level 1
├── CPS+4+3 Carton on pallet 2
│ └── LIN ... Products in that carton
└── CPS+5+3 Another carton on pallet 2
Under each CPS, a PAC group describes the physical unit at that level:
- PAC: how many packages and what type (
PAC+1++201::9'is one ISO 1 / Euro pallet, GS1 code 201) - MEA: measurements, such as gross weight (
MEA+PD+AAB+KGM:412.5') or length and width - PCI: what the package is marked with, such as an SSCC label
- GIN: the identification number itself, the SSCC (
GIN+BJ+350987650000000010')
Then LIN groups list the products in that package with their despatched quantities (QTY+12).
GS1 describes four levels of detail a DESADV can carry, from simplest to fullest:
| Option | What it describes | When partners use it |
|---|---|---|
| 1 | Products and total quantities only, one dummy CPS+1 | Small suppliers, parcel deliveries |
| 2 | Products and quantities, with the SSCC of each carton but no pallet structure | Carton-picked deliveries |
| 3 | Pallets with SSCCs and the products on each | Most retail DC deliveries |
| 4 | Pallets and cartons, both with SSCCs | Mixed pallets, cross-docking, store-picked deliveries |
Your partner's guide will say which level they need. Most UK grocery DCs expect at least option 3.
Example 1: single pallet, single order
The fictional supplier Kestrel Valley Homeware despatches order HL-PO-88355 from the fictional retailer Harbour Lane Stores on one Euro pallet. Every identifier is made up, with a valid GS1 check digit.
One SSCC-labelled pallet, two products
CPS+1 for the consignment and CPS+2+1 for the pallet, with gross weight, SSCC and the two product lines on it.
DESADV · Despatch advice · ref 1
- Document
- Despatch advice
- Document number
- KV-DES-7790
- Message function
- Original
- Document/message date/time
- 2026-10-19
- Despatch date/time
- 2026-10-19
- Delivery date/time, estimated
- 2026-10-20
- Reference date/time
- 2026-10-12
- Order number (buyer)
- HL-PO-88355
- Packages
- 1
Parties
| Role | Identifier | Name and address |
|---|---|---|
| Supplier SU | 5098765000002GS1 (GLN) | - |
| Buyer BY | 5012345000008GS1 (GLN) | - |
| Delivery party DP | 5012345000107GS1 (GLN) | - |
Lines (2)
| # | GTIN | Codes | Description | Despatch quantity | Price | Amount |
|---|---|---|---|---|---|---|
| 1 | 5098765100023 | SSCC: 350987650000000041 | - | 60 | - | - |
| 2 | 5098765100016 | SSCC: 350987650000000041 | - | 120 | - | - |
Interchange (UNB)
- Sender
- 5098765000002GS1 GLN
- Recipient
- 5012345000008GS1 GLN
- Prepared
- 2026-10-19 06:15
- Control reference
- KVH000201
- Syntax
- UNOC version 3
- Messages
- 1
| Segment | What it says |
|---|---|
UNH+1+DESADV:D:01B:UN:EAN008' | DESADV, directory D.01B, EANCOM subset version 008 |
BGM+351+KV-DES-7790+9' | Despatch advice (351), number KV-DES-7790, original (9) |
DTM+137 / DTM+11 / DTM+17 | Message date, despatch date, estimated delivery date |
RFF+ON:HL-PO-88355' / DTM+171 | The buyer's order number and its date |
NAD+SU / BY / DP | Supplier, buyer and delivery point GLNs |
CPS+1' / PAC+1++201::9' | Level 1, the consignment: one Euro pallet |
CPS+2+1' | Level 2, parent level 1: the pallet itself |
MEA+PD+AAB+KGM:318.4' | Gross weight 318.4 kg |
PCI+33E' / GIN+BJ+...' | The pallet carries an SSCC label, and this is its SSCC |
LIN / QTY+12 | 60 and 120 units of two GTINs on this pallet |
CNT+2:2' | Two LIN lines in the message |
Unlike ORDERS and INVOIC, DESADV has no UNS summary separator. The detail section runs straight into CNT. Many partners want the consignment level even for a single pallet, so build both levels every time and you will not need a special case.
DESADV segment reference
Status is M (mandatory) or C (conditional); repeats are the EANCOM 2002 maximum.
| Segment | Name | Status | Repeats | What it carries | X12 856 equivalent |
|---|---|---|---|---|---|
UNH | Message header | M | 1 | Message reference, type and version | ST |
BGM | Beginning of message | M | 1 | Despatch number and function | BSN01, BSN02 |
DTM | Date/time/period | C | 10 | Message, despatch and delivery dates | BSN03, DTM |
MEA | Measurements | C | 5 | Whole-shipment measurements | TD1 |
RFF (SG1) | Reference | C | 10 | Order number (ON), delivery note, contract | PRF, REF |
NAD (SG2) | Name and address | C | 99 | Supplier, buyer, delivery party, shipper | N1 loop |
TOD (SG5) | Terms of delivery | C | 10 | Delivery terms | FOB |
TDT (SG6) | Transport | C | 10 | Mode, carrier, vehicle | TD5, TD3 |
EQD (SG8) | Equipment | C | 10 | Trailer or container, with seals (SEL) | TD3 |
CPS (SG10) | Consignment packing sequence | C | 9999 | Hierarchy level and parent | HL01, HL02 |
PAC (SG11) | Package | C | 9999 | Number and type of packages | TD1, PO4 |
MEA | Measurements | C | 10 | Weight and dimensions of the package | TD1, MEA |
QTY | Quantity | C | 10 | Quantity per pack (52) | PO4 |
HAN (SG12) | Handling instructions | C | 10 | Fragile, keep frozen and similar | none direct |
PCI (SG13) | Package identification | C | 1000 | Marked with SSCC | MAN01 |
GIN (SG15) | Goods identity number | C | 99 | SSCC of the package (BJ) | MAN02 |
LIN (SG17) | Line item | C | 9999 | Line number and GTIN | LIN |
PIA | Additional product id | C | 10 | Supplier code, substitute GTIN | LIN qualifiers |
IMD | Item description | C | 25 | Description | PID |
QTY | Quantity | C | 10 | Despatched (12), ordered (21) | SN102, SN105 |
DTM | Date/time/period | C | 5 | Best before, expiry, production date | DTM |
RFF (SG18) | Reference | C | 99 | Line order number when one DESADV covers several orders | PRF |
LOC (SG20) | Place/location | C | 100 | Split delivery destination | N1 at order or store level |
PCI / GIN (SG22, SG23) | Line package identification | C | 9999 | SSCCs or batch numbers for this line | MAN |
QVR (SG25) | Quantity variances | C | 10 | Difference from ordered, with reason | SN108 |
CNT | Control total | C | 5 | Line count, packages, weight | CTT |
UNT | Message trailer | M | 1 | Segment count and reference | SE |
Qualifier and code tables
BGM document and function codes
BGM+351+KV-DES-7790+9'. Document code 351 is a despatch advice; EANCOM also defines 345 ready for despatch advice and 729 returns advice. The number is your despatch reference, and your INVOIC quotes it back in RFF+DQ.
| Function | Meaning |
|---|---|
9 | Original |
1 | Cancellation of a previous DESADV, identified in RFF |
4 | Change: only the changing areas are re-sent |
5 | Replace: cancels and replaces a previous DESADV |
7 | Duplicate, on the receiver's request |
31 | Copy, for a third party |
DTM qualifiers
| Qualifier | Level | Meaning |
|---|---|---|
137 | Header | Message date (mandatory) |
11 | Header | Despatch date |
17 | Header | Estimated delivery date |
358 / 359 | Header | Scheduled for delivery on or after / on or before |
2 | Header | Requested delivery date |
361 | Line | Best before date |
36 | Line | Expiry date |
94 | Line | Production date |
QTY qualifiers
| Qualifier | Level | Meaning |
|---|---|---|
12 | Line | Despatch quantity |
21 | Line | Ordered quantity |
59 | Line | Consumer units in the traded unit |
121 | Line | Over shipped |
192 | Line | Free goods quantity |
52 | Package | Quantity per pack |
PAC, PCI and GIN codes
| Code | Meaning |
|---|---|
PAC+n++201::9 | n ISO 1 (Euro) pallets, GS1 code |
PAC+n++09::9 | n returnable pallets, GS1 code |
PAC+n++CT | n cartons |
PCI+33E | Marked with SSCC, as used in GS1's own DESADV examples |
PCI+39 | Marked with SSCC, as listed in the current segment code list |
GIN+BJ | Serial shipping container code |
GIN+BX | Batch number |
On 33E versus 39: the EANCOM 2002 manual's DESADV examples use 33E, while the segment's code list in the current edition gives 39. Partner guides specify which they expect, so follow theirs.
CNT qualifiers
CNT+2:n counts LIN segments and is the one nearly everyone uses. EANCOM also defines CNT+1 (total of line quantities), CNT+11 (total packages, the sum of every PAC package quantity in the message) and CNT+7 (total gross weight, the sum of line-level MEA gross weights). Because CNT+11 adds every PAC, including the consignment level, agree with the partner exactly what they expect before sending it.
Example 2: multi-pallet despatch with transport details
Three pallets for one order: two single-product pallets and a third carrying two products. TDT records road transport by truck.
Three pallets, each with its own SSCC
CPS+1 is the consignment of three pallets; CPS+2, +3 and +4 are the pallets, each with weight, SSCC and contents. Pallet 3 carries two GTINs.
DESADV · Despatch advice · ref 1
- Document
- Despatch advice
- Document number
- KV-DES-7795
- Message function
- Original
- Document/message date/time
- 2026-10-20
- Despatch date/time
- 2026-10-20
- Date (358)
- 2026-10-21
- Reference date/time
- 2026-10-14
- Order number (buyer)
- HL-PO-88371
- Packages
- 3
Parties
| Role | Identifier | Name and address |
|---|---|---|
| Supplier SU | 5098765000002GS1 (GLN) | - |
| Buyer BY | 5012345000008GS1 (GLN) | - |
| Delivery party DP | 5012345000107GS1 (GLN) | - |
Lines (4)
| # | GTIN | Codes | Description | Despatch quantity | Price | Amount |
|---|---|---|---|---|---|---|
| 1 | 5098765100047 | SSCC: 350987650000000058 | - | 160 | - | - |
| 2 | 5098765100054 | SSCC: 350987650000000065 | - | 240 | - | - |
| 3 | 5098765100047 | SSCC: 350987650000000072 | - | 80 | - | - |
| 4 | 5098765100054 | SSCC: 350987650000000072 | - | 120 | - | - |
Interchange (UNB)
- Sender
- 5098765000002GS1 GLN
- Recipient
- 5012345000008GS1 GLN
- Prepared
- 2026-10-20 05:40
- Control reference
- KVH000204
- Syntax
- UNOC version 3
- Messages
- 1
Points to notice:
- The same GTIN can appear on several pallets. GTIN 5098765100047 is on pallet 1 (160) and pallet 3 (80), as two separate LIN lines. The buyer adds them up to match the order line.
- Line numbers run through the message, 1 to 4, not per pallet. EANCOM recommends sequential numbering starting at 1 in each message.
DTM+358says delivery is scheduled on or after 21 October. Some partners use it instead ofDTM+17.TDT+20++30+31'is main carriage (20) by road (30) on a truck (31). Add the carrier GLN or the vehicle registration if your partner asks for them.
SSCC and GS1 labelling
The SSCC (Serial Shipping Container Code) is an 18-digit GS1 number that identifies one logistic unit, such as a pallet or a carton, for its whole journey. It is made of an extension digit, your GS1 company prefix, a serial reference you allocate, and a check digit. GS1 sets out the rules on its SSCC page.
The same SSCC appears in two places, and they must match:
- On the pallet, on a GS1 logistic label as a GS1-128 barcode with application identifier (00).
- In the DESADV, in
GIN+BJ+<SSCC>', under the CPS level for that pallet.
A few practical rules:
- Never reuse an SSCC. Each pallet or carton gets a new serial reference. The GS1 General Specifications say an SSCC must not be reallocated within one year of the shipment date, and industry or regulatory rules can extend that.
- Label what you describe. If the DESADV describes cartons inside the pallet with their own SSCCs, those cartons need their own labels too.
- Generate both from one source. Print the label and build the DESADV from the same shipment record. Typing an SSCC into one system and printing it from another is how mismatches happen.
For more on the identifiers, see our glossary entries on the SSCC, GS1-128 and GTIN.
Example 3: mixed pallet with SSCC-labelled cartons
When a pallet is built from cartons that the buyer will break down and send on (to stores, for example), the buyer needs each carton's SSCC as well as the pallet's. That is a three-level tree: consignment, pallet, cartons.
One pallet holding three labelled cartons
CPS+2+1 is the pallet with its SSCC; CPS+3+2, +4+2 and +5+2 are cartons on that pallet, each with its own SSCC and contents.
DESADV · Despatch advice · ref 1
- Document
- Despatch advice
- Document number
- KV-DES-7801
- Message function
- Original
- Document/message date/time
- 2026-10-21
- Despatch date/time
- 2026-10-21
- Reference date/time
- 2026-10-16
- Order number (buyer)
- HL-PO-88390
- Packages
- 1
Parties
| Role | Identifier | Name and address |
|---|---|---|
| Supplier SU | 5098765000002GS1 (GLN) | - |
| Buyer BY | 5012345000008GS1 (GLN) | - |
| Delivery party DP | 5012345000107GS1 (GLN) | - |
Lines (3)
| # | GTIN | Codes | Description | Despatch quantity | Price | Amount |
|---|---|---|---|---|---|---|
| 1 | 5098765100016 | SSCC: 350987650000000096 | - | 12 | - | - |
| 2 | 5098765100016 | SSCC: 350987650000000102 | - | 12 | - | - |
| 3 | 5098765100030 | SSCC: 350987650000000119 | - | 24 | - | - |
Interchange (UNB)
- Sender
- 5098765000002GS1 GLN
- Recipient
- 5012345000008GS1 GLN
- Prepared
- 2026-10-21 06:00
- Control reference
- KVH000207
- Syntax
- UNOC version 3
- Messages
- 1
The parent numbers carry the structure: CPS+3+2' means "level 3, inside level 2", so each carton points at the pallet, and the pallet points at the consignment. A receiving system builds the tree from those numbers alone, so every parent must refer to a CPS level already sent in the message.
There is a lighter alternative, GS1's option 2 and 4 pattern: keep the pallet as the lowest CPS level and list the carton SSCCs under each line in a PCI/GIN group, for example GIN+BJ+<first SSCC>:<last SSCC>' for a range. It produces a shorter message but tells the buyer less about which carton holds what. Use whichever your partner's guide specifies.
Example 4: partial despatch against an order
This despatches order HL-PO-88231 after the supplier's ORDRSP confirmed 40 of the 60 salt and pepper mill sets, with 20 on backorder. The DESADV says exactly that.
Short despatch with backorder to follow
Line 2 ships 40 against 60 ordered: QTY+12 is what was despatched, QTY+21 what was ordered, and QVR+-20:21+BP records the 20 short with a backorder to follow.
DESADV · Despatch advice · ref 1
- Document
- Despatch advice
- Document number
- KV-DES-7781
- Message function
- Original
- Document/message date/time
- 2026-10-13
- Despatch date/time
- 2026-10-13
- Delivery date/time, estimated
- 2026-10-16
- Reference date/time
- 2026-10-11
- Order number (buyer)
- HL-PO-88231
- Packages
- 2
Parties
| Role | Identifier | Name and address |
|---|---|---|
| Supplier SU | 5098765000002GS1 (GLN) | - |
| Buyer BY | 5012345000008GS1 (GLN) | - |
| Delivery party DP | 5012345000107GS1 (GLN) | - |
Lines (2)
| # | GTIN | Codes | Description | Despatch quantity | Price | Amount |
|---|---|---|---|---|---|---|
| 1 | 5098765100016 | SSCC: 350987650000000010 | - | 120 | - | - |
| 2 | 5098765100023 | SSCC: 350987650000000027 | - | 40 | - | - |
Interchange (UNB)
- Sender
- 5098765000002GS1 GLN
- Recipient
- 5012345000008GS1 GLN
- Prepared
- 2026-10-13 06:40
- Control reference
- KVH000192
- Syntax
- UNOC version 3
- Messages
- 1
| Segment | What it says |
|---|---|
QTY+12:40' | 40 despatched |
QTY+21:60' | 60 were ordered |
QVR+-20:21+BP' | 20 fewer than ordered (21); partial shipment, backorder to follow (BP) |
Use CP instead of BP if the shortfall will not be sent later and the line should be closed. EANCOM also defines the reason WR (temporarily unavailable) in the fourth element. Line 3 of the order (the tea towels, promised for 19 October in the ORDRSP) is simply absent: it will travel on its own DESADV when it ships.
A DESADV must describe what is physically on the vehicle, not what was ordered. If you pick 40, the message says 40, even if your ERP still thinks 60 are allocated.
Other variations you will meet
Several orders in one delivery. The header RFF+ON can repeat, but then the buyer cannot tell which line belongs to which order. Put the order number on each line instead, in the line's reference group:
LIN+1++5098765100016:SRV'
QTY+12:120'
RFF+ON:HL-PO-88231'
Some partners require one DESADV per order instead. Check before you combine.
Best before and expiry dates. Food and health suppliers add dates under the line:
LIN+1++5098765100078:SRV'
QTY+12:96'
DTM+361:20270430:102'
DTM+361 is the best before date, DTM+36 expiry and DTM+94 production date. Batch numbers go in the line's package identification group as GIN+BX, in the layout your partner specifies.
Cancelling a DESADV. Send a new DESADV with BGM function 1 and the original despatch number in RFF, then the corrected one as an original. Or use function 5 (replace) if the partner supports it.
DESADV vs the X12 856
| Data | EDIFACT DESADV | X12 856 |
|---|---|---|
| Despatch / shipment number | BGM second element | BSN02 |
| Despatch date | DTM+11 | BSN03, or DTM*011 |
| Packing hierarchy | CPS level and parent | HL01 and HL02 |
| Level type | Implied by PAC content | HL03 (S, O, P, I) |
| Order reference | RFF+ON | PRF01 at order level |
| Pallet or carton ID | GIN+BJ (SSCC) | MAN*GM (SSCC-18) |
| Package count and type | PAC | TD1 |
| Weight | MEA+PD+AAB | TD1 weight elements |
| Carrier and mode | TDT | TD5 |
| Product | LIN with GTIN (SRV) | LIN with UP, EN, VN or other qualifiers |
| Despatched quantity | QTY+12 | SN102 |
| Ordered quantity and status | QTY+21 and QVR | SN105 and SN108 |
| Line count | CNT+2 | CTT01 |
The biggest conceptual difference is that the X12 856 normally has an explicit order level (HL*O) between shipment and pack. Many DESADV implementations carry the order reference once in the header RFF+ON, with one DESADV per order. If a single delivery covers several orders, check whether your partner wants one DESADV per order or line-level order references.
UK retailer DESADV requirements
The despatch advice is where UK retailers are strictest, because their depots book goods in by scanning the SSCC on each pallet against it. Confirm the current specification with each retailer during onboarding.
Tesco
- Send a despatch advice for deliveries into Tesco distribution centres before the goods arrive.
- Label every pallet with a GS1 logistics label carrying a unique SSCC that matches the despatch advice. The SSCC section earlier in this guide covers the label.
See the Tesco EDI requirements page.
Morrisons
- Morrisons has made advance shipping notices mandatory, sent as EDIFACT D96A DESADV.
- If an ORDCHG amended the order, the DESADV must reflect the amended quantities, so apply amendments before you pick.
See the Morrisons EDI requirements page.
Marks & Spencer
- Send an ASN for each delivery.
- Under self-billing, M&S raises the invoice from your ASN, so an error in the DESADV becomes an error in what you are paid. Our guide to self-billing (ERS) explains how that works.
See the Marks & Spencer EDI requirements page.
Sainsbury's
- Sainsbury's sets up advance shipping notices and proof of delivery per account. Requirements differ for suppliers delivering direct to depot and those delivering to a second-tier site such as a bonded warehouse.
See the Sainsbury's EDI requirements page.
Co-op and Boots (TRADACOMS)
The Co-op and Boots take ASNs in TRADACOMS rather than EANCOM DESADV. The Co-op publishes precise timings:
- Send the ASN no later than despatch, and make sure it is in Co-op's systems before the goods arrive.
- For chilled orders, send it before 02:00 on the day of delivery.
- For direct-to-store orders, send it before the delivery arrives and no later than 16:00 on the day of delivery.
- Label each pallet with an SSCC in a GS1-128 barcode, plus the product code, quantity, best-before or expiry date and batch code.
The TRADACOMS delivery notification file is DELHDR, the equivalent of DESADV. Don't confuse it with DLCHDR, the delivery confirmation the retailer sends back after receipt. The TRADACOMS file types reference lists both.
Common DESADV errors and how to fix them
| Problem | What happens | Fix |
|---|---|---|
| SSCC on the label does not match the message | Pallet booked in manually or refused | Print labels and build the DESADV from the same despatch record; scan each label at loading to confirm |
| Duplicate SSCC | The buyer's system rejects the second pallet or overwrites the first | Allocate serial references from one counter per company prefix, never reset |
| Invalid check digit | Scanners reject the label; the message fails validation | Calculate check digits in software, never type them |
| Wrong CPS parent | A carton points at a level that does not exist, and the tree breaks | Number CPS levels sequentially and check that every parent was already sent |
| Quantities that do not add up | Receiving discrepancy, RECADV query, then an invoice deduction | Send what was loaded, not what was ordered; use QVR for shortages |
| Sent too late | The DC cannot plan the delivery; some partners treat it as non-compliant | Send at despatch, before the vehicle arrives |
| Line on the wrong pallet | Store or DC stock records are wrong after cross-docking | Build lines from the pallet scan, not from the order |
| Missing or wrong order reference | The delivery cannot be matched to an order | Quote the BGM number of the ORDERS exactly in RFF+ON |
The EDIFACT inspector checks UNT, UNZ and CNT counts, and validates every SSCC and GTIN check digit, before your partner's system does.
Testing and onboarding checklist
- Confirm the hierarchy level the partner expects (GS1 option 1 to 4), and whether cartons need their own SSCCs.
- Confirm the codes:
PCI+33EorPCI+39, pallet type codes inPAC, and whichDTMqualifiers are mandatory. - Confirm timing: how long before arrival the DESADV must be received.
- Confirm one DESADV per order, per delivery, or per vehicle.
- Set up SSCC allocation from your GS1 company prefix, with a single counter and no reuse.
- Print test labels and test messages from the same record, scan the labels, and compare every SSCC with the message.
- Test the variations in this guide: single pallet, multi-pallet, mixed pallet, short shipment, and a cancellation.
- Reconcile to the invoice: the quantities in the DESADV should be the quantities on the INVOIC, which quotes the DESADV number.
Frequently Asked Questions
What is the difference between DESADV and ASN?
They describe the same business document. ASN (advance ship notice) is the common US name and the X12 856 is its format. DESADV is the UN/EDIFACT despatch advice message used in the UK, Europe and elsewhere. Both tell the buyer what was shipped, how it is packed, and how each pallet or carton is identified.
What does BGM+351 mean?
351 is the UN/EDIFACT document name code for a despatch advice. The second element is your despatch number and the third is the message function, usually 9 for an original.
What does CPS mean in DESADV?
CPS is the consignment packing sequence segment. Each CPS opens a level of the packing hierarchy and gives its own level number and its parent's level number, so a message can describe consignment, pallets, cartons and items as a tree.
What does GIN+BJ mean?
GIN is the goods identity number segment and BJ is the qualifier for a Serial Shipping Container Code. GIN+BJ+350987650000000010' says the package described at this CPS level carries that SSCC.
Does a DESADV need a UNS segment?
No. The EANCOM DESADV structure has no UNS. The last LIN group is followed directly by CNT and UNT. Adding a UNS can cause a partner's parser to reject the message.
Can one DESADV cover several purchase orders?
Yes, if the partner allows it. Put each order number on its lines in RFF+ON rather than relying on the header. Many partners require one DESADV per order, so check the implementation guide.
Is DESADV the same as a delivery note?
It does the same job as a paper delivery note, electronically and in advance. In TRADACOMS, the older UK standard, the equivalent is the delivery notification file. See TRADACOMS file types.
What comes after DESADV?
The buyer may send RECADV, the receiving advice (X12 861), to report what arrived. You then bill with INVOIC, quoting the DESADV number.
Related guides
- EDIFACT explained: syntax, envelopes and the X12 mapping
- EDIFACT message types: the full catalogue
- EDIFACT ORDERS and ORDRSP: the order and response before despatch
- EDIFACT RECADV: what the buyer received
- EDIFACT INVOIC: the invoice that follows
- EDI 856 ship notice: the X12 counterpart and its HL hierarchy
Sources
- EANCOM 2002 S3: DESADV despatch advice message, GS1 (structure, principles, examples and code lists)
- EANCOM 2002 S3: DESADV introduction, GS1 (the four levels of hierarchy detail)
- EANCOM 2002 S3: DESADV CPS segment, GS1
- Serial Shipping Container Code (SSCC), GS1
- UN/EDIFACT D.01B DESADV message, UNECE
Check your DESADV hierarchy, counts and SSCC check digits in the free EDIFACT inspector.