EDI for Australian retail suppliers, explained
By Built for Retail · Last reviewed 2026-08-07
The answer
EDI, electronic data interchange, is the standardised electronic messaging Australian retailers use to send purchase orders and receive invoices and advance shipping notices, the ASNs that tell the distribution centre what is arriving. It replaces email and PDFs once you scale. Budget months, not weeks, to build and accredit, and start the work before your first purchase order, because the buyer decides your ranging but the messaging must already work.
What EDI carries between you and the retailer
EDI, electronic data interchange, carries a fixed set of trading documents between your systems and the retailer's, each with a standard message type. The three that matter first are the purchase order, the invoice, and the ASN, the advance shipping notice that tells the distribution centre exactly what is arriving, on which pallets, before the truck does. Email and PDFs do not scale to this; EDI does.
Around those sit the supporting messages: the functional acknowledgement that confirms a document was received and readable, the purchase order acknowledgement that confirms you can supply, the order change, and the remittance advice that explains what the retailer actually paid against each invoice. Each retailer names and shapes these slightly differently, which is part of why no two builds are identical.
Underneath the messages sit your GS1 barcodes at unit, carton and pallet, the numbers that let a scan match a physical carton to a line on the ASN. Get the barcode hierarchy wrong and the electronic messages are perfect while the stock still fails at the door. The data and the pallet have to agree.
Why EDI builds take months, not weeks
Builds take months, not weeks, because EDI is an integration project, not a piece of software you switch on. You are mapping your own system's fields, product codes, units of measure, tax treatment, to the retailer's exact specification, then proving every message passes their validation before they let you trade live. The software is the easy part; the agreement between two systems is the slow part.
Retailer testing runs on the retailer's calendar, not yours. You submit test messages, wait in a queue, get errors, fix, and resubmit, often across several rounds. Range reviews happen roughly every six months, so a slipped test window can push a live date by a whole cycle. None of this moves faster because you are ready and waiting.
Then there is the fulfilment side. Your third-party logistics warehouse, or 3PL, has to receive the electronic order, pick and pack to the retailer's carton and labelling rules, and send an accurate ASN back. If the warehouse and the EDI are not integrated, you have two half-built systems and a compliance problem waiting for the first order.
What accreditation actually involves
Accreditation is the retailer signing off that your messages, your barcodes and your fulfilment all meet their standard, and it is a gate you pass, not a form you file. It usually means a supplier setup pack, a technical mapping stage, a structured test plan for each message type, and a controlled first live order watched closely on both sides.
Supplements and therapeutic goods add a layer: those claims are scoped to TGA specialists, and Built for Retail runs the retail and fulfilment half around them. Imported goods add another; Built for Retail runs the retail half, readiness, buyer case, FSANZ labelling localisation, GS1 and EDI, and coordinates with your customs broker rather than acting as importer of record.
The steps, in order
- 01Confirm the retailer's EDI specification and required message types
- 02Assign GS1 barcodes at unit, carton and pallet and validate the hierarchy
- 03Map your system fields to the retailer's spec with your EDI provider
- 04Run the retailer's test plan for each message, PO, invoice and ASN
- 05Complete a monitored first live order before trading at volume
Why the work starts before the first purchase order
The work starts before the first purchase order because the first order often lands one to six months after a ranging win, and it lands whether or not your EDI is ready. The retailer decides when they issue it. If your messaging, barcodes and warehouse are not accredited by then, the order arrives, cannot be processed cleanly, and your first impression is a failure to deliver.
That is why readiness is front-loaded. GS1 registration, artwork and labelling, the 3PL integration, and the EDI mapping all have long lead times and dependencies on each other. Starting them after the buyer says yes means racing every one of them at once, against a clock the retailer controls, in the window where getting it wrong costs you the range.
The steps, in order
- 01Register your GS1 barcodes as soon as ranging looks likely
- 02Brief your 3PL and start warehouse integration early
- 03Lock artwork and FSANZ labelling before the order window
- 04Begin EDI mapping and testing ahead of the first PO
- 05Model your trade spend and pricing before you commit
How EDI ties to DIFOT, chargebacks and trade spend
Accurate EDI protects the numbers that decide whether ranging survives its first review. DIFOT, delivered in full and on time, is measured off your ASN and delivery against the purchase order; a wrong ASN can score you as late or short even when the stock is correct. Retailers read DIFOT as your reliability, and a weak score puts your range at risk.
Chargebacks, the penalties a retailer deducts for non-compliance such as a late delivery or a mislabelled carton, typically run 1 to 5 percent of invoice value and are often triggered by EDI and fulfilment errors. They stack on top of trade spend, the rebates, promotional funding and co-op you pay the retailer out of gross sales, commonly 10 to 25 percent. Sloppy EDI quietly taxes an already thin margin.
All of it feeds the pricing waterfall, the step down from your list price to what you actually keep after retailer margin, commonly 25 to 45 percent by category, trade spend and chargebacks. Model that waterfall before you sign, because EDI failures show up in it as real dollars, not abstractions.
Getting ready before you pitch
The honest sequence is readiness first, then the buyer. Built for Retail has ranged brands as the agent into Chemist Warehouse, Woolworths, Coles and Priceline, including Dr Pickles, on Woolworths and Coles shelves today, Smile Makers, on Priceline and Chemist Warehouse, and Australian Glow, on Priceline, the founder's own brand, disclosed on a register of interests. Past rangings never promise yours; the buyer decides.
The Retail-Readiness Sprint is a fixed fee of 15,000 dollars for a single retailer, or 25,000 dollars multi-retailer, and runs about four weeks. It models your real trade spend, the pricing waterfall, the review calendar and the compliance gap, including where your EDI and fulfilment stand today. You keep the model. Sometimes its answer is not yet, and that is a cheaper answer to get now than after a failed first order. Use the contact form on this page.
Questions founders ask
Do I need EDI to sell to a major Australian retailer?
Yes for the majors. Woolworths, Coles, Chemist Warehouse and Priceline run purchase orders, invoices and ASNs through EDI, and trading manually does not scale past a handful of orders. Smaller or independent channels may accept email or a portal, but a national grocery or pharmacy range assumes EDI. Treat it as a cost of entry, budgeted and built before your first purchase order, not an upgrade you add later.
How long does an EDI build take?
Plan for months, not weeks. The mapping, the retailer's own test cycles, and your warehouse integration each take time and depend on each other, and testing runs on the retailer's queue rather than yours. A slipped test window can push a live date to the next range review, roughly six months away. Start early, because the first order often lands one to six months after a ranging win.
Can I add EDI after I win the range?
You can start after, but it is the expensive way. The first purchase order often arrives one to six months after a ranging win, and the retailer decides when. If your barcodes, mapping and 3PL are not accredited by then, the order cannot be processed cleanly and your first delivery fails. Front-load GS1, labelling, warehouse and EDI so the order lands into a system that already works.
What does EDI actually carry?
At minimum the purchase order the retailer sends, the invoice you send back, and the ASN, the advance shipping notice telling the distribution centre what is arriving. Around those sit acknowledgements, order changes and remittance advice. Underneath sit your GS1 barcodes at unit, carton and pallet, which let a scan match a physical carton to a line on the order. The messages and the pallet must agree.
How does EDI affect chargebacks and DIFOT?
Directly. DIFOT, delivered in full and on time, is measured off your ASN against the purchase order, so a wrong ASN can score you late or short even when the stock is right. Chargebacks, the penalties for non-compliance, typically run 1 to 5 percent of invoice value and are often triggered by EDI or labelling errors. Accurate messaging protects both your score and your margin.
Forecasting and Supply
Forecasting, stock cover, ordering, launch quantities and delivery-window performance, run on the same rails that ship your purchase orders.
Scope, price, processOr use the contact form at the bottom of this page. It lands straight in our inbox.
General information, not advice for your specific brand. Figures are market-typical ranges; your Sprint models your real ones. Written by the Built for Retail team.

