If you are thinking about Q4 inventory in October, you are already late. FBA Q4 capacity planning is an August problem. By the time the Buy Box starts flickering on your hero SKU in November, the decisions that would have prevented it were due eleven weeks earlier. The brands that run Q4 cleanly are not luckier. They did the math in August.
This is the model we run every year, in cubic feet, with the fee dates attached. It is not complicated. It is just unforgiving about timing.
Why August, and not October
Three clocks run against you in Q4, and they all start before October.
The first is your FBA capacity limit, which Amazon sets monthly in cubic feet through the Capacity Manager. It does not magically expand because you have a big quarter coming. If your November limit is tight, you find out in late October, and by then the inbound lead time has closed.
The second is inbound lead time. From PO to receivable-at-FBA, most brands run four to eight weeks depending on origin and the receiving backlog, and the receiving backlog is at its worst in October and November, when every seller is shipping at once. Ship in August and you skip the queue. Ship in October and you join it.
The third is the Q4 storage surcharge. As of 2026, monthly FBA storage for standard-size inventory runs roughly $0.78 per cubic foot most of the year, then jumps to about $2.40 per cubic foot for October through December. That is roughly a 3x step-up, and it is why FBA Q4 capacity planning is as much a cost-timing problem as a stock problem. Sending everything in early avoids the receiving queue but pays the peak storage rate for longer. The FBA Q4 capacity planning model exists to find the line between those two.
How your capacity limit actually gets set
You cannot plan around a number you do not understand, so start here. Your monthly capacity limit, expressed in cubic feet in the Capacity Manager, is driven mostly by your IPI score and your recent sell-through, not by your sales forecast. Amazon is rationing space based on how efficiently you have used it, not on how much you intend to sell.
That has two consequences for FBA Q4 capacity planning. First, the time to raise your limit is the quarter before, by clearing aged units and lifting sell-through, not the week you need the room. Second, when the organic limit is not enough, you can buy more through a capacity reservation, committing to a higher limit and paying a reservation fee, with overage and unused-reservation charges if you miss in either direction. That reservation is a bet, and the model is how you size the bet instead of guessing it. Reserve to your ranked, cube-weighted plan, not to your most optimistic revenue number.
And watch the limit through the quarter, not just at the start. Amazon adjusts capacity monthly, so a strong October sell-through can earn you room in November, and a weak one can quietly cost it. FBA Q4 capacity planning is not a single August calculation you file away; it is a number you re-check every few weeks as the quarter’s actuals land and the model updates against them. The August run sets the plan. The weekly check keeps the plan honest.
The four inputs
The model takes four numbers per SKU. Get these and the rest is arithmetic.
1. Peak-week demand. Not Q4 total, peak week. Usually the week containing Cyber Monday, or your category’s specific spike. Pull last year’s daily units for that week, adjust for this year’s growth rate, and add the promotional lift you are actually planning, not the one you are hoping for.
2. Unit cube. The cubic feet a single sellable unit occupies in the FBA bin, packaging included. Pedantically: measure it, do not estimate it. A unit you guessed at 0.4 cubic feet that is actually 0.6 cubic feet blows your capacity math by 50% at scale.
3. Capacity limit. Your current Capacity Manager limit in cubic feet, plus any reservation you have purchased. This is the ceiling. Everything else fits under it or does not ship.
4. Storage cost per cube. The $2.40-per-cubic-foot Q4 standard-size rate as of 2026, plus the aged-inventory surcharge if any SKU will cross 181 or 271 days on hand during the quarter.
The worked example
Take one hero SKU. Peak-week demand: 3,000 units. Unit cube: 0.5 cubic feet. You want four weeks of peak-rate cover going into the spike, call it 12,000 units.
That is 12,000 × 0.5 = 6,000 cubic feet for one SKU. If your total Capacity Manager limit is 9,000 cubic feet, this single hero just consumed two-thirds of your entire FBA footprint. Now layer your other 40 SKUs onto the remaining 3,000 cubic feet and the problem becomes obvious: you cannot hold four weeks of everything. The model forces the ranking you were avoiding.
The storage cost on that hero, held a full peak month: 6,000 cubic feet × $2.40 = $14,400 for one SKU for one month. Hold it two months because you shipped early to beat the receiving queue, and that is $28,800 in storage on a single SKU before you have sold a unit. That number is the whole reason FBA Q4 capacity planning is a model and not a gut call. You are trading receiving risk against storage cost, in dollars, per cube.
The inbound placement fee wrench
One more number changes the answer: the FBA inbound placement fee. As of 2026, Amazon charges a per-unit placement fee when you send inventory to a single receiving location and let Amazon distribute it, and waives or reduces it when you split the shipment across multiple inbound locations yourself. For a high-cube Q4 SKU, that fee is not a rounding error, it can rival a chunk of the storage math above.
So FBA Q4 capacity planning has a fork inside it. Consolidate to one destination and pay the placement fee but simplify your freight, or split across the required locations to cut the fee but add freight legs and complexity at the worst time of year to add complexity. There is no universal answer; there is a per-SKU answer. High-cube, high-volume heroes usually justify the split; the long tail usually does not. Model it on the SKUs that move the cube, and default the rest.
Step one: rank SKUs by cube-efficiency of margin
Capacity is the scarce resource, so you allocate it the way you allocate any scarce resource, by return per unit of it. For each SKU, compute gross margin dollars per cubic foot of peak cover. A high-margin, low-cube SKU earns its FBA space many times over. A low-margin, high-cube SKU is a liability that happens to sell.
This is the same logic behind the case that FBA aged-inventory surcharges turn slow movers into liabilities: the cubic foot is the unit that matters, not the SKU count. Rank by margin-per-cube and the bottom of that list is what you do not send to FBA for Q4, you hold it in 3PL or FBM and protect the capacity for the SKUs that earn it.
Step two: build the inbound schedule backward
Now you have your quantities. Work backward from peak week.
If peak week is the week of December 1 and your inbound lead time is six weeks including the October receiving backlog, your last safe arrival is mid-October, which means your PO and freight book in late August or early September. Anything later is a bet on the receiving queue clearing, and in Q4 it does not.
Split the inbound into at least two waves. The first wave carries you through early-to-mid November at normal storage exposure. The second wave, timed to arrive late October, tops you up to peak cover and only pays the $2.40 rate for the weeks it actually needs to. Two waves cost a little more in freight and save materially in storage versus shipping the whole quarter in August. That trade is the core of FBA Q4 capacity planning, and it is worth modeling per SKU rather than applying one rule to the catalog.
Step three: the buffer and the removal plan
Hold a capacity buffer of 10 to 15% under your limit. A full Capacity Manager has no room to absorb a hot SKU or a reslotting, and a stranded inbound shipment in November is the most expensive kind. The buffer is not waste; it is the option to react.
Plan the removals before the quarter, not after. Any SKU that will cross the aged-inventory thresholds during Q4, or that ranks at the bottom of your margin-per-cube list, gets a removal or a markdown plan dated for early January. The brands that skip this carry dead cube into Q1 and pay the off-season rate to store what did not sell. Decide the exit in August, when you can think clearly, not in January when the storage bill arrives.
If the math says a chunk of your catalog simply does not fit FBA for Q4, that is not a failure of the model, that is the model doing its job. Route the overflow to 3PL or FBM. The mechanics of that handoff are their own decision, covered in how we forecast replenishment without overcommitting Q4, but the capacity model is what tells you the overflow exists in the first place.
What to do in August
Run the four inputs for every SKU. Rank by margin per cubic foot. Decide the placement-fee fork on your high-cube heroes. Book the first inbound wave by early September and the second to land in late October. Set a 10 to 15% capacity buffer and date your January removals now.
None of this is exotic. It is cubic feet, fee dates, and lead times, multiplied out and decided early. The reason FBA Q4 capacity planning wins or loses in August is that every input is knowable then and none of them are fixable in November. Do the arithmetic while you still have options. The brands that treat Q4 as a math problem in August are the ones not paying for a stranded shipment or an empty Buy Box in December.
Written by the ClearSight Distribution Team. Reviewed by the Amazon Growth Team.
Related reading: