The ASN is where the money goes
I spent a week reading a couple of hundred public posts by people who run EDI for a living: forum threads, community answers, first-person write-ups and the retailers' own supplier guides. They disagree about almost everything, including which network to use and whether to run EDI in-house. They agree on one thing without being asked. The document that costs money is the advance ship notice, the ASN, known as the 856 in the American standard and DESADV in the one Australian retailers use, together with the pallet and carton labels that travel with it.
Why the ASN and not the order
An order that fails to load is visible immediately: nobody picks it, the retailer chases, someone fixes it. An invoice that fails is visible within a month because nobody gets paid. An ASN that is wrong is accepted. The retailer's system says yes, the truck arrives, and the loss shows up weeks later as a deduction, a rejected pallet, a slower payment or a lost place in an express-receiving programme. A former retailer-side EDI analyst listed the ASN faults the retailer charged suppliers for: no ASN, late ASN, the label on the wrong box, wrong items, a reused serial number, an unscannable label, a mismatch between the ASN and the bill of lading, a short shipment, a unit of measure the retailer did not recognise. They called it the riskiest transaction in the set, and nobody in the thread argued.
The reason is structural. Every other document describes an agreement. The ASN describes a physical thing, pallet by pallet, carton by carton, and it has to match that thing exactly. As one EDI programme manager put it in a post that stayed with me: EDI can only send what your warehouse knows. If the customer requires pallet-level detail and the warehouse does not capture pallets, that is not a mapping problem. The ASN is just where you discover it.
What Australian retailers tie to it
In Australia the ASN is not a logistics nicety. It is the thing that gets you paid, and the retailers say so in writing.
Myer's supplier standards make the ASN with SSCC labels mandatory, built by scan-packing each carton, and received before the merchandise arrives. Payment is by evaluated receipts settlement: the quantity received as detailed on the ASN, at the purchase-order price. There is no invoice. Get the ASN wrong and the payment is wrong, and non-compliant merchandise goes back at the supplier's cost.
Woolworths' distribution-centre guide wants two SSCC labels on every pallet, one on each forklift side, the oldest date code stated against the whole pallet, and no SSCC reused within twelve months. Its express receiving depends on the ASN, and the two faults the guide names are ASNs that do not match the paperwork and ASNs that arrive after the truck. Chemist Warehouse's process sheet asks for the despatch advice before the goods leave, one label per product per pallet, and one invoice per ASN. One grocery wholesaler's guide goes further: one purchase order per ASN, one ASN per truck, a separate invoice for each, and if the acknowledgement has not come back, do not despatch against that ASN. The same wholesaler admits suppliers to single-scan receiving only after four weeks at ninety-five per cent ASN accuracy or better.
None of the Australian documents I opened publishes a fee schedule. Enforcement here is rejection, redelivery at your cost, exception emails, scorecards and slower payment. That matters when you read American material, because the numbers are different there.
What Amazon vendors learn
Anyone planning to sell wholesale to Amazon, which means its vendor programme and its EDI rules, should read the American threads first. One vendor's EDI lead described weekly chargebacks for months, with every support ticket answered by a pointer to the routing-request document page, after the previous EDI person left without notice. A reply years later reported the same loop. A consultant who works with Amazon vendors summarised the pattern: you shipped on time, the purchase order was filled, and Amazon still deducted a few per cent of the cost of goods under several independent ASN-accuracy headings. The root cause vendors report most often is that the system fires the ASN from the order quantity rather than the confirmed pick. The fix is in the workflow, not on the warehouse floor.
The best worked example I found came from someone who built and ran EDI inside a distributor trading with Walmart, and wrote it up. The shipment left on the fourteenth. A nightly batch job stamped the ASN's ship date at half past midnight, so it said the fifteenth. The retailer's system flagged the mismatch and paid the invoice short. The observation that followed is the one to remember: the crime and the punishment happen in different departments, weeks apart, in different languages. The deduction lands in accounts payable coded in the retailer's dialect, gets booked as miscellaneous, and the person who owns the EDI map never sees the remittance.
The practices that come up again and again
Build the ASN from the confirmed pick, never from the order. If the warehouse ships ten cartons and the order said twelve, the ASN says ten.
Compare it to the bill of lading before it leaves. Ship date, carton count, weight. Hold anything that does not match. A dispute recovers one deduction; a fixed default recovers every future one.
Send it before the truck, not with it. Every Australian guide says this in some form, and the single-scan receiving programmes depend on it.
Own the labels. SSCC labels are part of the ASN, not an afterthought. One supplier spent six months failing to get labels out of their network, and labels generated inside a network have to be rebuilt per retailer if you ever leave it.
If a third-party warehouse packs your pallets, make sure its software can export what is on each one. A 3PL user in Australia described the alternative: the major retailers want each pallet's SSCC, batch and expiry on the ASN, the warehouse software could not expose pack-level data, so someone re-keyed the pallet contents into the network's portal by hand. That is where "ASN does not match the paperwork" comes from.
Log deductions by code, monthly, and close the loop to whoever owns the map. One EDI specialist who managed this for a retail brand took its monthly chargebacks down to almost nothing by disputing with carton totals, bill-of-lading photos and pallet-scale photos. Her advice: if you do not agree with the fee, fight it. Mine: fix the default first, then fight.