The best QR code menu examples share one trait: the guest scans once, sees prices within two seconds, and never has to pinch-zoom a PDF. Everything else, from the stand on the table to whether the menu can take the order, is a layer on top of that basic promise.
The twelve examples below are composites of patterns seen across cafes, dhabas, cloud kitchens and family restaurants, described by type rather than by name, so you can copy the idea without copying a brand. Each one solves a specific problem: a menu that changes daily, a crowd that does not trust QR codes, a kitchen that wants orders without waiters, a cafe that wants the scan to lead somewhere after the meal. A design checklist and the common mistakes follow at the end.
What separates a good QR menu from a bad one
- It opens as a web page, not a file. A PDF loads slowly on a 4G connection, needs zooming, and cannot be updated without reprinting the code's destination.
- Prices are visible without scrolling. Guests scan to decide, and price is most of the decision.
- Categories are tappable. A 90-item list needs a category bar at the top, not a long scroll.
- It works without an app or login. Any step that asks for a phone number before showing the menu loses a share of guests.
- The physical code is easy to find and explains itself. "Scan to see the menu and order" next to the code, on a stand that does not fall over.
The free QR code menu setup guide covers generating the code and the page; this post is about what to do with them.
12 QR code menu examples worth copying
1. The cafe with the one-line instruction
A small acrylic stand on each table with the code, the cafe's name and one line: "Scan for menu and order, pay at the counter or on your phone." Nothing else. Guests who have never used a QR menu know what will happen before they scan, and staff stop explaining it twenty times a day. The best version of this prints the Wi-Fi password on the same card, which solves the "no data" objection.
2. The dhaba with the code on the wall and on the bill
A highway dhaba with high table turnover puts one large code at eye level on every wall and a small one on each bill. The wall code is for the menu; the bill code opens the same menu with a line saying "order ahead next time you are passing". It turns a one-off stop into a reorder channel without a single table stand to lose.
3. The daily-changing tiffin menu
A lunch kitchen that cooks a different thali every day points its code at a page that changes with the day of the week. Monday shows Monday's dishes; a guest scanning on Thursday sees Thursday's. No reprinting, no "today's special" board that nobody updates. This only works with a web menu that supports scheduling by weekday.
4. The family restaurant with a printed backup
A restaurant with a large older clientele keeps two laminated menus per table and a QR stand. The stand says "prefer paper? just ask". Guests who are comfortable scanning do; the rest never feel pushed. Reprints dropped to once a year because only the printed copy's prices are hard-coded, and the QR menu carries the daily changes.
5. The scan-to-order cloud kitchen counter
A cloud kitchen with a small walk-in counter puts the code on the counter and on a board outside. Scanning opens an ordering page, the guest builds the order and pays by UPI on their phone, and the order prints on the kitchen printer. One person runs the counter at peak, because nobody is taking orders by hand. The QR ordering explainer describes this flow in detail.
6. The table-numbered code
Each table has its own code that encodes the table number. When a guest orders from the menu, the order arrives in the kitchen already labelled "Table 7", and the server never has to ask. This is the difference between a QR menu and a QR ordering system, and it is what makes dine-in ordering workable without staff walking the floor with notepads.
7. The bar with a drinks-first menu
A bar's code opens on the drinks page, with food one tap away, because that is the order in which guests decide. The lesson generalises: open the menu on the category most guests want first. A breakfast cafe opens on breakfast until 11am and on lunch after that.
8. The bakery with photos of everything
A bakery's menu is almost entirely photos, large and square, with the name and price beneath. Cakes sell on sight, and a text list of "chocolate truffle, 500g, ₹650" sells fewer than the same cake photographed in daylight. The page loads fast because images are compressed, which matters more than most owners think.
9. The code that collects a review on the way out
The same code on the bill folder opens the menu during the meal and, after the bill is paid, a short rating prompt. One code, two jobs, and a steady stream of reviews without staff asking. Restaurants that do this well keep the rating to one tap and the comment optional.
10. The multi-outlet brand with one code design
A brand with four outlets prints identical stands, but each code opens that outlet's own menu with its own prices and availability, so a price change at one outlet leaves the others untouched. Guests see consistent branding, kitchens see only their own items.
11. The hotel room service card
A small hotel replaces the room service folder with a card: scan, order, the order goes to the kitchen with the room number attached. Guests stop calling reception, and the kitchen gets an order ticket instead of a verbal relay that gets the room number wrong.
12. The street-food cart with pre-order by QR
A momo cart with a queue at 6pm puts a code on the cart and on its Instagram: scan, order, pay, come back when your name is called. The queue shrinks, the owner cooks in batches, and the regulars order before they leave the office. The cheapest QR menu example on this list, and often the one with the biggest effect on revenue.
QR menu design checklist
| Element | Do this | Avoid this |
|---|---|---|
| Code size | At least 3cm square on table stands, larger on walls | Tiny codes in a corner of a busy card |
| Contrast | Dark code on a light background | Coloured codes on patterned backgrounds |
| Instruction | One line saying what happens after the scan | No text, or a paragraph |
| Destination | A fast web page with tappable categories | A multi-page PDF |
| Prices | Next to every item, taxes stated | "Ask staff" or prices only at checkout |
| Photos | Compressed, daylight, consistent size | Stock images, or one giant uncompressed photo |
| Availability | Sold-out items marked or hidden | Guests ordering items you ran out of at noon |
| Placement | Eye level, one per table, plus one at the entrance | Under the napkin holder |
Mistakes that send guests back to paper
A QR menu that fails once is abandoned by that guest for good. The failures are predictable: a code that links to a dead page after a platform change, a PDF that takes twenty seconds to load, a menu that asks for a phone number before showing anything, prices that differ from the bill, and a stand that has been wiped so many times the code no longer scans. Check every code once a month by scanning it with a guest's eyes.
The other mistake is treating the QR menu as the whole system. A menu that cannot take an order, carry a table number, reach the kitchen and collect payment is a brochure. The digital versus printed menu comparison covers the cost side, and the order management guide covers what has to happen after the scan.
Tezzu's web menu is one way to run most of the examples above: a store page with tappable categories and prices, menu scheduling by weekday and time for the daily-changing menu, QR tables with table numbers for dine-in, KOT printing in the kitchen, UPI payment on the guest's phone and a rating request after the order. The dine-in setup guide shows the table-code flow.
See the QR menu and table ordering together
The restaurant solution page shows how QR tables, the web menu, KOT printing and payments fit a small dine-in restaurant.
See how it works for restaurantsFrequently asked questions
What is the best format for a QR code menu?
A mobile web page with tappable categories, prices beside every item and compressed photos. It loads faster than a PDF, needs no zooming, and can be updated without touching the printed code. If the page can also take an order and a table number, the same code handles ordering, which is where most of the operational savings come from.
How do restaurants design a QR code menu?
Start with the menu page: categories in the order guests decide, prices visible, sold-out items hidden. Then design the physical code: at least 3cm square, dark on light, with a one-line instruction and the Wi-Fi password if you offer it. Place one per table at eye level and one at the entrance, and scan every code monthly to check it still works.
Do customers actually use QR code menus?
Most guests under 40 scan without hesitation, and the habit spread widely during 2020 and 2021. Older guests and groups in low light are more likely to ask for paper. The practical answer is to offer both, make the QR menu faster and more current than the printed one, and let guests choose. Usage climbs when the code also lets them order and pay.
Can a QR code menu take orders?
Yes, if the code points to an ordering page rather than a static menu. The page lets the guest add items, attaches the table number encoded in that table's code, sends the order to the kitchen as a ticket, and can collect payment by UPI or card. A QR menu without ordering is a digital brochure; one with ordering is a table ordering system.