Selling to Amazon first-party is a different business from selling on the marketplace. In Vendor Central, Amazon is your customer: it cuts purchase orders, routes freight into its fulfillment network, and grades every response by machine. The entire relationship runs on EDI, and the rules below are the ones Amazon actually enforces.
Vendor Central, not Seller Central
The distinction decides everything downstream. Seller Central (third-party) merchants list and fulfill through APIs; Vendor Central (first-party) suppliers receive POs and trade the classic document chain. If Amazon invited you to become a vendor, you are in the EDI world — X12 4010 in North America, EDIFACT for European programs. Suppliers who operate on both sides can run them through one EDISQ connector, alongside Amazon Seller Central marketplace feeds.
The 24-hour acknowledgment clock
An 850 purchase order from Amazon expects an 855 acknowledgment with a line-level answer — accept or reject, per line — within 24 hours. Amazon also enforces the ship and delivery windows stated on the PO, so the acknowledgment is a commitment, not a formality: confirm only what you can actually meet. Because the clock is short and the volume can be high, this step should come straight from your ERP's availability data rather than from a person reading a portal.
The ASN and the chargeback list
Vendor Central chargebacks concentrate on ASN accuracy, on-time PO performance, and prep — and the 856 ship notice sits in the middle of all three. Three rules from Amazon's 856 requirements do most of the work:
- Quote the ARN. The Amazon Reference Number issued during routing must appear on the ASN.
- Cartons match physical prep exactly. What the document says is in each carton must be what receiving finds, and mixed-SKU cartons follow their own rules.
- BOL for freight. LTL and FTL shipments carry the bill of lading number.
An ASN generated from actual pick-and-pack data — not from the order — is the difference between a quiet chargeback report and a noisy one.
Invoices that survive the auto-dispute
Amazon matches the 810 invoice against the PO by machine, and cost variances auto-dispute. The invoice cost must equal the PO cost, line by line, and item identifiers carry an ASIN cross-reference alongside your own numbers. Build the invoice from the same data lineage as the ASN and the match takes care of itself; improvise and you will spend your margin on dispute resolution.
One vendor, two standards
Amazon's North American programs trade X12 4010; its European programs run on EDIFACT. If your vendor agreement spans regions, plan for both dialects from the start — same business documents, different syntax, and a separate testing pass per region. This is a mapping problem, not an operational one: with both standards handled in the translation layer, your ERP sees one order stream regardless of which continent cut the PO.
Whichever region you trade, watch the acknowledgment trail. Every document exchanged with Amazon should produce a 997 in minutes, and a missing one is your earliest warning that a transmission went astray — hours before it would surface as a late-PO or missing-ASN problem in Vendor Central metrics.
Getting compliant
The path is short when the plumbing is prebuilt. Connect your ERP — NetSuite, Dynamics, QuickBooks, or any of 30+ systems — load the item cross-reference with ASINs and UPCs, replay Amazon order scenarios in the sandbox, and go live with acknowledgment tracking on every document. With EDISQ's certified Amazon maps, the EDI side typically takes 2–4 days; Vendor Central's own onboarding sets the overall calendar.
What it costs is deliberately boring: EDISQ pricing is per document, with the first 25 documents free every month and rates starting at $0.50 that step down with volume to $0.30 at the top tier, billed marginally. Connectivity — AS2, SFTP, or VAN — is part of the service, and there are no setup, mapping, or per-partner charges. Amazon's volume is exactly what volume pricing is for.
FAQ
Is Amazon EDI for Vendor Central or Seller Central?
Vendor Central — the first-party relationship where Amazon issues purchase orders to you as a supplier. Seller Central marketplace selling runs on APIs instead. EDISQ supports both sides through the same connector.
How quickly must Amazon purchase orders be acknowledged?
Within 24 hours, with an 855 that accepts or rejects every line individually. EDISQ builds the acknowledgment automatically from availability data in your ERP.
Does Amazon charge back suppliers for EDI errors?
Yes — Vendor Central chargebacks cover ASN accuracy, PO on-time performance, and prep. Documents validated before transmission keep the document-driven portion of that list empty.
What does EDI with Amazon cost through EDISQ?
Per document only: the first 25 each month are free, then from $0.50 per document, decreasing with volume. No monthly, partner, or mapping fees.