Reduce order errors in your restaurant
A dish sent back is lost margin, a waiting table and a disappointed guest — often for an error that crept in between the table and the pass. Here’s where these errors come from, and how to make them fall.
Updated 8/11/26
In short
What you’ll learn: the true cost of an order error, the four places it slips in (handwriting, verbal relay, memory, availability), and five moves to cut them — without adding work for the team.
What an order error really costs
An order error isn’t just a dish to remake. It’s the lost ingredients, the kitchen time spent twice, the table waiting while the rest of the party is served, and — costliest of all — the dented trust of a guest who’ll hesitate to come back. On a busy service, a few errors are enough to throw the kitchen at the worst moment.
Where the error slips in
Almost always between taking the order and the kitchen, at one of four points:
- Handwriting: a notepad scribbled on the move, an abbreviation, and the dish read at the pass is no longer the right one.
- Verbal relay: between the server calling it out and the kitchen hearing it, in the noise of a rush, a word is lost.
- Memory: “table 12 wanted no onion”, kept in the head and forgotten three tables later.
- Availability: a sold-out dish taken because nobody flagged it in time.
The principle: fewer middlemen between table and kitchen
Every time an order is recopied, re-read or repeated, an error can slip in. Cutting errors means cutting those steps: what the server notes at the table should reach the kitchen as-is, with no re-transcription and no calling out.
Step by step
Remove the re-transcription
As long as the order goes from paper notepad to a call at the pass, it’s copied at least once — and every copy is a chance for error. An order that goes straight to the kitchen removes that step. With Illicoo, what the server types at the table shows up as-is on the kitchen screen.
Structure the entry
One dish, one quantity, a clear note (“no onion”): a structured order leaves no room for interpretation, unlike a line scrawled between two tables.
Make sold-out dishes visible in real time
When a sold-out dish is flagged with one tap and visible to the whole floor, nobody takes it in an order. The most frustrating error — promising a guest a dish that no longer exists — disappears.
Cut the verbal relay at the pass
The kitchen reads the order on screen, in arrival order, instead of catching it by ear in the noise. No more “what was table 7 again?” shouted mid-service.
Keep a record of who ordered what
Every order stays attributed and auditable. In doubt, you check instead of guessing — and the team learns from mistakes instead of repeating them.
Frequently asked questions
Does digitising order-taking slow the server down?
No, the opposite: tapping on a phone at the table is as fast as writing, and it removes the walk to the pass to call the order out. The server saves time while cutting errors.
Do you have to let guests order themselves to avoid errors?
Not at all. The error doesn’t come from the server, but from the copy-and-relay steps between the table and the kitchen. Remove those steps and the server stays central while errors fall.
How do you avoid serving a sold-out dish?
By making availability visible in real time: as soon as a dish is marked sold out, it disappears from the whole team’s order-taking, on every device, immediately.