HOW-TO · Inventory

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.

Rank channels
protect margin
Route stock
before conflict
Publish safely
to every listing
Shared stock decisionPriority active
bol.comHigh velocity34 reserved
AmazonRank protection22 live
ShopifyMargin leader18 protected
TikTok ShopViral cap12 max

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.

One poolphysical stock stays central
Four rulespriority, cap, buffer, freeze
Faster actionno spreadsheet debate
Safer growthchannels stay profitable

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.

Channel economics

List gross margin, ad spend, marketplace penalty risk and strategic value for every active channel.

Sellable-stock definition

Agree on how reservations, open orders, returns inspection, bundles and warehouse buffers reduce the quantity you publish.

Authority to change availability

Make sure the person setting rules can pause listings, reduce quantities, reserve stock or transfer inventory.

Practical rule: marketplace priority should not equal sales volume. A lower-volume B2B or Shopify channel can deserve protection when margin, customer value or cancellation risk is higher.

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.

Common mistake: treating channel inventory as separate when the warehouse only has one pile of units.

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.

Common mistake: letting a marketplace see units that are already committed in another workflow.

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.

Common mistake: prioritizing the channel that shouts loudest instead of the channel where one cancellation hurts most.

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.

Common mistake: using a fixed percentage split that ignores today’s demand and tomorrow’s inbound delivery.

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.

Common mistake: hiding stock from every channel while already-paid orders still have no protected units.

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.

Common mistake: waiting for the first oversell before reducing a channel that is already accelerating.

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.

Common mistake: freezing everything and losing profitable orders that could still be fulfilled safely.

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.

Common mistake: treating allocation as a one-time setup instead of a weekly inventory operating meeting.

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?”

Sellable stock
Priority score
Reservations
Safe publish

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.

Explore Inventory Reservations →

Shared marketplace stock priority FAQ

Start by defining sellable stock, then rank channels by margin, cancellation risk, marketplace health and strategic value. Reserve committed orders first, cap risky channels second, and freeze lower-priority channels when stock falls below the agreed threshold.

Not always. Equal quantities are simple, but they can waste stock on low-margin or high-risk channels. Fast-moving SKUs often need channel-specific caps, buffers or reservations.

A reservation protects units for a specific order, customer or commitment. An allocation decides how much of the remaining sellable stock each channel is allowed to publish.

Set lower-priority channels to zero when remaining sellable stock is needed for higher-value orders, marketplace health protection, B2B commitments or inbound lead-time coverage.

Yes, but only if one central inventory record controls available stock and each channel receives a safe published quantity. Without reservations and priority rules, shared stock can create oversells during busy periods.

Review fast movers weekly and after every oversell, stockout, failed reservation or emergency transfer. Seasonal items and campaign products need tighter reviews during peak weeks.

Related workflows to improve next

After channel priority is clear, tighten the stock controls that feed the rule.

Stock Level Sync

Publish safe stock to every sales channel.

Learn more

Stock Advice

Plan replenishment before priority rules become emergency rules.

Learn more

Stock Reconciliation

Find the discrepancies that make allocation rules unreliable.

Learn more

Set inventory buffers

Hold back risky last units across marketplaces.

Read the how-to

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.