Amazon Inventory Management: The Complete Guide

Posted 2026-05-17

You opened Seller Central this morning, saw two SKUs out of stock, and knew before clicking through that the Buy Box on both was already gone. The replenishment shipment? Sitting at a fulfillment center for nine days, still "checked-in." Meanwhile, two of last quarter's overbuys are racking up long-term storage fees that hit on the 15th.

That, right there, is Amazon inventory management. Not the dashboard. The Tuesday morning where margin walks out the door while you're still pouring coffee.

This guide is for Amazon sellers doing $50K-$500K/month who have outgrown spreadsheets, are tired of fighting Seller Central, and want to know what works. No theory. Real numbers, real fees, real workflows.

Quick answer (the snippet version)

Amazon inventory management is the practice of tracking, replenishing, and reconciling every unit you sell through Amazon — across FBA and FBM, across marketplaces if you sell elsewhere, and against your real per-unit cost from purchase to settlement. Doing it well means avoiding stockouts (which kill Buy Box and ranking), avoiding overstock (long-term storage fees and Aged Inventory surcharges), maintaining IPI above 400-450 to protect capacity, and reconciling every Amazon fee against the specific unit it came from. Sellers who do this in one tool spend 70-80% less time on inventory work than sellers stitching Seller Central, a separate tracker, ShipStation, and a spreadsheet.

Why inventory management makes or breaks Amazon sellers

Inventory is the only line item where a 5% mistake compounds into a 30% margin hit by quarter's end. Get it wrong, and Amazon punishes you on both sides — stockouts on one half of your catalog, storage fees on the other.

The cost of stockouts

A stockout is not just lost sales for the days you are out. It is:

• Buy Box loss the moment your offer goes inactive. Amazon's algorithm reassigns it to a competing seller within minutes.
• Ranking decay that starts inside 24 hours. The recommendation engine demotes products that can't ship. Recovery takes 2-4 weeks after restock, sometimes longer.
• Lost velocity tier, which feeds back into IPI scoring (more on that below). Slower sell-through means lower IPI means tighter capacity next quarter.
• The reorder rush — paying expedited shipping on the next inbound batch because you tried to recover. That's another $0.30-$1.50 per unit gone before it's even on a shelf.

A single 5-day stockout on a hero SKU doing $20K/month routinely costs $3,500-$5,000 once you stack lost sales, ranking recovery, and rush replenishment.

The cost of overstocking

Overstocking is the inverse trap, and Amazon charges for it explicitly:

• Monthly storage fees scale by month and double in Q4 (Oct-Dec). A unit that costs $0.78/month to store Jan-Sep costs $2.40/month Oct-Dec.
• Aged Inventory Surcharge on anything sitting in FBA past 181 days — starts at $0.50/cubic foot and ramps to $6.90/cubic foot for inventory over 365 days.
• Removal or disposal fees when you finally pull the plug — $0.97-$1.85+ per unit depending on size tier, plus return freight if you remove instead of dispose.

A pallet of slow-movers can quietly burn $200-$400/month in storage and surcharges before anyone notices the line item.

IPI score and capacity limits

Amazon's Inventory Performance Index (IPI) is the gate between you and storage capacity. It's calculated weekly from four signals:

• Excess inventory percentage — units with >90 days of supply at current sell-through.
• Sell-through rate — units shipped vs. average inventory over the last 90 days.
• Stranded inventory — listings with inventory but no active offer.
• In-stock rate — replenishable SKUs that are in stock vs. total replenishable SKUs.

Score below 400 and Amazon caps storage capacity. Score below 450 in Q3 and you walk into Q4 — the only quarter that matters — with restricted space. Operators who actively manage IPI run 500-700 and use the headroom to send heavy inbound ahead of Prime Day and Black Friday.

Seller Central tells you the score weekly but does not tell you what to do about it in a way that respects margin. It will happily suggest removing inventory that would have cleared in 30 days with a $0.50 price cut.

Amazon's built-in inventory tools (and their limits)

Amazon gives sellers a stack of inventory tools through Seller Central. They are good for what they are. They are not enough for a real operation.

Seller Central inventory dashboard

What it shows:

• Current stock by SKU and ASIN, split between fulfillable, reserved, and unfulfillable
• Inbound shipments and their check-in status
• Unfulfillable units waiting on a removal decision
• Per-SKU sales rank, Buy Box status, and the price history of your own offer

What it misses:

• Your real cost basis. Seller Central has no idea what you paid per unit. It knows what you sold it for and what fees came out — not what came in.
• Cross-channel context. If you also sell that unit on Walmart, eBay, or Shopify, Seller Central will not tell you. It treats Amazon as an island.
• Returns lifecycle. A return shows up as a refund line; what happens to the physical unit afterward — graded, refurbished, resold, disposed — lives somewhere else entirely.
• Per-unit settlement reconciliation. Settlement reports come in two-week chunks and bury per-unit fees in aggregated tables that take real work to break apart.

Seller Central is a single-marketplace operational console. It is not an inventory system.

FBA inventory reports

Three reports do most of the work most sellers actually look at:

• Inventory Health — flags excess, low-stock, and stranded inventory.
• Restock Recommendations — Amazon's suggested reorder quantities based on its forecast.
• Aged Inventory — units approaching or already inside the storage-surcharge thresholds.

The problems:

1. Reports are delayed. Most refresh every 24-72 hours. By the time the Aged Inventory report flags a unit, you've already paid one or two weeks of surcharge on it.
2. Reports are siloed. Nothing in Inventory Health knows that a unit also sells on Walmart at 2x velocity, where you could route it instead of disposing.
3. Restock recommendations assume your cost is constant. They don't account for a vendor that just raised pricing, a container that just landed at $5.83 instead of $4.20 per unit, or the fact that the next batch is going to be a different condition grade.

Useful as inputs. Dangerous as outputs.

IPI score and capacity squeeze

The IPI score itself is a single number, refreshed weekly. The interventions Seller Central offers — remove inventory, lower prices, fix stranded listings — are real, but they are point-in-time. They do not give you the rolling forward-looking view a serious operator needs: "If I do nothing this week, what's my IPI in 30 days?" That answer comes from your own data, not Seller Central.

Multi-channel complexity — when Amazon isn't your only channel

Most sellers doing real volume are not Amazon-exclusive. They are on Amazon plus Walmart, plus eBay, plus Shopify, often plus BackMarket for refurbished electronics, often plus one or two of the Mirakl retailers (Macy's, Best Buy, Lowe's). Every channel adds complexity that Seller Central cannot help with.

Inventory allocation across marketplaces

You have 100 units of a SKU in your warehouse. Do you list 100 on each channel and pray you don't oversell? Do you split 40/30/20/10? Do you reserve 20 for a vendor backorder you're trying to fulfill direct?

The answer is workflow-specific, but it requires a single source of truth for "how many do we actually have, where, and what is committed against them." Seller Central doesn't know about your eBay sales. Your eBay tool doesn't know about your Amazon FBA inbound. Your spreadsheet knows about both, but only as of last Friday when someone updated it.

The oversell problem

The most expensive failure mode for a multi-channel seller is selling the same unit on two channels. Two orders come in five minutes apart, you can only ship one, and Amazon flags you for an Order Defect Rate ding on the cancellation while your eBay account takes a Late Shipment Rate hit on the other.

Multi-channel sellers oversell something. The question is the frequency. Sellers running on real-time push sync between channels see oversell rates under 0.1%. Sellers running on hourly batch sync see 1-3%. Sellers running on spreadsheets and manual nightly updates see 5-12% — which on a 1,500-orders/month business is 75-180 oversells, each one a customer service problem and a metrics hit.

Why spreadsheets break at scale

A spreadsheet runs an operation up to about 300-500 orders/month, one SKU per row, with a careful operator refreshing daily. Above that, three things break:

1. Latency. By the time the spreadsheet is updated, two numbers in it are wrong.
2. Reconciliation. Pulling Amazon orders, ShipStation labels, and eBay sales into one row per SKU is an hour a day minimum. It does not scale linearly — it scales worse.
3. Human cost. Spreadsheet maintenance is the highest-hourly-cost task in your business that pays zero in revenue. Multiply across 12 months — that's a salary, gone.

This is the wall most $50K-$500K/month Amazon sellers hit. The spreadsheet that built the business will not run the business.

What to look for in Amazon inventory management software

Once you decide the stack is not working, the question becomes what to replace it with. Five non-negotiables.

Real-time sync across marketplaces

Push, not pull. When a unit sells on eBay, the available count on Amazon should drop within seconds, not within the next sync cycle. This is the difference between a 0.1% oversell rate and a 3% oversell rate. Bonus: channel-specific quantity buffers (list 95% of stock on Amazon, hold 5% for direct sales, never let the buffer trip a Low Inventory warning).

Per-unit cost tracking

Not per-SKU averages. Per unit. If two batches of the same SKU came in at $4.20 and $5.83 landed cost, the system should know which units are which and reconcile fees against the actual unit that shipped. Per-SKU averaging is what makes operators think they're profitable on a SKU when half the units are losing $2 each.

FBA inbound and removals management

The inbound side of FBA is half the workflow. Your inventory tool should generate shipments, track them through check-in, and reconcile what Amazon actually received against what you sent (the receiving variance is a real number every month). On the removals side, the tool should track every removal order, tie it back to the original units, and surface unclaimed FBA reimbursements. Most operators discover $1,500-$4,000/month of stuck reimbursements the first time they audit this seriously.

Warehouse operations that don't end at the label

Receiving, grading, bin management, and barcode-driven picking. If you do any refurbishment, regrading, or condition routing, the warehouse layer is where margin lives or dies. A unit that walks off the floor between grading and listing is a 100% loss. A grading workflow that ties the condition to the individual serial number — not the SKU — keeps that from happening.

Purchase orders and vendor management

Replenishment triggers based on real sell-through and real lead time, not on Amazon's forecast. Vendor terms (deposit/balance, net 30, net 60). Serial number scanning at receive so you know which units came from which PO at which landed cost. Bonus: container-import support for sellers sourcing overseas — duties, brokerage, freight allocated per-line item — so landed cost is reconciled, not estimated.

How to set up Amazon inventory management (step by step)

Five steps. Allocate a real two weeks to do it right. The payoff is years of saved time.

Step 1 — Audit your current inventory

Pull a full Active Listings report and a Fulfillable Inventory report from Seller Central. Walk the warehouse. Count physical stock. Reconcile against the report. The variance you find — and there will be variance — is the baseline noise level of your current system.

Document it. The same audit run a quarter from now should show a smaller variance. If it doesn't, the tool change did not fix the workflow problem.

Step 2 — Establish your real cost basis

For every SKU, document:

• Unit purchase cost (per batch if it varies)
• Inbound shipping allocated per unit
• Prep cost if you use a prep service
• Landed cost if imported (duties + brokerage + freight allocated per line)

This is the number Seller Central does not have. Without it, every profit number you look at is fiction. With it, you can finally answer: "Which 20% of SKUs make 80% of the profit, and which 20% are quietly losing money on every unit sold?"

Step 3 — Connect your channels

Connect Amazon first. Then any other marketplace where you sell the same units — Walmart, eBay, Shopify, BackMarket, the Mirakl retailers. Set quantity allocation rules per channel. Decide your buffer. The first 48 hours after connection are the highest-risk window for an oversell — most tools require an initial sync that takes minutes, and that window is when mismatches surface.

Step 4 — Set up warehouse workflows

Receiving (scan PO, scan unit, route to bin). Grading if applicable (test, mark condition, route to grade-specific bin). Picking (scanner-driven, no paper). Packing (rate-shop carriers, print label). The goal is "no spreadsheet, no clipboard, no Slack message between steps." If a unit moves between steps without a barcode scan, you will lose units. That is the iron law.

Step 5 — Monitor and optimize

Daily: stock levels, orders pending fulfillment, ship-ready batch status, anything aged on the pack bench.

Weekly: per-SKU P&L for the prior 7 days. Slow movers (>90 days inventory). FBA reimbursement check (Amazon owes someone something every week). IPI score trajectory.

Monthly: supplier performance (on-time delivery, defect rate, landed cost variance). Replenishment plan for the next 60 days. P&L by channel — is one marketplace quietly losing money while another carries it?

This is the cadence that turns inventory management from reactive firefighting into a forward-looking operational practice.

Common Amazon inventory mistakes (and how to avoid them)

Five mistakes do most of the damage. In rough order of cost-to-the-business:

1. Treating Seller Central as your inventory system. It is a marketplace console, not an inventory system. The moment you sell on a second channel or care about real per-unit cost, Seller Central stops being enough.
2. Tracking cost per SKU instead of per unit. Averages lie. If you bought 100 units at $4.20 and another 100 at $5.83, the average is a number that describes no actual unit you've ever shipped. Per-unit tracking is the only way real P&L works.
3. Ignoring FBA removals and reimbursements. Money you've already earned, sitting unclaimed. The first audit usually finds $1,500-$4,000/month. Compound that over a year.
4. Manual multi-channel sync via spreadsheet. This is the oversell factory. The math on saved subscription cost vs. cost of one Amazon Order Defect Rate hit is not close.
5. No grading process for returns or refurbished inventory. Units come back. Without a workflow, they sit on a forklift for two weeks, get listed at the wrong condition, get returned again. Every untracked unit is a 100% loss.

How Rilk handles Amazon inventory management

Rilk is an all-in-one inventory and fulfillment system. Amazon inventory management is one of the things it does — alongside Walmart WFS, eBay, Shopify, BackMarket, and 25+ Mirakl retailers. Stop paying ShipStation. Stop paying for the separate inventory tool. Stop running settlement reconciliation in a spreadsheet.

Here is what changes once Amazon inventory lives in Rilk:

• One catalog, every channel. A unit is a unit. It appears on Amazon as Renewed-Good, on BackMarket at the right grade, on eBay with the right condition note, on Walmart with WFS routing — all from the same record. Stock stays in lockstep. No oversells. How multi-channel sync works.
• Per-unit P&L from settlement, not estimates. Two weeks after the order ships, Amazon's deposit lands. Rilk reconciles every fee — referral, FBA, advertising, returns, reimbursements — against the specific unit it came from. The unit either made money or it didn't. There is no estimate. Reporting and reconciliation in Rilk.
• FBA removals tracked end-to-end. Every removal order, tied back to the original serial, with the reimbursement claim status. Included. How returns work in Rilk.
• Regrading workflows native. Phones come back, get tested, get graded A/B/C/parts, get re-listed at the right condition. The lifecycle lives in one place. How regrading works.
• Walmart Buy Shipping included. Nearly nobody else integrates it natively. If WFS is a real chunk of your business, that one feature alone pays for the move. Shipping in Rilk.
• Purchase orders, vendor terms, container landed-cost reconciliation. The PO is connected to the units it brings in. Landed cost is real. Purchase orders.

The pricing is flat. $499/month for one company, $1,499/month for up to three companies. Compare that to ShipStation Standard at $149.99/month plus your inventory tool at $400-$1,200/month plus the hours your team spends on the spreadsheet — and Rilk is usually cheaper before you count the time saved.

If you run a refurbishment operation, see the refurbisher use-case. If you run multi-channel new goods, see the multi-channel-brand use-case. If you are still paying ShipStation alongside a separate inventory tool, the ShipStation comparison breaks down the math.

---

Start free at rilk.ai. The free tier replaces ShipStation today — no inventory migration required. When you are ready to retire the separate inventory tool, the upgrade is the same login. Real per-unit profit on every Amazon order you ship.