Goods Receipt Is Your Most Expensive Bottleneck, Even If It Looks Like a Side Show

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 illustrative example with invented figures. Take a manufacturer of drive components, around 140 employees, with a well-known problem: too many short-notice reschedules in production. It puts them down to unreliable suppliers.

The measurement says something else. The suppliers are largely on time. Between arrival at the gate and the availability booking in the system, however, the example has an average of 2.7 working days, and up to five in peak weeks. Production is therefore systematically planning against stock that is physically already there.

The downstream cost can be put in numbers: 43 short-notice reschedules in one quarter, close to half of them triggered purely by delayed visibility. On top of that come expedited orders for material that is already in the building. The example puts those at roughly €18,000 in additional cost for the quarter, before counting the changeover time on the rescheduled orders. A business in that position can easily end up qualifying a second supplier to solve a problem its suppliers aren't causing.

The fix

None of this needs a meaningful investment. Three things change.

First, booking is decoupled from checking. Goods are booked immediately on acceptance as "in house, blocked". Planning can see them, though they are not yet released. That alone removes the single largest source of planning uncertainty. The checks that follow that first booking, and who owns each one, are set out in our receiving checklist from delivery note to blocked stock.

Second, the queue gets an order. Deliveries that a scheduled production order is waiting on get checked first. Planning already flags them with a marker when it places the order, so the new order in the queue is an agreed rule and needs no new software.

Third, arrivals are spread out. The business agrees fixed delivery windows with the five largest suppliers. The waves largely disappear, and with them the queue.

The example assumes that the span between gate and visibility then falls from 2.7 days to under four hours and that short-notice reschedules halve in the following quarter. The business then has no need for the second supplier.

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.