How to prioritize marketplaces when stock is shared
When Shopify, bol.com, Amazon, TikTok Shop and B2B buyers all draw from the same shelf, “sync everything everywhere” becomes risky. ChannelDock’s Inventory Reservations helps sellers decide which channel gets protected first when sellable stock gets tight.
protect margin
before conflict
to every listing
Shared inventory works until two channels behave as if they own the same last unit. Priority rules make the trade-off explicit before the oversell, cancellation or manual apology happens.
Before you start: what you need
Do not begin with software settings. Begin with business rules: which channel earns the next unit, which channel carries the highest penalty, and which demand spikes are worth capping.
List gross margin, ad spend, marketplace penalty risk and strategic value for every active channel.
Agree on how reservations, open orders, returns inspection, bundles and warehouse buffers reduce the quantity you publish.
Make sure the person setting rules can pause listings, reduce quantities, reserve stock or transfer inventory.
Step-by-step shared-stock priority workflow
Use this procedure when one SKU is sold on several channels and all orders ship from the same physical stock pool.
Map the shared stock pool
Start with one SKU family and document every place it can sell: webshop, marketplace, B2B portal, POS, bundles and any 3PL location. Then mark whether each channel receives the full quantity, a capped quantity or a reserved quantity.
Calculate true sellable stock
Use available stock, not physical stock. Subtract paid orders, pending marketplace orders, returns waiting for inspection, damaged items, bundle components, warehouse pick errors and the operational buffer you never want to publish.
Rank channels by business risk
Score each channel on margin, advertising dependency, marketplace health, customer lifetime value and cancellation penalty. Amazon or bol.com may deserve rank protection; Shopify may deserve margin protection; B2B may deserve relationship protection.
Choose a priority model
Pick one model per SKU tier: margin-first, marketplace-rank-first, key-account-first or velocity-first. Do not mix models inside the same product group unless the team can explain the exception in one sentence.
Set reservation rules before caps
Reserve committed stock first, then cap lower-priority channels. Reservations protect real orders and real commitments; caps only control what the next buyer is allowed to see.
Add channel caps for risky demand spikes
Give viral or promotion-heavy channels a maximum published quantity. TikTok Shop, Amazon deals and flash-sale email traffic can consume the last units faster than a normal sync cycle can react.
Define the freeze threshold
Decide when lower-priority channels go to zero while top-priority channels stay live. This is the rule that stops the last five units being promised in three places.
Review the rule after every exception
Each oversell, manual cancellation or emergency transfer should update the rule. The goal is not a perfect first setup; it is a control loop that gets sharper after real incidents.
The priority loop at a glance
A good shared-stock workflow separates the stock decision from the marketplace update. The team first decides what is sellable, then who should receive it, then what each channel is allowed to publish.
The question is not “how much stock do we have?” The better question is: “which channel is allowed to sell the next unit without creating a worse problem elsewhere?”
Common shared-stock pitfalls
- Publishing the same full quantity to every channel because the sync tool allows it.
- Making allocations by percentage without considering margin, marketplace penalties or lead time.
- Forgetting bundles where one component is shared by several parent SKUs.
- Letting pending orders remain unreserved while new buyers keep seeing available stock.
- Freezing every channel at low stock instead of preserving the highest-value path to sale.
Manual allocation vs. ChannelDock Inventory Reservations
Manual channel priority works for a small catalogue, but it becomes fragile when the same SKU sells through marketplaces, webshop, B2B and POS at the same time.
Without ChannelDock
- Teams argue in spreadsheets after stock is already low.
- The same last units stay visible on multiple channels.
- Reservations, buffers and marketplace quantities are managed in separate places.
With ChannelDock
- Inventory Reservations protect committed stock before new orders compete for it.
- Stock Level Sync can publish safer availability per channel from one central stock record.
- Teams can combine priority, caps and buffers without losing sight of the real warehouse quantity.
Shared marketplace stock priority FAQ
Related workflows to improve next
After channel priority is clear, tighten the stock controls that feed the rule.
Make shared stock safer before the next channel conflict
Use ChannelDock Inventory Reservations to protect committed stock, publish safer availability and keep high-value marketplaces live without promising the same unit twice.