Operations: fulfilment, packaging & compliance
A buyer at a regional chain says yes, then sends a vendor packet with a line about electronic data interchange in it. A brand doing a few hundred thousand dollars on Amazon does not have a system to connect, does not have anyone to run a project, and has three weeks before the first ship window.
The good news is that nobody expects a brand your size to build an integration. There are three routes to compliance, they cost very different amounts, and the right one depends almost entirely on how many orders a week you will receive and who is packing them.
The three ways to comply
A web portal run by a provider. You log in, a purchase order is sitting there in a readable form, and you fill in the reply documents on screen. The provider translates your typing into the formats the retailer expects. No integration, nothing to install, and you can be live in days rather than weeks. The limitation is that it is manual: a person reads each order and types each ship notice, and a ship notice with forty cartons in it is forty rows of typing.
A managed provider connected to your order system. Orders flow into whatever you use to run the business, and the documents go back out automatically. You still work with a provider who owns the mapping and the certification, but a person no longer re-keys anything. Setup takes weeks and costs more per month.
Your 3PL does it. Many warehouses that handle retail accounts already hold connections to the large retailers and will operate the shipment notice and sometimes the whole document set on your behalf. This is often the best answer for a small brand, because the ship notice has to describe cartons the warehouse built, and the warehouse is the only party that knows what actually went in each one.
| Web portal | Managed integration | 3PL operates it | |
|---|---|---|---|
| Time to live | Days | Weeks | Days, if they hold the connection |
| Ongoing effort | Manual per order | Low | Low |
| Ship notice accuracy | Depends on your typing | Depends on your data | Built from the actual pack |
| Best when | A few orders a week | Steady volume, own system | The warehouse packs everything |
Why the ship notice is the whole game
Of the documents in the set, the advance ship notice is the one that makes or breaks a small brand, and it is worth understanding precisely why.
The notice describes the shipment as a tree: pallets, then cartons, then contents per carton. Each carton carries a unique code, printed on a label stuck to it. The receiving clerk scans that label and the retailer's system books everything the notice said was inside, without opening anything or counting anything.
That means the notice has to be built from what was actually packed, not from what was ordered. If the warehouse short-shipped two units because one was damaged, and the notice still claims a full case, the scan disagrees with the count and you get a discrepancy.
This is the argument for letting the party that packs the boxes produce the notice. A brand keying it by hand from a pick list, hours after the truck left, is guessing. The structure of the document itself is described in EDI for Amazon brands, and the carton codes it relies on in GS1 barcodes for Amazon and retail.
The routing guide is the other half
EDI compliance and routing compliance are separate requirements that fail together.
A routing guide tells you how the freight moves: which carrier for which weight band, whether you must request routing in advance and how many days before the ship date, which day of the week deliveries are accepted at that facility, whether an appointment is required, how pallets must be built and labelled, and what paperwork travels with the driver.
Read it before you quote a price, not after you win the order. Guides contain real costs — a requirement to use the retailer's nominated carrier on their account changes your freight economics, and a requirement for appointment scheduling adds a step somebody has to own.
The routing guide also usually contains the deduction schedule, which is the part everybody skips and should not.
What deductions actually cost
Retailers charge back against your invoice for compliance failures. Each is a fixed fee or a proportion of the shipment value, and they are applied by software, not by a person deciding whether you meant well.
The usual list: shipment arrived outside the ship window, no advance ship notice, ship notice did not match the receipt, carton label missing or unreadable, pallet built wrong or overheight, wrong carrier, no appointment, item not set up correctly, quantity short.
Take a made-up first order to see the scale. Twenty cases of twelve units at a twelve dollar wholesale price is two thousand eight hundred and eighty dollars. A missing ship notice and a late delivery on that order can easily take a couple of hundred dollars off the payment, which is most of the margin on an order that already cost you setup time.
The lesson small brands take from that is not to fear the channel. It is to price the channel knowing the deductions exist, and to fix the recurring ones rather than disputing them one by one. Amazon runs the same playbook on its wholesale side, and sellers who have been through it describe the pattern in Vendor Central chargebacks.
Do log every deduction against the purchase order that caused it. Clerical errors get reversed if you ask within their window and stay uncollectable if you do not.
How to run the first account without a system
A workable setup for a brand with one EDI account and a few orders a month.
Use a portal or let the 3PL operate the connection. Do not build an integration for one account.
Keep one item master table — variant, barcode, case quantity, case code, dimensions, weight, cost, the retailer's own item number — and treat it as the source of truth for the portal, the item setup form and the invoice. Most document errors are data errors.
Put the routing guide's key facts on one page next to the pick station: ship window rules, carrier rules, label format, pallet height, appointment requirement, who to email. The person packing the order is the person who needs it.
Check the functional acknowledgements. They tell you a document arrived and parsed. Nobody will call to say your invoice never landed.
And reconcile every payment against the order and the invoice. Deductions are where the money goes missing, and the only way to see them is to look.
When to upgrade
Three triggers, any of which justifies moving from manual to integrated.
Order frequency high enough that a person is typing documents most days. At that point the labour cost exceeds the subscription difference.
A second or third EDI account. Each one adds a mapping and a certification, and running three portals by hand multiplies errors.
Or a recurring deduction you cannot fix by trying harder. If ship notice mismatches keep happening because a human is transcribing carton contents, the fix is structural.
Until one of those is true, manual is not a compromise, it is the correct answer. Plenty of brands run a real retail account off a portal and a well-organised warehouse for a year or more.
Before any of this, check the channel is real
EDI is downstream of having accounts that require it. If you are reading this speculatively, the useful first step is to find out whether your product belongs in the kind of account that hands out vendor packets at all.
Paste your listing into WholesalePilot and the preview shows which retailers and distributors stock products like yours. If they are mostly independents and small distributors, emailed purchase orders will serve you for a long time, and the operational money is better spent on case packs and barcodes. If they are chains, plan for the vendor packet before a buyer hands you one, and pick the 3PL accordingly — the capability differences are set out in 3PL vs FBA.