How to Sync Inventory Across Marketplaces and Your Own Store
Practice3 minInnovialabs editorial team
In short
Keep stock in one system and let every channel receive the available quantity with a small buffer from it; a sale in any channel immediately reduces the shared stock.
The core rule: one source of truth
If you sell on your website and several marketplaces, stock must be stored in one place: your accounting system, WMS, CRM or a dedicated sync service. Channels do not keep their own stock — they only receive the available-to-sell quantity from the center and report sales back.
The flow is simple:
- An order arrives from any channel.
- The central system reserves the item and reduces stock.
- The new available quantity is pushed to all other channels.
When stock is edited by hand in every seller dashboard, sooner or later the same item gets sold twice.
What available stock means
Physical stock in the warehouse and what you can sell are different numbers.
Available to sell = on hand − reserved for orders − safety buffer
- Reserved — items in placed but not yet shipped orders.
- Buffer — a small amount you do not show to channels. It covers the gap between a sale and the stock update in other channels.
You can set the buffer in different ways: a fixed quantity, a rule like "show zero if fewer than N remain", or a separate quota per channel. The buffer matters most for fast-moving items with low stock.
How marketplace APIs work
Major marketplaces offer APIs to update stock and fetch orders. Common points to plan for:
- Rate limits — you cannot send an unlimited number of single-item updates. Group updates into batches.
- Fulfillment models — when you ship from your own warehouse, you manage stock yourself; when the goods sit in the marketplace's warehouse, the platform manages that stock and syncing works differently.
- Product mapping — each platform has its own listing ID. You need a mapping table "your SKU ↔ platform ID".
- Fetching orders — via webhooks or regular API polling.
Before building, read each platform's documentation: rules and limits differ and change over time.
Update intervals
| Event | How often |
|---|---|
| New order in any channel | Immediately or within minutes |
| Cancellation or return | Immediately, stock goes back |
| Goods received at warehouse | After receiving is posted |
| Full stock reconciliation | Daily or more often |
Event-driven updates give you speed, while a regular full reconciliation fixes whatever slipped through: a failed request, a manual edit, an outage on the platform side.
Ready-made tool or custom integration
Multichannel commerce services fit when:
- your marketplaces are popular and supported by the service;
- your accounting system is standard;
- you need quick setup without development.
A custom integration makes sense when:
- you run a customized 1C or an in-house system;
- you need your own rules for reserves, quotas and channel priorities;
- some platforms are not supported by off-the-shelf tools;
- order volume is high and you need control over the logic.
Common mistakes
- Stock is edited manually in marketplace dashboards.
- No SKU mapping table — updates land on the wrong listings.
- Cancellations do not return items to stock.
- API errors are not logged, and a listing shows the wrong quantity for weeks.
- No buffer on items with only a few units left.