Sellable Stock Formula for Marketplace Inventory

On 17 August 2026, the recurring pattern in seller forums is not "we forgot to count stock." It is "the platform said we had stock, but another channel had already taken it." Shopify sellers discuss overselling across Amazon, eBay and Etsy; Amazon forum posts complain about reserved FBA units that are not really sellable; competitor pages promise real-time sync but rarely show the actual calculation behind the number sent to the marketplace.

That gap is where multichannel inventory breaks. A seller can have 120 units on hand and still only be safe to publish 73. The difference is not accounting theory. It is open orders, reservations, returns inspection, unfulfillable FBA stock, bundle components, warehouse location rules and marketplace buffers. This article gives ecommerce teams a concrete sellable stock formula they can use before syncing inventory to bol.com, Amazon, Shopify, Zalando, Kaufland, Temu or TikTok Shop.

The formula: what you can sell is not what you own

The useful starting point is simple: sellable stock = eligible on-hand stock − committed orders − reservations − non-sellable stock − bundle constraints − channel buffer. For marketplace publishing, add one more rule: the final quantity can be capped by channel priority. If Amazon is your highest-velocity channel and a smaller marketplace creates cancellation risk, both should not receive the same last 10 units.

"Eligible" is the word many guides skip. On-hand inventory in a warehouse that cannot ship to Germany should not feed Kaufland. Stock in a retail store that is reserved for POS traffic should not automatically feed bol.com. FBA stock that Amazon marks as reserved or unfulfillable should not be treated like clean warehouse stock. ChannelDock's inventory feature overview is built around this distinction: one stock view is only useful when it reflects the rules behind the promise.

Why marketplace oversells happen even when sync is enabled

Most ranking articles on multichannel inventory stop at "use real-time sync." That advice is correct but incomplete. Real-time sync only moves a number quickly. It does not decide whether the number is safe. A bad formula sent quickly can create a faster oversell.

In the research pass for this post, Shopify Community threads repeatedly surfaced the same operational anxiety: sellers want Shopify, Amazon, eBay and other marketplaces to update immediately because overselling during busy days damages customers and seller metrics. Amazon Seller Central documentation separates available, reserved and unfulfillable FBA inventory. Shopify documentation separates on-hand, available and committed inventory. G2 reviews for tools such as Linnworks and Veeqo praise centralised inventory, while also showing that sellers care about SKU-level mapping, warehouse control and occasional sync delays.

The six-step sellable stock calculation

Use the formula as an operating process, not a spreadsheet once per week. Every stock update, order import, return inspection and manual adjustment should trigger the same calculation. The implementation can live in your WMS, ERP, OMS or in a marketplace operations layer such as ChannelDock, but the order of operations should stay consistent.

1. 1
   Start from location-level on-hand stock

   Use only the warehouses, stores or FBA pools that are allowed to fulfill the channel. Do not include inbound shipments until they are receipted or deliberately marked as releasable.
2. 2
   Subtract commitments before buffers

   Remove open orders, marketplace reservations, draft or unpaid orders that still block stock, B2B allocations, wholesale promises and transfer holds.
3. 3
   Remove non-sellable statuses

   Quarantined returns, damaged units, inspection holds and unfulfillable FBA stock should never flow to public inventory, even if they still sit physically on a shelf.
4. 4
   Apply the bundle constraint

   For bundles and multipacks, calculate the maximum buildable quantity from component stock. The lowest component decides the bundle quantity.
5. 5
   Apply channel buffers and caps

   Hold back a channel-specific safety layer and cap lower-priority marketplaces when stock falls below an agreed threshold.
6. 6
   Publish, then audit the acknowledgement

   A sync is only finished when the marketplace accepts the update. Log rejected updates, stale quantities and partial failures by SKU and channel.

Worked example: from 120 units on hand to 73 units published

Imagine a SKU sold through Shopify, bol.com and Amazon. The warehouse has 100 clean units. A second location has 20 units, but that location is not allowed to fulfill bol.com orders. Shopify has 9 committed units from unpaid or unfulfilled orders. Amazon has 4 FBA units reserved and 3 marked unfulfillable. The warehouse team has 5 returned units in inspection and 4 units held for a B2B customer. The product is also part of a bundle where a companion component limits buildable bundle stock by 7 units. Finally, bol.com gets a 5-unit buffer because cancellations are expensive.

The naive sync would publish 120. The formula starts with 100 eligible units for bol.com, subtracts 9 committed Shopify units, 4 Amazon reserved units if they draw from the same replenishment pool, 3 unfulfillable units, 5 returns inspection units, 4 B2B holds and the 7-unit bundle constraint. That leaves 68. If the extra 20 units are eligible for Shopify but not bol.com, Shopify may receive a different number. This is why one global "quantity" is often too blunt for multichannel sellers.

What competitors usually miss: acknowledgement and stale-stock risk

Linnworks, ChannelEngine, Veeqo, Sellbrite and similar tools rightly focus their inventory pages on centralisation, stock sync and oversell prevention. The missing operational detail is what happens after the update is sent. Marketplaces can reject an update, throttle it, accept it late, or leave one listing stale while another listing updates. A seller who only checks the central dashboard may believe the stock is safe while a marketplace still shows yesterday's quantity.

This is where ChannelDock's integrations layer matters. A reliable inventory process does not end with "we sent quantity 73." It ends with "bol.com accepted 73 at 10:04, Amazon accepted 68 at 10:05, Shopify accepted 88 at 10:05, and Kaufland rejected one child SKU because mapping failed." That difference is what turns sync from a hope into an audit trail.

Channel-specific buffers should reflect business risk

A universal 5% or 10% buffer is easy to explain, but it is rarely optimal. Marketplace risk differs by channel. A DTC Shopify store gives you more customer communication options, so showing 95% of sellable stock may be acceptable for many SKUs. A marketplace with stricter cancellation metrics or slower update acknowledgements may need a larger buffer. A flash-sale SKU on TikTok Shop needs a time-based buffer that expands before the campaign goes live. A long-tail SKU with one sale per month may need a fixed unit buffer rather than a percentage.

Good buffers are dynamic. They react to sales velocity, sync latency, rejection rate, return rate and margin. If a product sells 30 units per hour across Amazon and bol.com, a two-unit buffer is not meaningful. If a product sells twice per week, the same two units may be too conservative. The goal is not to hide stock. The goal is to publish the maximum quantity that your operation can fulfill without creating apology emails and marketplace cancellations.

How to measure whether the formula is working

Inventory teams should measure sellable stock quality with operational metrics, not only revenue. Track oversell incidents by channel, stock update rejection rate, stale quantity age, manual stock corrections, bundle stock conflicts, units hidden by buffer and lost-sales estimates from over-conservative buffers. If hidden stock keeps rising while oversells are already near zero, the formula may be too defensive. If oversells continue after buffers, the issue is probably reservations, stale acknowledgements or SKU mapping.

For sellers using ChannelDock, this measurement belongs next to order routing and warehouse execution. Inventory is not isolated from operations. The quantity you publish decides which orders arrive; the orders reserve stock; the warehouse confirms what really shipped; returns decide what becomes sellable again. Linking these flows through order management and inventory sync gives the formula real feedback instead of guesswork.

FAQ

Conclusion

The safest marketplace stock number is not copied from a shelf count. It is calculated. Multichannel sellers need a sellable stock formula that starts with eligible on-hand units and then deducts every promise, hold, non-sellable status, bundle limit and channel risk before publishing inventory to marketplaces.

That is the practical difference between "stock sync" and inventory control. Sync moves a number. A formula protects the promise behind that number. For sellers scaling across Shopify, bol.com, Amazon, Zalando, Kaufland, Temu and TikTok Shop, ChannelDock turns that promise into an operating process: one dashboard, connected integrations and stock rules that update before customers buy the last unit twice.