EDIFACT DESADV explained: SSCC, GLN in NAD+DP and why retailers reject your despatch advice
An EDIFACT DESADV with an SSCC on every pallet and a GLN for every party is what a retailer's warehouse expects before the truck arrives. This guide walks through a complete DESADV D96A message, shows where the SSCC and the GLN go, how to compute their check digits, and the six mistakes that get a despatch advice rejected.
What a DESADV is for
DESADV is the UN/EDIFACT despatch advice: the supplier sends it when the goods leave, so that the receiving warehouse knows what is coming, on which pallets, for which order. In retail, the message follows the GS1 EANCOM rules, and most retailer guides still use the D96A directory with the EANCOM 1997 subset, which shows in the message header as DESADV:D:96A:UN:EAN005. In North America the same document is the X12 856 ship notice, often called an ASN.
The warehouse scans the SSCC barcode on each pallet label and looks for that number in the DESADV it received. If the number is there, the pallet is booked in with its contents without opening it. If the DESADV is missing, late, or does not contain the SSCC on the label, the pallet has to be checked by hand, and depending on the retailer's terms the message or the delivery can be refused. That is why a DESADV that is syntactically perfect can still be refused: the retailer reads its content, not only its envelope.
A complete DESADV D96A example, annotated
Two pallets for one order. Pallet A carries one article; pallet B carries two cartons with one article each. Every number is fictional, but every GLN, GTIN and SSCC has a valid GS1 check digit, and the file passes the EDI Reader check with no problem. One segment per line for reading; the apostrophe ends each segment.
UNA:+.? ' service string: : components, + elements, . decimal, ? release UNB+UNOA:2+5410738000008:14+5450534000000:14+260914:0730+12360' interchange: sender and receiver GLN (:14), date, time, reference 12360 UNH+1+DESADV:D:96A:UN:EAN005' message 1: DESADV, directory D96A, EANCOM subset EAN005 BGM+351+DES-2026-0311+9' 351 = despatch advice, number DES-2026-0311, 9 = original DTM+137:20260914:102' document date, format 102 (CCYYMMDD) DTM+11:20260914:102' despatch date DTM+17:20260915:102' estimated delivery date RFF+ON:PO-2026-0042' ON = the buyer's order number NAD+SU+5410738000008::9' supplier, GLN, 9 = GS1 code list NAD+BY+5450534000000::9' buyer, GLN NAD+DP+5450534000017::9' delivery party: the warehouse or store GLN CPS+1' level 1: the whole consignment PAC+2++201::9' 2 packages of type 201 (ISO 1 pallet, GS1 code) CPS+2+1' level 2, child of 1: pallet A PAC+1++201::9' PCI+33E' 33E = marked with an SSCC (GS1 code) GIN+BJ+354107380000000016' BJ = SSCC of pallet A (18 digits) LIN+1++3400935000019:EN' line 1: GTIN, EN = GS1 article number QTY+12:120:PCE' 12 = despatch quantity: 120 pieces CPS+3+1' level 3, child of 1: pallet B PAC+1++201::9' PCI+33E' GIN+BJ+354107380000000023' CPS+4+3' level 4, child of 3: carton 1 on pallet B PAC+1++CT' 1 carton PCI+33E' GIN+BJ+354107380000000030' LIN+2++3400935000026:EN' QTY+12:48:PCE' CPS+5+3' level 5, child of 3: carton 2 on pallet B PAC+1++CT' PCI+33E' GIN+BJ+354107380000000047' LIN+3++3400935000033:EN' QTY+12:24:PCE' CNT+2:3' 2 = number of line items: 3 LIN segments UNT+35+1' 35 segments from UNH to UNT included, message 1 UNZ+1+12360' 1 message, same reference as UNB
The header: who, when, for which order
BGM+351 says this is a despatch advice and gives its number; the retailer uses it to match corrections and duplicates. DTM+137 is the date of the message, DTM+11 the despatch date and DTM+17 the expected delivery date, all in format 102, eight digits, CCYYMMDD. RFF+ON carries the purchase order number the delivery answers. The three NAD segments identify the supplier (SU), the buyer (BY) and the delivery party (DP) by their GLN, each followed by ::9, which tells the receiver that the code comes from the GS1 list.
The CPS hierarchy: consignment, pallets, cartons
The detail section of an EANCOM DESADV always starts with CPS+1, the consignment level, even when no packing is described. Every following CPS has its own number and the number of its parent: CPS+2+1 is a pallet inside the consignment, CPS+4+3 is a carton inside pallet 3. Under each CPS come the package (PAC), its marking (PCI) and its identity (GIN), then the article lines (LIN and QTY) that sit in that package. A homogeneous pallet such as pallet A has its lines directly under the pallet; a mixed pallet such as pallet B has its lines under each carton.
PAC gives the number and type of packages: 201 is the GS1 code for an ISO 1 pallet (the 80 × 120 cm Euro pallet), which is why it is followed by ::9; CT is the UN code for a carton. On CPS+1, PAC+2++201::9 announces the two pallets of the whole consignment.
Read this file now
Copy the file below (the same example, without the notes), open the free online EDI viewer and paste it into “Or paste EDI text”. Each segment is named, NAD, CPS, PAC, PCI and GIN are explained element by element, and the check runs in your browser. Nothing is uploaded. Do the same with your own DESADV.
UNA:+.? ' UNB+UNOA:2+5410738000008:14+5450534000000:14+260914:0730+12360' UNH+1+DESADV:D:96A:UN:EAN005' BGM+351+DES-2026-0311+9' DTM+137:20260914:102' DTM+11:20260914:102' DTM+17:20260915:102' RFF+ON:PO-2026-0042' NAD+SU+5410738000008::9' NAD+BY+5450534000000::9' NAD+DP+5450534000017::9' CPS+1' PAC+2++201::9' CPS+2+1' PAC+1++201::9' PCI+33E' GIN+BJ+354107380000000016' LIN+1++3400935000019:EN' QTY+12:120:PCE' CPS+3+1' PAC+1++201::9' PCI+33E' GIN+BJ+354107380000000023' CPS+4+3' PAC+1++CT' PCI+33E' GIN+BJ+354107380000000030' LIN+2++3400935000026:EN' QTY+12:48:PCE' CPS+5+3' PAC+1++CT' PCI+33E' GIN+BJ+354107380000000047' LIN+3++3400935000033:EN' QTY+12:24:PCE' CNT+2:3' UNT+35+1' UNZ+1+12360'
Open the free EDI viewer online
Or install EDI Reader for VS Code, free, to read your files on your machine
Where the SSCC goes: PCI+33E and GIN+BJ
The SSCC (Serial Shipping Container Code) is the 18-digit number that identifies one logistic unit, one pallet or one carton, for its whole life. It is printed on the GS1 logistic label under the application identifier (00), and it must appear in the DESADV in the package group of that same unit:
CPS+2+1' pallet A, child of the consignment PAC+1++201::9' one ISO 1 pallet PCI+33E' 33E = marked with a serial shipping container code GIN+BJ+354107380000000016' BJ = SSCC; 354107380000000016 = the number on the label
An SSCC is built from an extension digit (3 here), the GS1 company prefix of the supplier (5410738 in this fictional example), a serial reference chosen by the supplier, and a check digit, 18 digits in all. Under the GS1 rules an SSCC is not reused for at least one year after the unit was shipped, so the same SSCC must never appear on two pallets of the same delivery, nor in two despatch advices for different goods.
How to compute the SSCC check digit (GS1 modulo 10)
Take the first 17 digits. From the right, multiply them alternately by 3 and by 1, so the 17th digit is multiplied by 3, the 16th by 1, and so on. Add the results. The check digit is the number that brings the total up to the next multiple of 10.
SSCC 3 5 4 1 0 7 3 8 0 0 0 0 0 0 0 0 1 | 6 weight 3 1 3 1 3 1 3 1 3 1 3 1 3 1 3 1 3 digits × 3: 3 + 4 + 0 + 3 + 0 + 0 + 0 + 0 + 1 = 11 → 33 digits × 1: 5 + 1 + 7 + 8 + 0 + 0 + 0 + 0 = 21 total 54, next multiple of 10 is 60 → check digit 6
The GLN: 13 digits for every party and the delivery point
The GLN (Global Location Number) identifies a company or a place: the supplier, the buyer, the invoicee, and above all the delivery party in NAD+DP, which is the exact warehouse, platform or store that will receive the pallets. A retailer with forty depots has forty GLNs; the DP tells its system which dock to expect the truck at. The GLN is the first element of NAD, followed by ::9.
A GLN has 13 digits, and its last digit is a check digit computed exactly like the SSCC one, on the first 12 digits. For the delivery point of the example, 545053400001 gives 4 + 0 + 3 + 0 + 0 + 1 = 8 times 3, that is 24, plus 5 + 5 + 5 + 4 + 0 + 0 = 19: total 43, so the check digit is 7 and the GLN is 5450534000017.
Why retailers reject a despatch advice, and how to fix each case
The wording of a rejection depends on the retailer: an APERAK message (the EANCOM application error and acknowledgement), a line in a supplier portal, or an e-mail. A syntax error in the envelope often comes back first in a CONTRL. These are the reasons that come back most often for DESADV, with the fix.
1. SSCC missing on a pallet
Typical reason: the scanned SSCC is not found in the despatch advice, or a package group has no SSCC. Cause: a CPS with its PAC but no PCI+33E and GIN+BJ, often when the warehouse system prints the label after the DESADV is generated. Fix: generate the DESADV after labelling, from the SSCCs actually printed, one GIN+BJ per labelled unit.
2. The same SSCC twice
Typical reason: duplicate SSCC. Cause: a label run that restarted its serial reference, or a pallet re-sent in a second DESADV. Fix: keep the serial counter in one place and never reset it; to correct a despatch advice, follow the replacement rule of the retailer's guide instead of reusing an SSCC for other goods.
3. An SSCC of 17 digits instead of 18
Typical reason: SSCC invalid or wrong length. Cause: the extension digit or the check digit dropped by a mapping that stores the SSCC as a number, or the (00) application identifier stripped the wrong way. Fix: store and send the SSCC as text, always 18 digits, and recompute the check digit before sending.
GIN+BJ+54107380000000016' ← wrong: 17 digits, extension digit lost GIN+BJ+354107380000000016' ← right: 18 digits, check digit 6
4. No GLN for the delivery party
Typical reason: unknown delivery point, or NAD+DP missing. Cause: the delivery address sent as text (NAD+DP++…+name+street) instead of the GLN taken from the order, or a GLN with a wrong check digit. Fix: copy the DP GLN from the ORDERS message you are answering, with ::9, and keep the name and address only if the retailer's guide asks for them.
5. Package counts that do not add up
Typical reason: the number of packages does not match. Cause: PAC+2++201::9 on CPS+1 while the hierarchy lists three pallets, or QTY lines whose total differs from what was ordered and labelled. PAC counts packages, QTY counts articles: a pallet of 120 pieces is PAC+1 and QTY+12:120. Fix: build PAC from the labelled units and QTY from the picked quantities, then compare the totals before sending.
6. A date outside format 102, or a UNT that miscounts
Typical reason: invalid date, or segment count error. Cause: DTM+11:14.09.2026:102 declares format 102 but carries a European date; UNT+34 after a pallet was added by hand. Fix: format 102 is exactly eight digits, 20260914; use 203 (CCYYMMDDHHMM) if the retailer asks for a time. UNT counts every segment from UNH to UNT included: 35 in the example.
DTM+11:14.09.2026:102' ← wrong: not CCYYMMDD DTM+11:20260914:102' ← right UNT+34+1' ← wrong: 35 segments from UNH to UNT UNT+35+1' ← right
EDI Reader Pro reports the segment count on the trailer (“Message trailer declares 34 segment(s), 35 counted.”), a missing BGM, DTM or LIN, a DESADV with no despatch or delivery date (DTM 11, 17, 2 or 35), and a line without a despatch quantity QTY+12. It does not compute SSCC or GLN check digits and does not know which parties your retailer requires: those are rules of your partner's guide.
More EDI errors explained: counts, control numbers, CONTRL and 997
Your retailer's guide has rules this page can't know
A checker built for your partner's guide: it flags every DESADV whose NAD+DP has no GLN or whose pallets have no SSCC, with the segment and the line. Fixed price per work package (see the offer page), delivered in 5 working days, refunded if it does not do what was agreed in writing.
Online validators, EDI providers and EDI Reader: an honest comparison
- Generic online EDIFACT validators check the syntax against a UN directory: segment order, mandatory elements, lengths. They are a good first pass; read their privacy terms first, since many work by upload, and a DESADV contains your customers' GLNs and your volumes.
- Your EDI provider or the retailer's portal validates against the retailer's own rules. It is the reference, but you usually learn about the problem after the message has been sent, sometimes after the truck has arrived.
- EDI Reader reads the file on your machine, in VS Code or in the browser, names every segment and runs a generic check by message type. It does not replace the retailer's guide and does not compute SSCC or GLN check digits; a checker for those rules is what the custom work package builds.
Frequently asked questions
What does DESADV mean?
DESADV is the UN/EDIFACT despatch advice message: the supplier's notice that goods have been sent, with the order they answer, the parties, the packages and their contents. The X12 equivalent is the 856 ship notice, often called an ASN.
What is the SSCC in an EDIFACT DESADV?
The SSCC is the 18-digit Serial Shipping Container Code that identifies one pallet or carton. In an EANCOM DESADV it sits in the package group of that unit: PCI+33E, then GIN+BJ followed by the 18 digits printed on the GS1 logistic label.
What is DESADV D96A?
A DESADV built on the D96A release of the UN/EDIFACT directory. Retail guides based on EANCOM 1997 use it with the subset code EAN005, which appears in the header as UNH+…+DESADV:D:96A:UN:EAN005. Your partner's guide says which directory and subset it expects.
How does SAP send a DESADV?
SAP sends the outbound delivery as an IDoc with message type DESADV and a DELVRY basic type such as DELVRY03. That IDoc is not the EDIFACT file: an EDI converter or the EDI provider maps it to DESADV D96A. When a retailer rejects the message, open the EDIFACT file that was actually sent, not the IDoc.
Is a DESADV the same as an ASN?
In practice, yes: both announce a shipment before it arrives. ASN (advance ship notice) is the usual name in North America, where it is an X12 856; DESADV is the EDIFACT message used in Europe and by most EANCOM retailers.
Is there a free EDIFACT validator or checker online?
The free EDI Reader viewer reads an EDIFACT file in your browser without uploading it, names every segment and runs a generic check for DESADV, ORDERS and INVOIC: segment counts, references, mandatory segments, despatch date. Check digits and retailer-specific rules need the partner's guide.
EDI Reader Pro: every problem on its segment, in VS Code
The free version names every segment and code of your DESADV, ORDERS, INVOIC and X12 files, on your machine. Pro shows each problem on its segment, checks whole folders, saves an HTML report and exports to CSV and JSON. EUR 24.17 + VAT where applicable, one-off purchase, up to 5 machines, refund within 14 days.