How to split Amazon FBA and FBM inventory without overselling
Hybrid Amazon sellers often run two promises for the same product: FBA stock that Amazon controls and FBM stock that the seller, 3PL or warehouse ships. The safe setup is not one blended number. It is a clear split between fulfillment pools, SKU rules and sellable quantities, managed through ChannelDock’s LVB/FBA workflows and Stock Level Sync.
FBA and FBM pools
offer SKUs correctly
only sellable stock
Forum threads and competitor guides agree on the pain: FBA, FBM and Shopify can all show stock, but they do not mean the same thing operationally.
Before you start: define the promise per offer
Amazon FBA and FBM are not just shipping methods. They decide who owns stock truth, which quantity can be promised and how fast a customer expects shipment.
List which SKUs can be fulfilled by Amazon, your own warehouse, a 3PL, LVB, bol.com, Shopify or manual orders. A product may have one commercial identity but multiple operational stock pools.
Decide whether FBA and FBM use separate Amazon seller SKUs or one internal SKU with separate locations. Seller Central threads often recommend separate SKUs when both offers must remain independent.
Use fulfillable and sellable stock, not raw on-hand. Exclude FBA reserved, inbound, unfulfillable, quarantine, open FBM orders and any buffer you keep for marketplaces.
Step-by-step: split FBA and FBM inventory
Use this workflow when the same product can sell through Amazon FBA, Amazon FBM, Shopify, bol.com, marketplaces or B2B without sharing the exact same fulfillment stock.
Separate the physical stock pools first
Create a clear operational split: units already in Amazon FBA, units in your own warehouse, units at a 3PL, units inbound to Amazon and units in quarantine or returns. In ChannelDock, connect this to the same discipline you use for warehouse sections and stock locations.
Decide the SKU model for Amazon offers
If FBA and FBM must sell independently, use separate Amazon seller SKUs and map both back to the internal product. If you keep one internal SKU, make the fulfillment location explicit so one order cannot consume the wrong pool.
Publish FBA from fulfillable stock only
For FBA-fed channels, start with Amazon’s fulfillable quantity. Do not include inbound shipments, reserved units, FC transfer stock, damaged units or unfulfillable inventory. If Shopify or another webshop can use Amazon MCF, publish only the amount you are prepared to promise through that route.
Publish FBM from warehouse sellable stock
For FBM, calculate availability from your own warehouse or 3PL: physical stock minus open orders, picking waves, damaged goods, reserved B2B stock, transfers and channel buffers. ChannelDock’s Inventory Reservations helps remove committed units before shipment.
Set failover rules deliberately
Hybrid fulfillment is useful when FBA runs low and FBM can protect revenue, but failover should be a rule, not a panic edit. Define when FBM takes over: FBA below threshold, Amazon receiving delay, regional stockout, or margin difference.
Reserve demand before sync publishes again
When an Amazon FBM, Shopify or marketplace order arrives, reserve its units immediately and publish the reduced availability to every channel. This is where Stock Level Sync prevents one channel from selling stock another channel already claimed.
Reconcile the split every day
Compare Amazon FBA reports, FBM orders, warehouse counts, return receipts and ChannelDock stock movements. Investigate any product where total physical stock, fulfillable stock and sellable stock tell different stories.
The split-stock operating model
The safest hybrid setup treats FBA, FBM and webshop stock as connected, but not interchangeable. Every published number should be traceable back to a fulfillment pool and a customer promise.
Never let Amazon FBA stock, FBM warehouse stock and Shopify stock collapse into one number unless every unit can ship through every promise.
Common FBA/FBM inventory pitfalls
- Using one blended Amazon quantity when FBA and FBM have different shipping promises.
- Counting FBA reserved, inbound or unfulfillable stock as webshop stock.
- Running FBA and FBM offers under confusing SKU names that warehouse staff cannot recognise.
- Letting Shopify, Amazon and a 3PL each calculate availability in a different way.
- Failing to test returns, removals, cancellations and partial shipments before peak season.
Manual split sheets vs. ChannelDock LVB/FBA workflows
A spreadsheet can document a stock split. It cannot reliably reserve units, update channels and explain exceptions while orders keep arriving.
Without ChannelDock
- FBA reports, FBM orders and Shopify quantities are reconciled after the risk already happened.
- Warehouse teams guess whether a SKU belongs to Amazon, webshop, bol.com or B2B demand.
- Buffers and reservations live in separate tools, so the last unit can still be double-sold.
With ChannelDock
- FBA, FBM, webshop and marketplace stock are mapped into one operational view.
- Reservations, sync rules and warehouse movements reduce sellable stock before channels overpromise.
- Related workflows such as tracking FBA and warehouse stock stay connected to the same inventory truth.
FBA and FBM inventory FAQ
Related workflows to tighten next
After the FBA/FBM split is clear, strengthen the adjacent stock controls that keep hybrid fulfillment stable.
Run FBA and FBM from one inventory truth
Use ChannelDock to separate fulfillment pools, sync safe quantities and keep hybrid Amazon inventory from creating oversells.