HOW-TO · Inventory

How to track FBA and own-warehouse inventory

Keep Amazon FBA, LVB, 3PL stock, and your own warehouse in separate but connected pools. 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.

Use LVB / FBA tracking Start free trial
Separate
FBA, LVB, 3PL, and warehouse pools
Sync
marketplace availability safely
Replenish
before FBA or local stock runs out
Inventory by locationLive view
Amazon FBA42884 reserved
bol.com LVB19031 inbound
Own warehouse31652 pickable today
Transfer to FBA120replenish this week

Hybrid fulfillment breaks when FBA stock, marketplace stock, and your own shelves are treated as one bucket.

Clear locationsstock split by pool
Less oversellingbuffers per channel
Cleaner syncavailability not guesses
Better replenishmenttransfer before stockout

Before you start: what you need

Tracking hybrid inventory works only when every location reports the same SKU logic and every channel knows which pool it may sell from.

SKU mapping per channel

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

Location access

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

Buffer and transfer rules

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.

Step-by-step FBA and own-warehouse inventory workflow

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

List every physical stock pool

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.

Common mistake: treating “Amazon stock” as one number while FBA, FBM, reserved, and inbound units behave differently.

Match SKUs before matching quantities

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

Common mistake: comparing FNSKU, EAN, and webshop SKU fields as if they were interchangeable.

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

Common mistake: counting inbound FBA shipments as available before Amazon has received them.

Connect each channel to the right pool

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.

Common mistake: letting every channel sell the same shared stock without priority rules.

Set buffers for slow updates and peak days

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.

Common mistake: using one global buffer for both FBA and the shelf ten metres from the packing bench.

Plan replenishment before the threshold is hit

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

Common mistake: waiting until FBA shows low stock, then discovering receiving takes longer than the remaining cover.

Reconcile exceptions weekly

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

Common mistake: fixing only the marketplace number while the warehouse location remains wrong.

The hybrid stock model at a glance

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.

Own warehouse
FBA / LVB
Buffers & rules
Sellable stock

Common FBA and warehouse inventory pitfalls

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

Without ChannelDock

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

With ChannelDock

  • Stock is visible per fulfillment pool, with availability synced to the right channels.
  • Reservations, buffers, and own-warehouse stock stay connected to order flow.
  • Teams can combine LVB / FBA tracking with Stock Level Sync and Warehouse Sections.

Explore LVB / FBA tracking →

FBA and own-warehouse inventory FAQ

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.

Related workflows to tighten next

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

Multi-warehouse inventory

Separate stock by location before syncing availability.

Read how-to

Stock Level Sync

Push safe availability to every connected channel.

Learn more

Prevent overselling

Use buffers and reservations for multichannel selling.

Read how-to

Warehouse Sections

Keep in-house stock locations clean and countable.

Learn more

Track FBA, LVB, and own-warehouse stock in one workflow

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

View LVB / FBA Book a demo