Amazon EDI Integration
Amazon EDI integration is not one integration. Vendor Central suppliers exchange EDI with Amazon through two separate programs, Wholesale and Direct Fulfillment. Seller Central (3P) sellers use Amazon's SP-API, not EDI. We build each one inside your ERP, with every X12 file read and generated using the EdiFabric .NET library.
+ RULES
Amazon EDI or SP-API: which do you need?
It depends on your relationship with Amazon, not on your ERP. On Vendor Central, the first-party (1P) side, Amazon buys from you as a supplier. That integration is EDI: X12 purchase orders, acknowledgments, ship notices and invoices.
On Seller Central, the third-party (3P) side, you sell on Amazon yourself. That integration is Amazon's Selling Partner API, not EDI. Amazon seller EDI and Amazon 3P EDI are common searches, but there is no EDI for Seller Central. Orders, inventory and FBA shipments run through Amazon SP-API integration.
Many businesses have both. Each relationship gets its own integration, built against the same items, orders and stock in one ERP.
The three Amazon programs, and which connection each one uses
Vendor Central Wholesale. Amazon buys your stock and you ship it to Amazon fulfillment centers, over EDI. Collect shipments add a routing exchange before the ship notice, covered in EDI 753 and 754 routing. Full detail: Amazon Vendor Central EDI.
Vendor Central Direct Fulfillment. Amazon takes the customer order and sends it to you as a dropship order over EDI, and you ship it to the customer's door. It runs on the same Vendor Central account as Wholesale, as its own connection. Full detail: Amazon Direct Fulfillment EDI.
Seller Central. You are the seller of record. It runs on SP-API, not EDI, including FBA and FBM orders and FBA inbound shipments. Full detail: Amazon SP-API integration.
What Amazon EDI integration covers
-
850Purchase orders into your ERP. Amazon purchase orders land as real orders against your own SKUs, with Amazon's item numbers mapped to yours. -
855Accept or reject from the stock screen. Vendor Central purchase orders are accepted or rejected back to Amazon from the screen that shows system, 3PL and allocated stock, so the acknowledgment reflects what you can ship. -
753/754Routing for Wholesale collect shipments. On a collect shipment Amazon arranges the freight, so the routing request and routing instructions run as their own step before the ship notice goes. Routing is Wholesale only; the full document set is on Vendor Central Wholesale EDI integration. -
856/810Ship notice and invoice that agree. The ship notice has to describe what actually shipped, and the invoice has to bill for the same goods, so what Amazon is told shipped and what Amazon is billed for agree. -
846Inventory, acknowledgments and adjustments. Inventory advice, 997 functional acknowledgments, 824 application advice and 812 credit or debit adjustments, each mapped to your own records. -
DFDirect Fulfillment as its own connection. Dropship orders run through a separate EDI connection on the same Vendor Central account, with their own mapping and rules. -
SP-APISeller Central over SP-API. Where you also sell on Amazon as a 3P seller, Seller Central orders and FBA shipments run through SP-API in the same ERP, not EDI.
What going live with Amazon EDI involves
The connection comes first. Vendor Central connects directly to your system over SFTP, with no network in between. You exchange the technical details so Amazon can reach you and you can reach Amazon.
Then each document is mapped to your ERP's own data: your item numbers against Amazon's, and your order and shipment records against the fields each transaction set expects. This is where the business rules sit, so it is where the real work is.
Then comes testing against Amazon's validation, followed by production, with acknowledgments and rejections watched closely on the first live orders. What your account must exchange is set by Amazon's own implementation guide for each program. Work from the current version for your account.
How we build Amazon EDI integration inside your ERP
Each program built as its own flow
Wholesale, Direct Fulfillment and Seller Central each get their own mapping and rules, so a change in one never risks breaking another.
Read and generated inside your ERP
Every X12 file is read and generated inside your ERP using the EdiFabric .NET library, with the mapping in your own code. Vendor Central connects directly over SFTP, with no network in between.
Every file logged
The raw file is stored next to the parsed result, so a rejection is traced to the exact value that caused it. For what each document does, see EDI transaction sets explained. For a walk-through of how both Vendor Central connections run day to day, see Amazon Vendor Central EDI inside your ERP.
One order view, separate flows underneath
Staff work from one order view, even though wholesale, dropship and Seller Central orders follow different paths behind it.
The pages under this one.
Amazon Vendor Central EDI Integration for Wholesale
We build Amazon Vendor Central EDI for Wholesale inside your ERP. Amazon's 850 purchase orders, your 855 acknowledgments, 753/754 routing, 856 ship notices and 810 invoices are read and generated with the EdiFabric .NET library and exchanged directly with Amazon over SFTP, as a connection separate from Direct Fulfillment.
850 · 856 · 810Amazon Direct Fulfillment EDI
Amazon Direct Fulfillment EDI is how Amazon sends dropship orders to you as a Vendor Central supplier, and you ship each one straight to the end customer rather than to an Amazon warehouse. It runs on the same Vendor Central account as Wholesale, as its own EDI connection, which we build inside your ERP.
GUIDEWhat Is Amazon EDI?
Amazon EDI is how Amazon Vendor Central exchanges purchase orders, ship notices and invoices with vendors, using ANSI X12 documents over a direct connection. Amazon runs two Vendor Central programs on it, Wholesale and Direct Fulfillment, and Seller Central is not EDI at all.
Amazon EDI integration across three Amazon accounts
- Amazon runs as three separate accounts: Vendor Central over direct EDI, a refurbished Seller Central account over SP-API, and a third account used only for Best Buy Optics inbound shipments.
- Vendor Central carries two EDI connections on one account: Wholesale, with 850, 855, 856, 810, 846, 997, 824, 812 and 753/754 routing, and Direct Fulfillment.
- Seller Central runs on SP-API, not EDI, covering FBA and FBM orders and FBA inbound shipments.
- Every X12 file is read and generated inside the ERP using the EdiFabric .NET library, and Vendor Central connects directly over SFTP, with no network in between.
- Vendor Central purchase orders are accepted or rejected from the same screen that shows system, 3PL and allocated stock.
Amazon EDI integration questions
What is Amazon EDI?
It is how Amazon Vendor Central exchanges purchase orders, ship notices and invoices with its suppliers, as ANSI X12 documents over a direct connection. For a plain-language explanation, see what Amazon EDI is.
Do Amazon 3P sellers need EDI?
No. Seller Central, where 3P sellers sell on Amazon themselves, uses Amazon's SP-API. EDI is for Vendor Central suppliers, where Amazon buys from you.
Is Vendor Central the same as Seller Central?
No. On Vendor Central, Amazon is the buyer of record and the integration is EDI. On Seller Central, you are the seller of record and the integration is SP-API. They are different relationships with Amazon, not two names for the same thing.
What documentation does Amazon EDI require?
Amazon publishes its own implementation guides for each Vendor Central program. They set which transaction sets your account exchanges, which fields are required and how Amazon validates them. Work from the current guide for your account, because requirements change over time.
Do we need SPS Commerce or another EDI provider to connect to Amazon?
No, if the documents are built into your ERP. Vendor Central can connect directly over SFTP. A provider is one option, not a requirement.
Can we run Wholesale and Direct Fulfillment on the same account?
Yes. Both run on one Vendor Central account, but with different transaction flows and rules, which is why we build them as separate integrations rather than one shared mapping.
Which one should we start with?
Whichever one Amazon has already enrolled you in. If you are asked to support both, they are still built and tested separately, since each fails in its own ways.
What are 753 and 754 used for?
They are the routing request and routing instructions for Wholesale collect shipments, where Amazon arranges the freight. The vendor sends the 753 with pallet and carton details, Amazon replies with a 754 naming the carrier and pickup, and only then does the 856 go. See EDI 753 and 754 routing.
Related to Amazon EDI integration
Not sure which Amazon program you're actually on?
Tell us whether Amazon buys your stock, sends you dropship orders, or you sell on Amazon yourself, and we will tell you which integration you actually need.