Why do wholesale orders always seem to come in late at night?

Kitchens write their order once service ends and the walk-in has been checked, which for most restaurants is between nine at night and midnight rather than during office hours. The order is not late by the kitchen's clock - it is only late by a wholesaler's.

Should I set a cutoff time for orders?

A cutoff does not change when a kitchen is free to write its order - it only decides what happens to the ones that miss it. In practice it either loses those orders to a wholesaler still taking them late or pushes kitchens to guess and send earlier, which is worse than sending late.

How much does a late order actually cost a wholesale business?

Mostly in compressed time rather than lost money on any single order: reading, checking stock and pricing several orders in the hours before a market run leaves takes real minutes that would otherwise go into buying well, and a buyer still confirming quantities at four in the morning has already lost the best of the market.

Can software fix late ordering on its own?

It can remove the wait between an order arriving and it being read, priced and matched to stock, so the work happens as the message lands rather than in a rush before the yard opens. It cannot change when a kitchen is free to send the order in the first place.

Blogs

Why your wholesale orders arrive at 10pm and what it costs you

20 Jul 20264 min read

Wholesale orders arrive late because kitchens can only write them once service ends, often nine, ten or eleven at night, not because chefs are careless. The cost lands on the wholesaler: buying, pricing and route planning get compressed into the fewest, worst hours before the market run leaves, which is when there is the least time to do them well.

The kitchen is not being difficult

A chef's day does not have a gap for admin until the pass is clear, the last table has gone, and someone has counted what is left in the walk-in. For most kitchens that moment lands somewhere between nine and midnight. The order gets written then, on whatever is nearest - a WhatsApp voice note, a photo of a scrawled list, a text sent from the back step before the chef goes home. It is not lateness in the way a missed appointment is lateness. It is the earliest the order could actually have been sent.

A wholesaler who expects orders by five or six in the evening is expecting something that only works for kitchens that finish lunch service and have a quiet afternoon - a minority of the book, not the whole of it. Everyone else sends when they send, and Friday is the worst of it: the busiest service of the week produces the order for the busiest delivery day, written by the most tired person in the building.

What the compressed window actually costs

A market run has a shape to it. The best of the fish and the best of the salad crop goes early - the buyer who is trading by five gets first pick, and the buyer who is still confirming quantities on the phone at half four has already lost it. Every order that lands after the buyer would otherwise be asleep either gets read and priced in a rush before the yard opens, or gets folded into the run half-guessed and corrected the next day.

The arithmetic is plain enough. Say ten of thirty kitchens send after nine at night, and each one takes eight minutes to read properly, check against what is in stock, and price against that customer's own arrangement - that is eighty minutes of work stacked onto a night that already had a four o'clock start sitting at the end of it. Eighty minutes is the difference between a buyer arriving at the market with a clear list and one arriving to make decisions on the move.

The order did not arrive late. It arrived exactly when the kitchen was finally free to send it.

The pile that never quite clears

One wholesaler's own WhatsApp history, kept over four years and running to 47,936 messages, shows the shape of the problem in a single number: on an average night, 384 of the 1,431 questions sitting in it were still open by morning. Not lost - still waiting, under the next night's orders, for someone to come back to them. Every one of those is a customer who asked something and did not get an answer before they needed it.

The cost of that pile is not dramatic on any single night. It is a kitchen that gets substituted something because nobody confirmed the swap, a query that gets answered a day late and reads as indifference, a stock decision made on half the picture because the other half was still sitting unread at five in the morning.

Two fixes, and only one of them works

The obvious answer is a stricter cutoff - orders after a set time do not go out until the following day. It does not work, because the kitchen does not control when service ends, and the practical effect is either losing that order to whoever will still take it late, or training the kitchen to guess and send earlier, which trades a late order for a wrong one.

The other answer is a person, specifically staffed to work the overnight window, reading and pricing whatever arrives as it arrives. It works, and it is also the most expensive hour of labour a wholesale business buys, bounded by how fast one tired person can read a message, find the product, and check the price. Software that reads the same messages the moment they land, matches them to the right customer's own catalogue and pricing, and has them ready before the buyer's alarm goes off removes the choice between the two - the work still happens overnight, it is just no longer a person doing it awake at four in the morning.

What changes first, whichever route you take

Whichever way a wholesaler solves this, the sequence that matters is the same: know what the order actually says before the buyer needs to leave, not after. A business that gets nothing else right about the overnight problem but that one thing has already fixed the part of it that costs money. Everything else - the staffing, the software, the cutoff policy - is really just a different way of getting to that one sequence.

Plainly

What it will not do on its own

It does not stop a kitchen sending an order at ten at night - nothing does, and nor should it try to.
It will not guess a quantity from a vague message. If a line is ambiguous, it holds it back for a person to confirm rather than pricing a guess.
Automatic WhatsApp template replies are waiting on Meta's approval; sending by hand works today and reads the same either way.
It does not replace the buyer's own market judgement on the morning - it gets him to the market with a clear list, not a finished decision.

Questions people ask

Why do wholesale orders always seem to come in late at night?: Kitchens write their order once service ends and the walk-in has been checked, which for most restaurants is between nine at night and midnight rather than during office hours. The order is not late by the kitchen's clock - it is only late by a wholesaler's.
Should I set a cutoff time for orders?: A cutoff does not change when a kitchen is free to write its order - it only decides what happens to the ones that miss it. In practice it either loses those orders to a wholesaler still taking them late or pushes kitchens to guess and send earlier, which is worse than sending late.
How much does a late order actually cost a wholesale business?: Mostly in compressed time rather than lost money on any single order: reading, checking stock and pricing several orders in the hours before a market run leaves takes real minutes that would otherwise go into buying well, and a buyer still confirming quantities at four in the morning has already lost the best of the market.
Can software fix late ordering on its own?: It can remove the wait between an order arriving and it being read, priced and matched to stock, so the work happens as the message lands rather than in a rush before the yard opens. It cannot change when a kitchen is free to send the order in the first place.

Give us one night.

Send us one evening's orders. We run the night next to you. In the morning you compare the two.

Book a demo Custom or off-the-shelf