如何为线上订单设置 POS 库存缓冲
POS 中的库存数量,不一定就是应该发布到线上渠道的数量。门店有 5 件商品,其中 1 件可能在陈列,1 件要留给到店顾客,1 件已被自提订单占用。本指南说明如何用 Stock Level Sync 设置安全的线上可售量。
盘点实物库存
扣除门店占用
发布安全线上库存
很多 POS 电商文章只说实时同步。真正的问题是:如何避免门店最后几件商品被线上同时卖掉。
开始前准备
只有当门店、网店和仓库对“可用”理解一致时,缓冲规则才有效。
把每个 POS 商品对应到各渠道使用的同一 SKU、EAN 或条码。
按门店计算缓冲,不要只看一个总库存池。
决定最后一件可售商品优先给门店、自提、网店、marketplace 还是批发客户。
分步设置 POS 库存缓冲
当门店、电商和 marketplace 共用库存时,可按此流程发布安全可售量。
发布前列出每一种库存状态
Write down the states that reduce online availability: open POS carts, paid store orders, display units, damaged returns, items in transfer, click-and-collect reservations, marketplace holds and the minimum floor stock you never want to sell online.
按产品组选择缓冲方式
Use a fixed unit buffer for low-volume SKUs, a percentage buffer for fast movers, and a stricter buffer for products with high in-store demand. For example: hold back 1 unit on slow accessories, 10–15% on high-velocity sizes, and all display units on showroom items.
按门店计算可售量
For each store, start with on-hand stock and subtract committed stock, reserved pickup stock, display stock, damaged stock and the buffer. Publish only the result to online channels. If the result is negative, publish zero and trigger a stock review.
在 ChannelDock 中应用渠道规则
Use ChannelDock to connect POS, webshop and marketplace stock flows through Stock Level Sync. Keep the buffer rule close to the channel export so bol.com, Amazon, Shopify and WooCommerce receive the same safe quantity.
测试最后一件商品场景
Before going live, simulate the risky moments: one unit left, a store sale during checkout, a pickup reservation, a return waiting for inspection and a transfer between store and warehouse. The published online quantity should never expose protected stock.
每周监控异常
Review oversells, cancelled pickup orders, stock adjustments and manual POS corrections. If store teams often reduce stock after online orders arrive, the buffer is too small or the stock count is not trusted.
公式:发布安全库存,而不是原始 POS 数量
常见错误是直接发布实物数量。平时看似可行,周末、促销和高峰期就会出问题。
好的全渠道 POS 先回答“哪些库存可以安全承诺”,再回答“门店里实际有多少”。
常见 POS 缓冲错误
- Using one global buffer for every store, even though a flagship location needs more floor stock than a small pickup point.
- Protecting stock in Shopify but not in marketplace exports, so bol.com or Amazon can still oversell the last unit.
- Counting returned products as available before inspection, cleaning and barcode confirmation.
- Letting store staff manually adjust stock without a reason code or audit trail.
- Forgetting that click-and-collect and ship-from-store need different buffers: pickup protects speed, ship-from-store protects fulfillment reliability.
手动缓冲 vs ChannelDock 规则
表格可以每个 SKU 扣 2 件,但无法管理原因、预留、渠道规则和审计记录。
手动
- A manager edits stock in POS, webshop and marketplaces separately.
- Buffers are remembered in spreadsheets or staff notes.
- Last-unit conflicts are discovered after a customer has paid.
- Marketplace stock is updated later than webshop stock.
- No clear audit trail for why online availability changed.
ChannelDock
- POS, webshop, marketplace and warehouse stock flow through one operational layer.
- Stock Level Sync publishes only safe available-to-sell quantities.
- Reservations and buffers reduce stock before another channel can sell it.
- Teams can connect the same logic to ship-from-store and click and collect.
- Reason codes and weekly exception reviews make buffer tuning measurable.