FBA Inventory Health After the 2024 Fee Change

The post-2024 Fulfillment by Amazon (FBA) inventory playbook is not “stop watching capacity.” It is to separate three signals before the next fee cycle: cubic-foot capacity usage, monthly storage cost, and units approaching the aged-inventory threshold. An agent can run that review through the Amazon Selling Partner MCP as a reusable Skill, grounded by Amazon Agent Atlas so the policy window and report fields are not guessed.

Amazon ended FBA inventory storage overage fees effective July 1, 2024 in the United States, Europe, United Kingdom, and Canada stores. That change does not remove monthly inventory storage fees or the aged inventory surcharge. The operator question is therefore narrower and more useful: which inventory is consuming capacity, which inventory is accumulating storage cost, and which inventory is close to the next age threshold? The same review can join Amazon Standard Identification Number (ASIN) inventory context to the campaign and demand signals available through the Amazon Ads MCP.

Why not just ask ChatGPT or Claude? A disconnected chat has no access to your data, no way to take action, and generic knowledge, not Amazon's. It cannot see your current FBA inventory, retrieve the reports, or apply the store-specific rules that determine which fee is relevant. The workflow below keeps those boundaries explicit: read live data, ground the interpretation, then decide what action deserves approval.

Separate the fee policy from the inventory decision

The first move is a policy check, not a removal recommendation. The FBA Inventory Storage Overage Fees playbook says the overage fee stopped being charged in the named stores on July 1, 2024. The same source still describes monthly storage fees and an aged inventory surcharge as separate charges. Atlas returns that distinction with the retrieval context, so the agent does not collapse “overage fee removed” into “storage is free.”

The output should be a short policy record: store scope, effective date, fee families still in play, and the source playbooks used. That record becomes the explanation for every downstream recommendation.

Measure capacity in cubic feet, not units

Capacity is a volume problem. The report exposes capacity_usage_volume, capacity_limit, overage_volume, and volume_unit; the unit is cubic feet. A unit count can rise while volume stays flat, or a small number of bulky units can create the larger constraint. The agent should read the Capacity Monitor or Inventory Performance view, then reconcile the report fields before ranking action.

inventory_health_snapshot:
  storage_type: oversize
  capacity_usage_volume: 600
  capacity_limit: 500
  overage_volume: 100
  volume_unit: cubic feet
  decision: investigate slow-moving bulky inventory

The useful artifact is not a generic “reduce stock” list. It is a ranked queue by storage type, cubic-foot contribution, velocity, and removal or replenishment option. Keep volume_unit attached to every number so a later operator does not mistake volume for units.

Review monthly storage separately

Monthly storage fees remain a distinct operating signal after the overage-fee change. Review the Monthly Storage Fee report by ASIN, then identify the SKUs whose storage cost is persistent without a matching sell-through or replenishment need. Atlas retrieval also surfaces storage-utilization surcharge and AWD waiver context, so the agent can mark a fee as a policy exception rather than treating every charge as a capacity breach.

This is where the operator separates diagnosis from action. A high monthly storage charge may justify a sell-through, liquidation, return, or replenishment change, but the action belongs after the evidence review. The Skill should present the report rows, the decision rule, and the expected trade-off together.

Catch aged inventory before the fifteenth-day snapshot

The aged inventory surcharge applies to units stored 181 days or longer and is assessed using an inventory snapshot on the fifteenth day of each month. The FBA Inventory tool can show inventory that is already subject or will become subject within 60 days. The review should therefore sort by days-to-threshold, cubic-foot exposure, and available action window.

next_snapshot: 2026-08-15
asin: B0EXAMPLE12
age_days: 176
days_to_181_day_threshold: 5
per_unit_volume: 0.102 cubic feet
recommended_review: removal, sell-through, or return economics

The Aged Inventory Surcharge report is the evidence layer after the decision. It provides itemized SKU quantities, per-unit volume, surcharge tier, and amount charged. Keep the pre-snapshot queue and the post-charge report together so the team can compare the avoided cost with the action it chose. For a related report-driven workflow, see FBA order and report review.

What happens next

Run the review on a schedule: policy check first, capacity volume second, monthly storage third, and aged-inventory countdown last. The agent should return a compact report with source playbooks, report fields, affected ASINs, and proposed actions. A human then approves removals, returns, liquidation, or replenishment changes through the Selling Partner MCP. The Amazon Agent Data layer keeps the policy context attached to the decision, and the Amazon Agent Flow can carry the approved workflow forward.

If your FBA review still asks only whether the overage fee exists, it is looking at one policy line instead of inventory health. Separate volume, storage, and age, then decide with the evidence in front of you.

Next in the series: turning the same age and volume queue into a controlled removal recommendation without losing the audit trail.