Why Reslotting Your Top SKU Often Saves Zero Feet

Here's a pattern that shows up in almost every slotting review: the team pulls a list sorted by pick count, starts at the top, and spends most of their energy on the busiest SKU in the building.

It feels right. High volume, high priority. Move the #1 item closer to the start point and you've made a meaningful dent.

Except you usually haven't.

The busy SKU is often already in a good spot

Think about how your warehouse actually works. The SKUs that get picked constantly are the ones everyone notices. Managers see them. Pick supervisors see them. Whoever did the last slotting review saw them.

Because of that, high-velocity items tend to get decent placement over time. Not perfect, but reasonable. Your #1 mover has probably already been nudged toward the front at some point, even informally.

So when you run a reslotting review and start with the top mover, you're often looking at a SKU that's already pulling 8 or 10 feet of round-trip distance per pick. Moving it to a bay that's 2 feet closer saves 2 feet per pick. At 1,000 picks a day, that's 2,000 feet. Just over a third of a mile.

That's not nothing. But it's probably not the best first move in your building.

The formula you're skipping

Walk savings for any reslot is: picks × (current distance minus target distance).

The second part of that — available savings per pick — is what most reviews skip entirely.

If your #1 mover is at 10 feet from parking and the best open bay is at 8 feet, you're working with 2 feet of per-pick savings. A thousand picks gets you 2,000 feet per day.

Now look somewhere else. A SKU picking 300 times a day, sitting 100 feet from parking, with a clear bay available at 15 feet. That's 85 feet of per-pick savings. Three hundred picks gets you 25,500 feet per day.

One-third the velocity. Twelve times the daily walk savings.

That's the move you make first. Not because it's a bigger SKU — it isn't — but because the geometry of where it sits versus where it could sit is so much worse.

What a real priority list looks like

When you rank reslotting candidates by picks × available savings per pick instead of just picks, the top of the list looks completely different.

You'll find mid-velocity items in terrible positions. Items that have sat in a poorly-located bay for years without ever cracking the top-mover report. Items nobody has thought about since the last time somebody said "we should really look at slotting."

Those are your best first moves. They're harder to find, but the payoff is immediate. You make ten of those moves and the floor impact is visible the same week.

Frequency-sorted reviews feel productive because you're touching your most active SKUs. Savings-sorted reviews actually move the needle.

The location scarcity problem

There's a second reason to stop starting with your top mover: prime locations near parking don't stay empty forever.

Good bays — the ones close to a cart parking spot, correctly typed, with enough capacity — are limited. If you burn one of those slots on a SKU that was already reasonably positioned, you've used up a resource you can't get back for the move that actually needed it.

And if your top mover needs a specific bay type (full-pallet footprint, flow rack dimensions, a certain shelf height), the options get even narrower. Spending your best available location on a marginal improvement is one of the most common ways slotting reviews underdeliver.

The type constraint nobody talks about

Generic reslotting lists also tend to ignore element type entirely.

A pallet item can't move into a flow rack slot. A split-case pick slot can't absorb full-case inventory. A floor-level pallet position can't substitute for an elevated pick face.

When a move list doesn't account for this, warehouse teams reject the recommendations on sight. A suggestion that looks great on paper becomes "we can't actually do that" the moment it hits the floor. The process stalls, trust in the tool erodes, and the next review starts from scratch.

A shorter list of moves your team can actually execute is worth far more than a longer list they have to manually filter. If you're generating fifty recommendations and implementing eight, the list isn't saving you time — it's creating work.

Calculate savings before you move anything

Most slotting reviews never produce a single number answering: how much walk does this specific move save per day?

It's not hard to calculate. You need the current location's distance from parking, the target location's distance, and the daily pick count. Multiply, subtract, done.

When you do this before touching anything, two things happen. Some moves that looked obvious turn out to be marginal — the distance improvement is small and they get deprioritized. And some items nobody was thinking about turn out to carry massive savings — those get fast-tracked.

That pre-calculation is what the priority queue should be built on. Not what's busiest. What actually saves walking.

The busy SKU will get its turn. It just usually shouldn't be first.