A warehouse rack is built to a standard module, and containers are built to fit products. Where those two modules do not relate, every shelf carries unused space at the front, the back or the side – and because it repeats across every bay in the building, the total is a meaningful fraction of the storage the company is paying for. Reconciling the two is one of the few changes that improves capacity without touching the building.
Where the waste comes from
A shelf is a fixed width and depth. A container occupies some of it, and the remainder is unusable because nothing else will fit. That remainder is the waste, and it is determined by how well the container footprint divides into the shelf. A container that divides evenly has almost no waste; one that leaves an odd gap has waste on every shelf, in every bay, permanently.
Dividing the shelf, not filling it
The instinct is to choose the largest container that fits. The better question is which container footprint divides into the shelf with the smallest remainder. A slightly smaller container that gives three across instead of two plus a gap usually stores more total volume, because the gap is eliminated rather than traded. This is the same arithmetic as pallet pattern efficiency, applied one level up.
Depth is the dimension usually wasted
Shelf depth is set by the rack and is often deeper than the container needs. Because the surplus is at the back, it is invisible, and it is the largest single source of waste in most racks. Where containers are chosen, checking the depth as carefully as the width is worth doing – and where the rack has adjustable beams, setting the depth to suit the container is a cheap change.
Height clearance and the vertical waste
The gap between the top of a container and the beam above it is set for access, and it is often larger than it needs to be. Where containers are a consistent height, the beam spacing can be tightened and a whole extra level sometimes appears in the same building height. That is the highest-value change available in most warehouses, and it depends entirely on the container height being consistent.
Mixed container heights in one bay
A bay holding containers of several heights wastes the difference, because the beam spacing is set by the tallest. Where a fleet can be arranged so that heights group – tall containers in one area, short ones in another – the beam spacing can differ by area and the waste falls. That is a layout decision enabled by the container family rather than a container change, and it costs nothing.
What a container family should share
For racking purposes, containers should share a footprint and differ in height. That lets the width and depth be set once and the beam spacing vary, which is the arrangement that wastes least. Where containers differ in footprint as well, every bay has to be set for the worst case, and the waste returns. Sharing a footprint is worth more here than matching each container to its product exactly.
Calculating the gain before acting
Measure the wasted width, depth and height per bay as a fraction of the bay volume, multiply by the number of bays, and the result is the volume being paid for and not used. Where the number is large – and in mixed fleets it often exceeds a fifth – the case for standardising the container module is straightforward. The related density question for empties is in folding empties and storage density.
What to do
Get the usable shelf envelope from the rack supplier, choose container footprints that divide into it, group heights so beam spacing can vary, and re-check before ordering. Four steps, and the first is free. Where a fleet already exists, the same exercise shows which sizes are causing the waste, and those are the ones worth retiring first.