Amazon + WMS: Managing FBA and FBM from One Dashboard
An Amazon WMS integration connects Seller Central to your warehouse system so FBA stock in Amazon fulfillment centers and FBM stock in your own warehouse show up as one inventory picture. You manage both fulfillment modes from a single dashboard, push accurate quantities to every sales channel, and route each order to the right pool without spreadsheet reconciliation.
An Amazon WMS integration connects Seller Central to your warehouse system so FBA units sitting in Amazon fulfillment centers and FBM units sitting in your own warehouse show up as one inventory picture. You stop reconciling two stock ledgers by hand, push accurate quantities to every sales channel, and route each order to the pool that should fulfill it.
Amazon WMS integration for FBA and FBM means treating Amazon as both a sales channel and a fulfillment network inside one warehouse management system, with separate location pools, shared SKU masters, and a single available-to-sell calculation.
If you sell on Amazon and anywhere else, that single dashboard is not a nice-to-have. It is how you avoid canceled orders, stranded stock, and storage fees you never planned for.
Why do FBA and FBM break inventory when they run in separate tools?
Fulfillment by Amazon (FBA) and Fulfillment by Merchant (FBM) look like two shipping choices. Operationally they are two different inventory worlds.
With FBA, Amazon stores your units, owns the pick-pack-ship process, and reports status buckets that do not exist in a normal warehouse: available, inbound, reserved, unfulfillable, and researching. With FBM, your team (or your 3PL) owns the physical stock, the pick path, the carrier label, and the late-shipment risk that hits Amazon account health.
Seller Central does not combine those worlds into a clean available-to-sell number for your Shopify store, your wholesale portal, or your TikTok Shop listing. You check one report for FBA, another screen for merchant-fulfilled quantity, then guess which total is safe to sell elsewhere.
That guess is where brands lose money. Industry research from the IHL Group projected that global retail inventory distortion (out-of-stocks plus overstocks) would cost retailers $1.77 trillion in 2023. Multi-channel Amazon sellers feel a smaller version of the same problem every week: one channel shows stock that another channel already sold.
A WMS closes the gap by becoming the ledger that both Amazon modes report into.
What should an Amazon + WMS dashboard actually show?
A useful Amazon WMS dashboard is not a prettier Seller Central clone. It answers four questions your floor team and your channel managers both need:
- How many units of this SKU can we sell right now across every pool?
- How many of those units are FBA fulfillable versus warehouse FBM?
- Which open orders should ship from Amazon versus from our dock?
- Which FBA units are aging toward storage surcharges?
At minimum, the screen should show per SKU:
- Warehouse on-hand / available for FBM and other merchant-fulfilled channels
- FBA fulfillable quantity (not "total inventory")
- Inbound to FBA and in-transit so restock planning is honest
- Reserved / committed units already tied to open orders
- Unfulfillable / stranded units that need a removal order or disposal decision
- Days of cover by pool, not just a blended average
When those fields live in one place, your team stops arguing about which spreadsheet is current. Tools like BinLogic WMS are built around that location-aware inventory model, so Amazon FBA and your warehouse FBM stock can share a SKU without sharing a misleading total.
How does Amazon WMS integration work for FBM orders?
FBM is the cleaner half of the integration because your warehouse still owns the units.
A solid flow looks like this:
- Amazon creates a merchant-fulfilled order in Seller Central.
- The integration pulls the order into the WMS with the mapped SKU, ship-by date, and shipping service level.
- The WMS reserves inventory at the correct warehouse location and creates a pick task.
- Your team scans, packs, and prints a label (or uses Amazon's shipping services if you prefer).
- The WMS posts tracking and shipment confirmation back to Amazon.
- Available quantity for that SKU refreshes on Amazon and on every other connected channel.
The non-negotiable detail is SKU identity. Your Amazon seller SKU, ASIN mapping, and warehouse item ID must resolve to one product master. If variants or bundles do not map cleanly, the sync will invent phantom stock or leave real stock invisible.
FBM also benefits from the same barcode discipline you use for other channels. If your team already scan-verifies picks, Amazon merchant-fulfilled orders should ride that same process instead of becoming a clipboard exception. For a deeper walkthrough of floor scanning, see our barcode scanning warehouse guide.
How should a WMS treat FBA inventory differently?
FBA inventory is yours on the balance sheet, but Amazon controls custody. Your WMS should not pretend those units sit on your rack.
Pull Amazon inventory reports (or Selling Partner API feeds) into dedicated FBA locations in the WMS. Map Amazon's status fields carefully:
- Fulfillable / available can support sellable quantity on other channels if you intentionally choose to share that pool
- Reserved is already spoken for and should not inflate available-to-sell
- Inbound helps restock planning but is not sellable yet
- Unfulfillable needs a workflow, not a channel push
Then decide a business rule per SKU: do other channels sell from FBA stock, from warehouse stock only, or from a prioritized mix?
Many brands keep FBA inventory reserved for Amazon velocity and Prime conversion, while warehouse stock covers Shopify, wholesale, and Amazon FBM overflow. Others use Amazon Multi-Channel Fulfillment (MCF) so non-Amazon orders can ship from FBA when the warehouse is short. Either model works. Mixing them without rules does not.
Nucleus Research has found that organizations deploying a WMS improve inventory accuracy by an average of 20 percent, with 46 percent of organizations seeing accuracy gains within a year. Those gains only stick if FBA and warehouse quantities are modeled as separate locations with clear available-to-sell logic.
How do you keep one source of truth across Amazon and other channels?
The source of truth should live outside Seller Central.
Amazon is excellent at fulfilling Amazon orders. It is a weak master system for a brand that also sells on Shopify, Walmart, TikTok Shop, or a wholesale portal. Your WMS (or a tightly paired OMS + WMS stack) should own:
- The product master and SKU map
- Location-level on-hand by warehouse and by FBA pool
- Channel buffers and safety stock
- Order routing rules
- Restock signals that account for FBA lead time and storage exposure
A practical sync pattern:
- Sale happens on any channel.
- Master inventory decrements immediately.
- Channel quantities refresh within minutes, not hours.
- Nightly or intra-day reconciliation catches failed API updates and stranded mismatches.
If you are already fighting oversells across marketplaces, pair this Amazon setup with the same discipline covered in how to prevent overselling across multiple channels and the broader multi-channel inventory management guide.
Safety buffers matter on Amazon more than most teams expect. Marketplace inventory feeds are not instant, and Amazon's own status buckets can move while your other stores are still selling. A small percentage buffer on shared SKUs absorbs latency without looking like you are out of stock on every listing.
What are the biggest Amazon + WMS failure modes?
Most failed Amazon integrations share the same mistakes.
Syncing total FBA inventory instead of fulfillable
If you push Amazon's total quantity to Shopify, you are advertising reserved, inbound, and sometimes unfulfillable units as sellable. Cancellations follow.
Letting Seller Central remain the master for warehouse stock
Your FBM quantity should come from scanned warehouse transactions, not from a manual Seller Central edit after someone counts boxes.
Ignoring aged inventory and inbound placement economics
Amazon has tightened aged-inventory pressure. Surcharges now escalate earlier in the inventory life cycle than many sellers planned for, and inbound placement choices can add per-unit cost before a unit ever sells. Your dashboard should surface days-on-hand and removal candidates before finance discovers the fee on a settlement report.
Treating hybrid FBA + FBM as a store-wide binary
Marketplace Pulse research cited by industry analysts puts hybrid usage at roughly 35% of high-volume Amazon sellers, and broader seller surveys still show FBA used by the large majority of active sellers. The winning pattern is per SKU: Prime-sensitive fast movers on FBA, bulky or slow units on FBM or a 3PL, overflow rules documented in the WMS.
Skipping returns and removals in the inventory model
FBA customer returns, warehouse returns, and removal orders all change available quantity. If those events never hit the WMS, your "one dashboard" becomes two again within a month.
What does a clean Amazon WMS setup look like in practice?
Here is a rollout sequence that avoids boiling the ocean.
Week 1: Identity and locations
Create FBA and warehouse locations in the WMS. Map every active Amazon SKU. Quarantine anything that cannot map cleanly.
Week 2: FBM live loop
Turn on order import, pick/pack, tracking export, and inventory push for merchant-fulfilled ASINs. Prove late-shipment risk is under control before you expand scope.
Week 3: FBA visibility
Pull FBA inventory statuses into the dashboard. Stop using spreadsheets for fulfillable versus inbound. Decide which SKUs may share FBA stock with other channels.
Week 4: Routing and alerts
Add rules for FBM overflow, MCF where useful, low-stock alerts by pool, and aged-inventory warnings. Only then automate replenishment recommendations.
If Shopify is also in the stack, keep that channel's mapping and sync rules consistent with the same product master. Our Shopify + WMS integration guide covers the storefront side of that handshake.
How should you decide FBA vs FBM inside the WMS?
Use unit economics and operational risk, not habit.
Put a SKU on FBA when:
- Prime conversion materially lifts sell-through
- The item is compact enough that storage and fulfillment fees still leave margin
- You can keep inbound flowing without constant stranded inventory
- You want Amazon to absorb peak pick capacity
Keep a SKU on FBM when:
- The item is heavy, oversized, fragile, or high-touch
- Velocity is too low to justify FBA storage risk
- You need tighter control of packaging or inserts
- You already have reliable warehouse capacity and carrier rates
Many catalogs end up split. That is fine. The WMS job is to make the split visible and enforceable: one SKU, two pools, one available-to-sell policy.
What results should you expect after Amazon and your WMS share a dashboard?
Expect operational results before vanity metrics.
Teams that centralize FBA and FBM usually see:
- Fewer Amazon cancellations caused by phantom FBM stock
- Fewer Shopify or marketplace oversells caused by ignored FBA sales
- Faster restock decisions because inbound and fulfillable are no longer buried in reports
- Clearer storage-fee control because aging FBA units are visible early
- Less daily reconciliation time between Seller Central and the warehouse
Inventory accuracy is the foundation. Without it, every forecast, purchase order, and channel buffer is guesswork. With it, Amazon becomes one more node in a controlled network instead of a second business running on a separate spreadsheet.
Getting started
If you already run a warehouse and sell on Amazon, start with one honest inventory map: every active SKU, every physical pool, and the rule that decides which pool can sell where. Then connect Seller Central so FBM orders and FBA statuses land in that same map automatically.
BinLogic WMS is designed for mid-market brands that need warehouse execution and channel inventory to stay aligned, including Amazon FBA and FBM in one operational view. If your current stack still forces you to reconcile Seller Central against a spreadsheet before lunch, it is time to put one system in charge.
Related reading:
Frequently asked questions
What is an Amazon WMS integration?
An Amazon WMS integration connects Amazon Seller Central to your warehouse management system so orders, inventory, and shipment confirmations sync automatically. For FBM, your WMS pushes available quantity and pulls merchant-fulfilled orders. For FBA, the integration reads Amazon's stock statuses and sales so your master inventory stays accurate across both pools.
Can one WMS manage both FBA and FBM inventory?
Yes. The WMS should treat FBA and FBM as separate location pools under one SKU master. FBM quantity is what your warehouse can ship. FBA quantity is what Amazon reports as fulfillable. The dashboard rolls both up so you see total on-hand without double-counting or mixing sellable and reserved units.
How do I stop overselling when I use FBA and FBM together?
Put one system in charge of available-to-sell, then sync every sale back to that system within minutes. Use Amazon's fulfillable quantity (not total) for FBA, keep a small safety buffer on shared SKUs, and never let Seller Central or a spreadsheet act as the source of truth for multi-channel brands.
Do I need a separate tool for Amazon Multi-Channel Fulfillment (MCF)?
Not always. Many Amazon WMS setups can route selected non-Amazon orders through MCF when FBA has stock and your warehouse does not. You still need clear rules so MCF does not drain FBA inventory you reserved for Prime velocity or storage-fee control.
What should sync between Amazon and a WMS first?
Start with SKU mapping, FBM inventory push, FBM order import, and shipment tracking back to Amazon. Add FBA inventory pull and sales adjustments next. Only then layer restock planning, aged-inventory alerts, and multi-channel quantity rules. Get the identity map right before you automate quantities.
Plan the route. We deliver the rest.
See how Binlogic powers last-mile logistics — routing, tracking, and the platform that turns the plan into the package on the doorstep.
Book a callback
