A restaurant system is judged in the two hours around Maghrib, not in an eleven o’clock demo. Four rows decide it: the floor plan, the kitchen display, splitting the bill, and delivery orders arriving without being re-keyed.
Before any feature list, check four things — because the absence of any one of them means your staff will run the floor on paper beside a system you paid for, and everything that happens on the paper is invisible to your reports.
Zones and tables that match your room, open tabs, transfers between tables, and a timer on every seated table.
Items routed by station, and course firing so starters do not land with mains.
By item, equally or by custom amount, each split producing a complete ZATCA invoice — not a slip of paper.
Jahez, HungerStation, Keeta and Talabat orders arriving in the system and the kitchen without being typed from a tablet on the wall.
In most Saudi restaurants the two hours around Maghrib and Isha produce a large share of the day’s revenue. A counter that is thirty seconds slower per transaction in those hours serves meaningfully fewer customers — and the ones it loses are those who looked at the queue and left.
So count the taps. Take your five most common orders and count the screen presses from start to payment. A well-configured system handles a common order in four to six; if yours takes twelve the problem is configuration rather than software — items buried in sub-categories, modifiers asking for a confirmation nobody needs.
Peak demand is also when networks fail. Because restaurant sales are almost all simplified invoices, a system that signs on the device can keep selling, signing and printing while disconnected — the honest exception being the kitchen display, which needs the local server, so keep a wired kitchen printer as the fallback and rehearse the switch once.
A SAR 60 delivery order at 30% food cost and 25% platform commission does not leave 45%. Add packaging, your share of funded promotions and refunds, and the real contribution lands near a third — half what the same order contributes in the dining room. A system that does not separate channels in its reporting hides exactly that.
The same goes for food cost: your recipes say 29% and your accounts say 35%, and that six-point gap is recipes that were never re-costed, over-portioning, unrecorded waste or theft — in that order. A system that holds costed recipes and records waste with reasons is what lets you find out which.
The pages that finish this one, each answering something of its own.
Ten: Jahez, HungerStation, Keeta, Talabat, Noon Food, Mrsool, Ninja, The Chefz, ToYou and Carriage. Orders arrive in the POS and on the kitchen display without anyone re-keying them from a tablet on the wall, tagged by channel so your reports can separate delivery from dine-in.
Restaurants and cafés
4 min read
A KDS is not a screen that shows tickets. It is station routing, course firing and a timer on every order — and it only pays off once your kitchen has more than one station.
4 min read
Zones, open tabs, transfers and a timer on every table. Here is what each one prevents, and why a restaurant without a floor plan ends up running the room on paper.
4 min read
Ten platforms, ten tablets, one exhausted staff member re-keying everything. Here is what integration changes, what it does not, and how to keep menus in sync across all of them.
Import your real product file, unplug the router, close a shift. Twenty minutes tells you more than any demo.
