Operator framework

Amazon FBA Inventory Health and Expiration Risk

How expiration-driven Disposal Requests, FEFO-blocked stock, and slow-moving expiration-dated inventory affect the Inventory Performance Index (IPI) — and the operator trade-offs that protect IPI while running an expiration-aware FBA operation.

Last reviewed·2026-05-29

Short version

Amazon's Inventory Performance Index (IPI) historically combines four pillars: excess inventory, sell-through rate, stranded inventory, and in-stock rate. Each pillar interacts with expiration handling. Expiration-driven Disposal Requests clear excess but can drop in-stock rate. FEFO pricing accelerates sell-through. Stranded units from FEFO blocks hit the stranded-inventory pillar directly. The operator framework is to time clearance levers (FEFO pricing, scheduled Disposal Requests, FBA-to-FBM conversion) against the pillar that's currently dragging IPI — and to verify pillar weights, the score threshold, and storage-limit consequences in Seller Central.

What IPI measures and why it matters

The Inventory Performance Index is Amazon's rolling weekly score for an FBA seller's inventory operations. The score affects the seller's storage limits — falling below Amazon's threshold can restrict how much inventory the seller can hold in FBA. For expiration-dated sellers running deep inventory across multiple MSKUs, the storage-limit consequence matters operationally: a restricted limit forces tighter sell-through discipline and earlier scheduled removals.

Amazon publishes the current pillar weights, threshold, and consequences inside Seller Central → Inventory → Inventory Performance Dashboard. The specifics update periodically; this page does not quote them because they go stale. Verify before relying on a specific number.

How expiration risk shows up in each pillar

IPI's pillars each respond differently to expiration handling. Tracking the interactions separately makes the operator trade-offs clearer.

Pillar 1 — Excess inventory

Excess inventory is on-hand stock above projected sell-through. For expiration-dated MSKUs, “projected sell-through” has to account for the Unsellable by Date — units the seller can't physically sell before the cutoff are excess by definition.

The expiration-aware view: a long-shelf-life MSKU with 18 months of runway can hold deeper inventory without hitting excess; a short-dated MSKU with 60 days of runway has to be sized tighter or the excess pillar drops. Operators with mixed shelf-life portfolios benefit from tracking projected sell-through against Unsellable by Date per MSKU, not in aggregate.

Pillar 2 — Sell-through rate

Sell-through rate measures how quickly inventory turns. For expiration-dated MSKUs, the rate matters twice — once for IPI and once for clearing the batch before Unsellable by Date.

FEFO pricing on the soonest-expiring MSKU is the cleanest IPI lever in an expiration context. The discount accelerates sell-through (positive pillar contribution), clears inventory that would otherwise become a Disposal Request (avoids the excess pillar), and recovers margin that would otherwise become a removal fee. The trade-off is per-unit margin on the discounted MSKU.

Pillar 3 — Stranded inventory

Stranded inventory is on-hand stock the seller can't sell — typically because of a listing issue, an FBA-to-FBM conversion, or a FEFO block past Unsellable by Date. The pillar weights stranded units negatively until they're resolved or removed.

For expiration-dated sellers, the stranded pillar is most often hit by FEFO-blocked units sitting between Unsellable by Date and physical disposal. The operator move: scheduled Disposal Requests close the stranded-inventory window faster than Amazon's automatic disposal cycle. See Amazon FBA stranded inventory + expiration.

Pillar 4 — In-stock rate

In-stock rate measures whether the seller has stock on hand for each active ASIN. When a Disposal Request clears the seller's last on-hand units, the in-stock-rate pillar drops on that ASIN.

The operator response when an active ASIN's only batch is approaching Unsellable by Date: ship the longer-dated replacement inbound before the active batch FEFO-blocks. The trade-off is the inbound carrying cost on the replacement units; the alternative is an in-stock-rate hit during the gap between disposal and the replacement landing at the FC.

The operator trade-offs

The four pillars often push in different directions. Naming the trade-offs makes the decision easier:

  • FEFO pricing helps sell-through; costs per-unit margin. Worth it when sell-through is the dragging pillar or when the alternative is a Disposal Request.
  • Scheduled Disposal Requests help excess and stranded inventory; can drop in-stock rate. Worth it when the disposed batch has no recovery path; pair with an inbound replacement to protect in-stock rate.
  • Inbound replacement units help in-stock rate; cost storage and add to excess inventory. Worth it on active subscriber MSKUs and on top-velocity ASINs; less critical on slow movers.
  • FBA-to-FBM conversion (for stranding) helps clear expired listings; hits stranded inventory pillar. Worth it as a step in the controlled-disposal sequence; resolve the stranded state quickly through the Disposal Request.

A real-shaped example

A supplements seller's IPI dashboard shows the excess-inventory pillar as the dragging score. The dashboard surfaces three culprit ASINs:

  • NUT-B26-LOT08 — 1,200 units, 126 days to Unsellable by Date, projected sell-through 756. Excess of 444 units.
  • NUT-B26-LOT12 — 800 units, 60 days to Unsellable by Date, projected sell-through 360. Excess of 440 units.
  • NUT-B26-LOT15 — 2,000 units, 270 days to Unsellable by Date, projected sell-through 1,800. Excess of 200 units.

The seller's response, by pillar:

  • LOT08: FEFO pricing at 8% discount + scheduled Disposal Request for the residual 192 units on the Unsellable by Date. Excess clears as inventory sells; the Disposal Request closes the remaining gap.
  • LOT12: aggressive FEFO pricing at 15% discount because 60 days isn't enough runway for an 8% discount to compound. Scheduled Disposal Request for the projected residual.
  • LOT15: no action — 270 days is enough runway that natural sell-through closes the excess without margin compression.

The composite effect: the excess pillar improves over 60 days as LOT08 and LOT12 clear. The sell-through pillar improves on the same cadence. The stranded pillar stays clean because the scheduled Disposal Requests fire on Unsellable by Date instead of leaving units stranded.

Patterns that protect IPI while managing expiration

The habits that consistently keep IPI healthy in expiration-aware operations:

  • Project sell-through at the MSKU level against Unsellable by Date. Aggregate forecasts hide which batches are at risk.
  • Apply FEFO pricing at 60 to 90 days out. Late discounts don't have time to compound; early discounts pay for themselves through accelerated sell-through.
  • Schedule Disposal Requests when you map the MSKU. The safety net costs nothing if the units sell.
  • Resolve stranded states quickly. Stranded units that linger drop the stranded-inventory pillar more than the same units removed promptly.
  • Pair Disposal Requests with inbound replacement on high-velocity ASINs. Protects in-stock rate.
  • Run the bin check weekly. The discrepancies that surface in week 2 are recoverable; the same discrepancies three months later have already compounded into IPI hits.

See FBA inventory bin check and the operator playbook.

How Shelfdoc helps

  • Per-MSKU projected sell-through against Unsellable by Date — the math each IPI pillar response depends on, in one view.
  • FEFO pricing per MSKU via the Listings Items API. Submissions are timestamped; Amazon decides Buy Box assignment.
  • Scheduled Disposal Requests fire automatically on the Unsellable by Date the seller chose. The stranded-inventory window stays as short as Amazon's removal SLA allows.
  • Weekly bin-check queue surfaces date discrepancies and quantity drift before they compound into IPI hits.
  • The audit log records every action with a timestamp — the evidence Seller Support cases need when an IPI calculation looks wrong.

What Shelfdoc does not do

  • Shelfdoc does not calculate the IPI score. Amazon owns the calculation, the pillar weights, and the threshold. The Inventory Performance Dashboard in Seller Central is the canonical record.
  • Shelfdoc does not guarantee that following the patterns above will produce a specific IPI score. The score depends on factors outside expiration handling (inbound velocity, ASIN restrictions, listing health on the rest of the catalog).
  • Shelfdoc does not appeal IPI-driven storage limit restrictions. The seller writes the appeal; Shelfdoc provides the audit trail.
  • Shelfdoc does not change Amazon's pillar weights or threshold values.

Frequently asked questions

What is Amazon's Inventory Performance Index (IPI)?
IPI is Amazon's rolling score for an FBA seller's inventory operations. The score is updated weekly and historically combines four pillars: excess inventory, sell-through rate, stranded inventory, and in-stock rate. A score below Amazon's threshold can restrict the seller's storage limits. Amazon publishes the score, the threshold, and the calculation inside Seller Central; verify the current values there because Amazon updates them periodically.
Does submitting a Disposal Request hurt IPI?
Disposal Requests reduce on-hand inventory, which can affect the excess-inventory pillar and the in-stock-rate pillar. The mechanism: if the disposed units were classified as excess, the score may improve as that excess clears; if the disposed units were the seller's only on-hand inventory for the ASIN, the in-stock-rate pillar drops. The net effect depends on which pillar dominated for that ASIN before disposal. Verify the current pillar weights in Seller Central.
Does FEFO pricing on soonest-expiring MSKUs help IPI?
FEFO pricing accelerates sell-through on the at-risk MSKU, which contributes positively to the sell-through-rate pillar. The trade-off is per-unit margin compression on the discounted MSKU. For operators where IPI is constrained, FEFO pricing is one of the cleanest levers — it moves a pillar positively while clearing inventory that would otherwise become a Disposal Request.
Does FBA-to-FBM conversion or stranded inventory affect IPI?
Stranded inventory (units the seller has on hand but can't sell — typically because of a listing issue, FEFO block, or fulfillment-channel conversion) directly hits the stranded-inventory pillar. The IPI scoring weights stranded units negatively until they're resolved or removed. The operator move when expiration causes stranding: resolve quickly through a Removal Order or Disposal Request rather than letting stranded units sit.
How do expiration-aware operators prevent IPI drops?
Three habits that compound. First, per-MSKU date discipline so the seller knows which batches are approaching Unsellable by Date weeks before the cutoff. Second, FEFO pricing on the soonest-expiring MSKU at 60 to 90 days out — early enough for the Buy Box rotation to accelerate clearance. Third, scheduled Disposal Requests as a safety net so residual units submit on the Unsellable by Date instead of accruing storage that compounds into excess-inventory IPI hits.
What's the current IPI threshold for storage limits?
The threshold changes periodically — Amazon has lowered and raised it more than once. This page deliberately avoids quoting a specific number because it goes stale. The current threshold for your account is in Seller Central → Inventory → Inventory Performance Dashboard. Storage-limit consequences for falling below the threshold are documented in the same surface.

Run the IPI-aware decisions per MSKU, automatically

Projected sell-through against Unsellable by Date on every row. FEFO pricing at the right discount, at the right time. Scheduled Disposal Requests that close the stranded-inventory window. The audit trail that defends an IPI calculation the seller wants to dispute.

Create account