Marketplace integrations
What each connected channel actually does: which direction data flows, whether changes are pushed or polled, and how often.
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.
| Channel | Import from | Publish to | Price & stock source of truth |
|---|---|---|---|
| Amazon | Yes | Yes | Not yet |
| eBay | Yes | Yes | Not yet |
| Shopify | Yes | Yes | Yes — pushed by webhook |
| Etsy | Yes | Yes | Yes — polled |
| CSV / JSON feed | Yes | — | Yes |
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.
Amazon
Report-based imports, separate content and price/stock submissions, per-country taxonomy, and why submission success isn't listing success.
Read pageeBay
Listing imports, why price and quantity travel with the inventory submission rather than separately, and the signing requirement on EU/UK order operations.
Read pageShopify
The most complete integration: bidirectional sync plus webhook-driven price and stock, with the events MarketplaceHub subscribes to.
Read pageEtsy
Why Etsy stock is polled rather than pushed, how the incremental read works without a modified-since filter, and the 10-minute to 6-hour cadence ladder.
Read page