Onboarding clocks, and why passing certification is not testing
Two kinds of clock run on every retailer EDI onboarding. The retailer's clock says how fast you must respond once live. The practitioners' clock says how long it takes to get there. Suppliers who know only the first one are the ones who write the frustrated posts.
The retailer's clock
Australian retailers state their response rules in the supplier guides, and they are stricter than most new suppliers expect. Chemist Warehouse wants the purchase-order response within forty-eight hours, accepts only one response per order, and if you changed anything, wants you to wait for the purchase-order change before shipping. Myer queries discrepancies within two working days, and where an order is revised the revised order must precede the ASN and the despatch by at least one working day. One grocery wholesaler's guide wants the order acknowledgement within three hours of the purchase order landing. Every one of them wants the despatch advice before the goods arrive, and most want it before the truck leaves.
These are not technical settings. A three-hour response window means someone, or something, accepts or rejects order lines during the working day, every day, and the back-order and partial-shipment policy has been decided in advance. The time to settle that policy is before the first test document, not after the first missed window.
The practitioners' clock
The American threads contain measured numbers, which is rare. One supplier connecting about ten retailers through a managed network recorded the average per document: twenty-eight days for the purchase order, sixty-one for the invoice, seventy-one for the ASN. The ASN takes two and a half times as long as the order because it is the one that has to match a physical process. Replies in the same thread ranged from a month in a mature in-house environment to eight to sixteen weeks per partner through a particular network, and one person's longest was eighteen months for five documents.
An engineering leader connecting a third-party warehouse through a managed service expected a month and found the project averaging one message type per month, each needing weeks of three-way meetings between their team, the warehouse and the provider. The first two weeks of the warehouse-shipment document were spent creating a shared understanding of what each field means. Others in the thread put a first integration at five to six months of project management with development about a fifth of the total, and warehouse set-ups at two to three times a retailer set-up. The design document, several said, is almost always the most intensive part.
Here the picture is better than it was. Woolworths' eBusiness lead described the old accreditation as a lot of back-and-forth that could take weeks or even months of end-to-end testing. A self-test service built with GS1 Australia cut it to days. Local networks quote four to eight weeks for a Coles supplier depending on the system and the document set. I treat those as the floor.
Why certification is not testing
The most repeated complaint across the threads is not that certification is slow. It is that it proves so little. One practitioner called the testing laughable, having passed many times only to run into mapping troubles the moment it went live. Another explained why: the portal test completes the testing between your network and the retailer's network, and you still need to do integration testing in your own system. A third had completed testing only to have things blow up at go-live.
Certification checks that your file has the right shape. It does not check that your system produced it from real data, that the unit of measure matches the retailer's, that the pack hierarchy on the ASN matches the pallets the warehouse actually builds, or that the order response is sent within the window. Those are the things that fail in production. A test passed with hand-edited documents proves nothing.
What good testing looks like
Test the messiest order you have. An EDI programme manager said their team asks for the messiest, most complicated case the supplier can come up with, not the clean one. Partial shipments, back-orders, multiple purchase orders in one delivery, a rejected line, a cancelled order, a split across two warehouses. A drop-shipper with no IT team found that when an order split across two warehouses the ASN went out for half of it.
Generate every test document from your own system. Not from the network's portal and not from a spreadsheet. The point of the test is to find out what your system actually produces.
Test under load. One supplier dropped seven hundred orders into a pickup folder at once and watched the receiving system spawn seven hundred processes and fall over.
Treat "already have EDI with them" as a warning. It may be another division, other documents, a different system, or a map nobody has looked at in years.
Check the retailer's extras before you start. A supplier moving onto Amazon's vendor programme found that the routing request and routing instructions were not covered by their software vendor's documentation and were told to hire a consultant. Walmart's suppliers ask whether every document has to be tested even when it is not used, and the contact who said no had left the business by the time the question mattered.
Budget in weeks per partner, more for warehouses and ASNs, stage the rollout by volume, and put the certification date on the plan as a milestone, not the finish line.