Picks per hour: your site, your standard

A site manager in the Midlands told me a few years ago that his 3PL contract had a picks-per-hour target written in at 65. His team were averaging 42. Six months of arguments followed with the client, none of which addressed the fact that the site was a narrow-aisle facility picking mixed-case ambient and chilled, on a paper system, with a product range running from a 200g sachet to a 25kg sack of clay granules. The benchmark came from a food-service DC somewhere in the south. It had no bearing on the site in question.

This happens constantly. Someone reads that “industry standard” is 80 picks per hour, or 120, or 200, and suddenly that number is in a contract or a performance review with no understanding of where it came from or what conditions it assumed.

Why benchmarks do not travel

Picks per hour is a ratio. The numerator is the number of picks completed; the denominator is the time taken. What the ratio hides is everything that sits underneath it: pick density, travel distance, unit weight, pick method, system support, SKU count, and the physical layout of the building.

A voice-directed picker in a well-slotted ambient warehouse with a narrow product range, working a single-pick trolley on a fixed route, will comfortably hit numbers that would be impossible for a manual-pick team working batch orders across three temperature zones with a 4,000-SKU range and a printed pick list. Both are described as pickers. The comparison is meaningless.

Benchmarks also tend to reflect best-performing sites, or averages across operations that have already invested in optimisation. If you are benchmarking against those numbers before you have done that work, you are comparing a starting position against someone else’s finished state.

What actually drives the number on your site

Before you set any standard, you need to understand what is genuinely controllable and what is fixed. Some things you cannot change quickly: the building shape, the rack configuration, the system you are on, the customer order profile. These set a ceiling on what is achievable.

Within that ceiling, there are variables that shift performance significantly. Slotting is the most consistent one. If your fastest-moving SKUs are at the far end of a long aisle, you are building travel time into every pick. That is not a picker problem. It is a slotting problem, and the labour standard should reflect current conditions until you fix it.

Pick method matters too. Batch picking, zone picking, single-order picking, and multi-pick trolleys all produce different throughput at the same level of effort. The standard you set needs to match the method your team are actually using.

Building your own baseline

The right way to start is to time-study your own operation under normal conditions. Not during a peak, and not on a quiet day. Take a representative week, pull your pick transaction data against clocked hours, and calculate what your team actually achieved per hour, by pick method and by zone if you have them.

That gives you a descriptive average. It is not the standard yet. The next step is to separate the losses from the baseline: time lost to system delays, to stock shortages, to unclear locations, to picking errors and corrections. Strip those out and you have a picture of what the team can do when the operation is running cleanly.

That cleaned number, perhaps with a modest improvement factor applied if the losses are addressable in the short term, becomes your working standard. It is yours. It reflects your building, your product mix, and your current system. It will not look like someone else’s benchmark, and it should not.

Setting the standard fairly

A fair standard is one a reasonably experienced picker can hit consistently without cutting corners or rushing to the point of errors. It should not require exceptional effort on every shift. If it does, it is not a standard; it is a target that creates pressure without creating improvement.

Once you have it, the standard becomes useful for scheduling, for spotting when something in the operation has changed, and for having honest conversations about performance. If a picker is consistently below standard, the first question is whether the operation is creating the conditions for success, not whether the individual needs performance-managing.

Review the standard at least once a year, or whenever the pick method or product range changes significantly. A standard set two years ago may no longer reflect the operation you are actually running.

Putting the number to work

A picks-per-hour standard is only as useful as the other operational data around it. If you are tracking it in isolation, you will draw the wrong conclusions. Pair it with accuracy rates, with travel time analysis if you have it, and with a clear picture of where time is actually going on the floor.

If you have not already mapped where productive time disappears, the losses calculator at losses.cadencestandard.com will give you a working framework. And if your site is earlier in the journey, running through the diagnostics before setting any labour standard will save you from building on a foundation you do not fully understand yet.

A number you derived yourself, from your own operation, with your own losses stripped out, is worth ten benchmarks from a trade association report. It will not impress anyone at a conference. It will, however, help you run your site.