Amazon EDI starts with a fork in the road: Vendor Central or Seller Central? EDI is the language of Vendor Central — the first-party channel where Amazon is your wholesale customer — while Seller Central runs on APIs. This walkthrough covers standing up the Vendor Central document flow; if you sell through both, EDISQ presents them as one connector. Budget 2–4 days for the technical build on Amazon, sequenced like this.
First, the prerequisites Amazon controls
Onboarding begins inside Vendor Central: an active vendor agreement, EDI enabled for your account, and your trading identifiers issued. Item setup matters just as much — Amazon identifies your products by ASIN alongside your own identifiers, so an ASIN cross-reference table is a prerequisite, not a nice-to-have. For European programs, note that Amazon trades EDIFACT there while North America rides X12 004010; decide up front which regions the setup covers.
Second, connect the system that answers orders
Amazon's cadence makes manual processing a liability from the first order: the 855 is expected within 24 hours with accept/reject decisions per line. That answer has to come from somewhere real, which means the connector must read availability from your ERP — NetSuite, SAP Business One, or whichever of the 30+ supported systems you run — and turn it into line-level acknowledgment data automatically. While connecting, also confirm the order path: Amazon's ship and delivery windows are enforced, so the 855 should be wired to commit only what your operation can meet.
Third, build the shipping flow around the ASN's references
The Amazon 856 carries more linking data than most retail ASNs, and the setup has to source each piece: the ARN (Amazon Reference Number) quoted from the routing process, the BOL number for LTL and FTL freight, and carton contents that mirror the physical prep exactly — mixed-SKU cartons follow their own rules. Practically, this means the ASN generator consumes pack-out data from your warehouse at ship-confirm, never a copy of the order. Get this plumbing right during setup and Amazon's chargeback program has very little to grade you on; the failure catalog is in How to Avoid Amazon EDI Chargebacks.
Fourth, rehearse the scenarios that fail in production
A useful Amazon sandbox run covers: an 850 with a line you cannot fully supply (does the 855 reject just that line?); a multi-carton shipment with one mixed carton (does the hierarchy describe it accurately?); a missing ARN (does validation block transmission?); and an invoice generated from the shipment record (does the cost equal the PO cost, since variances auto-dispute?). Certification against Amazon's test cases follows; teams that rehearse these four scenarios first tend to pass in one cycle.
Who needs to be in the room
Amazon setups go faster with three people involved from day one: whoever holds Vendor Central admin access (EDI enablement and routing both live behind it), a warehouse lead who can describe how pack-out actually works (the ASN will be built from that reality), and someone from finance who understands how your prices reach the PO (because the invoice must match it). The purely technical work is short; the waiting is almost always for one of these three inputs.
Fifth, go live watching the acknowledgment lane
Production monitoring for Amazon is mostly about latency: 997s confirmed on every transmission, 855 turnaround tracked against the 24-hour expectation, ASNs firing at ship-confirm. Alerts on those three lanes catch nearly everything before Amazon's metrics do.
Running it costs what the documents cost — nothing more. EDISQ's meter gives you 25 free documents monthly, then charges from $0.50 each, easing to $0.10 at the top tier under marginal-tier billing; connectivity on both the X12 and EDIFACT sides is bundled, there are no setup projects or mapping fees to fund, and the Production plan's $100/month minimum applies entirely to usage with Amazon included as your first live partner. See the pricing breakdown for exact tiers.
FAQ
Does Amazon EDI apply to Seller Central?
No — EDI is the Vendor Central (1P) channel. Seller Central (3P) runs on APIs. EDISQ supports both through the same connector, so a hybrid presence needs one integration.
How long does an Amazon EDI setup take?
Plan on 2–4 days for the EDI side. Amazon's line-level acknowledgment rules and ASN reference requirements add scenarios to the test plan compared with simpler retailers.
Which spec does Amazon trade?
X12 004010 for North America, with EDIFACT for EU programs. EDISQ maps both dialects into the same workflow on your side.
What is the hardest part of Amazon EDI setup?
The 24-hour, line-level 855 and the carton-accurate 856 with ARN and BOL references. Both need automation wired to real ERP and warehouse data, not manual portal work.