How to Do Warehouse Slotting Optimization (Method + Worked Example)
A step-by-step method for optimising where every SKU sits in the pick face, worked through one example that cuts a pick path from 214 metres to 96. Covers velocity ranking, golden-zone placement, cube-per-order and travel-distance logic, how often to reslot, and how to keep placement keyed to real pick frequency inside the system you already run.
Warehouse slotting optimization is the method of deciding which SKU sits in which pick location, using your own order data, so pickers walk less, reach less and replenish less for the orders you actually receive. It works in a fixed order: collect the data, rank SKUs by how often they are picked, size each pick face, place the fastest movers in the most accessible locations, keep items ordered together close, then reslot on a schedule and measure the result.
The practical problem is that most pick faces are arranged by history rather than by demand. New lines go into whatever slot is empty, seasonal items keep prime positions after the season ends, and bulky fast movers sit in small locations that need refilling several times a day. This guide is the step-by-step method with hypothetical worked examples. If you want the broader definition first, read warehouse slotting; if you are comparing tools, see warehouse slotting software.

Every pick is a walk, a reach and a handling movement, and slotting decides how long each one takes. Illustrative photograph, not an OpsMavix project.
Image credit: EqualStock, Unsplash License. No edits.
Key Takeaways
- Rank SKUs by pick lines (visits), not by revenue or units sold, because visits drive walking.
- Size each pick face from cube and daily demand so fast movers do not trigger constant replenishment.
- Give the most accessible, nearest locations to the most frequently picked SKUs, in strict rank order.
- Use affinity to place items ordered together close, but never at the expense of velocity.
- Reslot little and often, and move the stock record in the same transaction as the stock.
- Measure travel, lines per hour and replenishment before and after, on a comparable order mix.
In this guide:
- 1. Collect the Slotting Data First
- 2. Rank SKUs by Pick Velocity Not Sales Value
- 3. Size Each Pick Face by Cube and Days of Cover
- 4. Place Fast Movers in the Golden Zone
- 5. Keep Items Ordered Together Close
- 6. Work Through a Full Reslot Example
- 7. Set a Reslotting Cadence and Move Stock Safely
- 8. Measure the Results Honestly
- Frequently Asked Questions
- How OpsMavix Can Help
1. Collect the Slotting Data First
The six fields you need per SKU
Before you move a carton, build one table with a row per SKU and these fields:
| Field | What it means | Why slotting needs it |
|---|---|---|
| Pick lines | Number of order lines that touched the SKU in the period | Each line is a visit, and visits drive travel |
| Units picked | Total units taken in the period | Sets daily demand on the pick face |
| Units per line | Units picked divided by pick lines | Shows whether picks are eaches, inners or cases |
| Unit cube and weight | Dimensions and weight of the picked unit or carton | Decides which location type physically fits |
| Affinity | Which other SKUs appear on the same orders | Supports placing related items together |
| Current location | Where the SKU lives today, with location type | Lets you plan and count the moves |
Choose a representative period
Use a window long enough to smooth out weekly noise but recent enough to reflect current demand. A window of around 8 to 13 weeks is a reasonable starting point; check it against the same period last year for seasonal lines. Exclude one-off events such as a single bulk clearance order, or the ranking will reward a SKU that is not normally busy.
Check location accuracy before you start
If the location file is wrong, every calculation downstream is wrong too. If location naming is inconsistent, fix it first using a scheme like the one in warehouse bin locations.
2. Rank SKUs by Pick Velocity Not Sales Value
Why lines beat units and revenue
Ranking by revenue or units sold does not describe the picker’s day. A low-value consumable picked on half your orders creates far more walking than an expensive item picked twice a month. Rank by pick lines, highest first, then cut the list into velocity bands. The cut-line logic is the same as ABC analysis for inventory, but the measure is visits rather than usage value.
Worked example: ranking ten SKUs (hypothetical)
A hypothetical wholesaler takes a sample of ten SKUs over a 10-week window of 50 picking days. Total pick lines for the sample are 2,000.
| SKU | Pick lines | Lines per day | Share of lines | Cumulative share | Velocity band |
|---|---|---|---|---|---|
| SKU-01 | 600 | 12.0 | 30.0% | 30.0% | A |
| SKU-02 | 400 | 8.0 | 20.0% | 50.0% | A |
| SKU-03 | 300 | 6.0 | 15.0% | 65.0% | A |
| SKU-04 | 200 | 4.0 | 10.0% | 75.0% | A |
| SKU-05 | 150 | 3.0 | 7.5% | 82.5% | B |
| SKU-06 | 120 | 2.4 | 6.0% | 88.5% | B |
| SKU-07 | 100 | 2.0 | 5.0% | 93.5% | B |
| SKU-08 | 70 | 1.4 | 3.5% | 97.0% | C |
| SKU-09 | 40 | 0.8 | 2.0% | 99.0% | C |
| SKU-10 | 20 | 0.4 | 1.0% | 100.0% | C |
Here the A band is cut at 75% of lines and the B band at about 93.5%. In a full catalogue the A band is usually a much smaller share of SKUs than in a ten-item sample; choose cut lines that match the number of prime locations you actually have. Suppose SKU-09 sells 3,500 units in the period because customers buy it by the case. By units it would look like a top seller, yet it is visited fewer than once a day, so it does not need a prime slot.
Rank within each zone
Rank separately for areas that do not compete for the same space, such as ambient and chilled, or small parts and pallet picks. A fast mover in the small-parts zone should not be compared with pallet lines that could never fit there.
3. Size Each Pick Face by Cube and Days of Cover
The formula
Velocity decides priority; cube decides feasibility. For each fast mover, work out how many units the location can physically hold and how long that lasts:
Days of cover = units the location holds ÷ average units picked per day
Aim for at least one full peak day of cover on A-movers, so replenishment can happen on a planned schedule rather than interrupting picking. Check that the replenishment quantity also fits: a location that holds less than one inbound case forces split cases or overflow.
Worked example: two pick faces (hypothetical)
A standard shelf location is 100 cm wide, 60 cm deep and 40 cm high.
SKU-01 ships in cartons of 12 units measuring 40 × 30 × 25 cm. Across the shelf, 2 cartons fit in the width (100 ÷ 40, rounded down), 2 in the depth (60 ÷ 30) and 1 in the height (40 ÷ 25, rounded down), so the shelf holds 4 cartons, or 48 units. SKU-01 averages 26 units a day with a peak of 40, which gives 1.8 days of cover on an average day and 1.2 days at peak. The standard shelf works.
SKU-02 ships in cartons of 6 units measuring 60 × 40 × 40 cm. Only 1 carton fits the same shelf, which holds 6 units. At an average of 30 units a day that is 0.2 days of cover, or about 5 replenishments a day. Moved to a ground-level pallet position of 120 × 100 cm stacked 120 cm high, it holds 2 × 2 cartons per layer and 3 layers, so 12 cartons or 72 units: 2.4 days of cover.
| SKU | Location type | Units held | Units per day | Days of cover | Verdict |
|---|---|---|---|---|---|
| SKU-01 | Standard shelf | 48 | 26 | 1.8 | Fits |
| SKU-02 | Standard shelf | 6 | 30 | 0.2 | Too small |
| SKU-02 | Pallet position | 72 | 30 | 2.4 | Fits |
The reverse also applies: a small fast mover should not occupy a full shelf when a bin would do, because that frontage could hold several A-movers.
4. Place Fast Movers in the Golden Zone
Two axes: height and distance
The golden zone is the band of a bay that a picker reaches without bending low or stretching high, roughly between waist and shoulder height. UK guidance supports this: the HSE manual handling risk filter reduces its guideline weights when handling is done with arms extended or at high or low levels, because that is where injuries are most likely. Placement therefore runs on two axes:
| Velocity band | Height in the bay | Distance from despatch |
|---|---|---|
| A | Waist to shoulder | Nearest bays and the start of the pick path |
| B | Just above or below the golden zone | Middle bays |
| C | Top shelves and floor level, where safe | Far aisles and ends |
Heavy items deserve special care. A heavy A-mover is best at roughly waist height, and heavy items should not go on high shelves regardless of velocity.
Assign in strict rank order
Count the locations that are both in the golden zone and near despatch. Work down the ranked list from section 2 and give the best remaining location to the next SKU whose pick face size fits. Do not reopen the ranking for opinions about which products are important; the data already made that decision.
One guardrail: do not pack all A-movers into one or two bays, or pickers will queue there at peak. Spread them across the near end of several aisles.
Worked example: one swap (hypothetical)
SKU-10 (0.4 lines a day) sits in a golden-zone slot 5 m from the despatch bench. SKU-01 (12 lines a day) sits 35 m away, on the floor level. Treat each visit as a round trip from the bench to keep the arithmetic simple; batched routes will save less per line but follow the same logic. The extra distance is 30 m each way, or 60 m per visit.
- Moving SKU-01 near saves 12 × 60 m = 720 m a day.
- Moving SKU-10 far adds 0.4 × 60 m = 24 m a day.
- Net saving: 696 m a day, or 174 km over 250 working days.
It also removes 12 floor-level bends a day on the busiest line, while SKU-10’s bends happen less than once a day.
5. Keep Items Ordered Together Close
Measure affinity with simple counts
Affinity is the second-order gain. For each pair of SKUs, count the orders containing both. Then compare that with what chance would predict, so that two very popular SKUs do not look related just because both are everywhere.
Worked example: affinity and lift (hypothetical)
Across 1,000 orders, SKU-03 appears on 180, SKU-07 on 90, and both on 72.
| Measure | Calculation | Result |
|---|---|---|
| Share of SKU-07 orders that include SKU-03 | 72 ÷ 90 | 80% |
| Share of SKU-03 orders that include SKU-07 | 72 ÷ 180 | 40% |
| Lift | (72 ÷ 1,000) ÷ ((180 ÷ 1,000) × (90 ÷ 1,000)) | 4.4 |
A lift of 4.4 means the pair appears together about four times more often than it would if orders were random. That makes SKU-07, a B-mover, a good candidate for the best B location next to SKU-03.

Clearly addressed, empty locations make planned moves much easier to execute and check. Illustrative photograph, not an OpsMavix project.
Image credit: lim woojung, Unsplash License. No edits.
Affinity is a tie-breaker, not an override
Never demote an A-mover from a prime slot to sit next to a C-mover it sometimes ships with. Use affinity among SKUs of similar velocity, and for kits or standing trade baskets that repeat every week. For wholesale operations, repeat customer baskets are often the clearest affinity signal in the order history.
6. Work Through a Full Reslot Example
The starting position (hypothetical)
A hypothetical distributor has 200 pick locations across four aisles and one despatch bench. It picks about 400 lines a day. Ranking shows 30 A-SKUs carrying 70% of lines, or 280 lines a day. There are 40 golden-zone locations near despatch, but only 12 of the 30 A-SKUs are in them, carrying an assumed 112 of the 280 A lines a day.
The move plan
| Step | Calculation | Result |
|---|---|---|
| A-SKUs to move into prime slots | 30 minus 12 | 18 |
| Moves per swap, using a spare location | Occupant out, A-SKU in, occupant to its new slot | 3 |
| Total moves | 18 × 3 | 54 |
| Time per move, including system update and check count | Assumed | 10 minutes |
| Total move labour | 54 × 10 minutes | 540 minutes (9 hours) |
The expected travel change
To compare before and after without modelling every route, use a weighted distance index: lines per day multiplied by the one-way distance from despatch to the location.
| Line group | Before | After |
|---|---|---|
| A lines in near slots (8 m) | 112 lines × 8 m = 896 | 280 lines × 8 m = 2,240 |
| A lines in far slots (30 m) | 168 lines × 30 m = 5,040 | 0 |
| B and C lines | 120 lines × 20 m = 2,400 | 120 lines × 24 m = 2,880 |
| Total index | 8,336 | 5,120 |
| Index per line | 20.8 m | 12.8 m |
The index falls by 3,216, about 39%. B and C lines walk a little further because they gave up near slots, which is the intended trade. The index is a planning estimate, not a measured walk; confirm it with the measurement in section 8.
One order path, before and after
Take the most common order type, a 12-line trade order. Before the reslot, its lines are scattered across all four aisles and the picker doubles back to the far aisle twice. Measured with a trundle wheel, the hypothetical route is 214 m. After the reslot, nine of the twelve lines are A-SKUs in the two nearest aisles at reach height, and three tail lines need one detour. The same route measures 96 m: 118 m shorter, a 55% reduction for that order type.
A rare 30-line order reaching into the tail may walk further than before. That is acceptable, because slotting optimises against your actual demand mix rather than every possible order.
7. Set a Reslotting Cadence and Move Stock Safely
Three layers of reslotting
Demand moves, so a layout that is right today drifts out of date. Treat reslotting as a routine:
| Layer | Trigger | Scope |
|---|---|---|
| Continuous correction | A SKU changes band or a prime slot holds a dead line | A handful of moves each week |
| Seasonal reslot | Before a known peak or range change | SKUs whose band has changed since the last pass |
| Full reslot | Layout change, major range overhaul, or drift the small passes cannot fix | Ground-up re-ranking and reassignment |
Relying only on an annual full reslot means paying for months of extra walking first. Frequent small corrections plus a pre-peak pass usually disrupt less, provided re-ranking is quick.
Practical move checklist
- Freeze put-away into affected locations before the move window.
- Move during off-peak hours, one SKU at a time.
- Update the location record as each SKU lands, not in a batch afterwards.
- Count the new location immediately, using your inventory cycle count routine.
- Relabel the location and clear the old label.
- Release the SKU for picking only after the count agrees.
Guide new SKUs at put-away
Layouts decay when new lines go wherever there is a gap. Give each new SKU an expected band from similar items, direct it to a suitable location and review it after a few weeks of real picks.
8. Measure the Results Honestly
Choose a small set of measures
| Measure | How to capture it | What it shows |
|---|---|---|
| Lines per picking hour | Pick lines ÷ picker hours | Overall productivity |
| Travel per order type | Trundle wheel or system route length | Direct effect of slotting |
| Replenishments per day | Count of replenishment tasks | Whether pick faces are sized correctly |
| Short picks and wrong picks | Exceptions recorded at pick and pack | Location accuracy after moves |
| Low and high reaches | Observation of A-lines outside the golden zone | Ergonomic placement |
Worked example: comparing two fortnights (hypothetical)
Before the reslot, a team picks 400 lines in 6.4 picker hours a day: 62.5 lines an hour. Two weeks after it, the same order mix takes 5.5 hours: about 72.7 lines an hour. Before crediting slotting, check that order volume, line count per order, staffing and pick method were comparable in both periods.
Know when slotting is not the bottleneck
Slotting shortens the walk between picks. If pickers mostly wait for replenishment, search for misplaced stock or use a pick method that suits the profile poorly, fix that first. Observe walking time as a share of the pick cycle: if walking dominates, slotting is a strong lever.
Frequently Asked Questions
What data do I need for warehouse slotting optimization?
Per SKU: pick lines, units picked, units per line, unit cube and weight, affinity with other SKUs, and current location. All of it normally exists in order history and item master data; the work is making it quick to refresh.
Should I rank SKUs by sales value or pick frequency?
By pick frequency, counted as order lines. Walking is driven by how often a picker visits a location, not by the value or volume of what is picked.
What is the golden zone?
The band of a bay between roughly waist and shoulder height, reachable without bending low or stretching high. The most frequently picked SKUs belong there, as close to despatch as their size allows.
How big should a pick face be?
Big enough to hold at least one peak day of demand for an A-mover and at least one full replenishment quantity. Use days of cover, units held divided by units picked per day, to check each location.
How often should I reslot?
Make small corrections continuously, run a seasonal pass before known peaks and keep full reslots for layout or range changes. The right frequency depends on how fast your demand shifts.
Do I need dedicated slotting software?
Not always. Many operations can run the ranking, sizing and drift checks inside the system that already holds orders and stock. Dedicated tools can suit high volumes and complex constraints, which our separate guide to warehouse slotting software covers.
Can OpsMavix build a slotting tool for our warehouse?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can turn your order and location history into a live slotting view: SKUs ranked by pick lines, pick faces checked for days of cover, drift flagged as a worklist and location updates recorded with each move.
That may sit inside an inventory automation system, connect to a wholesale order management system, or extend the warehouse tools you already use.
Contact OpsMavix with one recent order type, the pick and location records behind it and the step that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.