Sizing a warehouse from your SKU list, not your gut

Key Takeaways

• Healthy warehouse space utilisation sits at 40-80% of cubic capacity; sizing for 100% utilisation guarantees you'll be too small the first time volume spikes.
• Sizing from cubic velocity per SKU, storage volume weighted by how often each SKU actually moves, gives a materially different (and more accurate) answer than sizing from total SKU count or last year's footprint.
• Fast-moving SKUs need forward-pick space with short travel paths; slow-moving SKUs belong in high-density reserve storage. Sizing the two categories the same way wastes either picking efficiency or storage density.

Most warehouse sizing decisions start from the wrong number: either last year's footprint plus a percentage for growth, or a round figure that felt safe when someone signed the lease. Neither is derived from what's actually being stored. Sizing from the SKU list, weighted by how much space each SKU needs and how often it moves, produces a materially different, and more defensible, number.

Why total SKU count is the wrong input

SKU count alone tells you almost nothing about space requirements. Two businesses with 500 SKUs each can have completely different footprint needs if one sells small, fast-moving electronics accessories and the other sells bulky, slow-moving furniture. The input that matters is cubic velocity: the physical volume each SKU occupies, weighted by how frequently it's ordered (cubic velocity methodology, retrieved 2026-09-08). A SKU that's small but sells constantly needs accessible forward-pick space; a SKU that's bulky but rarely moves needs cheap high-density storage, and confusing the two wastes either picking efficiency or storage density.

Run your actual SKU list, with unit dimensions and monthly order frequency, through the warehouse space calculator rather than starting from a target square footage. The output changes meaningfully once velocity is factored in against volume alone.

Don't size for 100% utilisation

A warehouse sized to be exactly full at expected peak volume will be over capacity the moment volume exceeds the forecast, which happens more often than most sizing exercises assume. Healthy space utilisation, monitored on an ongoing basis rather than as a one-time sizing input, sits at roughly 40-80% of cubic capacity (warehouse capacity and utilisation benchmarks, retrieved 2026-09-08). Sizing to land inside that band at expected peak, not at 100%, leaves room for seasonal spikes, new SKU introductions, and the operational slack that aisles, staging areas, and returns processing actually require, none of which show up if you size purely on stock volume.

Slotting fast and slow movers differently

Once cubic velocity is known per SKU, the sizing exercise splits into two different space types rather than one uniform layout:

• Fast-moving SKUs need forward-pick locations: shorter travel paths, easier reach, and faster replenishment cycles, which typically means selective racking with lower storage density per square metre.
• Slow-moving SKUs are better held in high-density reserve storage, drive-in racking or block stacking, that trades picking speed for a much higher cube utilisation ratio, since they're accessed rarely enough that travel time barely matters (SKU velocity slotting guidance, retrieved 2026-09-08).

Sizing the whole warehouse as one storage type, rather than a mix, either wastes picking efficiency (if everything is high-density reserve) or wastes footprint (if everything is low-density selective racking sized for fast movers that don't actually need it).

What to re-run the sizing on

SKU-based sizing isn't a one-time exercise. Re-run it when the SKU list changes materially, when a seasonal category is added or dropped, or roughly annually regardless, since velocity for individual SKUs drifts as products age, get discontinued, or shift between fast- and slow-moving as demand changes. A warehouse sized correctly for last year's SKU mix can be meaningfully wrong for this year's without anyone having changed the footprint.

For the broader growth-stage capacity planning this feeds into, see trading growth strategy.

Frequently asked questions

How much bigger should we size than our current stock volume?

Size to land at roughly 40-80% cubic utilisation at expected peak volume, not current average volume. The specific target within that band depends on how volatile your demand is; a business with sharp seasonal peaks should size toward the lower end of that range at peak.

Does this methodology apply to a shared or third-party warehouse?

The same cubic-velocity logic applies when negotiating space with a 3PL, it determines how much space you actually need to book, and whether a flat-rate or variable-rate 3PL contract suits your SKU mix better.

How often should warehouse sizing be reviewed?

At minimum annually, or immediately after a significant SKU list change, a new sales channel, or a seasonal category addition. Velocity drifts continuously; the sizing exercise doesn't have to be redone that often, but it shouldn't be treated as permanent either.

The bottom line

A warehouse sized from total SKU count or last year's footprint is a guess dressed up as a plan. Sizing from cubic velocity per SKU, split between fast-moving forward-pick space and slow-moving high-density reserve, and targeting 40-80% utilisation rather than 100%, produces a footprint that's actually defensible against a lease negotiation or an investor question.

Figures were verified on 8 September 2026 against published warehouse capacity planning and cubic velocity methodology references. Actual sizing depends on your specific SKU mix, seasonality, and growth trajectory; use these as planning inputs, not fixed targets.