A box pool is simple in theory: a fixed population of containers that circulates between sites. In practice most pools lose 15 – 30% of their population a year and the programme quietly dies. The causes are remarkably consistent.
Leak 1 — the return leg has no owner
Outbound is somebody's job. Return almost never is. Pools survive when one named person at each site is responsible for the empties, and when the return trailer is scheduled rather than requested.
Leak 2 — the footprint does not match
A container that overhangs the pallet gets damaged in every rack move. Half an inch matters. Measure the pallets you actually have, not the ones in the standard.
Leak 3 — no grading step
Without inbound grading, damaged containers re-enter circulation, fail under load, and poison confidence in the whole programme. One failure in a rack costs more goodwill than fifty successful trips earn.
Leak 4 — the pool is too small
Pools need slack. Our rule of thumb: population equals peak weekly demand multiplied by cycle time in weeks, plus 20%. Undersized pools generate emergency purchases of new containers, which is how a reuse programme ends up buying virgin board.
What a healthy pool looks like
- Named owner for empties at every node.
- Scheduled return freight, ideally a backhaul.
- Inbound grading within 24 hours of arrival.
- A repair bench, or a partner who has one.
- Quarterly reporting on trips-per-container, not just tonnage.
- 20% slack in population.
The number to watch
Trips per container per year. If it is rising, your pool is healthy. If it is flat while your volume grows, you are buying your way out of a process problem.
Our pieces are written by the people who do the work rather than by a content agency, which is why they contain more numbers and fewer adjectives than is fashionable. If a figure here does not match your experience, we would genuinely like to hear about it — two of our published coefficients have changed that way.