EDI System Integration

Connect Amazon to EDI instantly

Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Amazon and their trading partners on XEDI, no manual re-keying.

No credit card needed ✦ Free EDI mailbox included

Amazon logo
Overview

Getting started with Amazon EDI

XEDI connects you to Amazon as a vendor, handling the purchase orders, shipment notices and invoices a Vendor Central relationship runs on, with the compliance detail Amazon deducts against when it is wrong.

One managed platform, no custom code

XEDI maps Amazon to your trading partners and validates every document, so data flows straight into the systems your teams already use.

Vendor is a trading relationship; Seller is a marketplace

Amazon operates two entirely separate arrangements and they are routinely confused. As a vendor you sell to Amazon: they raise a purchase order, you confirm it, you ship to their fulfilment centres, you invoice them. As a seller you sell on Amazon to consumers, and there is no purchase order at all.

This page is about the first. If you are a marketplace seller, the Seller Central integration is the relevant one, and the difference matters because the documents, the obligations and the penalties are not the same.

Amazon measures you, and deducts when you miss

Few trading partners are as exacting. Acknowledgements are expected within a defined window, shipment notices have to arrive before the goods do, and the carton detail has to match what is physically delivered to the receiving site. Miss any of it and the deduction arrives automatically.

That is why the timing and content rules are held and enforced by us rather than left to a person watching a portal. A shipment notice that is accurate but late costs the same as one that never came.

What your team sees day to day

You get an EDI mailbox and a portal that works like an inbox. Amazon purchase orders arrive, your team is notified, and the acknowledgement window is visible rather than being something someone remembers.

The order becomes the shipment notice built from what is actually being sent, amended where you are supplying less than ordered, with SSCC labels for the pallets, and becomes the invoice, whose delivery is confirmed in the dashboard.

Where you run an ERP or warehouse system, the integration sits over that workflow and automates it. Smaller vendors work the portal alone; our API suits larger operations wanting finer granularity.

Documents you can exchange

  • Amazon purchase orders landing in your systems
  • Purchase order acknowledgements confirming what you will supply
  • Advance shipment notices carrying carton and pallet detail
  • Invoices raised against the shipment
  • Remittance and adjustment information
Who it's for

Built for Amazon teams

Whoever owns Amazon in your business, XEDI keeps EDI accurate and hands-off.

  • Brands supplying Amazon as a vendor
  • Supply chain and account teams
  • Despatch and warehouse teams
  • Finance teams handling deductions and reconciliation
  • Businesses moving off Vendor Central's web forms
Document flows

Amazon EDI document types

These are the flows a Vendor Central relationship runs on.

Document What it carries Direction
Purchase orders Amazon's demand, carrying the delivery window and fulfilment centre the goods must reach. Amazon to you
Purchase order acknowledgements Your confirmation of what will be supplied, expected inside the window Amazon measures. You to Amazon
Advance shipment notices Carton and pallet detail sent before the delivery arrives, matched against what the receiving site scans. You to Amazon
Invoices Raised against the shipment and referenced so Amazon can match without intervention. You to Amazon
Remittance advice What Amazon has paid and what it has deducted, against your own invoice record. Amazon to you
Catalogue data Item and pack data where Amazon requires it maintained against your range. You to Amazon
Integration

How to connect Amazon with EDI using XEDI

An Amazon vendor connection is as much about timing as about content. The sequence below is what onboarding looks like from your side.

  1. 01

    We confirm you are trading with Amazon as a vendor rather than a marketplace seller, since the two work nothing alike.

  2. 02

    We build the mapping between Amazon's documents and your own order, despatch and invoice records.

  3. 03

    We configure validation against Amazon's requirements, including the acknowledgement and shipment windows they measure you on.

  4. 04

    We prove the purchase order, acknowledgement, shipment and invoice flows against what Amazon actually requires.

  5. 05

    You get a connection that meets Amazon's timing rules, and we keep it right as those requirements change.

Ready to connect Amazon?

Talk through documents, mapping, testing and go-live with XEDI.

Detail

Everything about Amazon EDI

Common requirements
  • Your vendor account details and ship-from locations
  • Product identifiers as Amazon holds them
  • Carton and pallet configuration
  • Lead times and acknowledgement rules
  • Which other trading partners you deal with, or plan to
What we need from you to build it

Only what we cannot hold for you. Amazon's requirements, including the windows they measure, are already ours.

Vendor account details
The vendor codes and ship-from locations in scope, since Amazon's routing and measurement follow them.
Product identifiers
Your items against the identifiers Amazon holds, at each packaging level they expect to scan.
Carton and pallet configuration
Units per carton and cartons per pallet, because the shipment notice has to describe the physical delivery exactly.
Lead times
What you can realistically commit to, so acknowledgements reflect reality rather than optimism.
Your other trading partners
Amazon is rarely the only one. The rest are already held by us and can run through the same connection.
Why suppliers choose XEDI for Amazon
  • Amazon is connected already, as are the other retailers you are likely supplying alongside it.
  • Acknowledgement and shipment timing is enforced by the platform rather than remembered by a person.
  • Carton and pallet detail is built from what is actually being sent, which is what the receiving site scans.
  • Amazon's requirements are held and maintained by us, including when they change.
  • The same connection carries your other retailers, so Amazon is not a separate operation with its own process.
  • If Amazon raises a problem, it comes to us, and we rectify it rather than it arriving as a deduction you have to dispute.
Is this for Vendor Central or Seller Central?

Vendor Central, where Amazon raises a purchase order and buys from you. If you sell on the marketplace to consumers, the Seller Central integration is the relevant one, because there is no purchase order in that relationship.

Can you help with Amazon chargebacks?

Prevention rather than dispute. Most deductions come from late acknowledgements, shipment notices that arrive after the goods or carton detail that does not match, and those are enforced before the document leaves.

Do we need EDI to be an Amazon vendor?

Amazon expects electronic trading for meaningful volume, and the web forms become impractical quickly. The portal covers it without an integration, and the integration is added when re-keying becomes the constraint.

Next steps

Plan your Amazon EDI setup

Everything you need to scope, map and go live with Amazon, in one place.