What to Do If Your Brand Fails a Major Supermarket’s EDI Compliance Test

How to Fix a Failed Supermarket EDI Test Before Launch

A failed EDI test close to a supermarket launch can affect plans that are already in motion.

The cause can sit within the EDI connection, but it can also be a product identifier, case configuration, message mapping, price, mandatory field or piece of retailer data that does not match between systems.

The retailer rejection provides the starting point. Identifying the failed transaction and the information responsible for it allows the right team to correct the issue before another test is submitted.

Where launch activity is already underway, any effect on stock, warehousing, first orders, delivery planning or invoicing also needs to be understood while the failure is being resolved.

Key Takeaways

  • A failed EDI test can be caused by the connection, message mapping or the data contained within the transaction.
  • Start with the retailer rejection and identify the specific transaction or field that failed before making changes.
  • Product identifiers, case configurations, units of measure, pricing and retailer data need to match the live supply arrangement.
  • If testing fails close to launch, stock, warehouse preparation, first orders, deliveries and invoicing may also need reviewing.
  • Different parts of the fix may sit with the EDI provider, retailer, customer administration, warehouse, logistics or finance team.

What Has Actually Caused the EDI Test to Fail?

Two EDI failures can produce the same result for the brand — a rejected retailer test — while requiring completely different fixes.

A purchase order may never reach the supplier because of a connection or routing problem.

Another transaction may transmit successfully but be rejected because the retailer cannot match the product information within it.

A dispatch message may fail because a required reference is missing. An invoice may contain a price or purchase-order reference that does not correspond with the retailer’s records.

We have worked with brands where an issue during retailer testing initially appeared to sit with the technical connection. The messages were moving correctly, but information within the transaction did not match the retailer setup.

The EDI provider could confirm that transmission was working. Customer administration and the underlying product information then needed to be reviewed before another transaction was sent.

The retailer rejection or error report should help narrow down where the problem sits.

Test Failure What May Need Checking Who May Need to Be Involved
Purchase order not received Connection, routing or supplier/retailer identifiers EDI provider and retailer
Message received but rejected Mapping, format or mandatory fields EDI provider and retailer
Product cannot be matched GTIN, retailer product code or master data Customer administration, commercial and EDI
Quantity does not match Case configuration, unit of measure or pack mapping Commercial, logistics and EDI
Dispatch information rejected Shipment references, quantities, dates or required fields EDI, warehouse and logistics
Invoice rejected PO reference, pricing, VAT information or mapping Finance, customer administration and EDI

Once the cause has been identified, the issue can be passed to the people responsible for that part of the transaction rather than asking several providers to review the complete setup.

What Should You Check After an EDI Test Fails?

Making several changes at the same time can make it harder to understand what caused the rejection.

A clear sequence keeps the response focused on the actual failure.

1. Check the exact retailer rejection

Start with the error information supplied by the retailer or EDI provider. Confirm which transaction failed and, where available, the specific field or reason for rejection. A general message that EDI has failed does not provide enough information to decide what needs changing.

2. Confirm whether the transaction was transmitted

Establish whether the message failed before transmission or reached the retailer and was then rejected. If it was never transmitted, the connection, integration or routing may need checking. If it reached the retailer, the issue may instead sit within the message format, mapping or data.

3. Check the information connected with the failure

Review the information involved in that transaction rather than reopening the complete retailer setup. Depending on the failure, this may include:

  • GTINs;
  • GLNs;
  • retailer product codes;
  • case configurations;
  • units of measure;
  • pricing; or
  • customer and delivery information.

4. Check the mapping and required fields

Compare the rejected transaction with the retailer’s requirements. The underlying information can be correct, but still fail if a required field is missing or has been mapped differently from the format expected by the retailer.

5. Compare the transaction with what will actually be supplied

The information being tested needs to match the live supply arrangement. If a case contains six units, the retailer setup, EDI transaction and warehouse configuration should all reflect six units. Delivery information should match the stock and quantities that will actually be dispatched. Prices and references should match the retailer agreement. Passing a test with information that differs from the physical operation can move the same problem into the first live order.

6. Correct the issue at source

Once the cause is clear, correct the underlying data, mapping or process. A one-off change may allow a test through while leaving the same discrepancy in place for future orders.

7. Retest the affected transaction

Submit the corrected transaction and confirm that the retailer accepts it. Where that message feeds into later transactions, check those before live supply begins as well.

What Else Needs Reviewing If the Launch Is Already Approaching?

An unresolved EDI test can begin affecting the wider launch when production, stock and logistics are already moving ahead.

Production may be complete. Stock may already be held in the warehouse. A retailer promotion may have a fixed start date, and the first order may be expected within days.

We have seen launch preparations reach the point where inventory and logistics were ready, while an outstanding retailer-system or customer-administration issue still needed to be resolved.

The wider launch plan then needed updating while the EDI issue was being resolved.

The operational effect will depend on what has failed.

A case-configuration mismatch, for example, can affect more than the test transaction. If the retailer expects one case quantity while the warehouse is set up to pick another, the same discrepancy can appear again when the first live order arrives.

A delay can also affect stock planning. Inventory produced for a specific launch date may remain in storage for longer if the first delivery is pushed back.

If the expected go-live date changes, warehouse, transport and customer-administration teams need the revised information before they continue working towards the original date.

What Should Be Tested Beyond the Failed Transaction?

Correcting the failed transaction does not confirm that the complete retailer process is ready. A purchase-order test may pass while a later dispatch or invoice transaction still contains an error.

Where these transactions form part of the retailer’s EDI requirements, they should be checked against the same product, quantity, price and reference information before the first supply.

The Groceries Code Adjudicator’s 2026 annual survey, which received more than 2,600 responses, found that 20% of suppliers reported issues with retailer processes for resolving invoice discrepancies promptly.

The survey does not attribute those discrepancies to EDI, but it supports the need for consistent order, delivery and invoice information before live transactions begin.

A price, quantity or purchase-order reference can appear correct at one stage and cause a reconciliation problem later if the information changes between the order, delivery and invoice.

What Should Change Before the Next Retailer EDI Test?

A failed test should lead to specific changes in how the next retailer setup is handled.

Before future testing:

  • validate retailer and product data;
  • confirm case configurations against the physical stock;
  • assign ownership for the information used within each transaction;
  • involve warehouse and finance teams, where their information feeds into testing;
  • leave enough time between testing and first supply to correct rejected transactions; and
  • record retailer-specific failures and their resolutions for future launches.

If a retailer’s product code caused the rejection, add that check before the next test. If the warehouse case configuration did not match the retailer setup, compare both before testing begins. If invoice information was picked up too late, involve finance earlier in the retailer setup.

Recording those retailer-specific issues gives the team a practical checklist for the next setup rather than relying on the same problems being identified during testing again.

Keeping the EDI Fix Connected to the Wider Launch

An EDI provider can manage the technical connection, but resolving a failed retailer test may require information or action from customer administration, warehousing, logistics or finance.

At WFL, we work across these areas as part of our 4PL role. When testing fails close to launch, we can help coordinate the relevant parties and make sure changes made during the resolution are reflected in the wider supply plan.

If the first retailer order or delivery date changes while testing is being completed, warehouse and transport plans may also need updating. If the failure involves invoice data, finance and customer administration may both need to respond.

The technical correction remains with the relevant EDI or system specialist. Our role is to keep the operational activity around it aligned.

For brands approaching a supermarket launch, that can mean coordinating retailer administration, stock, warehousing, distribution and invoicing while the EDI issue is being resolved.

Passing the retailer test is one requirement. The wider operation still needs to be ready to receive the first order, supply it correctly and keep the information around that order aligned from the warehouse through to the invoice.

FAQs

What should an FMCG brand do first after failing a retailer EDI test?

Start with the retailer’s or EDI provider’s rejection information. Identify the transaction and specific field or error that caused the rejection before changing the setup.

Does a failed EDI test mean the technical connection is broken?

No. The connection may be transmitting correctly while the transaction contains information that does not match the retailer’s requirements. The problem can sit within mapping, product information, pricing, case configuration or another required field.

How much time should FMCG brands allow for retailer EDI testing?

The time required varies by retailer, EDI setup and any problems identified during testing. Brands should allow time between the planned completion of testing and first supply, so rejected transactions can be corrected and retested without immediately affecting the launch timetable.

What happens if EDI is not ready before a supermarket launch?

The brand should confirm which transactions remain outstanding and whether the issue affects first orders, warehouse preparation, deliveries or invoicing. Any change to the planned process or launch timing should also be coordinated with the retailer and the operational teams involved.

Should brands test invoicing before the first supermarket delivery?

Where invoicing forms part of the retailer’s EDI requirements, it should be checked before live supply. Order, delivery, pricing and invoice references need to remain consistent through the process.

How can a 4PL support a failed retailer EDI test?

A 4PL can coordinate the operational teams and information surrounding the failed transaction. Technical issues remain with the relevant EDI or system specialist, while the 4PL can help keep retailer administration, warehousing, logistics and invoicing aligned around the resolution.