Goods Receipt Isn't a Side Show — It's Your Most Expensive Bottleneck

The symptom

Ask a manufacturer where the bottleneck sits and you'll hear about machines, about assembly, about work preparation. Nobody names goods receipt. It appears in no presentation, rarely has a metric of its own, and is usually run by two people who also handle dispatch.

In those same businesses I hear sentences like: "But that material arrived last week." It did. It's in the yard, on a pallet, physically present and systemically non-existent. Between "delivered" and "available" lies a span of time nobody measures, because it falls between two areas of responsibility.

The mechanism

Goods receipt isn't a storage location. It's a translation step: physical goods become a quantity that accounting and planning can actually use. Four things have to happen — accept, check against the purchase order, release on quality, book in. Only the last of these makes the material visible to planning.

In practice those four steps almost never run consecutively. Acceptance happens immediately, because the driver is waiting. The check happens when someone has time. Quality release happens when the test equipment is free and the QA colleague isn't standing out on the shop floor. The booking happens at the end of the day, sometimes the end of the week, in a batch.

From this follows the actual damage: planning sees stock at zero and either re-orders or pushes out a production order — while the material stands on a pallet twenty metres away. This isn't sloppiness. It's a visibility problem, and it multiplies, because every downstream decision is built on a stock figure that isn't true.

There's a second effect I find nearly everywhere: goods receipt works in waves. Six deliveries arrive together in the morning, none in the afternoon. Two people cannot process six deliveries in parallel, so a queue forms — and nobody sets the order of that queue by urgency. It gets set by whatever is on top. The urgently awaited component happens to be processed fourth.

The cost

An anonymised example, altered in detail, real in pattern. A manufacturer of drive components, around 140 employees, had a well-known problem: too many short-notice reschedules in production. The assumed cause was unreliable supplier performance.

What we measured said something else. The suppliers were largely on time. Between arrival at the gate and the availability booking in the system, however, the average was 2.7 working days, and up to five in peak weeks. Production was therefore systematically planning against stock that was physically already there.

The downstream cost was easy enough to pin down: 43 short-notice reschedules in the quarter examined, of which — reconstructing case by case — close to half were triggered purely by delayed visibility. On top of that, expedited orders for material that was already in the building: roughly €18,000 in additional cost for the quarter, before counting the changeover time on the rescheduled orders. The business was on the point of qualifying a second supplier to solve a problem its suppliers weren't causing.

The fix

Nothing meaningful was invested. Three things changed.

First, booking was decoupled from checking. Goods are booked immediately on acceptance as "in house, blocked" — visible to planning, though not yet released. That alone removed the single largest source of planning uncertainty.

Second, the queue was given an order. Deliveries that a scheduled production order is waiting on get checked first, flagged by a marker that planning already sets at the point of ordering. Not a system — a rule.

Third, arrivals were spread out. Fixed delivery windows were agreed with the five largest suppliers. The waves largely disappeared, and with them the queue.

The span between gate and visibility fell from 2.7 days to under four hours. Short-notice reschedules halved in the following quarter. The second supplier was never qualified.

The underlying pattern travels: a process step nobody regards as a process is a step nobody measures — and unmeasured steps get systematically longer. That's exactly where a process analysis starts: mapping one core process end to end with real timestamps, instead of following the loudest assumptions. Fixed scope, fixed duration, fixed price.

The next step

One question you can answer this week without a project: how long does it take, on average, from unloading to the availability booking? If nobody knows the number, that's already the answer.