Why do key accounts demand EDI order confirmations, and what do brands get wrong?
Large retailers expect an electronic order response for every purchase order. What the message does, why it matters to the buyer and the mistakes that cost brands money.
KEY TAKEAWAYS Summary by the editors
- An EDI order confirmation, called ORDRSP in the GS1 EANCOM standard and 855 in ANSI X12, tells the retailer which order lines the supplier accepts, changes or rejects.
- According to GS1, the ORDRSP message lets a supplier indicate acceptance of all, part or none of the buyer's order, and acknowledgements, confirmations and proposed amendments may be mixed within one message.
- Key accounts depend on confirmations because their allocation, store planning and open-to-buy are calculated from what the supplier has confirmed, not from what was ordered.
- Common mistakes include confirming everything automatically, sending confirmations late, confirming dates that production cannot meet and failing to send updates when quantities change.
- AI can help by predicting which lines are at risk before confirmation, but a confirmation must reflect real stock and production commitments.
Key accounts demand EDI order confirmations because their buying, allocation and finance systems need a machine-readable answer to every purchase order: which lines, quantities, prices and dates the supplier will actually deliver. Without that answer, the retailer plans with the ordered quantities and discovers the gaps only when goods arrive short or late. Brands most often get it wrong by treating the confirmation as a formality rather than a commitment.
What is an EDI order confirmation?
In electronic data interchange (EDI), the retailer sends a purchase order and the supplier replies with an order response. In the GS1 EANCOM standard, widely used by European retailers, this is the ORDRSP message; in the North American ANSI X12 standard it is the 855 purchase order acknowledgement.
GS1's documentation describes ORDRSP as the message a supplier uses to respond to a purchase order or an order change request. It can indicate acceptance of all, part or none of the buyer's order, propose amendments, and mix acknowledgements, confirmations and amendments within one message. Responses can be given at header level or for individual order lines.
| Step | EANCOM (GS1) | ANSI X12 | Purpose |
|---|---|---|---|
| Purchase order | ORDERS | 850 | Retailer orders items, quantities, prices and dates |
| Order change | ORDCHG | 860 | Retailer changes an existing order |
| Order response | ORDRSP | 855 | Supplier accepts, changes or rejects order lines |
| Despatch advice | DESADV | 856 | Supplier announces the shipment before it arrives |
| Invoice | INVOIC | 810 | Supplier bills the delivered goods |
Why do key accounts care so much about confirmations?
- Allocation and store planning: the retailer decides which stores receive what, based on confirmed quantities and dates.
- Open-to-buy: unconfirmed or rejected lines free up budget that the buyer can spend with another supplier.
- Warehouse planning: distribution centres schedule receiving capacity around confirmed deliveries.
- Automated matching: confirmed data is later matched against the despatch advice and the invoice; discrepancies trigger manual work or penalties.
- Supplier scorecards: large retailers measure suppliers on how closely deliveries match what was confirmed.
Retailer vendor manuals typically set deadlines for the confirmation. An EDI provider's guide to Target's requirements, for example, states that the 855 acknowledgement typically has to be sent within 24 to 48 hours, and names late or inaccurate advance ship notices among the most frequent causes of chargebacks. Each retailer's own manual is the binding reference.
Smaller retailers and independents rarely use EDI, but large department stores, chains and platforms usually require it. For a growing brand, the first key account that demands EDI often triggers a wider change: product data, GTINs and order processes must be brought to a standard that the retailer's systems can process automatically.
What do brands get wrong?
- Auto-confirming everything. Some brands send an automatic acceptance for every order line because it is easy. When stock or production later falls short, the retailer has planned with numbers that were never real.
- Confirming late. A confirmation sent after the retailer's deadline may be ignored or count against the supplier's scorecard.
- Confirming dates production cannot meet. Delivery dates are copied from the order instead of from supplier commitments.
- Not sending updates. When a factory delay or a quality issue changes quantities, no updated response is sent, so the retailer learns about it from the despatch advice.
- Master data mismatches. GTINs, colour codes or size codes in the confirmation do not match the retailer's article data, so lines fail to match.
- Ignoring partial responses. Systems that can only accept or reject a full order force all-or-nothing answers, although the standard supports line-level changes.
How can AI improve order confirmations?
AI does not replace the EDI message, but it can improve what goes into it. Practical uses include predicting which order lines are at risk of short delivery based on production status and supplier history, flagging purchase orders that deviate from the agreed price list or delivery window before they are confirmed, and suggesting substitutes or split deliveries for lines that cannot be met. Models that learn from past discrepancies between confirmed and delivered quantities can highlight where confirmations are systematically too optimistic.
The limit is the data. If production dates in the ERP are not updated, or stock is not reserved per order, no model can produce a reliable confirmation.
What does a good confirmation look like for fashion orders?
Fashion orders have characteristics that make confirmations harder than in many other sectors. A single purchase order can contain dozens of styles, each in several colours and a full size range, with different delivery windows. Pre-orders are placed months before production is complete, so the first confirmation is often provisional by nature.
A good practice is to send an initial response that acknowledges receipt and confirms what can be committed at that point, followed by updated responses when production dates are fixed. Each update should change only the affected lines, state the new quantity or date clearly and reference the original order, as the GS1 standard foresees. Size-level detail matters: confirming a style in full when two sizes will be short leaves the retailer with broken size runs in stores.
Brands should also agree with each key account how substitutions are handled. Some retailers accept a replacement colour or a split delivery if it is proposed in the response; others require a separate approval. Writing these rules down avoids disputes when goods arrive.
How should brands organise the confirmation process?
A robust setup generates the order response from an available-to-promise check, routes exceptions to a person within the retailer's deadline, and sends updated responses whenever confirmed quantities or dates change. Brands should monitor confirmation timeliness and the gap between confirmed and shipped quantities per key account, because that is how the retailer will judge them.
Frequently asked questions
What is an EDI 855?
The 855 is the purchase order acknowledgement in the ANSI X12 standard used mainly in North America. The supplier uses it to confirm, change or reject the lines of a retailer's 850 purchase order.
What is ORDRSP in EANCOM?
ORDRSP is the GS1 EANCOM purchase order response message. A supplier uses it to accept all, part or none of an ORDERS or ORDCHG message, and can propose amendments at header or line level.
What happens if a supplier does not send an order confirmation?
The retailer may plan with the ordered quantities, which leads to gaps in allocation when goods arrive short. Depending on the retailer's vendor manual, missing or late confirmations can also affect supplier scorecards or lead to penalties.
Should order confirmations be automated?
Generating them automatically is sensible, but they should be based on an available-to-promise check against stock and production, not a copy of the order. Exceptions should be reviewed by a person before the retailer's deadline.
One edition every weekday morning. Read in five minutes. Free for industry professionals.
