Amazon

The Amazon connector turns every shipped business order on a seller's European Amazon stores into an e-invoice and uploads the invoice PDF back to Amazon, where the buyer finds it under Your Orders as they do today. It is built for sellers enrolled in Amazon's VAT Calculation Service (VCS) who chose the second invoicing option, "I will upload my own VAT invoices" — the option Amazon says is available only through a solution provider that implements its invoice-upload feed. GoRoute is that provider.

The connector is a pull connector (connector_type amazon): the seller authorises GoRoute once, and GoRoute reads orders, the VAT Invoice Data Report and the upload results through Amazon's Selling Partner API every few minutes. Nothing is installed on Amazon's side.

Availability

Amazon is switched on per organisation, and the connector is new (September 2026). GoRoute's Selling Partner application is registered with Amazon and awaiting Amazon's developer review for the Tax Invoicing (Restricted) role, which is what releases a buyer's name, address and VAT number to an application. Until that review completes, the connector works against Amazon's sandbox and against sellers Amazon has allowed to authorise the draft application; no real buyer's order is read before approval.

Two checks before you plan work around it: open Connectors in GoRoute and look for the Amazon card (if it is not there, ask us to switch the connector on for your organisation), and confirm your VAT Calculation Service is set to I will upload my own VAT invoices in Seller Central → Settings → Tax Settings → VAT Calculation Settings. Amazon has no API for that setting, so the connector asks you to confirm it with a checkbox.

Who it is for

A seller registered in one of the ten stores where VCS exists — Belgium, Germany, France, Italy, Spain, the Netherlands, Sweden, Poland, Ireland or the UK — with that country's identifier registered under Participants in GoRoute (the enterprise number under 0208 for Belgium, the VAT number under 9930 for Germany, and so on). The legal name, VAT number and address on the invoice come from Settings → Company; nothing is typed into the connector.

Buyers are the seller's business customers — Amazon Business orders (IsBusinessOrder) and any order whose buyer gave a VAT number. Consumer orders are never invoiced by GoRoute.

Connect

One click. In GoRoute open Connectors → Amazon, choose where you sign in to Seller Central, and press Connect with Amazon. Amazon's consent page asks you to authorise GoRoute; when you do, Amazon sends you back and the connector is active: your stores are discovered and the ten VCS stores among them are enabled. Starting from GoRoute's listing in the Selling Partner Appstore ends in the same place.

Fallback. A seller who has self-authorised the application in Seller Central (Apps & Services → Manage Your Apps) can paste the refresh token Amazon showed them instead, with the region. That is also how the sandbox is connected. The token is proven in three stages before anything is saved — Amazon's sign-in, the API, and whether any of your stores is a VCS store — and a failure names the stage. Tokens are stored encrypted and never shown again.

While GoRoute's application is still a draft with Amazon, the consent URL carries version=beta, which authorises the draft version; the connector page says so.

The readiness list

Once connected the connector page shows what is still needed, in facts, without calling Amazon:

Check	What it means
Amazon authorised	how (consent page or pasted token) and where (live or sandbox)
Stores found	which of the ten VCS stores you trade in
Seller identity complete	legal name, VAT number and address are on file under Settings → Company
Seller registered on the network	your identifier is registered for e-invoicing (SMP); until it is, nothing is sent and the connector says so
VCS set to "I will upload my own invoices"	your confirmation — Amazon exposes no API for it
Buyer details released by Amazon	whether Amazon issues the restricted token that carries buyer details (it does once the Tax Invoicing role is granted); invoices are built from the VAT Invoice Data Report meanwhile
VAT Invoice Data Report	the state of the last report request
Uploads within Amazon's business day	shipments past the window without an accepted upload, named

What gets invoiced

Every cycle (five minutes by default) the connector reads the orders updated since the last cycle, keeps the business ones, reads each such buyer once under a Restricted Data Token, and requests one VAT Invoice Data Report for all your stores at once. Amazon lists in that report every shipment and refund of the last 90 days whose invoice or credit note is still owed, with the VAT figures Amazon itself calculated.

In the report	What happens
A shipment of a business order	One invoice, numbered prefix + shipping id (default AMZ-), keyed on the shipment so a repeat in the next report is answered with the invoice already filed
A return or refund	One credit note citing the shipment's invoice, numbered prefix + CN- + Amazon's transaction id
A shipment for which Amazon issues the invoice itself, or one already uploaded	Nothing
A consumer shipment	Nothing — consumers are not e-invoiced

The invoice. Buyer name (the company legal name), billing address and VAT number as Amazon gave them; the buyer's Peppol address derived from the VAT number by country (the enterprise number under 0208 in Belgium, the VAT number under the country's VAT scheme elsewhere). One line per order item at Amazon's VAT-exclusive price and the rate Amazon applied, a Shipping and a Gift wrap line where Amazon charged them, promotions as allowances, an intra-Community supply exempt with Amazon's citation, EUR or the store's currency, the purchase-order number as the buyer reference, the shipment date as the delivery date, and a note that the order was paid through Amazon. The totals are Amazon's; if what GoRoute computes from the lines differs from Amazon's figures by more than a cent the document is held, never issued, because Amazon would reject the upload.

Delivery. Over Peppol when the buyer resolves on the network. When the buyer does not, and the seller's country allows a document outside the network (Germany and most of the EU), the invoice is issued and the PDF/A-3 hybrid (ZUGFeRD in Germany, Factur-X in France) is what Amazon shows the buyer. Where the law forbids that (Belgium, Italy, Poland) the shipment is held with the reason and re-presented every quarter of an hour.

The PDF back to Amazon. After the document is issued, GoRoute renders its PDF — the hybrid for an EU seller — and uploads it with Amazon's UPLOAD_VAT_INVOICE feed, carrying the shipment id, the invoice number printed on the PDF, Amazon's own total and VAT amount, and CreditNote plus the return's transaction id for a credit note. Amazon's processing report is read back and its acceptance, or its error text, is recorded on the transaction. An upload Amazon keeps refusing is tried six times and then reported on the connector page with Amazon's reason, so it can be uploaded by hand.

Amazon's clock. Amazon expects the invoice within one business day of dispatch. A shipment past that without an accepted upload is counted and named on the connector page.

Held shipments and their reasons

A shipment that cannot be invoiced is held — parked on the connector with a reason, listed on the connector page and in held invoices — and never blocks the shipments behind it. Reasons you will see:

Reason	What to do
… cannot receive e-invoices yet, and a seller in BE may not deliver a business invoice outside the network	The Belgian buyer has not appointed a Peppol provider. GoRoute asks the network every quarter of an hour. If they will not join, invoice by hand and upload the PDF in Seller Central
… is a business buyer but Amazon gave no VAT number for this shipment	Ask the buyer to add their VAT number to their Amazon Business account, or invoice by hand
… gave 'X' as its VAT number …, which is not a Belgian enterprise number / fails its mod-97 check digit	The number is wrong. Ask the buyer for the right one, or invoice by hand
… is billed in XX, for which GoRoute has no Peppol VAT scheme	Invoice that shipment by hand
The totals GoRoute computes from Amazon's lines … differ from Amazon's own figures	Ours to look at — email admin@goroute.ai with the shipment id
… could not be processed because of an error on GoRoute's side	Ours. Retried automatically; nothing to do

What the connector holds, and for how long

Every read of a buyer's details is logged with the organisation, the order and the purpose (tax_invoice). The order, buyer and item data Amazon releases, and the report rows, are kept only until the invoice is issued and for 30 days after the order's delivery, then deleted — the deletion is logged. The issued invoices and credit notes are tax records and stay in your register. Refresh tokens are stored encrypted; the platform's own Amazon credentials live in a secrets store, never in configuration or logs.

Limits worth knowing

• The Tax Invoicing (Restricted) role gates real orders. Until Amazon's review grants it, the restricted buyer read is refused; the connector says so on the readiness list and builds invoices from the VAT Invoice Data Report, which also needs that role for a real seller.
• The report is Amazon's. Only a seller enrolled in VCS gets the VAT Invoice Data Report; a seller on VCS option 1 (Amazon issues the invoices) has nothing for GoRoute to invoice.
• One report per cycle, one order list per minute. Amazon allows getOrders once a minute and the report request once a minute; the connector stays under both, so a shipment reaches the network within a cycle or two of Amazon listing it, well inside Amazon's business day.
• Refund amounts are Amazon's. A partial refund's credit note carries the figures Amazon put in the report, and Amazon's totals must match to the cent or the upload is rejected.
• No buyer email. Amazon anonymises the buyer's address; the hybrid PDF reaches the buyer through Amazon's own upload, not by an email GoRoute sends.
• The PDF uploaded to Amazon is GoRoute's English rendering of the document.

API

The connector uses the shared lifecycle endpoints plus its own one-click authorisation; the connect body and the authorisation actions are described under Connector API → Amazon.

What was verified against Amazon's documentation

Written against the Selling Partner API as Amazon publishes it (developer-docs.amazon, read 2026-09-25): the website and Appstore authorization workflows (the consent URL, version=beta for a draft application, the five-minute spapi_oauth_code, the authorization_code and refresh_token grants at api.amazon.com), the Orders API v0 (getOrders with LastUpdatedAfter, IsBusinessOrder, getOrderBuyerInfo and getOrderItems under a Restricted Data Token from the Tokens API), the Sellers API (getMarketplaceParticipations), the Reports API (GET_FLAT_FILE_VAT_INVOICE_DATA_REPORT with the pendingInvoices option; the column header of Amazon's own sample file), the Feeds API (UPLOAD_VAT_INVOICE with metadata:ShippingId, metadata:OrderId, metadata:InvoiceNumber, metadata:TotalAmount, metadata:TotalVATAmount, metadata:DocumentType and metadata:TransactionId, one upload every three seconds), the VCS error codes, and the store identifiers of the ten VCS stores. The sandbox proved the sign-in, the store list and the static order case; the report, the restricted buyer read and the upload wait for the first approved seller.