Setting Up EDIFACT DESADV for Retailer ASNs

What a DESADV Actually Does (And Why Your Retail Buyer Won't Drop It)

If you ship pallets to a retailer or an automotive OEM in Europe, there's a good chance "send us a DESADV" showed up somewhere in your vendor compliance manual. A DESADV, short for despatch advice, is a structured message used to notify a trading partner that goods have been shipped, providing detailed shipment information enabling efficient receiving, validation, and reconciliation processes across supply chains. In plain terms: it's an electronic packing slip that arrives before the truck does.

EDICOM describes it well: DESADV is the most widely used message in logistics, used to notify the customer of the dispatch of goods by the logistics operator, or the manufacturer can send it to notify the logistics operator of stock supply. If you've worked with US retailers or came up on ANSI X12, the naming confusion is understandable. ASN is also known by the abbreviation DESADV or the term Despatch Advice when working with the EDIFACT standard, widely used in other regions of the world and mainly in Europe. Functionally, DESADV and EDI 856 serve the same purpose as advance shipping notices. DESADV is used globally under EDIFACT standards, while 856 is used primarily in North America under ANSI X12. Both provide shipment details, packaging hierarchy, and item-level data.

If you supply OEMs directly rather than retail DCs, don't be surprised to see a different acronym in the vendor portal. Comparable message types include VDA 4913 Delivery Note and VDA 4987 Dispatch Advice in the VDA standard, the German automotive industry's own format. Same job, different envelope.

What You Need Before You Touch a Mapping Tool

Don't open your EDI mapper yet. Get these five things lined up first, because half of DESADV project delays come from skipping this step and discovering mid-build that you're missing a piece.

• A live EDI connection to the trading partner, whether AS2 direct or through a VAN, already tested at the transport layer
• The partner's published implementation guide confirming the exact message version you need to build against, since commonly used EDIFACT DESADV versions include DESADV D96A, DESADV D97A, and DESADV D01B
• A GS1 SSCC number range assigned to your company, plus label printing hardware at pallet or carton level
• An ERP or WMS that can export delivery/shipment data in a structured format, whether that's SAP, Dynamics 365, Infor or something homegrown
• A sandbox or test queue with the trading partner or your VAN provider, because you will not get this right on the first production send

One thing that catches first-timers off guard: DESADV rarely travels alone. 3M's own implementation guide is blunt about it, stating that 3M EDIFACT DESADV works only on this standard guide/map thus cannot accommodate any customer-specific requirements. If a customer signs up to receive the transmission of EDI DESADV they must agree to send/receive the suite of EDI procure to pay transactions (ORDERS, ORDRSP, INVOIC and DESADV). Budget for the full set, not just the one message your logistics team cares about.

Building and Sending Your First DESADV: Step by Step

1. Read the partner's implementation guide cover to cover. Confirm the exact version (D96A, D97A, D01B, or an older D93A some retailers still run), and flag any country- or retailer-specific segment requirements before you map a single field. Retailers like EDEKA and REWE publish their own DESADV specifics, and they're not identical.
2. Configure your SSCC packaging hierarchy in ERP/WMS first. Every pallet and, where required, every carton needs a unique Serial Shipping Container Code generated and printed before you build the DESADV payload. The message describes packaging you've already created, not the other way around.
3. Map your shipment data to the required EDIFACT segments. The core skeleton you're building toward looks like this: UNH opens and identifies the message, BGM carries the dispatch advice number, DTM carries dispatch and delivery dates, NAD identifies the ship-from and ship-to parties, RFF references the purchase order and other documents, LIN lists line items, PAC and CPS describe the packaging hierarchy (pallet, inner, outer), PCI carries the SSCC itself, and UNT closes the message. A real-world fragment from a live DESADV shows the shape of it: UNH+00000000000039+DESADV:D:96A:UN' BGM+351+DES587441+9' DTM+137:20220425054813125:304' followed by RFF, NAD and CTA segments carrying order references and party details. If you're working from a generic EDI platform rather than EDIFACT natively, you'll recognize the same job under Message Type: MPC_ADVANCE_SHIP_NOTICE, EDIFACT Format: DESADV, with UNH02.1 Message type DESADV and UNH02.2 Message version number.
4. Connect your TMS or ERP to a mapping layer or platform that can trigger DESADV generation automatically. You've got options here: dedicated EDI middleware like SEEBURGER or EDICOM, retail-focused connectors like TrueCommerce, or a TMS/multi-carrier platform such as SAP TM, Alpega, Transporeon or Cargoson that already holds the shipment and packaging data from the booking step and can push it out as a DESADV without you re-keying anything.
5. Transmit a test message into the partner's test queue and read the response. This is where CONTRL and APERAK matter. CONTRL operates at the syntax level: as a technical acknowledgment, the CONTRL message indicates receipt of an interchange, and as a functional acknowledgment, it indicates acceptance or rejection of the received interchange, group, or message, with a list of errors. APERAK goes a layer deeper, into the business content: a message being first controlled at system level (CONTRL) to detect syntax errors and to acknowledge its receipt is then transmitted to the application process to be processed, and if an error is detected at the application level, which prevents its complete processing, an APERAK message is sent to the original message issuer giving details of the error(s) encountered. No CONTRL back means your interchange never arrived. A CONTRL but no clean APERAK means it arrived but the application rejected something, a wrong GTIN, a missing reference, a date in the wrong format.
6. Move to production and fire the DESADV at goods-dispatch, not at order creation. This sounds obvious until you see it done wrong. If the DESADV timestamp doesn't match the moment the truck actually left the dock, your retailer's receiving window calculations are off before the pallet even moves.
7. Set up a daily exception report for anything that comes back rejected. Someone on your logistics or EDI team needs to see failed sends before the retailer's receiving window closes, not the next morning.

The Failure Mode Nobody Warns You About: Payload vs. Pallet Mismatch

Here's the scenario that causes more chargebacks than any mapping error. The DESADV goes out clean, CONTRL comes back positive, APERAK shows no errors. Then the truck arrives and the warehouse scans a pallet that doesn't match what the DESADV said was on it. Maybe a carton got relabeled at the last minute. Maybe a pallet was rebuilt to fit a different truck configuration. Maybe someone swapped product due to a stock shortage and nobody updated the EDI payload.

This is exactly the gap Amazon's own vendor guidance warns suppliers about, instructing them to confirm SSCC labels match the physical cartons before resubmitting. When the labels don't match, the retailer's receiving system can't reconcile the scan against the advance notice, and you're back to manual counting, the exact problem DESADV exists to eliminate, except now it's a rush job at the dock with a driver waiting.

The fix is a pre-dispatch audit step: before you transmit, run a reconciliation between what your WMS physically picked and packed and what the DESADV payload says is on the truck. If they don't match, the DESADV doesn't go out. This single check stops more chargebacks than any amount of segment-level mapping precision.

How You Know It Actually Worked

Forget dashboards for a second. The real test is what happens at the retailer's dock. WHIZTEC puts it simply: the warehouse pre-books the inbound against the order, and on arrival scans the SSCC pallet labels to receive and put away without opening and counting every carton. That's the whole point. If your pallets are still getting opened and manually counted at the DC, your DESADV isn't doing its job yet, even if the EDI logs show green.

The second confirmation is the RECADV coming back. As EDICOM explains, the RECADV (Receiving Advice Message) is the confirmation notice of the order receipt, serving for the logistics operator or distributor to confirm to the manufacturer or supplier that they have received the merchandise and whether it corresponds or not to what was advised. Track two numbers going forward: your ASN accuracy rate (DESADV line items matching RECADV confirmed receipt) and dock-to-stock time at your major retail accounts. Both should move in the right direction within a few weeks of going live.

Where This Fits in Your Wider EDI Stack

DESADV sits downstream of IFTMIN, the transport instruction message that books the move, and alongside IFTSTA, which tracks it in transit. DESADV is the "what's actually in the box" message that closes the loop before invoicing even starts. Manually mapping all three from scratch, for every retailer, is the kind of work that eats a logistics team's calendar for a quarter. That's increasingly the pitch behind connectivity-focused platforms: Cargoson alongside SAP TM, Alpega, and Transporeon now generate DESADV payloads directly from booking and shipment data they already hold, so the EDI mapping work shrinks to configuration rather than a from-scratch build for every new trading partner you onboard.

Next Steps

Pull your top three retail or automotive trading partners' implementation guides this week and check which DESADV version each one actually requires, you'll likely find they're not all on D01B even if your internal spec assumes they are. Then confirm your SSCC range and label printer are production-ready before you build a single segment map. The mapping is the easy part. The SSCC discipline and the pre-dispatch reconciliation are what determine whether your retailer's warehouse actually trusts your advance ship notices six months from now.