Plans, resources, company information, and legal documents.
Most operators staff receiving with their newest people. The data says they should be doing the opposite.
We pulled the error rates of every operation across about 240 Nautilus customers and ranked them by downstream cost. The most expensive operation, by a substantial margin, was not picking or counting or shipping. It was receiving.
This is counterintuitive enough that we want to walk through it, because if you accept the argument, it changes how you should be staffing your dock.
Why receiving errors compound
When an operator makes a mistake at receiving, the bad data is stamped into the system and travels with the product. A SKU received against the wrong product code will be counted as the wrong product, picked as the wrong product, and shipped as the wrong product, until someone notices. By the time someone does notice, the error has propagated through dozens or hundreds of subsequent operations.
Contrast this with a picking error. A picker grabs the wrong item, the customer flags it on receipt, a return comes back, the picker (or their manager) is told about the mistake. The feedback loop is hours to days. The downstream cost is contained to one shipment.
A receiving error has no immediate feedback loop. Receiving is invisible to customers. The first signal that something went wrong is usually a stockout (you thought you had 200 units, you really had 47) or a customer complaint (you shipped them a similar but wrong SKU). The signals arrive weeks later, and by then the receiving operator has done a thousand more receipts and has no memory of the bad one.
The numbers, from our dataset
Across our 240-warehouse sample, here's what we found, sorted by what we'd call "blast radius" (the average number of downstream operations affected by a single error):
Receiving errors: average blast radius of 47 downstream operations. The misallocated receipt produces wrong-count balances at putaway, mispick risk at the bin level, wrong shipments to customers, and incorrect inventory valuations in the accounting integration. About 8.2% of our customers' stockouts trace back to a receiving error that happened weeks earlier.
Picking errors: average blast radius of 1.2 operations. The wrong item gets shipped. The customer returns it. The system records the return and re-shelves the original. Done.
Counting errors at cycle count: average blast radius of about 3 operations. The cycle count records a wrong quantity, which gets corrected at the next count or at the next physical action. Self-correcting on a short timescale.
Shipping errors: average blast radius of about 1.5 operations. Similar to picking. The error gets noticed when the customer opens the box.
The asymmetry is large. A receiving operation is roughly 30 to 40 times more expensive when it goes wrong than a picking operation is. And receiving operators are often paid less than pickers, get less training, and rotate faster.
Why it's staffed wrong
We have spent enough time at warehouses to have a guess about how this happened. Receiving looks easy. The boxes show up, you scan them, you put them in their bins. The cognitive load looks low. So it gets handed to the newest people, who are by definition the most likely to make mistakes that the system will not catch.
Receiving is, in fact, harder than it looks. You have to disambiguate identical-looking products from different suppliers, deal with damaged or partial pallets, catch lot mislabels, notice when the count on the manifest doesn't match the count in the box, and decide what to do when something arrives that wasn't on the purchase order. None of this is automatable to the point where it doesn't need a thoughtful human.
What good receiving looks like
A few observations from customers who get receiving right. None of these are technological. They are staffing and culture.
The lead receiver is not new. We notice the best operations have a lead receiver who has been at the company for years and who actively trains the day-to-day team. This person is paid like a senior operator, because they are one.
Ambiguity gets escalated, not guessed. Good receivers stop the line and ask when something doesn't match. They don't try to figure out which SKU is "probably" right. The wrong answer is much more expensive than a 90-second delay.
Anomalies get photographed. Damaged pallets, partial cases, wrong SKUs, mismatched manifests: all get a photo attached to the receipt record. This sounds excessive until you're trying to charge back a supplier six weeks later for a shortage.
The first hour of a new receiver's shift is observed. This is the hour where errors cluster. The operations lead at one of our customers walks the dock for the first hour of every new receiver's first three days, and intervenes when patterns emerge. Their misallocated-receipt rate is the lowest in our dataset.
What we built for it
We have built a few things into Nautilus specifically to lower the cost of receiving errors. Multi-barcode disambiguation that asks instead of guesses (born out of the Mercantile Coffee incident we wrote about last month). A drift report that flags receiving events clustered in a new operator's first hour. Photo attachment on every receipt, one tap from the scan view. Lot-level traceability that lets a single bad receipt be unwound without rebuilding state from scratch.
None of these compensate for short-staffing the dock. The tools help the people who are there catch their own errors faster. They don't replace expertise.
The closing argument
If you do nothing else after reading this: walk to your dock tomorrow morning and watch your receivers for an hour. If they're the youngest, newest, lowest-paid people in your operation, that's a choice you've made, possibly without realizing it. The math says they should be among your most experienced.