What's the single biggest lever for cutting pick time?

Usually reducing walk distance, either by slotting fast-moving stock closer to dispatch or by sequencing pick lists in location order rather than SKU order.

Is batch picking always faster than picking one order at a time?

Only when orders overlap in location. If every order pulls from a completely different part of the warehouse, batching adds a sorting step without saving much walking.

Do I need software to run zone picking?

Not strictly, but without a system tracking which zone has completed its part, consolidation becomes a manual chase that eats back into the time saved.

Does pick path optimisation require rearranging the racking?

Not necessarily. Path and method changes work within the existing layout; they just change how it's worked, which is often the faster win before considering a physical reconfiguration.

Pick Path Optimisation, and Why Walking Dominates Pick Time

Walking is usually the single largest component of pick time, ahead of the actual pulling of stock off a shelf. Pick path design, and the zone, batch or wave method behind it, exists to cut that walking down.

Last updated 2026-08-23

Why walking dominates

A picker's day breaks roughly into travel, search, and the actual pick. In most operations, travel between locations takes up more of that time than any other single step, because the building is bigger than the order. A pick list generated in SKU order rather than location order can send a picker back and forth across the same aisle three times for one order, when a location-sequenced list would have covered it in one pass.

This is why where a SKU sits matters as much as how the route through it is planned. The best pick path software can't shorten the walk to a fast-moving item slotted at the far end of the building from dispatch. Where that slotting decision itself is increasingly informed by pattern-recognition software rather than a static periodic review is covered in how demand forecasting and slotting actually use machine learning.

Zone picking

Zone picking assigns each picker to a fixed area of the warehouse and has them pick only the parts of each order that fall within it, with the pieces consolidated afterward. It keeps individual walk distances short and lets pickers become genuinely fast within a small, familiar area, at the cost of needing a consolidation step to reassemble each order.

It suits sites with a stable layout and enough order volume to keep every zone busy. A site with narrow aisles and limited equipment access in some zones can also use zone assignment to keep specialised gear, like a VNA truck, working inside the area it's actually needed rather than crossing the whole building.

Batch and wave picking

Batch picking has one picker collect multiple orders in a single pass through the warehouse, sorting into individual orders at the end rather than walking the building once per order. It reduces total walking sharply when order lines overlap in location, at the cost of a sorting step and the risk of mis-sorting if it's done by hand rather than by system-directed tote.

Wave picking releases groups of orders to the floor at scheduled times, often tied to dispatch cut-offs or truck departures, rather than continuously. It's less about the walking route itself and more about matching picking effort to when orders actually need to leave, which matters more as dock and staging capacity becomes the tighter constraint than picking speed.

Choosing between them

None of these methods is universally better; they suit different order profiles. High order volume with a lot of overlap between orders favours batching. A wide spread of SKUs across a large footprint favours zoning. Tight dispatch windows favour waving, often layered on top of one of the other two rather than instead of it.

The method chosen also interacts with whether a WMS is directing the work. Zone and batch picking both get considerably easier to run accurately once a system is generating the sequenced lists and consolidating the sort, and the gains show up directly in overall labour productivity, not just in this one process.

Knowing if it's working

The simplest sign a pick path change is working is falling average pick time per line, tracked consistently rather than compared to a single good day. A less measurable but earlier sign is picker complaints about backtracking easing off, since that's usually noticed before it shows up cleanly in the numbers.

It's worth checking the change against a slow week and a busy week separately. A path that works well at normal volume can behave differently once extra temporary pickers join the floor, because they haven't built the same familiarity with the layout as permanent staff.

Whatever the path change achieves, it still has to be judged against a realistic target for the layout you actually have, not a number pulled from a different site — how layout sets the ceiling on a pick-rate target covers why the same effort produces different results in different buildings.

Common questions

What's the single biggest lever for cutting pick time?: Usually reducing walk distance, either by slotting fast-moving stock closer to dispatch or by sequencing pick lists in location order rather than SKU order.
Is batch picking always faster than picking one order at a time?: Only when orders overlap in location. If every order pulls from a completely different part of the warehouse, batching adds a sorting step without saving much walking.
Do I need software to run zone picking?: Not strictly, but without a system tracking which zone has completed its part, consolidation becomes a manual chase that eats back into the time saved.
Does pick path optimisation require rearranging the racking?: Not necessarily. Path and method changes work within the existing layout; they just change how it's worked, which is often the faster win before considering a physical reconfiguration.

Part of our guide to warehouse systems and processes.