Why order confirmation in wholesale takes four days

The symptom

A regular customer emails their order first thing Monday morning: 14 line items, a PDF exported from their own system, plus two lines typed into the body of the message because one part number has changed. They expect an order confirmation. What they get arrives Thursday afternoon.

In between, nobody was idle. The order landed in the shared orders@ mailbox, got read at some point, was forwarded to the right person in inside sales, went onto a to-do list, was keyed into the ERP the next day, triggered a query to the warehouse on two lines, and was finally confirmed. Four days for a task that contains less than ten minutes of real work.

If you run technical wholesale, a building-materials business, or C-parts distribution, you know this pattern. And you also know it is never about the individual order. It is the rule, not the exception.

The mechanism

On its way from the customer's email to a confirmation, the order crosses at least three handoffs — points where information changes systems and a person has to re-enter it by hand.

The first sits at the inbox. The order arrives as an email, often with a PDF attached, sometimes as a photo of a filled-in form. A shared mailbox is not a queue with clear ownership; it is a pile. Whoever looks first decides on the spot whether to handle it or pass it along. An order that belongs to no one in particular waits.

The second break is manual entry into the ERP. The customer's part numbers are not your part numbers. Someone maps them in their head or against a side list. Any line that is not immediately unambiguous spawns a query — and queries go back out by email, straight back into the pile.

The third break is the availability check. If stock in the ERP is not reliably maintained, inside sales phones the warehouse or walks over. That query is synchronous: it only works when both sides happen to have a moment. When they don't, the order sits until tomorrow.

Each break on its own costs only minutes. But they are not wired in series — they are separated by idle time. It is not the processing that takes four days; it is the waiting between steps. That is the decisive point: you are optimising the wrong variable if you try to make your people type faster.

The cost

Let's work it through calmly. A mid-sized wholesaler processes 120 incoming orders a day. Assume each order generates, on average, one query — sometimes about a part number, sometimes about availability — that ties up five minutes of work on each side, so ten minutes in total.

120 orders × 10 minutes = 1,200 minutes = 20 hours of pure query handling every day. At a fully loaded hourly rate of 45 euros, that is 900 euros a day, roughly 198,000 euros a year — spent entirely on queries that would never arise if the data were handed over cleanly in the first place.

And that is only the internal cost. The four-day lead time costs more on top, just less visibly. A competitor who confirms the same day wins the business when stock is tight. Customers who have to chase three times drift away — quietly, without ever complaining. Nobody can put an exact figure on that part, but it is real, and it is usually larger than the 198,000 euros.

The fix

The lever is not the speed of your people; it is the three handoffs. In this order:

First, turn the shared mailbox into a real queue. Every incoming order gets an owner and a status immediately. Whether through a ticketing tool, a rule in the mail client, or straight into the ERP — what matters is that no order sits there ownerless. That step alone often halves the idle time.

Second, automate the part-number translation. A maintained cross-reference between the customer's part numbers and yours removes the most common query entirely. For customers who order regularly, a structured order format or a lightweight EDI connection is worth adding on top, cutting out the manual entry step altogether.

Third, make stock trustworthy so the synchronous warehouse query disappears. When inside sales can trust the number in the ERP, the phone call goes away. That is less a software problem than a discipline one: book goods receipts and stock transfers promptly.

The order matters. Automate the data entry first while leaving the mailbox chaos in place, and you have only moved the problem. This exact sorting — which break costs how much, and what to tackle first — is the heart of a process analysis: measure where the idle time actually accumulates, then close one break after another, on purpose.

The next step

When your order confirmations routinely take days instead of minutes, the cause is almost never where people assume it is — and a single morning spent tracing one real order end to end tells you more than any gut feeling ever will.