Your heatmap is lying to you: why pick frequency is the wrong color
Most warehouse heatmaps color by pick count. The labor is hiding somewhere else, and the fix starts with one distance-aware toggle.
SlotWise Team
5 min read
Most warehouse heatmaps tell a clean story: red means busy, blue means quiet, and your highest-pick bays should get the most attention.
That story is useful. It is also incomplete.
Pick frequency tells you where activity happens. It does not tell you where labor is being spent. The missing variable is distance. A bay with modest pick volume at the far end of the building can burn more walking time than a bright red bay sitting beside the start point.
That is why a pick-count heatmap can look right while the floor still feels wrong.
Pick frequency is activity, not effort
Warehouse teams gravitate toward frequency because it is easy to explain. If a location gets 1,000 picks, it feels more important than a location with 100 picks.
For replenishment, inventory review, and SKU velocity, that instinct is often helpful. For slotting labor, it can send you to the wrong aisle.
The picker does not pay only for the pick. The picker pays for the trip. If the same SKU is picked from a prime bay beside the main route, the labor cost per pick is small. If it is picked from a slow corner, the labor cost per pick grows with every foot traveled.
So the operational question is not just "where are the picks?"
The better question is: "where are picks forcing people to walk?"
The walk burden formula
SlotWise uses a simple burden calculation inside the heatmap view:
walk burden = picks x round-trip distance
That single multiplication changes the color story. Pick frequency colors by volume. Walk burden colors by labor exposure.
If a bay has 500 picks and each visit creates a 70-foot round trip, that bay is carrying 35,000 feet of walk burden. If another bay has 1,200 picks and each visit creates a 12-foot round trip, it carries 14,400 feet.
The higher-pick bay looks hotter in a frequency heatmap. The lower-pick, farther bay is the bigger labor problem.
A quick example
Imagine two SKUs:
| SKU | Picks | Round-trip distance | Walk burden |
|---|---|---|---|
| A | 800 | 8 ft | 6,400 ft |
| B | 200 | 80 ft | 16,000 ft |
SKU A has four times the picks. In a basic heatmap, it probably gets the deepest red.
SKU B creates two and a half times the walking. In a burden view, it is the one that deserves the first look.
That is the trap. Frequency makes the busy spots visible. Burden makes the costly spots visible.
What burden view reveals
When you switch from picks to walk burden, three patterns usually start showing up.
First, cold-zone bays stop hiding. Low and medium movers in poor locations can create steady travel waste without ever cracking the top-pick list.
Second, prime real estate looks different. A high-pick SKU near the start point may already be doing its job. Moving it again might save almost nothing.
Third, slotting conversations become easier. A supervisor can look at the map and say, "This red bay is not red because it is popular. It is red because every pick is too far away."
That distinction matters when you are trying to justify a reslotting pass. It moves the conversation from gut feel to feet walked.
The map should match the labor
Many slotting reviews begin with an export sorted by pick count. That is a reasonable starting point, but it misses the geometry of the building.
Warehouses are not spreadsheets. They have start points, parking spots, cross aisles, blocked routes, mezzanines, flow racks, reserve zones, and staging areas. Two SKUs with the same pick count can have completely different labor costs because they live in different parts of the layout.
That is why the SlotWise heatmap does not stop at coloring by frequency. The burden mode uses the layout distance and pick activity together, so the visual priority matches the work happening on the floor.
How to use this in your own data
Start with one layout and one recent pick dataset. You do not need a full WMS integration to learn something useful.
Upload the pick file, confirm the locations are matched, and open the heatmap. Look at the normal pick-frequency view first. Screenshot the top five red areas.
Then switch to burden mode and do the same thing.
If the two lists are identical, your pick frequency view is probably a good enough first pass. If they diverge, the burden list is where the labor story starts.
The practical next step is not to move everything. Start with the top three burden locations and ask a simple question for each one: "Is this SKU far away because it has to be, or because nobody has looked at it recently?"
The takeaway
A heatmap should not only show where picks happen. It should show where the building is charging you for them.
Pick frequency is still useful. It tells you what is active. But if you are trying to reduce walk time, labor cost, and picker fatigue, activity is not enough.
Color by burden when the question is labor.
Color by frequency when the question is volume.
Knowing the difference is where better slotting starts.