Syncing stock across channels: a guide to avoid overselling

Syncing stock across channels means your online store, Amazon and every marketplace you sell on show the same real-time availability, deducting instantly whatever sells on any one of them. Get it wrong and the day your best-selling product runs low, you'll sell the same unit twice, have to cancel, and the marketplace will log it against your account.

The reliable way to do this has four parts: a single master inventory (your warehouse system, an ERP, or your logistics operator's system), the same SKUs across every channel, updates every time something happens rather than just overnight, and a safety margin per channel. Below you'll find how to set it up, which tool fits your volume, a worked example with figures, and the mistakes we see every day in the warehouse even when the integration is up and running.

What syncing stock across channels actually means

Syncing stock across channels means keeping a single inventory figure per SKU and distributing it automatically to every place you sell. When an order comes in through any channel, stock arrives at the warehouse, or a return is validated, the master system recalculates the sellable quantity and pushes it out to every channel within minutes, not at the end of the day.

Watch out: this isn't about publishing the same number everywhere. Say you have 500 units of a product. Of those, 40 are reserved for paid orders still being picked, 25 have a quality issue, and 80 are committed to an already-confirmed B2B order. Your available stock isn't 500: it's 355, and from there each channel gets whatever your rules decide.

Physical, reserved and sellable stock

Separating these three states avoids most of the headaches. Physical stock is what's physically counted in the warehouse. Reserved stock covers sales, transfers or commitments that already use up units even though they haven't shipped yet. Sellable stock is the quantity you decide to offer on each channel.

When these three get muddled into a single field, overselling follows. And so does the opposite: phantom stockouts, with product sitting on the shelf that isn't listed because nobody updated the figure after a delivery or a return fit for resale.

Ways to sync inventory: from spreadsheets to warehouse systems

Not every store needs the same setup. Here are the four common approaches, from simplest to most robust.

Manual, with a master spreadsheet

You track stock in a shared spreadsheet and update each channel by hand or by importing a CSV. It works with few SKUs, a single extra channel and low turnover. The problem shows up as soon as you sell several units a day of the same SKU: between one update and the next, every channel is selling stock that no longer exists.

Multichannel apps and connectors

Shopify, WooCommerce and PrestaShop have apps and modules that publish your catalogue on Amazon and marketplaces and deduct stock across them. For a store that picks its own orders in-house, they're a solid step up. Their limit: they know what's being sold, but not what's happening in the warehouse (a delivery that arrives three units short, a damaged item, a return that isn't resaleable).

An ERP as the source of stock

If you already use an ERP or a management tool like Holded for invoicing and purchasing, it can act as the master and push stock out to your channels. It fits when purchasing, sales and accounting all live there. It demands discipline: every warehouse receipt and adjustment needs to be logged in the ERP, or the figure drifts.

The warehouse or logistics operator's system

This is the most reliable option because stock is calculated where the goods actually are: counted receipts, locations, confirmed picking, dispatches and checked returns. It's standard once you pass a few hundred orders a month across several channels, or when you outsource logistics. As a rough guide: with one channel and low turnover, a spreadsheet or app will do; with three or more channels and products that sell out, the master should be the system that physically touches the goods.

How to sync stock across channels, step by step

The process starts before you pick a connector. Automating a messy catalogue just propagates errors faster.

1. Define a single master inventory

Choose one system as the only one that knows the physical quantity per SKU. Everything else (store, marketplaces, ERP) receives the figure from there. Your store can show availability to customers, but it shouldn't be the place where someone manually corrects quantities. If two people adjust stock in different systems, discrepancy isn't a risk: it's a certainty.

2. Standardise SKUs and variants

Every product and every variant (size, colour, format, pack) needs a unique SKU, identical across every channel. A similar-sounding title doesn't cut it. Before connecting anything, check for duplicates, SKUs reused from discontinued products, and variants created manually in just one channel.

Packs are the classic trap. If you sell a three-pack alongside the single item, selling the pack has to deduct three units from the component. If the pack is its own SKU with independent stock, the channel will keep selling single units that have already gone out inside packs.

3. Map each channel's identifiers

Amazon works with your seller SKU and the ASIN; many marketplaces ask for the EAN; your store uses its own variant ID. Build an equivalence table and check that every reference on every channel points to the correct master SKU. A cross-mapping error (size M listed as L) causes returns that look like picking mistakes but aren't.

4. Reserve stock when the order is created, not when it ships

A unit should stop being available the moment a paid order comes in, not when it leaves the warehouse. Also decide what happens with orders pending payment, transfers, or B2B orders confirmed by email: if they use up stock, they need to reserve it immediately.

5. Set buffers and priorities per channel

A buffer is a quantity you don't publish even though it exists. It absorbs sync delays, simultaneous sales and small counting discrepancies. A fixed buffer (2-5 units, as a rough guide) works for stable lines; a percentage-based one suits fast-moving products better.

You can also set thresholds: when a SKU drops below 10 units, it's marked out of stock on marketplaces while staying on sale in your own store down to a minimum reserve. It's a commercial decision: your store gives you more margin and customer data; the marketplace gives you volume but penalises cancellations more heavily.

6. Have a plan for when the integration fails

Connections fail: an expired token, an API change, a deactivated listing. The system should alert you, log the error and, if the risk is high, lower the published availability. Selling less for a couple of hours is cheaper than accepting orders you can't fulfil. Test with real orders on your best-selling SKUs before trusting it fully.

How often to sync inventory between channels

It depends on how fast each product moves. An overnight sync might be enough for a slow-moving catalogue with comfortable stock levels. For launches, promotions or lines with few units left, the gap between updates is exactly where overselling is born.

Event-based updates are ideal: every order, receipt, cancellation or validated return triggers a change across every channel. If your tool only allows set intervals, shorter is better, and compensate with higher buffers on your best sellers. Ahead of peaks like Black Friday, check your integrations can handle the volume before it hits; we cover this in how to