HOW-TO · STOCK

Comment analyser les écarts de stock sur marketplaces

Un écart de stock marketplace n’est presque jamais un simple chiffre faux. Il vient souvent d’une rupture entre stock physique, réservations, stock canal, alias SKU, retours et timing des connecteurs. Ce guide explique comment trouver la cause, corriger proprement et utiliser ChannelDock Stock Reconciliation avec Stock Level Sync.

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.

Pourquoi ce sujet : l’analyse concurrentielle montre une demande commerciale autour du multichannel inventory management software. Les pages classées restent générales, alors que les forums parlent de problèmes concrets : rapports Amazon incohérents, apps Shopify qui écrasent les emplacements et stock eBay difficile à lire.

Sourcetruth
SKUaliases
Timingsync
Returnsloop

Identifiez d’abord le type d’écart

Une bonne analyse commence par nommer l’écart. “Amazon indique 0 mais l’entrepôt 12” n’est pas le même problème que “Shopify a 12 mais eBay vend encore 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.

Pas à pas : analyser un écart de stock marketplace

Utilisez ce flux lorsqu’un SKU, une variante ou un bundle ne correspond pas entre l’entrepôt, l’outil stock et les marketplaces. Protégez d’abord les ventes, puis corrigez la cause.

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.

Utilisez une matrice d’écart, pas une chasse au coupable

Le stock affiché peut varier à cause des buffers, du statut de listing, des réservations, d’un délai API, d’un alias SKU, d’un composant bundle ou d’une priorité d’emplacement.

La bonne question n’est pas “qui a changé le chiffre ?”, mais “quel état de stock a été autorisé à devenir une promesse client ?”

Physical
Reserved
Sellable
Channel

Pièges fréquents des écarts de stock

  • 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.

Réconciliation manuelle 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 sur les écarts de stock

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-tos liés au contrôle du stock

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

Corrigez la cause, pas seulement la quantité

Utilisez ChannelDock pour réconcilier les mouvements de stock, protéger le stock vendable et synchroniser la bonne quantité vers chaque marketplace.