Amazon FBA Inventory Management Software for Hybrid Vendors: What to Check Before You Buy

If you sell some ASINs through Vendor Central and replenish others into FBA through Seller Central, your inventory picture lives in two consoles that do not talk to each other. On the vendor side Amazon writes the purchase orders, and on the FBA side you decide what to send. The software built for FBA sellers handles the second half well and has nothing to say about the first, so a hybrid operator who buys it without checking ends up with a forecast that covers part of the catalog and leaves the rest blank.

Two posts on this blog already cover the single-program view. Amazon Inventory Management Software: What It Actually Means for a Vendor covers how a pure 1P vendor should evaluate a tool, and Amazon FBA Inventory Management explains how your FBA capacity limit gets set. This piece covers the part neither of them does: what to check when the same tool has to serve both programs at once.

Two Inventory Systems, One Catalog

A hybrid account is a brand that holds both a Vendor Central and a Seller Central account and runs the two Amazon relationships in parallel. Amazon gives you no unified login, combined dashboard, or cross-platform reporting for that setup. Each account has its own credentials and its own reports, and consolidated reporting means exporting from both and reconciling the files by hand every period.

The inventory consequence follows directly from how the two programs work. Under 1P, Amazon buys your units and becomes the retailer of record, so the retail price is Amazon's to set and the order is Amazon's to place. Under 3P you stay the seller of record, price your own listings, and decide what goes into fulfillment centers and when. The 1P vs 3P comparison walks through the economics. What matters for inventory is that one catalog now has two different parties deciding when stock moves.

Sometimes the split is clean, with high-volume SKUs on Vendor Central and narrower lines through Seller Central. Often it drifts, and the same product family has stock moving through both. When that happens, three questions get hard to answer from either console alone:

• How many units of this ASIN are committed to Amazon in total, across open vendor POs and FBA inbound shipments?
• Is Amazon's demand forecast on the vendor side telling the same story as your FBA sell-through?
• If you cut an FBA replenishment because vendor POs picked up, will you notice in time when those POs drop off again?

What the FBA-Only Tools Assume

Open the pages that rank for this query and the feature set is consistent. Helium 10's inventory tool promises to "complete supplier orders and send inventory to Amazon, all in one place," with forecasting and custom presets that adjust lead times, reorder frequency, and shipment speeds. Getida's roundup of eleven tools, from Linnworks and Veeqo to RestockPro and SkuVault, organizes the category around demand forecasting, multichannel sync, and automated shipping.

Amazon's own Seller Central stack follows the same model. The Inventory Performance Dashboard sends an alert when stock runs low and suggests recommended inventory levels and shipment timelines. The FBA Restock Tool and the Inventory Age Report sit alongside it, and the Inventory Performance Index (IPI) scores how efficiently you manage your FBA inventory.

Every one of those tools rests on the same assumption: you decide when to reorder. The tool watches your sell-through, compares it with what you have on hand and inbound, and recommends a quantity and a ship date for you to act on.

None of those pages mentions Vendor Central, vendor purchase orders, or hybrid selling. That scope is fine for a pure FBA business, but for a hybrid vendor it means the tool sees half the stock moving through Amazon and treats it as the whole.

Where the Vendor Side Breaks That Assumption

On Vendor Central you do not decide when Amazon reorders. Amazon generates vendor purchase orders from its own sales forecast, current inventory levels, and demand data on the item, and your job is to confirm each PO accurately inside the acceptance window Amazon specifies and then ship it. The vendor software post makes the full case for why reorder-point tools answer the wrong question for a vendor. For a hybrid operator the short version is that an FBA tool has no input for an order you did not place.

That gap shows up in three places once both programs share a catalog.

1. Forecasts. The FBA tool forecasts from your Seller Central sell-through. Amazon's forecast for your vendor ASINs, which you see in Vendor Central's Forecast and Inventory Planning report, is a separate number Amazon produces from its own retail data, and neither console puts the two side by side.
2. Committed stock. If one warehouse feeds both programs, units you have confirmed on an open vendor PO are already spoken for. A restock recommendation that reads your warehouse on-hand without those POs can send the same units to FBA that you promised to Amazon Retail.
3. History. Vendor Central exposes its reports over a limited window, so the record you need to compare this quarter against last year's has to be kept somewhere else. The FBA post's advice to reconcile the record against your own count before you plan against it still holds, and in a hybrid catalog you have two records to reconcile.

Reconciliation Questions to Ask in a Demo

Bring one hybrid ASIN to the demo, ideally one that had both an open vendor PO and an FBA shipment in the last quarter, and ask the sales engineer to show you each of these on that ASIN.

1. Does it read Vendor Central data at all? Ask which Vendor Central reports it pulls and whether open POs are among them. If the answer is a Seller Central connection plus a spreadsheet upload for other channels, the vendor side will be hand-maintained and late.
2. Does it put vendor and FBA stock for the same ASIN on one row? You want open vendor PO units, FBA on-hand, and FBA inbound side by side, without switching accounts or views.
3. Does it flag when the two programs disagree? If Amazon's vendor forecast for an ASIN climbs while the FBA restock recommendation for the same ASIN also climbs, you may be about to over-commit warehouse stock, and the tool should flag that before you ship against both.
4. Does its FBA recommendation subtract units on open vendor POs? Ask how it computes what you can ship from your own warehouse, and whether confirmed PO quantities reduce that figure.
5. Does it keep history Amazon drops? Ask how far back it stores Vendor Central data, and whether that history starts on the day you connect or can be backfilled. Planning a hybrid catalog means comparing seasons, and a tool that only mirrors the current console window cannot do it.
6. Can it record which program each ASIN belongs to? If you assign each SKU to one program to avoid channel conflict, those assignments will change over time, so the tool should know where an ASIN sits this quarter and keep a record of when it moved.

Score the answers using the trial approach in the vendor post, run against a quarter you already know well, so every number the tool shows you can be checked against one you already trust.

What Amazon's Native Tools Still Can't Do

The Seller Central tools are useful for what they cover, but everything they show, from the Inventory Performance Dashboard to the Restock Tool and the Inventory Age Report, describes your FBA stock.

Vendor Central's Retail Analytics covers the other half through Inventory Health, Real-Time Inventory, and Forecast and Inventory Planning, all of which describe Amazon's stock of your products. The Vendor Central report definitions guide explains what each one holds.

Nothing in either console joins the two, because Amazon offers no combined dashboard or cross-program report for a hybrid account. Reconciling them becomes a weekly export from two consoles into one sheet, and the history in that sheet begins on the day someone started keeping it.

InsightLeap is the tool that keeps that join running. It pulls Vendor Central sales, inventory, open POs, and Amazon's demand forecast, reads FBA inventory for Seller Central accounts, keeps historic Vendor Central reports beyond the window Amazon shows you, and sends a daily digest of the changes as they happen.

If you came from Seller Central

In Seller Central you decide what goes into fulfillment centers and when. Vendor stock doesn't move on your schedule, because you confirm and ship the POs Amazon writes. IPI measures how efficiently you manage FBA inventory, so it scores your Seller Central side only and tells you nothing about how your vendor ASINs are doing. The 1P, 2P, 3P glossary entry covers the vocabulary differences.

Where to Start

Before you sit through a demo, build the picture the software is supposed to give you, even if only for a handful of ASINs:

• List every ASIN that had stock in both programs over the last two quarters, and the program each one is supposed to be in.
• For each one, note open vendor PO units, FBA on-hand, and FBA inbound as of this week.
• Pull Amazon's forecast from Forecast and Inventory Planning and put it beside your FBA sell-through for the same ASINs.
• Mark the ASINs where those two numbers point in different directions, and bring those to every demo.
• Ask each tool the six questions above on those ASINs, and drop any tool that cannot show vendor POs and FBA stock on the same row.
• Start a weekly export of both sides now, so you have your own history to check any tool's numbers against.