A basic QR menu
- Scan
- Read the menu
- Wait for a waiter
A code that opens a picture of your menu. Prices go stale, sold-out items stay on the page, and every order still has to be taken by hand and re-typed into the till.
QR ordering · UAE & GCC
QR Menu & Ordering System for Restaurants in the UAE
Guests scan the code on the table, browse your live menu, customise what they want and order — with nothing to download. Every order lands on your kitchen screen and your POS as part of the same table check.
- Works in any phone browser — no app, no download
- English and Arabic menus with right-to-left layout
- Prices in AED with VAT added the way your invoices do it
The guest ordering screen, as it ships.
More than a QR menu
A PDF on a phone is not an ordering system
Most QR menu tools stop at replacing the printed card. The guest reads, puts the phone down and waits for someone to come over. Everything after the scan is still manual.
Tahlib QR Menu
- Scan
- Browse the live menu
- Customise
- Order
- Kitchen & POS
- Add another round
- One bill
The same scan, but the menu is live and the guest can act on it. The order becomes a real ticket the moment it is placed, and the table keeps one bill however many rounds it takes.
Same sticker on the table. The difference is what happens in the ninety seconds after the guest scans it.
How QR ordering works
From scan to settled bill, in eight steps
Nothing here needs a guest account, an app, or a member of staff standing over the table.
The guest scans the code
The table sticker carries a code unique to that table. The phone camera is enough — no reader app.
Your menu opens
Categories, photos, descriptions and prices as they are right now. The header shows which table they are sitting at.
They pick size and extras
Variants and add-on groups appear the way you set them up, priced as they go, with a note field for the kitchen.
They place the order
Name and phone, a look at the bill with VAT, and confirm. Loyalty rewards can be redeemed here if you run them.
The kitchen gets the ticket
It prints to the right station on your kitchen display, with modifiers and notes attached, the second it is sent.
The guest sees the order
A live status screen: confirmed, preparing, ready. Per-item state, so a slow dish is visible instead of mysterious.
They add another round
Anything ordered later joins the same open check for that table rather than starting a second order.
You close the bill
Staff settle the table check on the POS and the tax invoice is issued from your figures — VAT line by line.
Guests can also call a waiter or ask for the bill from the same screen.
What you get
Everything the scan needs to be worth something
Grouped by the job each part does, rather than a wall of feature names.
A QR code for every ordering situation
Table codes bind an order to a seat. One restaurant code covers takeaway and delivery from a poster or a bag sticker.
- Per-table codes that pre-select the table and lock the order to dine-in
- One restaurant-wide code for takeaway and delivery, with the guest choosing at checkout
- Codes point at a web address, so changing the menu never means reprinting
- Compromised table code? Rotate it and reprint that one card — the old one stops working
A menu that is actually live
The guest sees your catalogue as it stands, not a snapshot exported last Ramadan.
- Photos, descriptions, dietary badges and allergen tags
- Variants and modifier groups with their own prices
- Take an item off the menu and it disappears from the next scan
- Time windows per category or item — a breakfast list that closes at 11:30, an iftar menu that opens at sunset
- Search and category jumps for long menus
Built for how people order at a table
A dining party orders in rounds. The portal is built around that rather than around a single checkout.
- The table has one running check, not an order per round
- The check survives a refresh, a closed tab or a second phone at the same table
- Rounds your staff ring up on the POS appear on the same check
- Live order status with per-item kitchen state
- Call a waiter, ask for water or request the bill from the same screen
- No account, no login, no download
Made for guests in the UAE
A mixed dining room is the normal case here, not an edge case.
- English and Arabic menus with proper right-to-left layout
- Item, variant and add-on names carry both languages
- Prices in AED with 5% VAT shown before the guest confirms
- Dine-in, takeaway and delivery — you choose which channels are open
- Delivery fee and minimum order come from your own settings, so the quoted total matches the bill
- Designed on a phone first, because that is the only screen it ever runs on
Connected to the rest of the restaurant
The order is a real order everywhere else in Tahlib the moment it is placed.
- Kitchen Display — station routing, timers and modifiers
- POS — staff see and add to the same table check
- Tax invoice with UAE VAT and a ZATCA-style QR, downloadable by the guest
- Loyalty and CRM — guests are matched by phone, points earned, rewards redeemed at checkout
- Feedback — a rating request once the order is done
- Analytics — how many people scanned your menu today, this month and in total
The table check
A second round should not mean a second bill
This is the part most QR ordering tools get wrong. A table is a party, and a party gets one bill — so Tahlib keeps one open check per table and appends to it.
The table is remembered, not the browser
Scanning a table code issues a signed, short-lived session tied to that exact table. The check comes back after a refresh, after the tab is closed, and on the second phone at the same table.
New items join the open order
The checkout says “Add to order #1042” and shows what is already on the check next to what is being added, so nobody agrees to one number and is handed another.
POS rounds are on the same check
If a waiter rings a round in at the till for that table, it lands on the same order the guest is looking at. One ticket, one total, one thing to settle.
It closes when the table closes
The check stays open until it is paid or voided. After that a fresh scan starts a clean one for the next party.
Connected operations
QR ordering is useful alone and better attached
You can run the QR menu on its own. It gets more valuable each time another part of the restaurant is on the same system, because the order stops being re-typed.
- QR Menu
- Orders
- Kitchen
- POS
- Loyalty
- Tax invoice
Kitchen Display
Tickets route to the right station with modifiers, notes and a timer. Nothing is re-keyed from a paper chit.
Point of Sale
The same table check is on the till. Staff add rounds, apply discounts and settle without opening a second order.
Loyalty & CRM
Guests are matched on the phone number they type at checkout. Points accrue and rewards can be redeemed in the QR checkout itself.
Feedback
A rating request lands on the tracking screen once the order is finished, while the meal is still fresh.
Chain Dashboard
Run one master menu and push it to every branch, keeping per-branch prices where they differ. Each branch keeps its own codes.
Analytics
Menu scans today, this month and all-time sit next to sales and channel mix, so you can see how many scans turn into orders.
Products are switched on individually — see the full catalogue and prices on the products page.
Where it fits
What QR ordering changes, by type of restaurant
The mechanics are the same everywhere. What it saves you is not.
- Cafés
- Long dwell times and small repeat orders — a second karak, another slice. Each of those is a round that would otherwise need a waiter, and each joins the same check instead of a new one.
- Casual dining
- Big menus and big tables. Guests read at their own pace, pick their own add-ons, and the kitchen gets an accurate ticket instead of a shouted amendment.
- Quick service
- A restaurant code on a poster or the counter takes takeaway orders while the queue is still forming, so the kitchen starts earlier than the till would let it.
- Food courts and shared seating
- There is no table service to fall back on. A table code lets a seated guest order and reorder without giving up the seat they just found.
- Multi-branch groups
- Every branch has its own codes and its own live menu, while a master menu pushed from the chain dashboard keeps the shared items consistent.
- Delivery-led kitchens
- One restaurant code on packaging and social posts sends repeat customers straight to your own ordering page — an order that arrives without an aggregator commission.
Built here
The details that matter in a UAE dining room
Not a global product with an Arabic toggle bolted on afterwards.
Two languages on the same table
Guests switch between English and Arabic and the whole page flips to right-to-left. Item names, sizes and add-ons all carry both, so nobody orders by pointing.
VAT the guest can see
5% is calculated on the bill before they confirm, and the tax invoice they can download afterwards carries a ZATCA-style QR — the same document your accountant expects.
Menus that follow the day
Breakfast lists that close, a brunch that only exists at the weekend, an iftar menu that opens at sunset in the restaurant’s own timezone. Set the window once.
Phones, not terminals
Guests here order from their own phone as a matter of course. Nothing to install for them, and nothing proprietary for you — the staff side runs in a browser on the tablet you already own.
Your code, your brand
The card on the table should look like it belongs there
The QR builder is part of Tahlib, not a third-party generator you paste a link into.
- Eight starter styles, or set your own brand colour by hex
- Square, dotted or rounded code modules
- Drop your logo into the centre of the code
- Card text in English and Arabic — name, line underneath, and the call to action
- Save a brand style and reuse it for every reprint
- Download a PNG, or a print-ready PDF sheet with one, two, four or six cards per A4
- Print every table in one pass — each card carries its own table’s code
Al Noor Caféمقهى النورScan to order · امسح للطلب
Nothing for your guests to install
The menu opens in the browser that is already on the phone. No download, no account, no sign-in — the barrier that quietly kills most table-ordering rollouts is simply not there.
Works the same for a first-time guest and a regular.- Scan
- Menu opens
- Order
Getting started
How to get QR Menu
Two ways to get it. Add it to the paid plan you already have, or start on the plan that bundles it. The free plan still gets you a live menu and a branded QR card — you just cannot take orders on it.
Start with a Tahlib plan, then add the products you need — or move to a plan that already includes them.
Questions, answered
What restaurant owners ask before they print the cards
What is a restaurant QR menu?
A code on the table, the counter or the packaging that opens your menu in the guest’s phone browser. A basic one shows a menu and stops there. Tahlib’s opens a live menu the guest can order from, so the scan produces a kitchen ticket rather than a request for a waiter.
How does QR ordering work?
The guest scans, the menu opens with their table already identified, they pick items along with sizes and add-ons, then confirm with a name and phone number. The order goes straight to your kitchen display and onto the table’s check on the POS. They can watch it progress and keep adding to it.
Do customers need to download an app?
No. It runs in the phone’s browser. There is no app, no account and no sign-in — they scan and the menu is there.
Can guests order directly from the QR menu, or only look at it?
Both are supported and it is your choice. On the free plan the menu is view-only, which is a fine way to replace a printed card. On any paid plan the same code takes orders — either because your plan bundles QR ordering, or because you added it.
Can every table have its own QR code?
Yes. The QR builder prints one card per table, each carrying that table’s own code, and a scan pre-selects the table so the order is bound to it. You can print every table in one PDF sheet.
Can customers add more items to an order they already placed?
Yes — that is the point of the table check. Anything ordered later joins the same open order for that table instead of starting a new one, and rounds your staff ring in at the POS appear on it too. The check comes back even if the guest refreshes or closes the tab.
Does the QR menu work in Arabic as well as English?
Yes. Guests switch language on the menu itself and the layout flips to right-to-left. Items, categories, sizes and add-ons all carry Arabic names alongside the English ones, so long as you have entered them.
Does it connect to my kitchen and till?
Yes, when you run those on Tahlib. The order appears on the kitchen display with its station, modifiers and notes, and on the POS as part of the table’s open check. Nothing is re-typed.
Can I put my own branding on the QR code?
Yes. Set the brand colour, choose square, dotted or rounded modules, drop your logo in the centre, and write the card text in English and Arabic. Save the style and reuse it for every reprint, then export a PNG or a print-ready PDF.
Do I have to reprint the codes when the menu changes?
No. The code points at a web address, not at the menu itself. Price changes, new items and sold-out items are live on the next scan. You only reprint if you retire a table code or redesign the card.
How do guests pay?
Today the order is placed on the QR menu and settled with your staff — at the table, at the counter or on delivery — and the tax invoice is issued from the POS with VAT and a ZATCA-style QR. Guests can download that invoice from their tracking screen. Card payment inside the guest portal is not live yet.
Does this work for a group with several branches?
Yes. Each branch has its own menu and its own QR codes. With the Chain module you keep a master menu and push it out to the branches, overriding prices where a branch differs.
Can I use it for takeaway and delivery, not just dine-in?
Yes. One restaurant-wide code — on a poster, a bag sticker or a social post — opens the menu and asks the guest to choose takeaway or delivery, showing only the channels you have switched on. Dine-in stays reserved for table codes so an order is never bound to a table nobody is sitting at.
What stops someone photographing the code and ordering from home?
Scanning a table code issues a signed session that expires after about 90 minutes and is tied to that one table, so a photographed code stops working quickly. There is also a per-table rate limit on repeat orders, and you can rotate a leaked code and reprint that single card.
Turn every table into an ordering point
Print the cards, put them on the tables, and let guests order and reorder without waiting for someone to be free. The rest of the restaurant sees it as an ordinary order.
No card to start · nothing to install · cancel whenever