MarketplaceHub Docs Docs

Amazon

Report-based imports, separate content and price/stock submissions, per-country taxonomy, why submission success isn't listing success, and how orders arrive by notification.

Amazon is both a source and a publishing target. It is not currently available as a price and stock source of truth.

Amazon imports run through a report Amazon builds first, publishing splits into a content submission and a separate price and stock submission, and an accepted submission is not the same as a live listing IMPORTING — AMAZON BUILDS A REPORT FIRST Request a report we ask, Amazon queues Amazon builds it minutes, not instant We download it then enrich each row Rows land in the hub “nothing yet” is normal PUBLISHING — TWO SEPARATE SUBMISSIONS Content submission Title, description, images, attributes and the product type. Sent when the listing itself changes. Price and stock submission A separate, much smaller feed. This is why a price change does not re-send the whole listing. Accepted is not the same as live Amazon takes the submission, then validates it afterwards. A second wave of verdicts can arrive later and reject individual items. Taxonomy is per country: each Amazon country carries its own product types and required fields, so the same product can need different attributes in each.
A report first, then two separate submissions out.

Importing from Amazon

Products are pulled through Amazon's reports pipeline: a report is requested, Amazon prepares it asynchronously, and MarketplaceHub collects it when it is ready. Because that is a batch process rather than a live query, an import is not instantaneous — how long depends on Amazon's queue, not on catalog size.

Imported products carry the Amazon product type they were already filed under, so publishing back to Amazon in the same country skips classification entirely and costs no AI credits.

Publishing to Amazon

Listings are submitted as feeds. Content and price/stock go through separate submissions, which is what allows a stock change to be pushed without republishing a listing.

Amazon accepts a submission and validates it afterwards, so a successful submission is not yet a successful listing — the outcome arrives later and surfaces as a notification. Listings rejected at that stage are usually missing a field the product type requires, which is what the review step flags before you publish.

Taxonomy

Amazon product types are imported per country on a recurring schedule. Amazon UK and Amazon DE are different taxonomies with different required fields, and are versioned independently — see Product types and taxonomy versions.

Identifiers

Amazon both ranks and gates on product identifiers, so supplying a barcode in your feed materially affects whether a listing is accepted. See the product feed format.

Orders

Amazon orders are pulled into MarketplaceHub, and three actions can be sent back: confirming an order as shipped, cancelling it, and refunding it.

How new orders arrive

Two paths, and they cover for each other. Amazon notifies MarketplaceHub when an order changes, which triggers a pull straight away; independently of that, a pull runs on a schedule roughly every ten minutes.

The notification is treated as a doorbell rather than as data — the order itself is always read from Amazon — so a notification that arrives late, twice, or out of order costs nothing, and a burst of them collapses into a single pull.

Sending actions back

Confirmations, cancellations and refunds are sent as feeds, the same mechanism listings use, and they go out on a short recurring sweep rather than the instant you act.

So the caveat from publishing applies to orders too: Amazon accepts a feed and validates it afterwards, which means a submitted action is not yet a completed one. This is the practical difference from eBay, where the equivalent operations are direct API calls that report success or failure in their own response.