# Warehouse incentive pay and piece rates, without the disputes

> Warehouse incentive pay people can trust. Why hourly pay caps output and how piece rates work with per-task standards, scan data and a balance workers see.

Page: https://opsalute.ai/en/blog/piece-rate-pay
Русская версия: https://opsalute.ai/llms/ru/blog/piece-rate-pay.md
Published: 2026-08-25 · Hrusty

The night shift is wrapping up at a warehouse with no incentive pay. Two pickers hand in their scanners. One picked almost twice as many lines as the other.

Their pay stubs will show the same number: eleven hours at the same rate.

The faster picker notices. A couple of weeks later she has either slowed down to the floor average or moved to the warehouse down the road that pays for output.

The slower picker changes nothing. There is no reason to.

That is how hourly pay works. It pays people for being on shift. It does not pay them for what they get done.

## Why hourly pay caps output

On an hourly rate, the slowest people set the pace. A strong worker has no reason to push: the money is the same and the day is more tiring.

The manager sees the plan slipping and adds headcount. Labor cost goes up while output per person stays flat.

Economists have studied this for a long time. Edward Lazear looked at Safelite, a US auto glass company that moved its installers from hourly wages to piece rates. [Output per worker rose by 44%](https://www.aeaweb.org/articles?id=10.1257/aer.90.5.1346).

Part of the gain came from people working faster. The rest came from the company attracting and keeping stronger installers.

Fitting windshields is not warehouse work, but the mechanics carry over. Pay for results and people do more, and the best ones stay.

## Why incentive programs get dropped after a few months

Plenty of warehouses have tried piece rates and gone back to hourly pay. The cause is rarely the people or the rates. It is the disputes.

> I picked more yesterday, so why did I get paid less?

Supervisors hear this on every payday. Output is pulled together in a spreadsheet once a week, from three different sources, with half the fixes typed in by hand.

The worker cannot check the number and the supervisor cannot explain it. A month in, nobody trusts the system, and going back to an hourly rate looks easier.

For incentive pay to stick, you need four things:

- fair standards;
- data nobody has to retype;
- a number workers can see for themselves;
- a rule that nothing changes after the fact without approval.

## Set labor standards per task, not per building

One rate for the whole warehouse does not work. Receiving pallets, putaway, each picking, packing and bulky picking all run at different speeds. Pay a flat amount per unit and everyone will fight for small items, leaving the heavy work for the end of the shift.

So each task gets its own standard: how many units per hour a trained worker handles at a normal pace. In the industry these are often called engineered labor standards.

Each standard gets a rate per unit. Measure standards on real shifts rather than borrowing them from a gut feeling or another company's handbook.

A few rules that save months of arguments:

- Announce standards in advance and explain how you set them.
- Do not raise the standard every time people beat it. They will quickly learn not to beat it.
- Give new starters a separate standard for their first shifts. They do not know the locations yet, and a full target will simply push them out.
- Factor in quality. Mispicks and wrong items should reduce pay, or people will buy speed with errors.

Check local rules on overtime too, because piece rates do not cancel it. In the US, for example, workers covered by the federal Fair Labor Standards Act are owed overtime past 40 hours a week, calculated from their average hourly earnings, piece rate pay included.

## Take the data from scans, not from memory

In a warehouse almost every action already leaves a trace. A worker scans a location and an item on a handheld scanner, and the warehouse management system (WMS) records who did what, where and when.

That record is the output. Nobody has to recall it, reconcile it or copy it from a paper sheet.

Scans have a limit. A scan shows that the work was done. It does not prove how many hours the person was on shift.

Hours come from a separate source: clock-ins and clock-outs or the access control system. Output is calculated from scans and time from clock events. You need both for a fair picture.

Watch for anomalies as well. Output at 240% of standard might be a record, or it might be someone else's login on the scanner.

The same person at two sites on the same date is definitely an error. Records like these should go to review before payout, not after.

## A balance workers can see

Most piece rate disputes are about things the worker never saw. They find out what they earned from a pay stub three weeks later and no longer remember what they did that Tuesday.

It works better to show the balance during the shift: tasks completed, percent of standard, earnings for today and for the period. A simple phone screen or a chat message is enough. When the number is visible right away, the question about low pay comes up the same day and is easy to answer.

Visibility helps in the other direction too. Workers see which tasks pay more and ask to be moved there. Supervisors find it easier to staff the unpopular areas.

## Adjustments only with approval

Manual fixes will always happen: a scanner breaks, someone gets moved to another area, scans fail to sync. The fixes are fine. The trouble is that nobody can see them, which makes them one of the common [frontline payroll leaks](https://opsalute.ai/en/blog/frontline-payroll-leaks).

A supervisor can add hours for friends, and nobody notices until the reconciliation.

The rule is simple. Every adjustment to output or hours carries a reason, an author and an approver.

Everything is kept in the change history. Blank or repeated reasons are a signal to look at that area.

## How to move to piece rate pay

You do not need to switch the whole warehouse at once. A workable order:

1. Pick one task in one area where output is easy to count from scans. Usually that is picking or packing.
2. Measure the standard over several shifts and agree on the rate.
3. For two or three weeks, calculate incentive pay alongside current pay and show people what they would have earned.
4. Work through the questions, adjust the standards, and only then move the area to the new pay.
5. Add the next task once the first one has stopped causing disputes.

Running both calculations side by side removes the biggest fear, that the new system pays less. People see their numbers early and come to the switch with their questions already answered.

## Where Hrusty fits

Hrusty calculates piece rate pay from your WMS scans and checks it against actual hours. Anomalies such as a double shift or output far above standard go to the supervisor for review, timesheet adjustments go through approval, and payout gets a ready register. More than 2,500 people work in Hrusty today.

The product draws on our team's experience: before Hrusty, we built a [frontline workforce system](https://opsalute.ai/en/cases/hrms) at Yandex Market, for a fulfillment center running 800 worker shifts a day. You can open a live shift in Hrusty on the [product page](https://opsalute.ai/en/hrusty) with no sign-up.

## Sources

- [Edward P. Lazear. Performance Pay and Productivity. American Economic Review, 2000](https://www.aeaweb.org/articles?id=10.1257/aer.90.5.1346)
- [US Department of Labor. Fact Sheet 23, Overtime Pay Requirements of the FLSA](https://www.dol.gov/agencies/whd/fact-sheets/23-flsa-overtime-pay)