EDI connectivity with European retail chains
EDI connectivity with a retail chain rarely fails due to the format; the root causes are master data issues: incomplete GTIN codes, unit of measure discrepancies and unmapped delivery addresses. Pre-mapped workflows cover orders, despatch advice and invoices, completing the full cycle.
10
retail chains with pre-mapped workflows
3
messages covering the full cycle: order, notice, invoice
230+
integrated courier firms for delivery
35+
countries covered by the courier network
Collection methodology
- The study is based on EDI workflows implemented and running in production for suppliers delivering to major retail chains.
- For each chain, we documented the required messages and the master data that needs cleansing before the first electronic delivery.
- We do not publish volumes or client names; we publish workflow structures and rejection causes, as these are useful to any supplier.
The three messages that make the difference
Electronic orders eliminate manual data entry. Despatch advice sent before the goods arrive speeds up receiving at the retailer's warehouse. The electronic invoice closes the cycle and reduces disputes over discrepancies.
| Message | Direction | Purpose |
|---|---|---|
| Order | Retailer to supplier | Imported directly into the CRM, eliminating manual entry and quantity errors |
| Despatch Advice | Supplier to retailer | Faster receiving, matching by pallets and logistic units |
| Invoice | Supplier to retailer | Correlates with the order and advice; also complies with national tax authority e-invoicing |
Why the first electronic delivery often fails
In almost all cases, the cause lies in the master data, not the connection. Retailer product codes are not mapped to supplier items, units of measure differ between pieces and cases, and delivery points lack unique identifiers.
Practical conclusion: cleansing the master data before connection shortens the project more than any subsequent technical optimization.
| Cause | Remedy |
|---|---|
| Product code not mapped to retailer code | Correspondence table between supplier and retailer items, maintained in the CRM |
| Different units of measure | Defining conversion factors (piece - case - pallet) at the item level |
| Delivery point without identifier | Location master data with unique identifiers for every store or warehouse |
| Price discrepancies vs contract | Contractual price list validated before the invoice is issued |
Frequently asked questions
How long does it take to connect with a chain where the workflow is already mapped?
The technical phase is short because the messages already exist. Real time is spent on master data cleansing and the testing required by the retailer.
Does EDI replace statutory e-invoicing?
No. The invoice to the retailer can travel via EDI, while the legal obligation to the national tax authority is handled separately via XML RO_CIUS.
Next
Data may be cited freely, provided CRMconnect is credited with a link to this page. Last updated: 2026-09-05