From the blog
Short, practical pieces on EDI documents, product data and the places they break.
Which order model are you trading under? Department stores, Amazon and the documents each one needs
A retailer never asks for "EDI". It asks for documents that fit the way it buys: into a DC, direct to store, cross-docked, drop-shipped, on consignment or through a marketplace. Most suppliers run two or three models at once.
Onboarding clocks, and why passing certification is not testing
Retailers publish response times for order responses and ASNs, and practitioners publish how long each document really takes to bring live. The two sets of numbers explain most failed go-lives.
Silence is not success: what an EDI acknowledgement proves and what it does not
A functional acknowledgement says the other side could parse your file. It does not say they accepted the order, the ASN or the invoice. The practitioners who learned this the hard way describe the same failures, and the same fixes.
The ASN is where the money goes
Across every platform and every retailer, the advance ship notice and its pallet labels are the document that costs suppliers money. Here is why, what Australian retailers tie to it, and what Amazon vendors learn the hard way.
Why your product master data breaks your EDI
Most EDI rejections are not EDI problems. They are product, pack and location data problems that the mapping transmitted faithfully. Here is how the dependencies work and what to validate.
How a retailer EDI onboarding actually runs
A new retailer wants purchase orders, ASNs and invoices by EDI by a date. Here is the sequence, who does what, and what has to be ready in your ERP before the first test.
What an ASN rejection actually means
The advance ship notice is the one EDI document a retailer checks against physical reality. Here is what it carries, the five reasons it bounces, and where to look first.
Contact
Seabrook, Melbourne