The arithmetic that decides the architecture
Magento plus four marketplaces is five channels. Synced as pairs, that is ten relationships, each with its own mapping table, its own timing and its own way of writing a stale number over a fresh one. Synced through one hub it is five relationships and a single authoritative available quantity. That is the whole design decision, and it is worth making before you connect the second channel rather than after.
Magento keeps what it is good at: catalogue, content, pricing rules and the storefront experience. What it should stop owning is the number that says how many you can sell — because Magento cannot know that a Temu order reserved three units ninety seconds ago.
Who owns what
| Data | Owner | Direction |
|---|---|---|
| Product content, images, SEO | Magento | Stays in Magento |
| Internal SKU and barcode | Inventory hub | Mapped to every channel identifier |
| Available quantity | Inventory hub | Pushed outward to Magento and all marketplaces |
| Orders | Each channel | Pulled inward into one order book |
| Fulfilment and tracking | Inventory hub | Pushed back to the originating channel |
| Channel price | Whoever prices that channel | Do not centralise this by default — margins differ per channel |
The order to do it in
- Magento first. It usually has the cleanest catalogue and you can verify a mapping by looking at a product page. Import products and variants, and map configurable products at the child level, because that is where stock actually lives.
- Highest-volume marketplace second. Enable order import only. Watch a day of real orders land with the right SKUs, addresses and totals before you let anything write stock.
- Turn on stock push for a small SKU set. Ten SKUs, across the two connected channels, for a few days. Compare the pushed number against a physical count on two of them.
- Add Temu and Groupon. Map Temu goods IDs deliberately — goods ID mapping has its own failure modes. Groupon needs the deal quantity thought about before the deal, not after.
- Widen to the full catalogue, then put the unmapped identifier count on a weekly report and keep it there.
Buffers, per channel and not globally
A buffer is the quantity you hold back from a channel to absorb the gap between a sale happening and every other channel hearing about it. The right size depends on how fast the channel can sell and how badly it punishes a cancellation:
- Groupon deal, TikTok livestream: concentrated demand with a start time. Ring-fence a quantity rather than relying on a buffer at all.
- Amazon, eBay on fast movers: a small buffer sized from peak hourly velocity, not average daily.
- Slow-moving long tail: often zero. A buffer on a SKU that sells twice a month is just stock you cannot sell.
- Magento storefront: usually the lowest buffer, because it is the channel where you control the cancellation experience.
The oversell risk calculator will size these from your own velocity and update interval.
The failure mode to instrument for
Unmapped identifiers. A marketplace listing with no mapping still imports its orders perfectly, which is why this hides so well — the order book looks healthy. What it never receives is a stock update, so it keeps advertising whatever quantity it last knew about, and it oversells silently until a customer complains.
Treat the unmapped count as an operational metric with an owner, not a setup task you completed in week one. New listings appear, variants get added, and a supplier changes a pack size; each of those creates a new unmapped identifier.
Bundles and kits
A Magento bundle needs a component definition in the hub so availability can be computed from the scarcest part. Without it, the bundle inherits a stock number from nowhere in particular and promises kits you cannot build. Define the components, then let the hub derive the sellable quantity — and re-derive it every time a component moves.
Where to go next
The connector detail is on the Magento integration page, the full live connector list is on marketplace integration, and the step-by-step version of this with validation checkpoints is the multi-channel stock sync playbook.
Magento is live. Shopify is at foundations and limited-onboarding stage rather than an unconditional live connector; WooCommerce and OnBuy are roadmap items. Reviewed 23 August 2026.