Amazon Vendor Central EDI Requirements: The 2026 Supplier Guide
Amazon Vendor Central's EDI requirements: EDI is mandatory for the core 1P wholesale flow — X12 850, 855, 856, and 810 (plus 846 and 820) over AS2 or SFTP, with the 855 due within 24 hours and the 856 transmitted before your shipment reaches the fulfillment center. Miss those windows and chargebacks commonly run 2–10% of PO or shipment value, tiered by your compliance rate. This guide covers setup, testing, and how to stay out of the penalty tiers.
Updated July 2026 · 10 min read · Christopher Rosecrans
What are Amazon Vendor Central's EDI requirements?
Amazon requires EDI for the core Vendor Central (1P) wholesale flow: the 850 purchase order, 855 acknowledgment, 856 advance ship notice, and 810 invoice, plus the 846 inventory advice and 820 remittance. Documents are exchanged as X12 4010/5010, with AS2 the recommended transport (SFTP is also used). Setup is self-service via Vendor Central → Settings → EDI Integration. Amazon's SP-API covers Direct Fulfillment and data/reporting, but Amazon has announced no end-of-life for EDI — for wholesale POs, EDI remains the requirement.
EDI Standard
ANSI X12 4010/5010
Protocol
AS2 (recommended) / SFTP
Portal
Vendor Central
Chargeback risk
2–10% of PO value, tiered
Amazon Vendor Central vs. Amazon Seller Central
This guide covers Vendor Central (1P) — the channel where Amazon buys directly from you as a wholesale supplier. Amazon sends you a Purchase Order (EDI 850), you fulfill it, and Amazon resells the products.
Seller Central (3P) is the marketplace channel where you sell directly to consumers. Seller Central uses its own API-based integration, not traditional EDI. If you are using Seller Central, this guide does not apply.
Vendor Central is invitation-only. If Amazon has invited you to become a vendor, you will need to comply with their EDI requirements before you can receive and fulfill purchase orders at scale.
Required EDI transaction sets
| Code | Document | Direction | Notes |
|---|---|---|---|
| 850 | Purchase Order | Inbound | Amazon sends POs via Vendor Central; ASIN and UPC mapping both required |
| 855 | PO Acknowledgment | Outbound | Due within 24 hours — late/missing triggers a tiered 2–10% chargeback |
| 856 | Advance Ship Notice | Outbound | Must transmit before the shipment reaches the FC; SSCC-18 on every handling unit |
| 810 | Invoice | Outbound | Must match PO exactly; late or inaccurate invoices trigger tiered chargebacks |
| 846 | Inventory Inquiry/Advice | Inbound | Real-time inventory snapshot from Amazon; can be daily or more frequent |
| 820 | Remittance Advice | Inbound | Payment notification; reconcile against each 810 invoice |
Additional documents you may need: EDI 753/754 (Routing Request/Instructions — required for collect shipments where Amazon arranges freight), EDI 860 (PO Change Request).
How fast do you have to acknowledge an Amazon PO? The 24-hour 855 rule
Amazon's most aggressively enforced EDI requirement is the 24-hour 855 acknowledgment window. When Amazon sends you a Purchase Order (EDI 850), you must send back a Purchase Order Acknowledgment (EDI 855) within 24 hours — or face a chargeback that commonly runs 2–10% of the PO value, tiered by your overall compliance rate.
The 855 can acknowledge the order in three ways:
- AC — Accepted as submitted — You will fulfill the PO exactly as ordered
- AD — Accepted with changes — You will fulfill but with quantity or date modifications
- RJ — Rejected — You cannot fulfill the PO; Amazon will reorder or source elsewhere
Most EDI platforms can be configured to auto-generate an 855 AC immediately upon receipt of an 850, giving you the full 24 hours to actually review the order. This is the safest approach if your order volumes are high or if you receive POs outside business hours.
⚠️ The 24-hour rule applies 7 days a week
Amazon sends POs on weekends and holidays. Configure your EDI system to acknowledge 850s automatically — don't rely on someone checking email on Saturday morning.
ASIN and UPC mapping: getting it right from day one
Amazon's EDI 850 includes both the ASIN (Amazon Standard Identification Number) and the UPC/GTINat the line level. Your EDI mapping must correctly parse both, and your downstream systems (ERP, warehouse, order management) must be able to receive and process orders using Amazon's identifiers.
Common ASIN/UPC mapping mistakes that cause downstream problems:
- Your ERP only knows products by your internal SKU — you need a cross-reference table from Amazon ASIN to your SKU
- Multiple ASINs map to the same UPC (bundle products, packs) — each ASIN needs a separate mapping
- UPC changes after a product update — old mappings cause ASN mismatches and chargebacks
Before your first production PO, build a complete ASIN-to-SKU mapping table and verify it against Vendor Central's item list. Update it every time you add or change a product in Vendor Central.
Amazon 856 ASN requirements and SSCC-18 labels
The 856 Advance Ship Notice must be sent before the shipment arrivesat Amazon's fulfillment center. Amazon is strict about timing — a late 856 triggers chargebacks even if the freight itself arrives on time.
Label and ASN accuracy are now measured together: in January 2026, Amazon consolidated its Label and ASN chargebacks into a unified "Receive Accuracy" category, with billing active from January 19, 2026. If your physical SSCC-18 labels and your 856 data disagree, the deduction lands in that single bucket.
What the 856 must include:
- Shipment-level data: carrier, PRO/BOL number, shipping date, Amazon destination code
- Order-level data: Amazon PO number, your acknowledgment number from the 855
- Pack-level data: number of cartons, SSCC-18 code for each carton
- Item-level data: ASIN, UPC, quantity, unit of measure
Every handling unit (carton and pallet) must have a GS1-128 label with an SSCC-18 code. The SSCC code in the label barcode must match the SSCC code in the EDI 856 exactly. Amazon's receiving system scans labels at the dock and reconciles them against the ASN in real time. Any mismatch creates a receiving exception.
SSCC-18 generation requires a GS1 Company Prefix. If you don't have one, register at gs1us.org (typically takes 1–2 business days). Your EDI platform should handle SSCC generation automatically once your GS1 prefix is configured.
Free: Amazon EDI compliance checklist
Every transaction set, label requirement, chargeback trigger, and testing deadline for Amazon and 23 more major retailers — in one printable PDF. Used by 3,000+ SMB suppliers.
Amazon Vendor Central chargeback amounts: the numbers that matter
Amazon's EDI-related chargebacks commonly run 2–10% of PO or shipment value, tiered by your compliance rate — the worse your recent compliance, the higher the percentage. Two recent program changes matter for 2026 planning: in July 2025 Amazon reduced the "Not Filled" penalty from 10% to 5% of COGS, and in January 2026 it merged Label and ASN chargebacks into the unified Receive Accuracy category (billing active from January 19, 2026).
| Violation | Chargeback amount |
|---|---|
| Late or missing 855 PO Acknowledgment | 2–10% of PO value, tiered by compliance rate |
| Late or missing 856 ASN | 2–10% of shipment value, tiered by compliance rate |
| Label/ASN mismatch (SSCC code doesn't match physical label) | Receive Accuracy deduction (unified category since Jan 2026) |
| Late or inaccurate 810 Invoice | 2–10% of PO value, tiered by compliance rate |
| Missing or incorrect SSCC-18 labels on handling units | Receive Accuracy deduction |
| PO not filled | 5% of COGS (reduced from 10% in July 2025) |
| Incorrect ASIN on 856 or 810 | Invoice rejection |
AS2 setup for Vendor Central
Amazon recommends AS2 as the transport for Vendor Central EDI; SFTPis also used. Setup is self-service: Vendor Central's EDI Integration section walks you through a survey that captures your transport choice, identifiers, and document set.
To set up AS2 with Amazon:
- Log into Vendor Central and navigate to Settings → EDI Integration, then complete the self-service setup survey
- Download Amazon's AS2 certificate and note your assigned AS2 ID (format:
amazon-vcm-prod) - Provide Amazon with your AS2 URL and your public certificate
- Configure your EDI platform or AS2 software with Amazon's endpoint URL, their certificate for encryption, and your own AS2 credentials
- Send a test 997 to confirm the connection before submitting EDI test documents
If you use an EDI SaaS provider, they will manage the AS2 connection on your behalf. Provide them with your Vendor Central AS2 credentials and they will handle the certificate exchange and endpoint configuration.
Testing and go-live timeline
Amazon's EDI testing process is self-service through Vendor Central — there is no dedicated EDI coordinator assigned to most new suppliers. You submit test transactions, review 997 responses in the portal, and iterate until all documents pass validation.
Typical timeline for a new Vendor Central supplier using a platform with pre-built Amazon mapping:
- Day 1–3: Vendor Central EDI setup, AS2 connection test, ASIN mapping loaded
- Day 3–7: 850/855 test cycle — common issues: ASIN format, date qualifiers
- Day 7–14: 856 ASN testing — SSCC generation, hierarchy levels, label matching
- Day 14–21: 810 Invoice testing — ASIN/UPC/quantity reconciliation
- Day 21–30: Production go-live; monitor first 5–10 POs closely
Go live without the chargeback tiers
The suppliers who hit Amazon's chargebacks most often are the ones who rushed the 855 configuration, skipped SSCC testing, or assumed their ERP would handle ASIN mapping automatically. All three are avoidable.
The ones who go live cleanly are the ones who set up auto-acknowledgment for 855s, validated SSCC generation against physical labels before shipping, and used an EDI provider with a tested Amazon mapping rather than building their own. For SMB teams without an in-house EDI specialist, self-serve EDI onboarding with Amazon's document set pre-mapped is the shortest path to a clean go-live.
Amazon Vendor Central EDI: frequently asked questions
Is EDI mandatory for Amazon Vendor Central?
Yes — for the core 1P wholesale flow (850, 855, 856, 810, plus 846 and 820), EDI is mandatory. Amazon's SP-API covers Direct Fulfillment and data/reporting, and Amazon has announced no end-of-life for EDI, so wholesale vendors should plan on EDI as the standard.
What chargebacks does Amazon issue for EDI non-compliance?
Late or missing 855s, 856s, and 810s commonly cost 2–10% of PO or shipment value, tiered by your compliance rate. Since January 2026, Label and ASN accuracy failures are billed under the unified Receive Accuracy category, and since July 2025 the "Not Filled" penalty is 5% of COGS (down from 10%).
When does the Amazon 856 ASN have to be sent?
Before the shipment arrives at the fulfillment center. A late 856 is charged back even if the freight itself is on time, so trigger ASN generation from your shipping confirmation — not from a nightly batch.
How do other retailer EDI programs compare?
Amazon's tiered percentage chargebacks differ from the flat-fee models at other retailers — compare Walmart's OTIF and SQEP programs, Costco's EDI certification requirements, CVS's per-shipment ASN penalties, and Dillard's per-carton label charges.