Amazon FBA Capacity Manager: Fees and When to Say No

Quick answer: FBA Capacity Manager lets eligible sellers request additional storage capacity and specify a maximum reservation fee. Amazon may grant some or all of the request, and performance credits from resulting sales may offset the fee, but extra capacity isn't automatically profitable. It's a commitment to create enough contribution from the added space before the period ends, and two ASINs using identical cubic space can produce very different economics.

A seller's best ASIN was climbing, his factory needed a production decision, and Seller Central showed less FBA capacity than the purchase order required. He opened Capacity Manager, requested a large increase, and entered a reservation fee near the upper end of what he could tolerate to improve the odds of approval. The request was granted, which felt like a win until demand softened: a competitor came back in stock, CPC increased, and conversion fell. He used only part of the additional capacity, and the units that did arrive sold more slowly than expected. Performance credits didn't offset the full reservation cost. He'd solved a storage problem without proving he had a profitable sales problem to solve.

What Capacity Manager is doing

FBA capacity limits are measured by storage type and period. Capacity Manager lets sellers ask for more space than the system currently plans to provide, generally specifying the requested additional capacity, the future period, and a maximum reservation fee per unit of capacity. Amazon evaluates requests and can approve an amount, with the fee based on the granted capacity and applicable reservation rate. Performance credits may offset that fee as inventory using the extra space produces sales. The economic logic underneath: you're saying this additional cubic space can generate enough sales during the period to justify the cost of reserving it.

Capacity is measured in space, but profit is created by units

This creates the central edge case. One cubic foot used by 30 small beauty items with $6 contribution each produces $180 of contribution if the units sell. The same cubic foot used by 2 bulky home products with $18 contribution each produces only $36. A capacity request should therefore be modeled at SKU level, not cubic feet. A useful internal metric, not an Amazon one, is contribution density: expected contribution from units stored divided by cubic capacity used. If one ASIN produces three times more expected contribution per cubic foot than another, sending both merely because both purchase orders are ready is poor allocation.

Composite case study: a toy seller before Q4

A toy company had five FBA products under consideration for a capacity request: a card game (4,000 units, 160 cubic feet, $5.20 contribution, 90% expected sell-through), a large activity kit (1,100 units, 290 cubic feet, $11.00 contribution, 55% sell-through), a travel puzzle (2,500 units, 90 cubic feet, $3.80 contribution, 95% sell-through), a gift bundle (900 units, 220 cubic feet, $14.50 contribution, 70% sell-through), and a legacy board game (700 units, 240 cubic feet, $7.00 contribution, 35% sell-through). The first instinct was requesting enough capacity for all planned units. The better plan removed most of the legacy board game and delayed part of the activity kit, basing the capacity request on the card game, travel puzzle, and a controlled quantity of gift bundles. This reduced requested space while preserving most expected contribution, and it made the reservation fee easier to recover because the approved capacity would actually be used by products likely to sell during the period.

The break-even question

Before submitting a request, estimate the reservation fee if the full request is granted, the performance credits expected from sales using that capacity, and the contribution from the incremental units. Net value of extra capacity equals incremental contribution minus net reservation fee (reservation fee minus earned performance credits) minus incremental storage and inbound costs. Don't assume the credits will equal the fee, model a low, base, and high sales case instead.

The alternative-cost test

Capacity Manager is only one way to handle excess supply. Compare it against sending fewer units and replenishing more often, storing inventory in AWD, holding inventory at a 3PL, delaying the purchase order, or removing old FBA stock to free capacity. The correct question isn't "can I get more FBA capacity?" It's "is paid FBA capacity the cheapest reliable way to protect profitable sales?"

Edge cases that change the answer

The capacity period and the sales period don't always match, a seller may need units physically available before an event, but the product sells over several months afterward, making the reservation economics look poor even when the purchase order is sensible over a longer horizon. Approval can be partial, a request for 500 cubic feet may be granted at a smaller amount, so the seller needs a priority list, without one, the warehouse ships whichever products are ready rather than the ones with the best contribution density. The product can sit near a size-tier boundary, where a small packaging change can alter cubic usage and fulfillment economics, so the capacity plan should use current measured dimensions, not the factory's design specification. And demand can depend on advertising that hasn't been stress-tested, if the forecast assumes a fixed ACOS, run a sensitivity test since capacity can be filled by units that only sell when ads are unprofitable.

A practical request workflow

Clean current FBA inventory first, identifying stranded, unfulfillable, aged, and low-contribution units to free capacity before buying more. Build a SKU capacity table with unit dimensions, units planned, expected sell-through, contribution per unit, and contribution density. Create three sales cases, conservative, base, and upside, with the conservative case including weaker conversion and slower receiving. Set a maximum fee from economics, not urgency, choosing the point where extra capacity no longer beats the alternative. Pre-rank the inventory so you know which units get the space if only part of the request is granted. Track the capacity after approval: granted versus requested capacity, actual space used, incremental units sold, and reservation cost not offset.

---

EcomSanity can't determine whether Amazon will approve a capacity request, but it can help identify the ASINs whose sales velocity, days of inventory, and contribution justify one. A useful workflow exports the proposed SKU list from your capacity model, then validates it against current sales and stock movement, though the seller should still confirm Amazon's current rates inside Capacity Manager before submitting. For the storage-cost side of this same decision, see Amazon storage utilization surcharge.