What Is EDI in Fulfilment? A Plain-English Guide for Brands Supplying UK Retailers

‍EDI in fulfilment is the exchange of standard electronic messages between a retailer and its supplier (purchase orders, despatch advice, receipt confirmations and invoices) so that every order, delivery and payment is recorded without manual keying. For a brand supplying UK retailers, the warehouse's job is to make the physical delivery match those messages exactly. That is the work Fulfil with Synergy's retail and wholesale fulfilment service is set up to do.

GS1 UK defines EDI as "the interchange of structured data according to agreed message standards, by electronic means" (GS1 UK, EDI Guidance: the bigger picture).

‍

Two standards matter in UK retail. EDIFACT is the UN standard, and most retailers use GS1's EANCOM subset of it. TRADACOMS is the older UK standard, introduced in 1982 and still found in grocery. GS1 UK stopped supporting TRADACOMS in 2017 and advises new users to adopt EANCOM (GS1 UK), yet EDI providers such as TrueCommerce still run TRADACOMS links for Tesco, Asda and Morrisons suppliers. Your retailer tells you which one it uses.

The five EDI messages a retail supplier actually meets

Most UK retail suppliers deal with five core messages: the order, the order response, the despatch advice (ASN), the receipt advice and the invoice. The EANCOM names below come from GS1's EANCOM message list; TRADACOMS file names come from TrueCommerce's TRADACOMS reference.

‍

The purchase order travels from the retailer to the supplier when the retailer's replenishment system or buyer raises an order. Its EDIFACT (EANCOM) name is ORDERS, and its TRADACOMS name is ORDHDR (Order).

‍

The order response travels from the supplier to the retailer when the supplier accepts, amends or declines order lines, usually according to available stock. It is called ORDRSP in EDIFACT (EANCOM) and ACKHDR (Acknowledgement) in TRADACOMS.

‍

The despatch advice, or ASN, is sent by the supplier to the retailer once goods have been picked, packed and labelled, before the vehicle leaves. Its EDIFACT (EANCOM) name is DESADV, and its TRADACOMS name is DELHDR (Delivery note).

‍

The receipt advice travels from the retailer to the supplier when the retailer's distribution centre scans in the delivery and records any shortages. It is called RECADV in EDIFACT (EANCOM) and DLCHDR (Delivery confirmation) in TRADACOMS.

‍

The invoice travels from the supplier to the retailer at despatch or, for some retailers, after confirmed receipt. Its EDIFACT (EANCOM) name is INVOIC, and its TRADACOMS name is INVFIL (Invoice).

‍

Not every retailer uses all five. Some skip the order response; some never send a receipt advice and simply deduct for shortages on the remittance. The ASN is the one that touches the warehouse most directly, because it describes the physical delivery: pallets, cases, quantities and order references. GS1 UK notes that invoices can then be matched three ways (order, ASN, invoice) or four ways (adding the receipt advice).

Walk one retailer purchase order through EDI

A single retail purchase order generates at least three EDI messages, and the warehouse's data feeds the most important one. Take a beauty brand supplying a high street chain.

‍

On Monday morning the retailer's system sends an ORDERS message for 1,200 units across eight SKUs, for delivery to its Midlands DC on a stated date. The message lands with the brand's EDI provider, which translates it and passes it into the brand's ERP or order system. The brand checks stock and sends an ORDRSP confirming 1,140 units, because one SKU is short.

‍

The brand's system then releases the confirmed order to its 3PL as a wholesale order. The warehouse picks to the case and pallet configuration the retailer requires, prints the labels, builds and wraps the pallets, and books the delivery slot. Once despatch is confirmed, the warehouse sends back exactly what left: quantities per SKU, batch numbers, carton counts and pallet identifiers.

‍

That despatch data becomes the DESADV, which reaches the retailer before the vehicle does. At the DC, goods-in scans each pallet's SSCC barcode and checks it against the ASN. If everything matches, a RECADV (where used) confirms receipt and the INVOIC is paid against it. If anything differs, the difference becomes a query, a deduction or a rejected load.

Where your 3PL sits in the EDI chain

Your 3PL sits between the order and the ASN: it receives the order from your system and returns the despatch facts that your ASN is built from. In most set-ups the 3PL does not talk to the retailer at all. The data flow looks like this:

‍

1. Retailer to EDI provider: ORDERS arrives in EDIFACT or TRADACOMS format.
2. EDI provider to brand ERP or order system: the message is translated into the brand's own order format.
3. Brand system to 3PL: the order is sent to the warehouse by API, SFTP flat file or SOAP web service.
4. 3PL back to brand system: despatch confirmation with line quantities, batches, cartons, pallets and label references.
5. Brand system to EDI provider to retailer: the DESADV and INVOIC are generated and sent.

‍

This is why EDI is often run through a specialist provider rather than built by the brand or the warehouse, a point covered in more depth in our guide to choosing between API, SFTP and EDI. The 3PL's responsibility is data quality: if the warehouse sends back the wrong carton count, the ASN is wrong, whoever transmits it.

‍

The judgement call for a brand is where to put the translation. Brands on NetSuite, SAP or Microsoft Dynamics usually let the ERP hold the EDI connection and pass orders to the 3PL. Smaller brands with one or two retail accounts often use an EDI provider's web portal and send orders to the warehouse by SFTP file. Both work if the despatch data comes back in a structure the ASN can use.

EDI mistakes that turn into retailer fines

Most EDI penalties come from a mismatch between the ASN and what physically arrives, not from the EDI software itself. Retailer supplier manuals set their own charges, so check yours, but these are the errors that recur.

‍

• ASN quantities that do not match the delivery. If the despatch advice says 48 cases and the DC counts 46, the retailer will query or deduct. This usually starts with a warehouse confirming the planned quantity rather than the scanned quantity.
• SSCC on the label not matching the SSCC in the DESADV. GS1 UK notes that SSCCs on pallet labels "can be matched to those in the ASN message to provide a cross-check on the actual goods delivered" (GS1 UK). A reprinted label with a new number breaks that check.
• ASN sent late or not at all. The DESADV is meant to arrive before the goods. Some DCs will not receipt a delivery without it.
• GTIN or product code errors. A barcode on the case that differs from the product code in the order means lines fail to match, even when the stock is correct.
• Order changes not passed through. An amended or cancelled order that reaches the retailer but never reaches the warehouse ships the wrong goods against a valid ASN.
• Booking and delivery date failures. The data can be perfect and the load still refused for a missed slot or wrong pallet height, which is why it is worth reading why wholesale deliveries get rejected at the DC.

How Fulfil with Synergy supports retail EDI flows

Fulfil with Synergy supports retail EDI flows by integrating with the brand's ERP or EDI provider through API, SFTP or SOAP, and by producing the scanned despatch data and retail-compliant deliveries that a correct ASN depends on. Fulfil with Synergy is a founder-led UK 3PL and growth partner for ambitious, fast-growing consumer brands, operating a technology-led fulfilment centre in Northampton for health, wellness, beauty, supplement and lifestyle brands across D2C, marketplace, retail and wholesale channels.

‍

Integration built by an in-house team. Fulfil with Synergy is API-first, with flat-file SFTP and SOAP web services alongside, and integrates with NetSuite, SAP, Microsoft Dynamics, Sage, Unleashed and bespoke systems. Retail orders arrive through the same connection as D2C and marketplace orders, drawing on one stock pool. The in-house integration team maps the despatch confirmation to the fields your EDI provider needs, and tests it jointly during the Build and Test phases of an 8 to 10 week onboarding, before any live retail order ships.

‍

Despatch data from scans, not plans. RedPrairie Dispatcher WMS records stock to unit, SKU, batch and location, with a time-stamped audit trail of every movement. What goes back to your system is what was scanned at pick and pack, which is the basis of an accurate DESADV.

‍

Retail-grade pick, pack and labelling. The retail team picks at unit, case and pallet level, prints barcodes and box-end labels in house, and handles re-labelling and re-ticketing when a retailer's requirements change. Fulfil with Synergy's site is ethically audited and SOP compliant with most high-street retailers, and account managers work to retailer RDD dates, delivery and packaging requirements. You can see how Fulfil with Synergy's technology and automation fit together, including the 57,000-tote AutoStore grid with 99.99% pick accuracy.

‍

Evidence under retail pressure. In Hello Bubble's kit programme, the requirement grew within days of signing to 400,000 kits across 8 variations plus 2 million individual units, with sizeable shipments into Boots, ASOS and Amazon. The team designed the programme within hours, recruited and onboarded 30 new colleagues in a week and staggered production over 10 weeks as SKUs and packaging arrived.

‍

People who pick up the phone. Every client has a named Client Manager and a Client Support Specialist on the floor, with escalation to the Head of Operations, the COO and Gary Rees personally. When a retailer queries an ASN, the person who can check the pallet is a call away.

FAQ

Do I need EDI to sell to UK retailers?

Most large UK retailers expect suppliers to trade by EDI for orders, despatch advice and invoices, and many make it a condition of listing. Smaller retailers and independent stockists often accept email or portal orders instead. Your retailer's supplier manual or onboarding pack will state the standard, the messages required and any approved EDI providers. If you only have one retail account, a web-based EDI service from a provider is usually enough to start, with orders passed to your 3PL by file or API.

What is the difference between EDIFACT and TRADACOMS?

EDIFACT is the international UN standard for EDI, and EANCOM is the GS1 subset most retailers use. TRADACOMS is a UK standard from 1982 that GS1 UK no longer supports, though some UK grocers still trade on it. The messages do the same jobs (orders, despatch, invoices) with different names and formats. Your EDI provider handles the translation, so your 3PL works with the same order data whichever standard the retailer uses. If you supply both a grocer and a department store, expect to run both standards side by side through one provider.

Is an ASN the same as a DESADV?

Yes. DESADV is the EDIFACT name for the despatch advice, which UK retailers and warehouses usually call the advance shipping notice or ASN. It tells the retailer what is on its way before the vehicle arrives: SSCCs, pallets, cases, quantities and order references. In US standards the same message is the 856. The ASN is built from your warehouse's despatch confirmation, so its accuracy depends on the warehouse sending back scanned quantities rather than ordered quantities. A late or inaccurate ASN is one of the most common causes of retailer queries.

Can a 3PL send EDI messages to my retailer directly?

Some 3PLs connect to retailers directly, but in most UK set-ups the brand's EDI provider or ERP owns the retailer connection and the 3PL feeds it. That keeps invoicing and pricing with the brand while the warehouse supplies despatch facts. Fulfil with Synergy integrates with brands' systems by API, SFTP and SOAP and returns despatch data for ASNs. Ask any 3PL to show you a sample despatch file with carton and pallet detail before you sign, and check your EDI provider can map every field it needs from that file.

How do I see what my 3PL has despatched against each retail order?

A good 3PL gives you live order status, despatch confirmation and tracking for every wholesale order, not just a weekly report. Fulfil with Synergy's 24/7 client portal shows order status, inbound ASN status, live inventory and custom reports, with data also available by API, SFTP or flat file. That lets your team answer a retailer query quickly, with batch, carton and despatch time to hand rather than waiting on an email from the warehouse. There is more on what a fulfilment client portal should show you.

EDI in fulfilment comes down to one rule: the messages your retailer receives must describe exactly what your warehouse sent. The EDI provider handles the format; your 3PL handles the facts behind it. Fulfil with Synergy brings an in-house integration team, RedPrairie Dispatcher WMS data and a retail-trained team to that job, so your ASNs match your deliveries.

‍

If you are setting up your first retail account or tidying up an existing one, talk to the Fulfil with Synergy team about your retail EDI flows.

‍