QR code food menu: writing the food so it sells on a phone

Getting the square to work is the easy half, and it is where most advice stops. The harder half starts after the scan, when a phone screen has to do the job a waiter and a printed page used to share. This article is about the food itself: names, photos, choices, allergens and language, written for a kitchen in Doha whose guests read English and Arabic in the same evening.

A phone is a narrow window, not a small page

A printed menu is read all at once. A phone is read a few lines at a time, with a thumb.

The Nielsen Norman Group tested reading on both, across 1,629 cases, and found comprehension on mobile roughly matched a computer. The interesting part is how: readers spent about 30 milliseconds more per word on difficult content, working harder to keep up. Your guest will not do that for a paragraph about your chef's philosophy while their friends are choosing.

So the rule for a qr code food menu is simple. Short lines, ordinary words, and the important thing first.

Names first, description second

The name carries the decision. "Grilled hammour, garlic rice" tells a guest more than "Chef's catch of the day", which tells them to ask a waiter, which is the thing the code was supposed to replace.

Keep descriptions to one line where you can. Say what is in it and what it comes with. Leave adjectives to the photograph.

Put the categories in the order people order

Not the order the kitchen thinks in. Starters, mains, sides, drinks, sweets is fine for a dining room. A delivery menu often does better leading with what sells at that hour. Categories and items are reordered by dragging, so trying a different order costs a minute, and you can look at the sales dashboard by day and item afterwards to see whether it helped.

Photographs, and which dishes deserve one

A photo sells a dish and slows a page. Get Menu compresses photos automatically so pages stay quick, and there is a photo style toggle for square pictures, tall ones, or none at all if your food does not photograph well.

Two habits worth keeping. Shoot in daylight against a plain surface, and do not photograph a dish you are not proud of, because a bad picture sells less than no picture. Choose from 12 layouts to suit what you have: an image-led one when every dish is shot, a plainer one when only a few are.

The questions a waiter would have asked

This is where most QR menus quietly lose money. A printed page says "burger". A waiter asks how you want it, and whether you want cheese.

Items carry options and add-ons with their own prices, and a choice can be marked required with limits the kitchen can trust, so an order cannot arrive without a spice level. The customer sees the price change as they pick, and every line is priced again from your live menu at checkout, so what they were shown is what they pay at the door.

What you must be able to answer about ingredients

Someone will ask about nuts. On a phone, nobody to ask, they leave.

Get Menu carries a declaration against the fourteen listed allergens, item by item. It is deliberately strict about the difference between "nobody has said anything about this dish" and "a person has reviewed this dish and declares it free of all fourteen", because those are different facts and only one of them is safe to show. The declaration is your restaurant's own statement about your own food, and the software never guesses one from a dish name.

This is normal practice elsewhere and worth adopting before anyone asks you to. In the European Union, allergen information is mandatory for non-prepacked food, including food served in restaurants and cafes, with the list of substances set out in the regulation's Annex II. Many of your Doha guests are used to seeing exactly that.

Two languages, one menu

Item names and descriptions can be written in Arabic as well, so the menu reads properly for the guest who prefers it. That is a small piece of work when you build the menu and a large piece of respect when somebody scans the code.

Sold out before the apology

Nothing damages a first order like a phone call saying the dish is finished. Stock counts fall as orders arrive, per item and per option, so running out of one sauce does not take the whole dish down. Sold out flips itself at zero with nobody watching, and a low-stock alert reaches you before it becomes a problem. Cancel an order and the stock comes back.

Making the menu sell, gently

Once the food reads well, a few switches are worth turning on. Upsells offer pairings, ladders and thresholds, so a guest ordering two coffees is offered the third at a better price rather than being nagged. Bundles let you sell any three items for a fixed price. Coupons carry caps, exclusions and expiry dates, and discounts never stack by accident, because the best one wins rather than all of them applying.

"A menu on a phone is read with one thumb, standing up, sometimes in a lift. We built the item sheet around that: the name, the price, the choices, and nothing between them." — Tanzeel ur Rehman, co-founder of Get Menu

After the guest presses order

The menu's job ends at the order, and the rest should be quiet. 3 messages go out over WhatsApp in about 2 seconds: a confirmation to the customer, a ticket into the managers' group, and a rider dispatch link with the GPS pin dropped at checkout. Indoors, a code is generated for every table, so the ticket already knows where the food goes.

Payment is cash or your card machine at the door. There are no online payments in the product, so no card details exist anywhere in it. Invoices carrying your tax number download as a PDF without a login. Stamps turn into rewards, regulars grow into tiers, and the loyalty card sits in Google Wallet, updating itself with no app to install. Order details older than 120 days are removed without anyone lifting a finger.

Try it with your own dishes

Build the menu, put a code on the table, and watch what people open. You get 15 days with no card asked for at signup, and a flat monthly price afterwards with 0% commission on your sales. For more, digital menus covers the screen side, menu engineering covers what to promote, and the QR code menu guide covers printing and placing the code.

Frequently asked questions

How many photos does a QR code food menu need?

Fewer than people think. Photograph the dishes you want to sell more of and the ones that are hard to picture from a name. A page with six good photographs beats one with forty poor ones.

Should item descriptions be long?

No. One line saying what is in the dish and what comes with it. Guests read menus with a thumb, and long descriptions get skipped rather than read.

Can the menu show allergens?

Yes, as a declaration you make item by item against the fourteen listed allergens. The system stores what you declare and never invents an answer from the dish name.

Can I have the menu in Arabic as well as English?

Yes. Item names and descriptions can be written in Arabic, which matters in a market where a table often reads both languages.

What happens when a dish runs out mid-service?

The count reaches zero and the item shows as sold out on its own. No one has to remember, and the guest never orders something the kitchen cannot cook.