Order #2841
Table 12Classic Beef Burger
Medium • No onion
− 2 +
76
Chicken Shawarma
Spicy
− 1 +
25
Cola
− 3 +
24
Subtotal125
VAT 14%18
Service 12% (dine-in)15
Total158 EGP
One platform for Point of Sale, Kitchen Display, Dispatch, call-center CRM and Inventory — built Arabic-first for multi-branch operators.
Instead of wiring five systems from five vendors, get one platform that speaks one language from the cashier to the stockroom.
Build the menu once, then price it per branch, per area and per date range with pricing cohorts. Variants, modifiers, discounts, multi-VAT, and the cash drawer all on the same screen.
Every station gets its own screen profile: which order types and categories it sees, which states items move through, and which action buttons the cooks get. Colour escalation on your own time thresholds.
Open a branch dispatch shift, start driver shifts, assign ready orders, and confirm delivery. Cash collected on delivery is booked straight into the branch drawer, so the shift still reconciles.
One customer record with multiple phones and addresses, each tied to a known delivery area so the fee is never guessed. Call-center orders are handed over to a branch, which accepts or rejects.
Stock lives in its own append-only ledger across locations. Link each menu variant to the stock items it consumes, and selling it draws down stock. Transfers between branches follow an approval flow.
Most systems ship one fixed kitchen workflow. Ordrun lets you define the states, the transitions and the buttons — per station.
Each screen filters by order type, category, item and item state — so the grill sees grill work and nothing else.
Define the item states your kitchen actually uses and which moves are legal between them. Recall a bumped item, or push one to the front.
Prep and average prep time per screen, plus recently bumped items — so you can see where the kitchen is losing minutes.
Set warning and urgent thresholds per device, with colour escalation, sound and auto-recall. Override them screen by screen.
Click any module to see how it works.
Not features on a slide — these are the things that break in month three, and what we built for them.
Define as many tax rules as you need — percentage or fixed amount — and scope each to specific branches, delivery zones and order types. Percentages compute on the after-discount net, and every order keeps a snapshot of what was charged, so old receipts stay correct after you change a rate.
The cashier opens their own shift with an opening float, records pay-ins, pay-outs and safe-drops, then closes on a counted amount. Ordrun works out the variance, holds the shift for approval when it crosses your threshold, and prints the itemised report on the thermal printer.
One menu, many price lists. Prices resolve branch override first, then area, then your global list — with effective dates and bulk percentage changes when everything moves at once.
Order-level or item-level, percentage or fixed, with caps. Either a shared code or a generated pool of single-use codes you can export. Usage is counted, and applying one writes a snapshot to the order.
Fine-grained permissions grouped by module and attached to roles, not people. Branch scoping means a branch manager sees their branches only, and the backend enforces it — the UI just reflects it.
Every restaurant runs on its own isolated database and identity realm. Branches carry their own geography, delivery zones and settings, and reporting consolidates across them.
Receipt templates in HTML at 58mm or 80mm, printed 1:1 with no scaling. Arabic rows mirror properly, your logo is embedded, and the currency symbol and its position are yours to set.
Apps check in for their own updates by channel, download and install themselves, and a release can be marked mandatory. You don't drive to a branch to upgrade a tablet.
This is the part we built most carefully, because it is the part that costs you money. Here is exactly what happens — and what it honestly doesn't cover.
Dine-in and takeaway orders are created, paid in cash and completed entirely on the device.
The receipt is generated on the cashier itself — right paper width, Arabic laid out properly, your logo included. No server round-trip.
The cashier serves the kitchen screens over the branch network. KDS tablets find it automatically — no IP addresses to type in.
Orders queue on the device and upload themselves when the connection returns. Duplicates are impossible: every order carries its own id.
We're early — we pick our customers carefully and work closely with them.
Fast cashier flow, hold and resume an order mid-queue, and a kitchen screen per station.
Deep modifier system for drinks, quick repeat orders, and a shift that reconciles at close.
One menu across branches with prices resolved per branch and area, and reporting that consolidates.
Take the order centrally, hand it to the right branch, and settle cash-on-delivery into that branch's drawer.
Order by table number, coordinate several kitchen stations, and split the work across shifts.
Multiple brands and locations on one back office, with stock tracked per location and transfers between them.
The biggest thing is the system never stops when the internet drops — orders keep flowing and sync catches up on its own. That changed our day across both branches.
Every plan includes the back office, updates and support. Tell us your branch and terminal count and we'll quote you.
Dine-in and takeaway orders, cash payment, and receipt printing all run on the cashier itself — the receipt is generated on the device, not fetched from a server. Your kitchen screens keep working too: the cashier serves them over the branch network and the KDS tablets find it automatically. Orders queue locally and upload themselves when you're back, with no duplicates. What does need the connection: delivery and call-center orders (we deliberately don't store customer and address data on devices), card payments, and discount codes. Manual discounts keep working.
Yes. You define as many tax rules as you need — percentage or fixed amount — and scope each one to specific branches, delivery zones and order types. So VAT can apply everywhere while a service charge applies to dine-in only. Percentages are calculated on the after-discount total, and each order stores a snapshot of what it was charged, so changing a rate never rewrites old receipts.
Yes — from the POS app, if you give them the permission. They open with an opening float, record pay-ins, pay-outs and safe-drops through the day, then close on a counted amount. Ordrun computes the variance and, when it crosses the threshold you set, holds the shift for a supervisor's approval. The itemised shift report prints straight to the thermal printer.
For a single venue it's usually 2–3 days from agreement: we install, train your team, and migrate your menu and data. For larger chains we plan around your branch count.
Ordrun is built Arabic-first with full RTL across the back office, the apps, the kitchen screens and the printed receipts — including the offline receipts rendered on the device. English is available too, and each user picks their own language.
You build the menu once and attach price lists (we call them cohorts) to branches and areas. A price resolves branch override first, then area, then your global list — with effective dates, and bulk percentage changes when everything moves at once. So one menu can be priced differently in Zamalek and Nasr City without duplicating it.
The menu is what customers order. Inventory is a separate append-only ledger of what you actually hold, per location. You link each menu variant to the stock items it consumes and at what quantity, so selling a dish draws down stock. Transfers between locations follow an approval flow.
We build integrations on request rather than shipping a fixed catalogue — our development team reviews your case and builds the right one. Talk to us and we'll scope it.
The apps check for their own updates and install them, per release channel, and a release can be marked mandatory. Nobody has to drive to a branch to upgrade a tablet.
Every restaurant runs on its own isolated database and identity realm, so your data is never mixed with another customer's. Sign-in is handled by a dedicated identity server, permissions are enforced on the backend rather than hidden in the UI, and devices hold only what they need to keep serving offline. We currently operate in Egypt.
Leave your details and we'll reach out personally — or message us right now on WhatsApp.
Book a demo with our team. We'll show you exactly how Ordrun fits your operation.