EDI onboarding with a new retail partner: the brand-side checklist
Before the first electronic purchase order arrives, a brand has to agree documents, identifiers, transport and tests with the retailer. This checklist covers each step and the usual failure points.
KEY TAKEAWAYS Summary by the editors
- EDI onboarding with a retailer is a project with a deadline: Nordstrom, for example, expects suppliers to be EDI enabled within 60 days of initial setup.
- The core document set for a wholesale fashion account is usually the purchase order, the order response, the despatch advice (ASN) and the invoice, plus technical acknowledgements.
- Clean master data, meaning GTINs per size and colour, location codes and agreed prices, causes more onboarding delays than the EDI connection itself.
- Testing should use real assortment data, including split deliveries, size runs and cancellations, not a single clean sample order.
- AI tools can help read retailer specifications and pre-check test files, but sign-off on mappings and compliance rules should stay with a named person.
EDI onboarding with a new retail partner means agreeing which electronic documents you exchange, in which standard and version, over which transport channel, with which identifiers, and then proving it works in tests before live orders flow. For a fashion brand the work is mostly on its own side: master data, ERP mappings and warehouse processes have to match the retailer's specification. The checklist below follows the order in which most onboarding projects run.
What does a retailer expect from a brand during EDI onboarding?
Large retailers publish supplier requirements and expect brands to meet them on a timeline. Nordstrom's supplier compliance programme, as summarised by SPS Commerce in June 2025, requires suppliers to be EDI enabled within 60 days of initial setup, either in house or through a third party tested through the retailer's chosen compliance service. The required documents named there are the 850 purchase order, 856 advance ship notice, 810 invoice and 997 functional acknowledgement, which are the ANSI X12 formats used in North America.
European department stores and specialist chains more often use EANCOM, the GS1 subset of UN/EDIFACT. GS1's EANCOM 2002 manual lists the equivalent messages, among them ORDERS (purchase order), ORDRSP (purchase order response), DESADV (despatch advice) and INVOIC (invoice), together with CONTRL and APERAK for syntax and application acknowledgements. The first job of onboarding is to obtain the retailer's implementation guide and confirm exactly which of these it uses, in which version, and which segments it treats as mandatory.
Which documents and data should a brand confirm first?
Before anyone writes a mapping, the commercial and data teams should agree the following with the retailer's buying and supply chain contacts.
- Document scope: which messages are in scope from day one (order, order response, despatch advice, invoice) and which come later (sales and inventory reports, price catalogues).
- Standard and version: X12 or EANCOM, the exact version, and any retailer-specific profile or industry recommendation it follows.
- Party and location identifiers: the codes for the retailer's buying entity, invoicing address, distribution centres and stores, usually GS1 Global Location Numbers, and your own supplier identifiers.
- Product identifiers: a GTIN for every size and colour, and how the retailer's own article numbers map to yours.
- Prices and terms: which price (net, gross, retail) the retailer sends on the order and which you must return on the invoice.
- Order change rules: whether the retailer accepts order responses that change quantities, dates or substitutions, and within what deadline.
- Logistics rules: carton labelling, packing per store or per size, and how logistic units are identified.
In fashion, the product identifier point is where projects stall. A retailer cannot process an order line for a size that has no GTIN in its system, and a brand that assigns barcodes late in the season will see rejected lines rather than a failed connection.
How should the technical connection be set up?
The transport layer decides how files physically travel. Common options are a value added network or EDI service provider, a direct point to point link, or a retailer portal for low volume suppliers. AS2, defined in the IETF's RFC 4130, sends EDI and other business data over HTTP with digital signatures, encryption and signed receipts (MDNs), which give both sides proof that a file was delivered. Whatever the channel, agree certificates, test and production endpoints, file naming and who monitors failed transmissions outside office hours.
| Workstream | Main questions | Typical owner |
|---|---|---|
| Commercial scope | Which documents, which ship-to locations, start date | Key account manager |
| Master data | GTINs, location codes, price lists, size scales | Product data or PIM team |
| Mapping | Retailer fields to ERP fields, both directions | IT or EDI provider |
| Transport | AS2, network provider or portal, certificates | IT |
| Logistics | Carton labels, packing rules, ASN timing | Warehouse or 3PL |
| Finance | Invoice content, tax data, deduction handling | Accounts receivable |
How do you test EDI with a retailer before going live?
Testing usually runs in two rounds. In the first, files are checked for syntax and structure against the retailer's specification, and the retailer's system returns technical acknowledgements. In the second, scenario tests check that the content is right: the order arrives in the ERP with the correct customer, delivery address and size lines; the order response reflects real availability; the despatch advice matches what was packed; the invoice matches the order and the delivery.
Brands get better results when test orders look like real fashion orders. That means multiple delivery windows, store-specific packing, partial deliveries, a cancelled line and a back order, not a single tidy order with three items. Ask the retailer which scenarios have caused problems with other suppliers; most will say.
What goes wrong after go-live, and how do you prevent it?
Most problems after go-live are process problems that the connection simply makes visible. Typical examples are warehouse staff overriding packing rules under time pressure, new colours being sold before GTINs are sent to the retailer, and order changes agreed by email but never sent as an EDI message. Nordstrom's requirements, for instance, ask that advance ship notices match both the shipment and the purchase order down to store and SKU level, which only works if picking and despatch data are captured accurately.
- Name an owner for the account's EDI flow on both sides and agree an escalation path.
- Monitor acknowledgements daily for the first weeks and treat any rejected file as urgent.
- Review the first invoices and any deductions line by line with the retailer.
- Re-test whenever the retailer updates its specification or you change ERP or warehouse systems.
How long does EDI onboarding take?
Timelines depend far more on data readiness and the retailer's test calendar than on technology. Where a retailer sets a deadline, as Nordstrom does with its 60 day expectation, plan backwards from it and secure test slots early. Brands that already have a mapped ERP and clean product data can often reuse much of an existing integration; brands connecting their first large account should budget for master data clean-up as a separate workstream.
Frequently asked questions
What EDI documents does a fashion brand need for a department store?
Most retailers start with the purchase order, purchase order response, despatch advice (ASN) and invoice, plus technical acknowledgements. In EANCOM these are ORDERS, ORDRSP, DESADV, INVOIC and CONTRL or APERAK; in X12, Nordstrom for example requires 850, 856, 810 and 997. Always confirm the exact list in the retailer's own guide.
Do I need my own EDI software to supply a retailer?
Not necessarily. Many brands use an EDI service provider or network that handles translation and transport, and some retailers offer web portals for small suppliers. What a brand always needs is accurate master data and an ERP or order system that can receive and send the agreed data.
What is AS2 in EDI?
AS2 is a protocol, defined in IETF RFC 4130, for sending EDI and other business documents over HTTP with encryption, digital signatures and signed delivery receipts. It is one of several transport options; the retailer's specification states which ones it accepts.
Why do EDI orders get rejected during onboarding?
Common causes are unknown product or location identifiers, missing mandatory fields, wrong message versions and prices that do not match the agreed list. In fashion, missing GTINs for specific sizes or colours are a frequent cause.
One edition every weekday morning. Read in five minutes. Free for industry professionals.
