Weekly inventory health check for FBA operators

A weekly inventory health check keeps problems small. The goal is not to review every SKU in detail. The goal is to surface the few inventory states that can quietly destroy contribution margin: stockouts, excess cover, stranded units, aging inventory, and SKUs with mismatched replenishment assumptions.

Start with coverage

Group SKUs by days of cover, not just units on hand. A slow mover with 200 units can be healthy, while a fast mover with 80 units can be a stockout risk. Use trailing velocity, inbound quantities, reserved units, and available FBA stock to classify each SKU.

• Under 14 days: confirm inbound timing and decide whether to expedite.
• 14 to 45 days: healthy for most replenishable SKUs.
• 45 to 90 days: review margin, storage risk, and future demand.
• Over 90 days: plan markdowns, bundles, removal, or advertising changes.

Check stranded units

Stranded inventory is cash with no sales path. Review stranded SKUs before reordering related products. The common causes are suppressed listings, missing offers, pricing rules, hazmat review, and deleted parent-child relationships.

Every stranded line should receive an owner and a next action. If the issue is listing-related, fix the offer. If the product is blocked, decide whether the inventory should be removed before storage fees compound.

Compare decisions to margin

Inventory choices should not be based on sales volume alone. A SKU that sells quickly but loses money after storage and fulfillment fees should not receive the same replenishment priority as a slower SKU with stable profit.

Build the weekly review around three outputs: replenish, investigate, or exit. That keeps the conversation operational and prevents the health check from becoming a passive dashboard review.

Add thresholds before the meeting

The health check works best when thresholds are defined before the team opens the report. If every SKU gets debated from first principles, the review will turn into a long meeting with inconsistent decisions. Set simple thresholds by SKU class: minimum days of cover, maximum days of cover, acceptable stranded age, and the storage age that triggers a removal or markdown discussion.

Those thresholds should be different for fast movers, seasonal goods, and experimental products. A new product may tolerate lower cover while demand is being proven. A seasonal SKU may need earlier liquidation planning. A reliable evergreen SKU may deserve faster replenishment because the stockout cost is high and predictable.

Tie every exception to one owner

Inventory health gets worse when exceptions have shared ownership. Catalog may think operations owns stranded units. Operations may think finance owns aged inventory. Finance may think the buyer owns replenishment. The weekly review should end with one owner per exception and a due date that is close enough to matter.

Use the smallest useful owner set: buyer, catalog, warehouse, finance, or operator. If a SKU needs multiple actions, record the sequence. For example: catalog fixes suppression first, then finance reviews the fee impact, then the buyer decides whether to replenish. That avoids parallel work on a SKU that may not be sellable yet.

Save the decision history

Inventory decisions compound. A SKU that was marked "watch" three weeks in a row is no longer just a watch item; it is a decision the team has avoided. Store the reason, owner, expected action, and review date. This gives the next review context and prevents the same discussion from restarting every week.

Decision history is also useful when forecasting is wrong. If a stockout happened because a supplier missed a date, update the lead time. If overstock happened because demand fell after a promotion ended, update the sales window. The review should make the planning model smarter each week.