How a Riyadh Fast Food Chain Cut Order Errors by 80% and Stopped Losing Money on Remade Meals

The Situation

Al Durra Fast Food had been running three branches in Riyadh for four years when they reached out to us. By any visible measure the business was doing well. Tables were full during lunch. The drive-thru queue moved. Revenue was consistent month to month.

But the owner, Khalid, had been tracking something quietly that nobody else in his operation was paying attention to. Every time an order came back from a customer — wrong item, missing side, wrong drink size, modification ignored — he logged it on his phone.

Over six weeks he counted 340 remade orders across three branches.

He did the maths. Average food cost per remade order: around 12 SAR. Staff time to handle the complaint, apologise, and remake: another 8 SAR in labour equivalent. Customers who received a wrong order and did not complain but did not come back: harder to measure, but Khalid estimated it conservatively at 40 SAR in lost future value per incident.

He was not looking at a service problem. He was looking at a systems problem that was costing him somewhere between 6,800 and 20,000 SAR per month depending on how conservatively he calculated the customer retention side.

He wanted to know what was causing it and whether it could be fixed.

What We Found

We spent two days across his three branches before recommending anything. We watched the full order flow from the moment a customer spoke to a cashier until food reached their hands.

The problem was not his staff. His team was experienced — most of them had been with him for over two years — and they genuinely cared about getting orders right. The problem was the handoff between the front counter and the kitchen.

Every branch was running on a basic POS that printed paper tickets to the kitchen. The ticket printer was fast. But fast is not the same as accurate.

Here is what the failure chain actually looked like. A customer orders a chicken burger with no tomato, extra sauce, medium meal, Pepsi with no ice. The cashier types this into the POS. A ticket prints. The ticket comes out in a font size that is, generously, readable if you are standing still with good light and no other tickets arriving at the same time. In a busy kitchen at 1pm on a Friday, none of those conditions exist.

The kitchen worker reads the ticket while already in motion. They catch chicken burger, medium meal, Pepsi. They miss the no tomato. They miss the no ice on the drink because that was at the end of a long line of text and the next ticket just printed.

The order goes out wrong. Sometimes the customer notices at the counter. Sometimes they notice in their car. Sometimes they notice at home with their family. The complaint lands wherever it lands and Khalid's team handles it.

We counted 14 active tickets pinned to the kitchen rail at peak on a Friday at one branch. Fourteen paper tickets, some overlapping, one with a grease smudge across a modification note. This is not a poorly run kitchen. This is a fundamentally unworkable system at that volume.

There was a second problem Khalid had not flagged. During peak hours, cashiers were verbally calling modifications to the kitchen because they did not trust the ticket to communicate urgency. This well-intentioned habit was making accuracy worse. Verbal instructions in a loud kitchen at peak hour are less reliable than even a small-font paper ticket.

What We Recommended

The fix was a kitchen display system connected directly to the POS, replacing the paper ticket printer entirely.

On a kitchen display system, the order appears on a screen in the kitchen the moment the cashier confirms it at the front. The full order is displayed clearly. Modifications are listed separately and visually distinct from the base item — not buried at the end of a line of text. The screen shows the time the order was placed. The kitchen team marks each item as it is completed. The screen flags orders that have been waiting longer than a set threshold.

No paper. No printer. No 14 overlapping tickets on a rail. No font-size issues. No grease smudges. No verbal relays shouted across the pass.

We installed KDS screens across all three branches over two nights, scheduling between 10pm and 6am to avoid any disruption to service. Staff training at each branch took around four hours. The interface is straightforward and the team adapted without issues.

We also made one small but important change to the POS configuration. We set it to require cashiers to confirm modifications as a separate step rather than as part of the base item entry. This added roughly four seconds to each order but eliminated the most common input error — modifications being entered in a notes field that did not display correctly on the old system.

We also instructed cashiers to stop the verbal relay practice entirely once the display was live. With every modification now clearly visible on the kitchen screen, there was no reason for it and it was causing more confusion than it solved.

What Changed

Khalid tracked results for eight weeks after installation using the same method he used before.

Remade orders across three branches in the first month after installation: 61.

That is an 82 percent reduction from his pre-installation average of 340 per six-week period.

Direct food cost saving on remade orders in that first month: approximately 4,400 SAR.

But when we spoke to Khalid six weeks after the installation, the number he kept coming back to was not the food cost saving. It was the Friday lunch service.

He said on the first Friday after installation he stood at the pass for 20 minutes during peak hour and watched. No verbal relays. No cashiers glancing back at the kitchen with a worried expression. No customer standing at the counter saying that is not what I ordered. He said it felt like a completely different restaurant even though nothing visible had changed from the customer's perspective.

His kitchen team noticed something else. The work felt less stressful. When there is a clear screen showing every order in sequence with a timer, the team knows exactly what to do next. There is no ambiguity about which order is oldest, no confusion about what a modification said, no second-guessing. Ambiguity in a busy kitchen becomes noise and noise becomes mistakes. Removing the ambiguity removed a layer of pressure the team had been carrying for four years.

The second branch saw a slightly lower error reduction at around 71 percent, because that branch had a more complex menu with more modification combinations. We adjusted the display layout at that branch to group modification options by category rather than listing them linearly, which improved the numbers further over the following weeks.

What It Cost

Most case studies skip this section. We include it because it is the first thing every restaurant owner actually wants to know.

Hardware and installation across three branches including KDS screens, mounting, cabling, and POS reconfiguration: 18,400 SAR total.

At a conservative saving of 4,400 SAR per month on direct food cost alone, the hardware paid for itself in just over four months.

That calculation does not include staff time saved handling complaints, the customer retention benefit from fewer wrong orders, or the operational improvement from removing the verbal relay system. When Khalid included a rough estimate of all those factors he put his real monthly benefit closer to 9,000 SAR, which moves the payback period to just over two months.

What Khalid Said

We asked Khalid if we could share what he told us at the two-month follow-up.

"I spent four years thinking order errors were just part of running a busy kitchen. I tracked them for six weeks before I called anyone, just to prove to myself that the problem was real. I wish I had done something about this two years earlier. The system paid for itself before I even noticed it was there."

The Broader Point

Al Durra's situation is not unusual. It is the default state of most QSR kitchens in Saudi Arabia that grew from one branch to two or three without updating the core systems in between.

Paper tickets work when you have one busy period a day and one person in the kitchen who has memorised the menu. They stop working when you have multiple branches, a drive-thru, a Ramadan rush, and a menu with 40 items where half of them have modification options.

The technology that fixes this is not complicated. It is not expensive relative to what the errors cost every month. The barrier is usually that the problem is invisible until someone decides to sit down and count it.

Khalid counted it. That is why it got fixed.

If you want to run the same exercise for your kitchen before making any decision, we can walk you through it. The counting costs nothing.