HOW-TO · 库存

如何在共享库存中为各市场设置优先级

当 Shopify、bol.com、Amazon、TikTok Shop 和 B2B 客户都使用同一批库存时,“所有渠道同步全部数量”会变得很危险。ChannelDock 的 Inventory 预留 可以帮助卖家在可售库存紧张时决定优先保护哪个渠道。

渠道排序
保护利润
分配库存
避免冲突
安全发布
到每个 listing
共享库存决策优先级已启用
bol.com高周转34 已预留
Amazon排名保护22 在线
Shopify高利润渠道18 已保护
TikTok Shop爆发上限12 max

共享库存只有在两个渠道都认为自己拥有最后一件商品之前才安全。优先级规则能在超卖、取消订单或人工补救发生前,把取舍明确下来。

一个库存池实体库存集中管理
四条规则优先级、上限、缓冲、冻结
更快处理不再用表格争论
更安全增长渠道保持盈利

开始前需要准备什么

不要从软件设置开始,而要先定义业务规则:哪个渠道应获得下一件库存,哪个渠道取消订单损失最大,哪些需求高峰需要设置上限。

渠道经济性

列出每个活跃渠道的毛利、广告投入、平台处罚风险和战略价值。

可售库存定义

明确预留、未完成订单、退货质检、套装商品和仓库缓冲如何减少可发布数量。

修改可用量权限

确保负责规则的人可以暂停 listing、降低数量、预留库存或发起库存转移。

实用规则:市场优先级不等于销量。销量较低的 B2B 或 Shopify 渠道,如果利润、客户价值或取消风险更高,也可能更值得保护。

共享库存优先级操作步骤

当同一个 SKU 在多个渠道销售,并且订单都从同一个实体库存池发货时,使用这套流程。

梳理共享库存池

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 已预留 quantity.

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

计算真实可售库存

使用可用库存,而不是实体库存。扣除已付款订单、待处理平台订单、待质检退货、损坏品、套装组件、拣货误差和永远不应发布的运营缓冲。

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

渠道排序 by business risk

按利润、广告依赖、平台健康度、客户价值和取消处罚为每个渠道打分。Amazon 或 bol.com 可能需要保护排名;Shopify 可能需要保护利润;B2B 可能需要保护客户关系。

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

选择优先级模型

每个 SKU 分层选择一种模型:利润优先、平台排名优先、关键客户优先或销量速度优先。除非团队能用一句话解释例外,否则不要在同一产品组混用模型。

Common mistake: using a fixed percentage split that ignores today’s demand and tomorrow’s inbound de在线ry.

先设置预留,再设置上限

先预留已承诺库存,再限制低优先级渠道。预留保护真实订单和承诺;上限只控制下一个买家能看到的数量。

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

为高风险需求峰值添加渠道上限

为容易爆发或促销频繁的渠道设置最大发布数量。TikTok Shop、Amazon 促销和闪购邮件流量可能比正常同步周期更快消耗最后库存。

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

定义冻结阈值

Decide when lower-priority channels go to zero while top-priority channels stay 在线. 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.

每次异常后复盘规则

每次超卖、手动取消或紧急转移都应更新规则。目标不是第一次就完美,而是建立一个会从真实事件中变得更准确的控制循环。

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

优先级循环概览

好的共享库存流程会把库存决策与平台更新分开。团队先决定什么可售,再决定谁优先获得,最后决定每个渠道发布多少。

问题不是“我们有多少库存?”,而是“哪个渠道可以卖出下一件商品,而不会在其他地方造成更大的问题?”

可售库存
优先级评分
预留
安全发布

共享库存常见错误

  • 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 un已预留 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 预留

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.

没有 ChannelDock

  • Teams argue in spreadsheets after stock is already low.
  • The same last units stay visible on multiple channels.
  • 预留, buffers and marketplace quantities are managed in separate places.

使用 ChannelDock

  • Inventory 预留 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 预留 →

共享市场库存优先级 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.

接下来可优化的相关流程

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

在下一次渠道冲突前让共享库存更安全

Use ChannelDock Inventory 预留 to protect committed stock, publish safer availability and keep high-value marketplaces 在线 without promising the same unit twice.