Available-to-Sell Inventory: The Marketplace Stock Formula
Amazon Seller Central's cancellation-rate policy says seller-fulfilled offers can be deactivated when the cancellation rate rises above 2.5%. That number matters for multichannel sellers because many cancellations do not begin with a bad pick. They begin with the wrong stock number being published to a marketplace.
Available-to-sell inventory, often shortened to ATS, is the control layer between physical stock and sales-channel stock. It answers one operational question: how many units can this channel safely accept right now after reservations, damaged stock, safety stock, buffers and channel commitments are removed? For sellers active on bol.com, Amazon, Shopify, WooCommerce, Zalando, OTTO, Kaufland, Temu or TikTok Shop, that answer is more important than the raw warehouse count.
Why raw stock creates marketplace risk
Most competitor content on multichannel inventory management says the same useful but incomplete thing: centralize stock and sync it in real time. Linnworks talks about stock buffers and listing suppression. ChannelEngine documents stock reservations before marketplace updates. Veeqo, Cin7, Brightpearl and other platforms all position real-time inventory sync as the answer to overselling.
The missing layer is the formula behind the number. A seller can sync quickly and still publish the wrong quantity if the source field is on-hand stock instead of available-to-sell stock. Shopify's own inventory states make the distinction clear: on-hand inventory is the sum of committed, unavailable and available units. Available stock is what can be sold. When an integration ignores that difference, stock sync becomes fast error distribution.
The ATS formula multichannel sellers should use
The cleanest ATS formula starts with sellable on-hand inventory, not total physical stock. A warehouse may physically hold 120 units, but 9 are damaged after returns, 14 are already committed to open orders, 5 are reserved for B2B buyers and 4 are held as a channel buffer for Amazon. Publishing 120 to every channel would be reckless. Publishing 88 may be safe.
Practical formula: available-to-sell = on-hand sellable stock − open reservations − damaged or quarantined stock − channel buffer − protected commitments.
Incoming purchase orders should not enter ATS until the goods are received, checked and usable for the channels that will see the quantity.
ChannelDock's inventory feature overview and marketplace integrations are built around this principle: channels should receive controlled stock updates from one operational source of truth, not disconnected manual edits.
What current ranking pages usually miss
Search results for “multichannel inventory management” are strong on benefits and weak on decision rules. They explain overselling, stockouts and centralized dashboards, but they rarely say which units should be subtracted before the marketplace sees a quantity. Forum discussions are more practical. Shopify Community threads repeatedly mention SKU mapping, source-of-truth conflicts, sync delays and missing audit logs. Reddit sellers describe the same pain in simpler terms: one system says stock exists, another system has already promised it.
That gap is where ATS control earns its value. The purpose is not only to avoid selling the last unit twice. It is to make every marketplace quantity explainable.
Raw on-hand sync
- Publishes the physical warehouse count.
- Ignores open orders that are not picked yet.
- Lets damaged or quarantined units leak back into sales.
- Looks simple until two channels sell the final units.
Available-to-sell controlRecommended
- Publishes stock after reservations and buffers.
- Protects key marketplaces from cancellation penalties.
- Handles POS, webshop, B2B and marketplace demand from one rule set.
- Creates an audit trail when a channel quantity changes.
The five-step control model
For an ecommerce team, ATS should be an operations workflow before it becomes a software setting. The following sequence works because it separates stock classification, reservation timing, channel risk and exception handling.
- 1Separate physical stock from sellable stockCount what exists, then classify what can actually be sold. Damaged, quarantined, returned, reserved and inspection stock stays out of ATS until it is cleared.
- 2Reserve stock at order creationThe central inventory system should reserve units as soon as an order lands, before the next stock push goes to slower marketplaces.
- 3Apply channel-specific buffersUse larger buffers where cancellation penalties are harsher, sync latency is slower or the SKU sells in bursts during campaigns.
- 4Publish ATS, not on-handEvery connected channel should receive the safe quantity, not the warehouse total. The webshop, marketplace and POS can still display different values if the rule is intentional.
- 5Reconcile exceptions dailyAudit SKUs where marketplace quantity, WMS quantity and Shopify available stock no longer match. Most oversells start as a small unmapped exception.
Where buffers help and where they hurt
Buffer stock is useful when the sales channel is slower than the warehouse reality. It protects against API delay, order bursts, weekend staffing gaps and marketplace latency. But it should not be a universal tax on the catalogue. A high-margin bol.com bestseller and a slow-moving spare part do not need the same rule.
A fixed buffer of 5 units on every SKU feels safe, but it can quietly hide sellable stock on slow movers and still be too small for a viral TikTok Shop product. Buffers should follow velocity, margin, channel penalty and sync reliability.
A better model uses channel-specific buffers. Amazon seller-fulfilled stock may need a stricter rule because cancellations can affect account health. A webshop might accept lower buffers because the seller controls the customer communication. B2B commitments may need protected stock pools because a key account order can matter more than a single marketplace sale.
How ATS connects to reservations, returns and bundles
Available-to-sell control becomes especially important once a catalogue includes bundles, kits and returned stock. If one bundle consumes the last unit of a component SKU, every other bundle using that component needs an immediate stock update. If a return arrives damaged, it should increase on-hand stock but not ATS. If a POS sale happens in a store, the marketplace stock should fall before a second buyer can take the same unit online.
This is why sellers should connect ATS logic to order processing, returns and warehouse events. A stock formula that only updates after a nightly import is not a control system. It is a delayed report.
The safest marketplace stock number is not the biggest number you can defend. It is the smallest number that still lets the right channels keep selling without creating cancellations.
What to measure after you publish ATS
Once ATS replaces raw on-hand stock, measure whether the rule improves operations. Track oversell incidents by channel, cancelled orders caused by stock mismatch, buffer-held units by SKU, stockouts where hidden buffer could have sold, and sync exceptions that failed to update a marketplace. These metrics tell you whether your formula is too loose, too strict or simply missing one inventory state.
The strongest teams review exceptions daily during peak periods and weekly during stable periods. They do not wait for finance reconciliation to discover that a marketplace, WMS and Shopify no longer agree.
- Treat available-to-sell inventory as a controlled output, not a field copied from Shopify, ERP or a spreadsheet.
- Give one system authority over reservations, buffers, damaged stock and channel allocations.
- Make every stock push explainable: which rule changed the quantity, when it changed and which channel received it.
- Start with your top 50 fast-moving SKUs before rolling the formula across the full catalogue.
FAQ
What is available-to-sell inventory?
How is available-to-sell different from on-hand inventory?
Should incoming purchase orders be included in marketplace stock?
How often should multichannel sellers recalculate ATS?
Can ChannelDock publish different stock quantities per marketplace?
Conclusion
Available-to-sell inventory is the practical bridge between inventory accuracy and marketplace growth. Real-time sync matters, but only after the right number has been calculated. Multichannel sellers should publish ATS to every channel, protect risky channels with intentional buffers, reserve stock the moment an order lands and keep an audit trail for every quantity change.
For sellers that want this control without spreadsheet reconciliation, ChannelDock centralizes stock, orders and marketplace connections so the quantity shown to each channel follows the operational reality in the warehouse.