Marketplace integrations

Every connection is a source, a publishing target, or both. What each channel supports differs, mostly because of what its API offers rather than what we chose.

Orders

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

Shopify and Etsy do not sync orders. Their listings and their stock do — orders stay in the store.

Two rules that apply everywhere

• Publishing never duplicates a listing. When MarketplaceHub already holds a native id for a SKU on a marketplace and country, publishing revises that listing instead of creating a second one. The ids are stored per SKU — see Platform Product vs Product.
• A price or stock change never echoes. When a change arrives from one channel it is propagated to the others but explicitly excluded from being pushed back to the channel it came from, which is what stops a webhook triggering a write that triggers the same webhook again.

Your own system, through the API

The table above is about marketplaces. The MarketplaceHub API lets your own system act as a channel: create products, read orders and confirm, cancel or refund them, and — like Shopify and Etsy — be a source of truth for price and stock, so an ERP or in-house system can drive your catalog without a feed file.

Changes arriving that way propagate to every connected marketplace under the same two rules above. You can also register an endpoint to receive events, so your system is told when something happens instead of polling to find out.