In this guide 6 sections
Each channel keeps its own count. Sync delay, bundles that draw on shared components, returns not back on the shelf and stock held in carts all create phantom units that no warehouse can ship. One central record with reservation rules answers all four causes, because channels then ask for stock instead of owning it.
Every channel believes its own number
You list one SKU on two marketplaces and on your own Shopify or WooCommerce store, and each platform holds its own quantity. When an order lands on one channel, the others stay unaware until the next sync runs, and the gap grows when the connector polls only on a timer.
The gap can last minutes or hours. A fast-moving item sells out inside that gap, and the extra orders are real and paid, yet the warehouse has no unit left to put in the box. Those orders cannot ship.
Before changing anything, pull last month’s cancellations marked out of stock and group them by channel and SKU, because the pattern tells you which cause to fix first.
Sync delay and the polling gap
Many connectors poll marketplace orders on one timer and push stock levels back on another timer, so every sale waits for two clocks before the count falls. If the warehouse system updates only after a pick is confirmed, a third step sits between the sale and a reduced count on the marketplace listing.
Webhooks shorten the wait. Only some platforms offer them, and some marketplaces cap how often you may push inventory, so a burst of sales can outrun the limit.
Keep a buffer on fast sellers. List fewer units on each channel than you own, which is blunt but still keeps promises to buyers while the real fix is being built.
- Order poll interval per channel
- Delay between order and stock change
- API rate limits on inventory updates
- Safety buffer per fast moving SKU
Bundles, kits and shared components
A gift set is the classic trap. The set has its own SKU and its count, yet each unit consumes stock from the single items, so selling the singles leaves the set showing as available.
Define the bundle as a recipe. Its available quantity is the lowest result of each component’s stock divided by the amount the set uses, and the system calculates it, because typed counts drift.
Variants cause the same trouble. A shirt in six sizes and four colours is twenty four separate counts, and a listing mapped to the wrong one oversells quietly until the cancellations arrive.
Returns and stock held in carts
Returned goods often wait on a packing bench for days after the customer is refunded, so the unit is missing from sellable stock. The reverse also happens, with an unchecked return going straight back on sale in poor condition, which earns a complaint and a second refund.
Give returns a state. Received, inspected, restocked and written off are the four states, and only restocked units count toward the quantity shown to buyers, whichever channel they use.
Carts add pressure on your own store. Holding a unit for a shopper for fifteen minutes protects that buyer, but it also hides the unit from the marketplaces while the cart sits idle. Release holds on a timer.
What a central record with reservation rules changes
One stock record keeps one on-hand figure per SKU and location, and channels ask it for a reservation when an order lands instead of counting for themselves. The record answers yes or no.
Reservation rules decide who gets scarce units, so you might protect your own store, cap each marketplace or release stock to whichever channel pays the better margin.
Start with one page. Write down the buffer, the hold time, the bundle recipes and the return states, then check whether your current tools can carry every one of those rules.
Oversell cause log
One line per cancelled order. Columns cover order date, channel, SKU, ordered units, units on hand at that moment, minutes since the last sync and the suspected cause. The cause column offers four choices, namely sync delay, bundle, return not restocked or cart hold, so a month of lines sorts itself into a ranking.
Open a blank worksheet to printQuestions owners ask
Can a safety buffer solve overselling alone?
A buffer reduces overselling but wastes sales on slow days, so use it as a stopgap while you fix the sync gap and the bundle logic. It is a patch.
How should bundles be counted?
Treat the bundle as a recipe and calculate its availability from the scarcest component, so the gift set can never promise more than the singles allow. Never type a quantity on the bundle.
Do marketplaces penalise cancellations for no stock?
Most track a cancellation rate and may limit or suspend sellers who exceed it, so read the seller policy of each channel you use. Policies differ by channel.
Where should returned items be counted?
Only after inspection and shelving. Give returns states so that a refund never adds stock before the unit is physically back on the shelf and fit to sell.