HOW-TO · INVENTARIO

Cómo investigar diferencias de stock en marketplaces

Una diferencia de stock en marketplaces casi nunca es solo “un número incorrecto”. Suele ser una rotura entre stock físico, reservas, stock del canal, alias de SKU, devoluciones y tiempos de sincronización. Esta guía muestra cómo encontrar la causa, corregirla y usar ChannelDock Stock Reconciliation con 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.

Por qué este tema: el análisis competitivo muestra demanda comercial en multichannel inventory management software. Las páginas que rankean suelen ser generales; los foros muestran el dolor real: informes de Amazon que no coinciden, apps de Shopify que sobrescriben ubicaciones y ajustes de eBay que cambian el stock visible.

Sourcetruth
SKUaliases
Timingsync
Returnsloop

Primero identifica qué tipo de diferencia tienes

Una investigación rápida empieza nombrando la variación. “Amazon muestra 0 y el almacén 12” no es lo mismo que “Shopify tiene 12 pero eBay sigue vendiendo 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.

Paso a paso: investigar una diferencia de stock marketplace

Usa este flujo cuando un SKU, variante o bundle no coincide entre almacén, sistema de inventario y marketplaces. Primero protege la venta; después corrige la causa.

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.

Usa una matriz de variaciones, no una búsqueda de culpables

El stock por canal puede cambiar por buffers, estado del listing, reservas, retrasos API, alias de SKU, componentes de bundle o prioridad de ubicación.

La pregunta correcta no es “¿quién cambió el número?”, sino “¿qué estado de stock se convirtió en promesa al cliente?”

Physical
Reserved
Sellable
Channel

Errores frecuentes con diferencias 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.

Reconciliación manual 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 sobre diferencias 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 relacionados con control de inventario

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

Corrige la causa, no solo la cantidad

Usa ChannelDock para reconciliar movimientos de stock, proteger stock vendible y sincronizar la cantidad correcta en cada marketplace.