HOW-TO · Bestand

So verfolgen Sie FBA- und Eigenlagerbestand

Halten Sie Amazon FBA, LVB, 3PL-Bestand und Ihr eigenes Lager in getrennten, aber verbundenen Beständen. ChannelDock’s LVB / FBA feature helps sellers see which units are available, reserved, inbound, or ready to replenish without merging every location into one unsafe number.

Trennen
FBA, LVB, 3PL, and warehouse pools
Synchronisieren
marketplace availability safely
Auffüllen
before FBA or local stock runs out
Bestand nach StandortLive-Ansicht
Amazon FBA42884 reserved
bol.com LVB19031 inbound
Eigenes Lager31652 pickable today
Transfer zu FBA120replenish this week

Hybrides Fulfillment scheitert, wenn FBA-Bestand, Marketplace-Bestand und eigene Regale als ein einziger Bestand behandelt werden.

Klare Standortestock split by pool
Weniger Überverkäufebuffers per channel
Saubere Synchronisierungavailability not guesses
Bessere Nachschubplanungtransfer before stockout

Vor dem Start: Was Sie brauchen

Hybridbestand funktioniert nur, wenn jeder Standort dieselbe SKU-Logik nutzt und jeder Kanal weiß, aus welchem Bestand er verkaufen darf.

SKU-Mapping pro Kanal

Match Amazon SKUs, bol.com LVB items, webshop SKUs, and warehouse labels before you compare stock numbers.

Standortzugriff

Connect the sales channels and fulfillment locations that should feed ChannelDock, including FBA/LVB, your warehouse, and any 3PL.

Puffer- und Transferregeln

Decide which units are sellable, reserved, inbound, damaged, or held back as safety stock before syncing availability.

Tip: do not add FBA and own-warehouse units together unless the channel can actually fulfill from both locations within the promised delivery time.

Schritt-für-Schritt-Workflow für FBA und Eigenlager

Use this procedure to keep Amazon FBA, bol.com LVB, 3PL, and in-house stock visible without creating oversell risk.

Jeden physischen Bestandspool erfassen

Create a clear list of locations: Amazon FBA, bol.com LVB, your warehouse, 3PL sites, returns shelves, and inbound transfers. Each pool should have an owner and update rhythm.

Häufiger Fehler: treating “Amazon stock” as one number while FBA, FBM, reserved, and inbound units behave differently.

SKUs abgleichen, bevor Mengen verglichen werden

Confirm that the same sellable product uses one internal SKU or a documented mapping across Amazon, bol.com, Shopify, WooCommerce, and warehouse labels.

Häufiger Fehler: comparing FNSKU, EAN, and webshop SKU fields as if they were interchangeable.

Trennen available, reserved, and inbound units

Available stock can be sold now. Reserved stock belongs to open orders. Inbound stock is useful for planning but should not be synced as sellable unless you allow pre-orders.

Häufiger Fehler: counting inbound FBA shipments as available before Amazon has received them.

Jeden Kanal mit dem richtigen Pool verbinden

Decide whether Amazon orders should use only FBA, whether your webshop may use own-warehouse stock, and whether bol.com should prefer LVB or local fulfillment.

Häufiger Fehler: letting every channel sell the same shared stock without priority rules.

Puffer für langsame Updates und Spitzentage setzen

Use channel-specific buffers for locations with slower stock updates, high return rates, or long receiving times. Buffers should be higher for fast-moving SKUs near stockout.

Häufiger Fehler: using one global buffer for both FBA and the shelf ten metres from the packing bench.

Nachschub planen, bevor der Schwellenwert erreicht ist

Track sales velocity and lead time, then create transfers from your warehouse or supplier before FBA or LVB drops below the reorder point.

Häufiger Fehler: waiting until FBA shows low stock, then discovering receiving takes longer than the remaining cover.

Ausnahmen wöchentlich abgleichen

Review discrepancies between ChannelDock, marketplace reports, and warehouse counts. Investigate cancellations, returns, damaged stock, lost FBA units, and manual corrections.

Häufiger Fehler: fixing only the marketplace number while the warehouse location remains wrong.

Das hybride Bestandsmodell auf einen Blick

The goal is not one big total. The goal is one trusted view where each sales channel sees the stock it can safely promise.

Hybrid fulfillment works when stock is shared for planning, but separated for selling.

Eigenes Lager
FBA / LVB
Buffers & rules
Sellable stock

Häufige Fallstricke bei FBA- und Lagerbestand

  • Using the marketplace “available” number without checking reserved, inbound, or stranded inventory.
  • Letting Amazon, bol.com, and your webshop pull from the same last units without a safety buffer.
  • Forgetting that FBA replenishment lead time includes prep, shipment, carrier transit, and Amazon receiving.
  • Mapping one product variant differently across channels, which makes stock reconciliation look worse than it is.
  • Ignoring returns and damaged units until the monthly count, instead of correcting them as soon as they are processed.

Spreadsheet-Tracking vs. ChannelDock LVB / FBA

Manual tracking can explain yesterday’s stock. A connected workflow shows what can be sold now and what should be replenished next.

Ohne ChannelDock

  • FBA, LVB, warehouse, and webshop reports are checked in separate tabs.
  • Buffers and reservations are updated after orders already changed the stock picture.
  • Auffüllenment decisions depend on exported CSVs and manual formulas.

Mit ChannelDock

Explore LVB / FBA tracking →

FAQ zu FBA- und Eigenlagerbestand

Track FBA and own-warehouse units as separate stock pools, map the same SKU across channels, separate available from reserved and inbound stock, then sync only the safe sellable quantity to each marketplace.

Use one combined planning view, but keep separate sellable pools. FBA stock, FBM stock, and 3PL stock have different cutoffs, delivery promises, and replenishment lead times.

Set a buffer for FBA SKUs, monitor reserved and inbound units, and use replenishment thresholds before the marketplace shows low stock. For broader prevention, read how to prevent overselling across channels.

Yes, but Shopify should receive an availability number based on the fulfillment promise you can actually meet. Many sellers reserve FBA for Amazon demand and use own-warehouse stock for webshop orders.

Available inventory can be sold immediately, reserved inventory is already tied to open orders, and inbound inventory is on the way but not ready to promise unless you deliberately sell pre-orders.

Fast-moving SKUs should be reviewed weekly, and exception-heavy products should be checked more often. Reconcile marketplace reports, warehouse counts, returns, damaged units, and transfers in one workflow.

Yes. Use multi-warehouse inventory management when the main question is location control, and use LVB / FBA when marketplace fulfillment pools are part of the setup.

Verwandte Workflows als nächstes optimieren

Hybrid stock tracking improves faster when the surrounding inventory workflows use the same source of truth.

Multi-warehouse inventory

Trennen stock by location before syncing availability.

How-to lesen

Stock Level Synchronisieren

Push safe availability to every connected channel.

Mehr erfahren

Prevent overselling

Use buffers and reservations for multichannel selling.

How-to lesen

Warehouse Sections

Keep in-house stock locations clean and countable.

Mehr erfahren

FBA, LVB und Eigenlagerbestand in einem Workflow verfolgen

Use ChannelDock to separate fulfillment pools, sync safe availability, and replenish before the next stockout.