Preventing order mistakes
Wrong orders cost food, comps and regulars. Where order mistakes come from, the fix at each stage from the order to the pass, and how to measure accuracy.
- Where order mistakes come from
- Let the guest enter the order
- Make modifiers impossible to skip
- One menu across every channel, so nothing is re-keyed
- Route each item to the station that makes it
- Check every order at the pass
- 86 an item before it is sold
- How to measure order accuracy
- Where Opero helps and where it does not
A wrong order costs more than the plate. There is the food thrown away, the time to remake it while other tickets wait, often a comp, and sometimes a regular who quietly stops coming. Telling staff to be more careful rarely fixes it, because most mistakes are not carelessness. They come from the number of times an order changes hands between the guest and the plate.
Every hand-off is a chance to drop a modifier. Fewer hand-offs, and a check at the end, is the whole strategy.
Where order mistakes come from
Almost every wrong order is introduced at one of five points: taking the order, the modifiers, a handwritten or verbal relay, re-keying from another channel, or the pass. Knowing which one is yours tells you which fix to buy and which to skip.
- Taking the order. Mishearing at a loud counter, a guest who changes their mind halfway, or a server who rings what they expected rather than what was said.
- Modifiers. A required choice such as size, doneness or side that nobody asked for, a removal that was missed, or a free-text note the kitchen never saw.
- Handwriting and verbal relay. Shorthand only one person can read, or a shouted extra item that never reached the right station.
- Re-keying between channels. A phone or third-party order typed into the register by hand, where every retype is a fresh chance for error and the item may not even exist on the other menu.
- The pass. Two similar plates, two orders under the same name, or a bag sealed without being checked against the ticket.
The measurement section below shows how to find out which of these causes most of your remakes. Most kitchens are surprised by the answer.
Let the guest enter the order
The most reliable order is one the guest builds themselves, because nothing is heard, written or retyped between what they want and what the kitchen reads. Self-order kiosks and QR ordering do exactly that.
At a kiosk or on a phone, the guest sees the actual menu with the actual options and reviews the whole order before paying. A guest who can read the menu in their own language makes fewer accidental choices too. What guest entry does not fix is a badly built menu: a guest can only choose the options you created, so the next fix matters even more.
For orders staff still take, the old discipline still works: read the order back, modifiers included, before charging.
Make modifiers impossible to skip
Any choice the kitchen needs to make the item, such as size, doneness, side or sauce, should be a required modifier group, so the order cannot be sent without it. A required group turns a forgotten question into a screen that will not move on.
Set minimums and maximums so a guest cannot pick four sauces where two are allowed, and turn common requests into options rather than free text. "No onion" and "sauce on the side" as options print the same way every time; typed notes arrive in a dozen spellings, or not at all. The guide to restaurant modifier groups covers structure and naming in detail.
One menu across every channel, so nothing is re-keyed
Every channel should read from the same menu and send its orders straight to the kitchen, so nobody ever types an order from one system into another. Re-keying is the hand-off most kitchens forget they have.
It creeps in when online ordering, the kiosk and the register run on separate systems. Someone reads orders off one screen and rings them into another, and the menus drift apart: an option exists online but not at the register, so the cashier picks the closest thing. One menu removes both the retyping and the drift.
Route each item to the station that makes it
A kitchen display that sends each item to its station, with its modifiers printed under it, removes the step where someone reads a full ticket aloud and splits it up by hand. Each cook sees only their own items, so a removal on the grill item is not buried in a list of drinks and desserts.
Routing also prevents a quieter mistake: the duplicate. When a ticket is reprinted and the copy looks like a new order, the line cooks the same food twice. Reprints should be clearly marked. The guide to kitchen display station routing covers how to split a kitchen into screens, and the guide to KDS vs kitchen printer covers when paper still makes sense.
Check every order at the pass
One person comparing every finished order against the whole ticket before it leaves catches the mistakes stations cannot see, because each station only saw its own part. The expo check is the last cheap place to fix a wrong order.
- Check the modifiers on the plate, not just the item. A burger is right only if the removals are right too.
- Count items into every bag against the ticket before it is sealed.
- Use order numbers rather than names at handoff, so two orders for the same name are never swapped.
- Hand a wrong plate back with the reason, so the stage that caused it gets counted.
86 an item before it is sold
When an item runs out, take it off every channel at once. A sold-out item that can still be ordered becomes a wrong order, a substitution the guest never chose, or a refund, and it usually happens at the busiest moment. The guide on how to 86 an item covers the sequence and where the gaps usually are.
How to measure order accuracy
Count remakes and voids, give each one a reason and a stage, and review them weekly. The reasons tell you which of the five sources is yours, and they stop the kitchen and the front of house blaming each other.
- Keep a remake log at the pass: the time, the item, the channel, what was wrong and which stage caused it.
- Give every void a reason code such as duplicate, walkout or kitchen error, so the voids explain themselves at the end of the week.
- Sort by stage and by channel. Mistakes clustered on one channel point to the menu there; mistakes clustered on one station point to routing or training.
- When a guest complains, look up the actual ticket before deciding who was wrong. The ticket shows whether the order was entered wrong or made wrong.
- Work on the biggest bucket first rather than chasing a target number.
Where Opero helps and where it does not
Opero removes most of the hand-offs between the order and the station and makes the remaining ones checkable. It does not replace the expo check, and some of the measurement still lives on paper.
- Guests enter their own orders at the self-order kiosk or from their phone through QR and online ordering. The kiosk runs in English and Spanish while kitchen tickets stay in English, so the line reads one language. Kiosk orders are pay-first, so an abandoned order never reaches the kitchen. Each kiosk takes cards on its own card reader, bought from Opero.
- One modifier picker is shared by the register, the tableside handheld and the kiosk. It enforces required groups, minimums, maximums and option quantities, and the server checks every option again.
- The register, the kiosk, QR and online ordering and the kitchen display all read the same per-location menu, so orders reach the kitchen without being typed in again.
- The kitchen display routes each item by its station, any screen can be locked to one station, and a whole-order view suits expo. A cook can recall a ticket bumped by mistake, reprints are stamped REPRINT, and an optional printed expo checklist lists the whole order for the pass.
- An item 86ed from the kitchen screen or the register disappears from every ordering channel at that location, and a sold-out item is refused at order time.
- Voiding an unpaid order needs a manager PIN and a reason code such as walkout, duplicate or kitchen error. The kitchen display's history covers the last 31 days and searches by order number, guest name or item.
The honest limits: the register has no per-item notes field, so special requests have to be built as modifier options. There is no comp button, and refunds are full-amount only, so a remake of a paid order is not recorded with a reason in Opero; keep the remake log at the pass. There is no course firing. Delivery-marketplace ordering is not live yet. Opero has no offline mode, so the kitchen display needs a working internet connection, and it runs on Android tablets only.
See station routing, recall and the 86 panel on one kitchen screen.
Explore Opero KDSCompare what each plan includes.
See pricingFrequently asked questions
What causes most order mistakes in a restaurant kitchen?
Hand-offs. An order that is heard, written down, retyped into another system or read aloud to a station has several chances to lose a modifier before it reaches the plate. Missed modifiers and re-keying between channels are the usual culprits, with mix-ups at the pass close behind.
How do I improve order accuracy without slowing service?
Remove steps rather than adding checks. Let guests enter their own orders where you can, make required choices impossible to skip, keep one menu across every channel and route items to stations automatically. The one check worth adding is a fast expo look at the pass, which costs seconds and saves remakes.
Do self-order kiosks reduce order mistakes?
They remove the mishearing and retyping steps, because the guest builds the order on the real menu and reviews it before paying. They cannot fix a menu with missing options or vague names, and guests can still choose the wrong thing, so required modifier groups and clear naming matter as much as the kiosk.
Should expo check every single order?
During the rush, yes, at least for modifiers and item counts. Each station only sees its own part of the order, so the pass is the only place the whole order is compared against the ticket. A quick look there is far cheaper than a remake after the guest has opened the bag.
How should I track remakes and voids?
Give every remake and void a reason and the stage that caused it, then review weekly. In Opero, voiding an unpaid order needs a manager PIN and a reason code. There is no comp button and refunds are full-amount only, so remakes of paid orders belong in a simple log at the pass.
Can staff add a special-instructions note to an item in Opero?
Not at the register: there is no per-item notes field. Build common requests as modifier options instead, such as no onion or sauce on the side. Options print the same way every time and reach the right station, which is more reliable than free text anyway.
Run your whole restaurant on one platform
POS, kiosk, QR ordering, kitchen display, and payments on one spine — you bring the tablets, and the card reader is the one piece you buy from us. Unlimited devices, no per-device fees.
Explore the platform
Keep reading
Setting Up Modifiers the Kitchen Can Actually Read
A modifier is an instruction to a cook. Most modifier problems are really naming problems.
How to 86 an Item Without Losing an Order
The damage is rarely the shortage. It is the twenty minutes before every channel finds out.
Kitchen Display Station Routing: How Many Screens and What Goes Where
Most disappointing KDS rollouts are one screen showing every item to everyone. Routing is the part that does the work.
KDS vs. Kitchen Printer: Do You Still Need Paper?
The honest answer for most kitchens is not one or the other. Here is which jobs each is genuinely better at.