Field notes/NO. 005

Your Retailer Just Asked for EDI

A plain-English guide for suppliers who have just been told they need to be EDI compliant. What EDI is, which documents your retailer will ask for, whether you need an EDI provider or can use a free portal, and how long setup actually takes.

A retailer has told you that you need EDI. Probably with a date attached.

If you have never dealt with it before, the word does a lot of damage on first contact. It sounds like infrastructure and it arrives like a threat.

It is smaller than it sounds. Here is the whole thing in plain terms, including the part where the free option might be the right one for you.

What is EDI, in plain terms

EDI is a file format for business paperwork. That is the entire idea.

Instead of a purchase order arriving as a PDF attached to an email, it arrives as a structured file your system can read without anyone retyping it. Same information, different container. The retailer wants it because at their scale, humans retyping purchase orders does not work.

The standard used in North American retail is called X12. You will see documents referred to by number. The numbers are just names. There is nothing to understand about the numbers themselves.

Which EDI documents your retailer will ask for

Most retailers want four documents to begin with.

The 850 is the purchase order, and they send that one to you. The 855 is your acknowledgment, confirming you got the order and can fill it. The 856 is the advance ship notice, telling them what is on the truck before it arrives. The 810 is your invoice.

The 856 is the one that causes the most trouble, and it is better to know that now. It has to describe the physical shipment accurately, down to what sits in which carton on which pallet. It is the only one of the four where the file has to match the real world, which is why late or wrong ship notices are among the most common causes of compliance charges.

Do you need an EDI provider, or is the free portal enough?

A web portal. The retailer gives you a web form. You log in, read the order, type in the shipment details, submit. Walmart offers this free. It is genuinely free, and for a supplier doing a handful of orders a month it is also genuinely the right answer. The catch is that it stays manual forever, and it stops working at the point where typing becomes the bottleneck.

An EDI provider. You pay a monthly fee to a company that handles the format, the connection and the retailer relationship. This is what most suppliers end up doing. Get more than one quote, because pricing in this market is not standardised and the range is wide.

Build it yourself. Only sensible if you already have engineers and a system worth integrating into. For most suppliers this is not the answer.

The honest test is volume. Count the orders you expect in a month. If that number is small and stays small, the portal is fine and you can stop reading the sales emails. If it grows, or if manual entry is already going to cost you a person, integrate.

Why EDI files fail when nothing looks wrong

Almost never the connection. Two systems agreeing to exchange files is a solved problem and has been for years.

What goes wrong is the data inside. Your warehouse is Store 123 and theirs expects 00123. Your item number and their item number both exist, and only one of them belongs in that field. The pallet on the truck does not match the pallet on the notice.

None of that is exotic. It is just that a file can be technically perfect and still be wrong, and the way you find out is a deduction on a remittance several weeks later.

Where to get your retailer's EDI requirements

Before you talk to a single vendor, get the retailer's EDI specification. It goes by various names, EDI guidelines, vendor manual, supplier compliance guide, but every large retailer publishes one and it costs nothing.

That document is the source of truth for everything anyone will later quote you a price to interpret. It tells you which documents they want, which fields they require, and what they charge you for when it goes wrong.

It is dull, and it is the highest value hour you will spend on this.

How long EDI setup actually takes

Setup is not the slow part. Once your files are right you go into the retailer's testing queue, and that runs on their calendar rather than yours. Testing commonly takes two to six weeks, and it is not something you can pay to accelerate.

So the date on the email has less room in it than it appears. Being ready is not the same as being live, and only one of those is yours to control.

Nobody expects you to become an EDI expert. They expect your files to be right. If you would rather not become an EDI shop at all, that is roughly the business we are in, but read the vendor manual either way.

Send 5 documents. See what comes back.

PDFs, scans or emails in. Spec-compliant EDI out, returned within 48 hours, no commitment.

Send 5 docs