Back to Blog
Published:
Last Updated:
Fresh Content
Warehouse Pick OptimizationChapter 9

Why Slotting Savings Must Be Shown Net of Replenishment

3 min read
614 words
high priority
Muhammad Mudassir

Muhammad Mudassir

Founder & CEO, Cognilium AI

A pallet being moved to replenish a pick face, the hidden cost that offsets placement savings

TL;DR

Every item you move closer to packing is an item you now replenish more often, and a restock costs more than a pick. Any slotting savings that ignore replenishment labour are only half the picture.

Answer first

When you move an item to a better pick location, you usually also make its pick face smaller, which means it runs out faster and has to be replenished more often. A replenishment trip costs more than a pick. So any slotting analysis that shows you travel savings without subtracting the added replenishment labour is showing you half the equation. Real slotting savings are net of restock, and anyone who quotes you a number that is not should be asked why.

The trade nobody mentions

The pitch for slotting is simple and appealing: move your fast movers close to packing and your pickers walk less. It is true. But there is a second half to it that vendors tend to leave out.

Forward pick locations, the good ones near packing, are usually small. That is what makes them convenient. It also means they hold less. So an item you move into a small forward location empties faster, and someone has to bring more inventory to refill it, more often, from bulk storage further away.

That refill is a replenishment trip, and it is not free. In fact it costs more than a pick, because a picker grabbing an item is a quick action while a replenishment is a larger movement of stock. The rough rule of thumb in the field is on the order of one replenishment worker for every several pickers, which tells you replenishment is a real and separate cost, not a rounding error.

Why this makes or breaks a slotting number

Here is the trap. You can show a beautiful reduction in pick travel by moving a lot of items forward. On paper the picking gets faster. But if you moved items forward that do not have the volume to justify a small pick face, you have created a stream of replenishment trips that eats the pick savings, and can even exceed them.

The academic literature puts it directly: if too little is stored forward, restock costs consume the pick savings. Some items positively hurt efficiency when they are slotted forward in less than their full quantity.

So a slotting recommendation that only counts the walking it saves is not actually a recommendation. It is a guess that happens to look like arithmetic. The real question for every proposed move is not "does this reduce pick travel" but "does the pick travel it saves exceed the replenishment travel it creates."

What good analysis does about it

Sound slotting nets the two out, item by item. It asks, for each candidate move: how much pick travel does this save, given how often the item is picked, and how much replenishment travel does it add, given how fast the smaller forward location will empty. Only moves where the first exceeds the second are worth making. The rest either stay put or belong in a different kind of location.

This is also why slotting is not simply "put all the fast movers forward." Some fast movers, in the right quantity, absolutely belong forward. Others move so much volume that the replenishment cost of a small forward face outweighs the benefit, and they may belong in a different storage mode entirely.

The takeaway

When you evaluate slotting help, whether from a tool, a consultant, or an internal analysis, ask one question: are the savings net of replenishment. If the answer is a clear yes, with the replenishment cost shown alongside the pick savings, you are looking at real analysis. If the answer is a travel-reduction number with nothing underneath it, you are looking at the appealing half of a two-sided trade, and the other half is waiting for you on the warehouse floor.

Share this article

Muhammad Mudassir

Muhammad Mudassir

Founder & CEO, Cognilium AI

Mudassir Marwat's argument is that ERP systems record decisions they never optimise.

Founder & CEO of Cognilium AI; 37 AI agents in production across four products; 4 production AI products built and operated; three clouds in production (AWSGCPAzure)
Agentic AIRAG → GraphRAG retrievalVoice AIMulti-Agent Orchestration
Next in this series
Should You Optimize Slotting or Picker Routing First?
Chapter 10 · 9 min