EDI for Amazon Brands: What the Documents Actually Do

EDI is the retail industry's way of sending business documents between computers without anyone typing. A retailer's ordering system produces a purchase order in a standard format, transmits it, and your system reads it and produces the reply documents in the same format. No PDFs, no email, no portal logins.

For an Amazon brand this is unfamiliar territory only in form. The content is the same commercial conversation you already have — here is an order, we confirm it, here is what shipped, here is the bill. What is new is that the retailer expects it to be machine-readable, on time, and accurate to the carton.

Why retailers insist on it

A grocery chain receives tens of thousands of orders' worth of goods a week. Every shipment that arrives without a matching electronic notice has to be counted and keyed by hand, which is slow and error-prone at a dock where trucks are queuing.

So the requirement is not bureaucracy, it is throughput. The documents let their systems do three things automatically: expect a delivery, receive it by scanning one label per carton, and match the resulting invoice against both the order and the receipt without a human comparing three pieces of paper.

That three-way match is the reason your invoice gets paid or does not. If any of the three disagree, payment stops and a query opens.

The documents you will actually use

Each document type has a number. You do not need to memorise the whole catalogue, but you will meet these.

Two of them deserve more detail because they are where brands get into trouble.

The advance ship notice is not a summary. It is a hierarchy: this shipment contains these pallets, each pallet contains these cartons, each carton contains this many of that item, and each carton is identified by a serial shipping container code that matches the label physically stuck on it. Send an accurate one and receiving scans a label per carton and books the whole thing. Send a sloppy one and the shipment is counted by hand at your expense. The label side of this is explained in GS1 barcodes for Amazon and retail.

The functional acknowledgement looks like noise and is your early warning system. It tells you the retailer's system received and could parse your document. If you never look at these, the first sign that your invoices are not arriving will be an aged receivable a month later.

Some accounts add more: a product catalogue document for item setup, a payment advice explaining deductions, an inventory advice if the account is consignment. They arrive as the relationship deepens.

How this differs from the portals you know

An Amazon brand usually has two reference points, and neither is quite EDI.

Seller Central is a marketplace interface. Orders appear, you ship, money arrives on a cycle. There is no purchase order, no acknowledgement and no invoice, because there is no trade credit.

Vendor Central is closer, because Amazon there is a retailer buying from you wholesale. It issues purchase orders, expects confirmations and shipment notices, and deducts for compliance failures. The difference is that Amazon gives you a web portal that will do the whole conversation by hand, and only pushes you to a connection when volume justifies it. If that side is unfamiliar, Vendor Central purchase orders covers what the order document contains and how it is confirmed.

That portal habit is the thing to unlearn. Most retailers outside Amazon either require EDI from the start or offer a portal that becomes impractical above a handful of orders a week.

What a connection consists of

Three parts, and it helps to know which is which when someone quotes you a price.

The transport: how documents physically move. Historically a value-added network that acts as a mailbox between trading partners; increasingly a direct secure file transfer. Your provider handles this and you mostly never think about it.

The mapping: translating between the retailer's exact expectations and your own system's fields. This is where the work is, because every retailer implements the standard slightly differently — different segments required, different qualifiers, different rules about how a case quantity is expressed.

The integration: whether the documents flow into and out of your order system automatically, or whether a person reads them on a screen and keys the result. Both are legitimate at different volumes, and the choice is the subject of EDI for small brands.

The part nobody puts in the quote

Setting up an EDI connection is not a software purchase, it is a certification process with the retailer.

You will be given their implementation guide, which is a long document describing exactly which fields they require in each message. You map to it. Then you run test transactions: they send a test order, you return a test acknowledgement, a test shipment notice and a test invoice, and their team checks each one against the guide. Corrections go back and forth. Only when every document passes are you moved to production.

Budget weeks, not days, and budget attention from whoever knows your order data. The mapping questions are business questions, not technical ones: what is your item identifier on their file, how do you express a case quantity, which address is the ship-from, what does your invoice do about freight.

And be aware that a second retailer means a second certification. The standard is common; the implementations are not.

Does an Amazon-first brand need this yet

Almost certainly not on day one, and certainly before the account you actually want.

Independent shops, most distributors and smaller chains will happily work from emailed purchase orders and invoices. That covers the entire early wholesale phase, and the manual version of that flow is set out in wholesale fulfillment for Amazon sellers.

The requirement shows up the moment you are talking to a chain with a distribution centre, or to a distributor who serves them. At that point it is not negotiable and it is not fast, so the useful move is to ask early. A simple question in the first serious conversation — what are your electronic document requirements — tells you whether you have a six-week project ahead of the first shipment.

If you do not yet know which kinds of accounts your product belongs in, that is the thing to settle before worrying about document formats. Paste your listing into WholesalePilot and the preview shows the retailers and distributors that stock comparable products, which tells you whether you are heading for independents who email orders or chains that will hand you an implementation guide.

What to do with this now

Two small things cost nothing and save the panic later.

Keep your item data clean and in one table: variant, barcode, case quantity, case code, dimensions, weight, cost. Every EDI mapping and every item setup form draws on exactly this, and a brand that has it can answer a buyer in an hour instead of a fortnight.

And when a buyer mentions a routing guide or a vendor manual, read it before you quote. The document requirements are in there, along with the label formats and the deduction schedule, and knowing them changes what price you should be asking for.