HOW-TO · BESTAND

So untersuchen Sie Bestandsabweichungen auf Marketplaces

Eine Bestandsabweichung auf Marketplaces ist selten nur eine falsche Zahl. Meist ist die Kette zwischen physischem Bestand, Reservierungen, Kanalbestand, SKU-Aliasen, Retouren und Connector-Timing gebrochen. Dieser Leitfaden zeigt, wie Sie die Ursache finden, sicher korrigieren und ChannelDock Stock Reconciliation mit Stock Level Sync für Amazon, bol.com, Shopify, eBay und weitere Kanäle nutzen.

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.

Warum dieses Thema: Die Wettbewerbsanalyse zeigt kommerzielle Nachfrage rund um Multichannel Inventory Management Software. Viele Ranking-Seiten bleiben allgemein; Seller-Foren zeigen den operativen Schmerz: Amazon-Berichte widersprechen sich, Shopify-Apps überschreiben Standorte und eBay-Optionen verändern sichtbaren Bestand.

Sourcetruth
SKUaliases
Timingsync
Returnsloop

Klären Sie zuerst, welche Abweichung vorliegt

Schnelle Untersuchungen beginnen mit der richtigen Einordnung. „Amazon zeigt 0, das Lager 12“ ist nicht dasselbe wie „Shopify hat 12, aber eBay verkauft 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.

Schritt für Schritt: Bestandsabweichungen untersuchen

Nutzen Sie diesen Ablauf, wenn eine SKU, Variante oder ein Bundle zwischen Lager, Inventarsystem und Marketplaces abweicht. Erst Verkäufe schützen, dann Ursache beheben.

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.

Arbeiten Sie mit einer Abweichungsmatrix, nicht mit Schuldzuweisung

Kanalbestand kann wegen Puffern, Listing-Status, Reservierungen, API-Verzögerungen, SKU-Aliasen, Bundle-Komponenten oder Standortprioritäten abweichen.

Die richtige Frage lautet nicht: Wer hat die Zahl geändert? Sondern: Welcher Bestandsstatus durfte zum Kundenversprechen werden?

Physical
Reserved
Sellable
Channel

Häufige Fallen bei Bestandsabweichungen

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

Manuelle Reconciliation 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 zu Bestandsabweichungen

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.

Verwandte How-tos zur Bestandskontrolle

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

Beheben Sie die Ursache, nicht nur die Zahl

Nutzen Sie ChannelDock, um Bestandsbewegungen zu reconciliieren, verkaufbaren Bestand zu schützen und die richtige Menge an jeden Marketplace zu synchronisieren.