Setting Up a QR-Code Menu That Increases Order Value: A Guide for GCC & Iraq Restaurants

Why a QR menu raises order value

At a table with a paper menu, the order is limited by time and by the server. The guest has to decide while someone is waiting, the server may be too busy to suggest a larger size or a dessert, and the add-ons the kitchen can make are often not written on the menu at all. A QR menu removes all three limits. The guest scrolls at their own pace, every option is shown with its price, and a second round (another coffee, a dessert for the table) is one scan away instead of waiting to catch someone's eye. Olo, a US ordering platform, reports that check averages rise by USD 2–4, or roughly 12%, when guests order from a digital interface. Its explanation is that guests spend longer on the menu and add extras without feeling judged. That uplift is not automatic, though. It depends on the menu being connected to your POS and your kitchen, on add-ons being priced and visible, and on the menu reading naturally in Arabic as well as English, which is the norm for most guests in Riyadh, Manama, Muscat, Doha and Baghdad.

A PDF behind a QR code vs. a menu connected to the POS

The QR sticker looks the same either way. What matters is what the code opens. A static PDF saves printing and nothing else. A menu generated from the POS catalogue can actually change what guests order.

How to set up a QR menu in your restaurant, step by step

1 — Build the menu once, in both languages, from your POS catalogue

Start from the catalogue your POS already uses rather than a separate menu tool, so there is only one price list to maintain. In Culina, turning on Restaurant Mode on a Culina Profile adds floors and tables. Create your floors (Main Hall, Terrace, Family Section) and tables, then use the QR Codes button on the floor plan to print one code per table. Scanning a code opens the branded guest menu at /menu?table=…, which takes its colours and branding from Culina Settings and has an ع / EN toggle so each guest reads it in their own language. Every item, modifier group and modifier option has an Arabic name field, so write real Arabic menu copy rather than a machine translation. Guests will read the Arabic first in most of the region. Keep names short and specific, for example Spanish Latte — Iced rather than Coffee 4, because the same names appear on the kitchen ticket and the receipt.

2 — Price every upsell as a modifier

This is the step that lifts order value. In Culina, modifier groups are created under More → Modifiers and come in three types. Single means choose exactly one (Size: Small / Medium / Large). Multiple means choose any (Extras: extra shot, oat milk, syrup). Removal covers 'no …' options such as no onions, which are never priced. Each option carries a price delta, for example Large +0.300, and a group can be attached to a whole category or to specific items. It then appears whenever those items are added, and the choice is printed in the active language on the cart, the receipt and the kitchen ticket. Three habits make modifiers pay. Set the default size to the one you want to sell, which is usually the middle size and not the smallest. Price extras in round steps guests can add up in their head (+0.200, +0.250). And keep removals free and visible, because guests who can customise a dish are less likely to leave it off their order.

3 — Send guest orders straight to the floor and the kitchen

A QR menu that only displays items still leaves the order with a server. With guest ordering enabled in Culina, an order placed from the table menu appears on the floor plan as a New order, a separate status next to Free, Occupied and Bill requested. Staff accept it and press Send to kitchen, which creates one kitchen ticket per station (Grill, Barista, Pastry), shown on the Kitchen Display or printed as a paper KOT. Only items added since the last send go to the kitchen, so a second round never duplicates the first. The /order page offers the same branded, bilingual menu for takeaway and delivery orders. Dine-in bills can also pick up the profile's service charge automatically if you set one.

Menu design choices that lift the check

• Put your most profitable dishes first in each category. Culina's Menu Engineering report places recipe-backed items on a Star / Plowhorse / Puzzle / Dog matrix by units sold and contribution margin, so you can see which dishes are worth featuring.
• Offer three sizes and default to the middle one. Most guests keep the default.
• List pairings as their own items in the category guests read last, such as a pastry next to the coffees or a dessert after the mains, so the second order is one tap away.
• Write Arabic and English names separately rather than word-for-word translations, and keep descriptions to one line so they read well on a phone.
• Keep images light. Many guests scan on mobile data, and a menu that loads slowly gets closed.
• Show prices the way local rules require: VAT-inclusive in the UAE, with the tax set up in the profile's tax template in every VAT country.

A worked example: a café in Manama

Take a 40-table café in Adliya, Manama. Call it Qahwat Al-Adliya. It serves 220 dine-in checks a day at an average of BHD 4.500 net, and about 180 hot and cold drinks a day. All figures below are net of Bahrain's 10% VAT, which the profile's tax template handles on the receipt. The café replaces its PDF QR code with a table menu connected to the POS and prices three upsells as modifiers and pairings: a Large size at +BHD 0.300, extras (oat milk, extra shot) averaging +BHD 0.250, and a pastry pairing at BHD 1.500 listed right after the coffees. After the switch, 30% of drinks go Large, 20% of drinks take one extra, and 10% of checks add a pastry. Ingredient cost is estimated at BHD 0.080 for the extra volume in a Large, BHD 0.090 per extra and BHD 0.500 per pastry. Here is one day:

Over a 30-day month, that is BHD 1,746.000 in extra net sales (58.200 × 30), about USD 4,644 at the fixed rate of BHD 0.376 per dollar, on a baseline of BHD 29,700.000. After ingredient cost it adds BHD 1,189.200 in contribution (39.640 × 30), about USD 3,163. The café hired no one and bought no hardware beyond printed table cards. Two points matter in this example. The 5.9% lift is deliberately conservative, about half the 12% Olo reports, so the case does not depend on the best-case figure. And the pastry pairing, which is a menu-design decision and not a technology one, brings in more than half of the extra money (33.000 of 58.200). The QR menu makes that pairing visible to every table, the modifiers make sure the Large and the oat milk are charged every time, and the item-level sales in Culina show within a week whether each change is working.

The bottom line

A QR menu increases order value when it is more than a picture of your paper menu. Build it from the POS catalogue so there is one set of prices, write it properly in Arabic and English, price every size and extra as a modifier, and let orders flow to the floor plan and the kitchen without re-typing. Culina, a restaurant management system built on ERPNext and used across the GCC and Iraq, provides this in one system: per-table QR codes and a branded, bilingual guest menu, an /order page for takeaway, Single / Multiple / Removal modifier groups with price deltas and Arabic labels, New orders on the floor plan, kitchen stations with KOT and a Kitchen Display, and a Menu Engineering report showing which dishes to feature. Payment still settles on your local rails at the till, whether that is KNET, BENEFIT, NAPS / Himyan, OmanNet, mada, or cash, Qi Card and Zain Cash in Iraq.