HOW-TO · INVENTORY

How to investigate stock discrepancies across marketplaces

A marketplace stock discrepancy is not just “the number is wrong”. It is a broken chain between physical stock, reserved stock, channel listings, SKU aliases, returns and connector timing. This guide shows multichannel sellers how to trace the variance, fix the source and use ChannelDock Stock Reconciliation with Stock Level Sync to keep Amazon, bol.com, Shopify, eBay and other channels aligned.

3 views
physical, reserved and channel stock
6 checks
before editing marketplace quantities
1 owner
system allowed to publish sellable stock
Discrepancy triageAudit mode
1Freezepause risky sync or protect the SKU with a buffer
2Comparesystem, warehouse, reservations and channel values
3ExplainSKU alias, return, transfer, FBA status or API delay
4Correctsync only the approved sellable number
Never “fix” every channel manually before you know which number is true.

Why this topic: the weekly competitor analysis highlights “multichannel inventory management software” as a low-difficulty, commercial keyword. Current ranking content explains generic reconciliation, but seller forums show the real pain: Amazon reports can disagree with Seller Central, Shopify apps can override locations, and eBay out-of-stock settings can make active listings look different from sellable stock.

Source of truthone system publishes availability
SKU aliasesmarketplace IDs map to one item
Sync timingdelays become oversell windows
Returns loopinspection before sellable stock

First decide what kind of discrepancy you are seeing

The fastest investigations start by naming the variance. “Amazon says 0 but the warehouse says 12” is different from “Shopify has 12 but eBay still sells 14”, and both are different from “physical count found 9 where the WMS expected 12”. Each points to a different failure point.

Physical vs. system

The shelf, bin or FBA report does not match the quantity in your inventory system. Look for receiving gaps, mis-picks, damage, returns, transfers or count errors before touching marketplace listings.

System vs. channel

ChannelDock, Shopify or your WMS has one number, while bol.com, Amazon, eBay or another marketplace displays another. This usually points to connector timing, API errors, missing SKUs, channel buffers or listing status.

Sellable vs. total stock

Total units include reserved, inbound, unsellable, transfer or inspection stock. Sellable stock is the smaller number a marketplace should be allowed to promise.

Research insight: Amazon Seller Central threads often show three “correct” numbers at once: Manage Your Inventory, FBA Inventory Report and the seller’s own stock ledger. The fix is not guessing; it is separating sellable, reserved, unsellable, inbound and transfer quantities before updating channels.

Step-by-step: investigate a marketplace stock discrepancy

Use this workflow when one SKU, variant or bundle shows a mismatch between your warehouse, inventory platform and marketplaces. The goal is to protect live sales first, then correct the source of the error so the same discrepancy does not return tomorrow.

Freeze the risky promise before editing numbers

If the SKU is close to zero, has active promotions or sells on several channels, lower the marketplace buffer or pause the listing before making corrections. This prevents a second oversell while the investigation is open.

Common mistake: correcting Amazon, bol.com and Shopify manually in a panic. You may hide the symptom while breaking the audit trail.

Capture four numbers at the same timestamp

Record physical count, system on-hand, system available-to-sell and marketplace displayed quantity at the same time. Add reserved, inbound, damaged, return-inspection and transfer quantities if they exist. Screenshots help, but a timestamped export is better.

Common mistake: comparing Monday’s warehouse count with Tuesday’s marketplace export after orders, returns and adjustments have already moved.

Check SKU mapping and variant aliases

Confirm that every marketplace listing ID, ASIN, EAN, barcode, Shopify variant and internal SKU points to the same product. Pay special attention to bundles, color-size variants and products renamed after migration.

Common mistake: assuming product title equals product identity. Marketplaces often sell by listing ID while warehouses pick by internal SKU or barcode.

Rebuild the stock movement timeline

Walk backwards from the mismatch. Review the last receipts, pick confirmations, cancellations, returns, manual adjustments, transfers, stock imports and connector errors. A good stock reconciliation process explains the variance before it adjusts it.

Common mistake: treating the discrepancy as a count problem when the real cause was an order cancellation or return that did not restore stock correctly.

Separate sellable from reserved and unsellable stock

Amazon FBA, 3PLs and warehouses can hold stock in states that should not be published as available: reserved orders, inbound shipments, FC transfers, damaged stock, stranded inventory and returns waiting for inspection. Only the approved sellable quantity should flow to channels.

Common mistake: syncing total stock to every marketplace. Total units are useful for finance; sellable units protect customer promises.

Inspect connector logs and sync ownership

Check which app or system last pushed stock to the channel. Shopify merchants often discover that a third-party app, marketplace connector or manual import overwrote the intended number. Decide which system owns publishable availability and turn off competing writers.

Common mistake: letting Shopify, a marketplace app and a warehouse tool all update the same listing. Three writers create one unreliable number.

Approve the correction and sync once

After the cause is known, correct the inventory record in the source-of-truth system, then let the normal integration publish the number to channels. Use inventory reservations or buffers for SKUs where timing risk remains high.

Common mistake: fixing one marketplace directly and leaving the source system wrong. The next sync will reintroduce the bad quantity.

Turn the finding into a prevention rule

A useful investigation ends with a rule: SKU alias validation, return inspection status, cycle-count trigger, connector alert, buffer threshold or permission change. If the team only changes a quantity, the same discrepancy will come back under pressure.

Common mistake: celebrating a corrected count without documenting the root cause and owner.

Use a variance matrix, not a blame hunt

Most ranking pages stop at “count stock and adjust it”. Multichannel sellers need a richer model because each sales channel can display stock for a different reason: buffers, listing status, reserved units, API delay, SKU alias, bundle component stock or location priority.

The right question is not “who changed the number?” It is “which stock state was allowed to become a customer promise?”

Physical
Reserved
Sellable
Channel

Common stock discrepancy traps

  • Comparing reports from different timestamps and treating the gap as a real variance.
  • Counting FBA, 3PL or inbound units as sellable before they are actually available for customer orders.
  • Allowing two inventory apps to publish stock to the same Shopify, eBay or bol.com listing.
  • Ignoring bundle component stock, where one missing component makes several marketplace listings unsafe.
  • Correcting quantities without preserving the audit trail of who changed what, when and why.

Manual reconciliation vs. ChannelDock

Manual correction can solve today’s visible mismatch. ChannelDock helps stop the same mismatch from becoming tomorrow’s oversell by connecting stock, orders, reservations and channel sync.

Manual reconciliation

  • Exports are compared after orders have already moved.
  • Corrections are typed into several marketplace portals.
  • Reserved, damaged, inbound and return stock are easy to mix.
  • The cause is stored in someone’s head or a spreadsheet note.

With ChannelDock

  • Stock movements, orders and channel updates sit in one operational flow.
  • Stock Reconciliation helps teams explain variances before syncing corrections.
  • Stock Level Sync publishes the approved sellable number to connected channels.
  • Reservations, buffers and audit trails reduce repeated oversell risk.

Explore inventory features →

Stock discrepancy FAQ

Freeze the risky SKU, capture physical, system, available and channel quantities at the same timestamp, check SKU mapping, rebuild the stock movement timeline, separate sellable from reserved or unsellable stock, then correct the source-of-truth system and let normal sync publish the approved number.

Amazon reports can separate or combine sellable, reserved, inbound, in-transfer, unsellable and stranded units differently from your own ledger. Compare the status categories before assuming one report is wrong.

Common causes include missing SKUs, wrong location settings, third-party apps overwriting quantities, webhook or API delays, imports that bypass the source system and marketplace listings that are not linked to the correct variant.

Usually no. Correct the source-of-truth inventory record, then let the integration sync the approved sellable quantity. Manual channel edits should be temporary emergency controls, not the normal fix.

Buffers hide a small number of units from marketplaces so the last physical units are not promised twice during sync delays, audits, returns or high-velocity sales. They do not replace reconciliation, but they reduce customer-facing risk.

Trigger a cycle count when the variance affects a fast-selling SKU, a low-stock SKU, a bundle component, a high-value item or any product that recently had returns, transfers or manual adjustments.

Related how-tos for inventory control

Use these guides to prevent the discrepancy patterns that appear most often in multichannel operations.

Sync inventory across channels

Keep marketplace stock aligned.

Read how-to

Prevent overselling

Use buffers and reservations.

Read how-to

Manage multi-warehouse inventory

Separate stock by location.

Read how-to

Set low-stock alerts

Catch risk before stockout.

Read how-to

Fix the cause, not just the quantity

Use ChannelDock to reconcile stock movements, protect sellable availability and sync the right number to every marketplace from one place.