HOW-TO · 库存

如何排查各平台的库存差异

Marketplace 库存差异通常不只是“数字错了”。问题往往出在实物库存、预留库存、渠道库存、SKU 别名、退货和连接器同步时间之间。本指南说明如何追踪原因、正确修正,并用 ChannelDock Stock Reconciliation 与 Stock Level Sync 保持 Amazon、bol.com、Shopify、eBay 等渠道一致。

3
stock views
6
checks before sync
1
source of truth
Discrepancy triageAudit
1Freezeprotect the SKU
2Comparesystem, warehouse and channel values
3Explainalias, return, transfer or delay
4Correctsync approved sellable stock
Investigate before manually editing every channel.

为什么选择这个主题:竞品分析显示 multichannel inventory management software 有商业搜索需求。排名内容多为通用说明,而卖家社区的问题更具体:Amazon 报表不一致、Shopify 应用覆盖地点、eBay 设置让在售数量和可售库存不同。

Sourcetruth
SKUaliases
Timingsync
Returnsloop

先判断你看到的是哪类库存差异

快速排查从定义差异开始。“Amazon 显示 0、仓库有 12”不同于“Shopify 有 12、eBay 仍在卖 14”。

Physical vs. system

Check receiving, picking, damage, returns, transfers and count errors before changing listings.

System vs. channel

Look for connector timing, API errors, missing SKUs, buffers and listing status.

Sellable vs. total

Total stock can include reserved, inbound, transfer or unsellable units.

Seller forums show the same pattern: several reports can be technically correct because they measure different stock states.

分步排查 marketplace 库存差异

当某个 SKU、变体或组合商品在仓库、库存系统和 marketplace 之间不一致时,使用这套流程。先保护销售承诺,再修复根因。

Freeze the risky promise

Protect the SKU with a buffer or pause before correcting numbers.

Do not erase the audit trail with emergency edits.

Capture the four quantities

Record physical, system on-hand, available-to-sell and channel quantity at the same timestamp.

Do not compare exports from different days.

Check SKU mapping

Confirm listing IDs, ASINs, EANs, barcodes, variants and internal SKUs point to one product.

Product title is not product identity.

Rebuild the movement timeline

Review receipts, picks, cancellations, returns, transfers, adjustments and connector errors. Stock Reconciliation should explain the variance before adjustment.

The cause may be a return or cancellation, not a bad count.

Separate sellable stock

Do not publish reserved, inbound, transfer, damaged or return-inspection units as available stock.

Total stock is not always sellable stock.

Inspect sync ownership

Find which system last pushed stock and turn off competing writers.

Three apps updating one listing create one unreliable number.

Approve and sync once

Correct the source-of-truth record and let inventory reservations or buffers reduce risk.

Do not fix only one marketplace.

Create a prevention rule

Add SKU validation, return status, cycle-count trigger, connector alert or permission control.

A correction without root cause will repeat.

使用差异矩阵,而不是追责

渠道库存可能因缓冲、listing 状态、预留、API 延迟、SKU 别名、组合商品组件或地点优先级而变化。

正确的问题不是“谁改了数字?”,而是“哪个库存状态被允许变成客户承诺?”

Physical
Reserved
Sellable
Channel

常见库存差异陷阱

  • Comparing reports from different timestamps.
  • Publishing reserved, damaged or inbound stock as sellable.
  • Letting multiple apps update the same listing.
  • Ignoring bundle components and returns.
  • Correcting quantities without an audit trail.

手动对账 vs. ChannelDock

Manual edits solve the visible mismatch; ChannelDock connects stock, orders, reservations and sync.

Manual

  • Exports arrive after orders moved.
  • Teams type corrections into portals.
  • Reserved and damaged stock get mixed.
  • Causes stay in spreadsheets.

ChannelDock

  • Movements, orders and updates stay connected.
  • Stock Reconciliation explains variances.
  • Stock Level Sync publishes approved sellable stock.
  • Reservations, buffers and audit trails reduce risk.

Explore inventory features →

库存差异 FAQ

Freeze the SKU, compare quantities, check mapping, rebuild movements, separate stock states, correct the source and sync once.

FBA reports may count reserved, inbound, transfer, unsellable and stranded stock differently from your own sellable inventory.

Missing SKUs, location settings, apps overwriting quantities, API delays and unlinked variants are common causes.

Only as a temporary emergency control. The durable fix belongs in the source-of-truth system.

Buffers hide a small quantity from marketplaces so sync delays and count drift do not oversell the last units.

库存控制相关 how-to

Related workflows that prevent repeated discrepancies.

Sync inventory

Keep channels aligned.

Read how-to

Prevent overselling

Use buffers.

Read how-to

Multi-warehouse

Separate locations.

Read how-to

Low-stock alerts

Catch risk early.

Read how-to

修复原因,而不只是修正数量

使用 ChannelDock 对账库存流转,保护可售库存,并把正确数量同步到每个 marketplace。