The Inventory Is Fine.
The Placement Is Not.
How fast a picker reaches what they need, and how much product fits in the space you are paying for. Most operations are quietly losing on both.
Inventory Strategy and Velocity Slotting
Two numbers tell you how healthy an operation really is, and neither one shows up on a dashboard. The first is how long it takes a picker to reach what the order needs. The second is how much product actually fits in the cubic footage you are paying rent on. Inventory can look correct in the aggregate while both of those quietly erode.
The symptoms are familiar to anyone who walks the floor. Fast movers buried in back corners. Pallet positions wasted to honeycombing — partial pallets holding full locations. Pick faces running dry mid-shift because replenishment triggers were set for a different volume. And a system that swears a bin is full when it is empty, stopping a shipment cold. None of it registers as a failure. It registers as the building being a little slower every quarter.
What the work actually is
The discipline that fixes it starts with classification. Every SKU gets ranked by how often it is picked and how much space it occupies — velocity and cube together, because a fast mover in a bulky package is a different problem than a fast mover in a small one. That ranking sorts the catalog into tiers. A items are the small share of SKUs driving the large share of picks, and they belong in the golden zone: waist to shoulder height, closest to pack and ship, no ladder and no reaching. B items sit adjacent, still accessible. C items move to higher and lower levels where a longer reach costs less because it happens less. D items — the slow and the dead — get consolidated, pushed to the back, or flagged for a conversation about whether they should be stocked at all.
Two things separate a real slotting program from a one-time exercise. Velocity is seasonal, so an A item in June is often a C item in November and the classification has to be re-run before peak rather than after it. And slotting only holds if replenishment holds — min and max logic tuned so pick faces never run dry, and cycle counting frequency set by tier so the fast movers get counted most. In food and beverage operations the constraint is tighter still, because code dates and temperature zones limit where product can go before velocity is even considered.
Done properly, travel time drops and picks per hour rise without adding people. Storage density improves enough that SKU growth fits inside the footprint you already have. And inventory integrity comes back, because the locations match what the system believes.
Placement is a flow problem as much as a storage one, which is where warehouse workflow optimization picks up.
What Holds Inventory Accuracy
Slotting decides how fast the building runs. Accuracy decides whether any of it can be trusted. Four things hold it, and none of them is the system.
1. Cycle Counting Cadence
The cadence that works is a full cycle count every quarter — every SKU, every location, four times a year — with the counting spread across the quarter rather than run as one push. That is heavier than the tiered ABC schedules most operations use, and it is why it works. Tiered counting assumes errors follow velocity. They follow traffic, and slow movers are where errors sit undetected longest.
The benefit most operations never account for is financial. Lenders and auditors relax the wall-to-wall physical inventory requirement when the discipline is demonstrable — a documented quarterly cycle with tracked and proven accuracy levels migrates most institutions to spot checks. It takes time to earn. In a building starting from a poor baseline, expect roughly a year of stabilizing counts and adjustments before the numbers hold well enough to show anyone.
Once auditors are comfortable, the quarterly audit stops being a crisis and becomes an event on a calendar. That is a shutdown avoided, a count crew not hired, and a season not interrupted, every year.
2. Counting the Location, Not Just the Quantity
A count that confirms the number and ignores the position hides the more common error. Product in the wrong bin reads as correct on a total-quantity count and stops a shipment cold when someone goes to pick it.
The errors come from the floor, not the system, and they scale with how many hands touch the product. An e-commerce facility running hundreds of pickers through the same zones — most seasonal, many temporary — generates location errors no software prevents. Someone scans every prompt correctly and pulls from the location beside the one the system sent them to. On a multi-unit pick, the scan gets overridden once and the rest come from wherever is closest. The quieter version: product falls out of a pick face, someone walking past puts it in the nearest open location the way a shopper abandons an item in the wrong grocery aisle, and no record follows it. Neither shows up as an exception. Both leave the count right and the location wrong.
Location accuracy and quantity accuracy are separate measures and should be tracked separately. An operation running high quantity accuracy and poor location accuracy will pass an audit and still miss orders.
3. Finding the Cause, Not Just the Variance
Adjusting the system to match the count closes the ticket and guarantees the error repeats. Every variance has a source: a receiving error, a pick from the wrong face, an unrecorded damage, a putaway to an unscanned location.
The count is a detection tool. The correction is a process change upstream of it. An operation that adjusts without investigating is running a very expensive way of keeping its books tidy.
4. Replenishment Discipline
Slotting only holds if pick faces stay stocked. Min and max levels have to be tuned to actual pick rates, and they drift as velocity shifts — the same seasonality that moves a June A item to a November C item moves the replenishment trigger with it.
A pick face running dry mid-shift is not a slotting failure. It is a replenishment failure that looks like one, and it sends a picker to a reserve location for product that should have been waiting at waist height. That trip is lost travel time the slotting program was designed to save, and it compounds — every dry face costs the same walk, every shift, until someone retunes the trigger.
Straight Answers
Q: How often should I cycle count?
A full cycle count every quarter — every SKU, every location, four times a year — with the counting spread across the quarter rather than run as one push. That is heavier than the tiered ABC schedules most operations use, and it is why it works. Slow movers are where errors sit undetected longest, and a D item holding a location the system believes is empty costs the same as an A item in the wrong bin.
Q: Can cycle counting replace a full physical inventory?
Often, though it has to be earned. Lenders and auditors relax the wall-to-wall requirement when the discipline is demonstrable — a documented quarterly cycle with tracked and proven accuracy levels migrates most institutions to spot checks. In a building starting from a poor baseline, expect roughly a year of stabilizing counts and adjustments before the numbers hold well enough to show anyone. Once auditors are comfortable, the quarterly audit becomes an event on a calendar rather than a crisis.
Q: What is ABC slotting and how do I set it up?
Rank every SKU by two things together: how often it is picked and how much space it occupies. Velocity alone is not enough, because a fast mover in a bulky package is a different problem than a fast mover in a small one. A items are the small share of SKUs driving the large share of picks and belong in the golden zone — waist to shoulder height, closest to pack and ship. B items sit adjacent. C items move to higher and lower levels where a longer reach costs less because it happens less. D items get consolidated, pushed back, or flagged for a conversation about whether to stock them at all.
Q: How often should slotting be re-run?
Before peak, not after. Velocity is seasonal — an A item in June is often a C item in November — and slotting to last season's ranking puts the wrong product in the golden zone during the weeks it matters most. Re-running the classification ahead of the season is the difference between a slotting program and a one-time exercise.
Q: Why does my system say a location is full when it is empty?
Because the count confirmed the quantity and ignored the position. Location accuracy and quantity accuracy are separate measures, and an operation can run high quantity accuracy with poor location accuracy — passing an audit while still stopping shipments. Product in the wrong bin reads as correct on a total-quantity count and fails the moment someone goes to pick it.
Q: Why do my pick faces run dry mid-shift?
That is a replenishment failure that looks like a slotting failure. Min and max levels have to be tuned to actual pick rates, and they drift as velocity shifts — the same seasonality that moves a June A item to a November C item moves the replenishment trigger with it. A picker sent to a reserve location for product that should have been waiting at waist height is losing travel time the slotting program was designed to save.