What is a QR code menu for a restaurant, exactly?
A QR code menu is a web page with your menu, reached by scanning a printed code on the table with a phone camera. Nothing needs to be installed; the page opens in the phone’s browser. That definition covers three very different products, and mixing them up is how restaurants overpay or under-deliver.
Level 1: view-only
Guests scan, browse and then call a captain to order. It replaces laminated cards and reprints. Cheap, quick and useful for almost every restaurant, café and dhaba.
Level 2: table ordering
Each table has its own code. Guests add dishes to a cart and submit; the order reaches the kitchen as a ticket, usually after a captain confirms the first round. This changes your service model, so it needs planning.
Level 3: pay at table
The running bill shows on the guest’s phone with a UPI or card payment button. Guests leave when they are ready instead of waving for the bill, and the cashier sees the payment land.
Most restaurants should start at level 1, see how guests react, and move up only if waiting for orders or bills is a real bottleneck. The rest of this guide explains each level and what it costs.
View-only QR menu or QR ordering: which does your restaurant need?
Choose view-only if your service is built on captains who suggest dishes and upsell, and choose QR ordering if guests often wait to order or you are short of floor staff. The decision is about service style more than technology.
Fine-dining places, family restaurants where elders prefer talking to a waiter, and bars where the captain’s recommendation is part of the experience usually do best with view-only. The menu is always current, photos help first-time guests, and captains still own the table.
QR ordering shines in cafés, food courts, college canteens, rooftop lounges with large floors, and quick-service places where guests already know what they want. It lets a single captain cover more tables, lets repeat orders (another round of chai, one more naan) happen without eye contact across the room, and reduces order-taking mistakes because guests choose modifiers themselves.
- Choose view-only when captains drive upselling and tables turn slowly
- Choose ordering when guests wait more than a few minutes to be served
- Choose ordering when one captain covers many tables or a large terrace
- Choose pay-at-table when the bill queue is your slowest moment
- Keep a printed menu for guests who prefer it, whichever you choose
How does QR code ordering work from table to kitchen?
A guest scans the table’s code, the menu opens already knowing the table number, the guest submits an order, and the kitchen receives it as a KOT on a printer or screen. Behind that, a few rules keep it from going wrong.
First, every table’s code carries a signed token, not just “table=7”, so nobody can edit the link and order to another table. Second, a table session opens when the first order arrives and closes when the bill is settled, so the next guests start fresh. Third, the first order of each session goes to a captain’s phone for a one-tap confirmation. That single step stops prank orders from a code someone photographed last week, and it lets the captain greet the table.
After confirmation, orders flow straight to the right stations. Guests see status (received, preparing, served) and can add items to the same bill. If your restaurant already runs POS software, orders become normal POS orders. If not, we provide a simple kitchen screen and a counter view for billing. Our custom restaurant POS page explains the fuller system.
UPI pay-at-table: how guests settle the bill from a QR menu
With pay-at-table, the guest taps “Bill” on the QR menu, sees the itemised bill with GST, and pays by UPI or card from their own phone; the cashier’s screen marks the table paid as soon as your payment provider confirms. No waiting for the folder, no card machine walking between tables.
How it is built matters. We generate a payment request for the exact bill amount through your own payment account, and the bill is marked paid only when the provider’s server confirms it to ours. A guest showing a “success” screenshot is never treated as proof. Split bills work by item or by equal share, so a group of friends can each pay their part.
Keep a fallback. Some guests will still want to pay cash or hand over a card, and the cashier can always settle from the counter screen. Tips can be added as an optional line if you choose. Settlement reports show every UPI payment against its bill number, which makes the day close much faster for your accountant.
We integrate whichever payment provider you already hold an account with; see our payment integration page for what that involves.
Can you change a QR code menu without printing new codes?
Yes. The printed code only holds the address of your menu page, so you can change dishes, prices and photos as often as you like and every table shows the new version at the next scan. This is the main reason restaurants switch.
Managers edit through a simple phone screen: tap an item, change the price, save. Mark an item sold out and it greys out for guests at once, which avoids the awkward “sorry, that’s finished” moment. Specials can be scheduled for a date range, and time-slot menus can switch breakfast to lunch at 11:30 without anyone remembering to do it.
One caution about so-called dynamic QR codes from generator tools. They point to the tool’s own short link, which then redirects to your menu. If the subscription lapses or the tool shuts down, every table code can break at once. We print a plain QR that points directly at a page on your own domain, so the code keeps working as long as you own the domain, and changes happen on the page, not in the code.
Multilingual QR menus: Hindi, regional languages and tourists
A multilingual QR code menu for restaurant guests shows a language switch at the top and remembers the choice. It helps in tourist towns, in cities with many migrant workers, and anywhere older guests read Hindi or a regional language more comfortably than English.
Each dish keeps one record with a name and description per language, so a price change applies everywhere at once. Dish names often stay in their original form (“Pesarattu”, “Litti chokha”) with a short explanation in each language, which is better for tourists than a literal translation. Scripts such as Devanagari, Tamil or Bengali render with proper web fonts so they do not break on older Android phones.
We work in English and Hindi. For other languages, you supply or approve the translations, from your staff or a translator, and we build the structure so adding a new language later is just filling a column. Search engines see each language version clearly marked with language tags, which helps guests searching in that language find the menu.
Currency and units stay simple: prices in rupees with a clear note if GST is extra, and portion sizes written the way your kitchen serves them (half, full, per piece, per 100 g). Foreign guests mostly need to know spice level and whether a dish contains meat, egg or nuts, so icons do more work than long translations.
What should a digital restaurant menu show under FSSAI rules?
A digital menu should carry the same information your printed menu must carry. FSSAI’s Food Safety and Standards (Labelling and Display) Regulations, 2020 ask food service establishments to show the veg or non-veg logo and allergen information against items on menu cards or boards, and allergens may be shown with easy-to-understand symbols.
The same regulation adds a calorie requirement for bigger operators: food service establishments with a Central licence or with outlets at 10 or more locations must show calorific value in kcal per serving, with serving size, against items, and display a reference line that an average active adult requires 2,000 kcal a day. The regulation exempts event caterers and premises operating fewer than 60 days in a calendar year.
A QR menu makes this easier than print, because each item record holds the logo, allergens and calories, and the display follows automatically. We build the fields; the values come from your kitchen or a food consultant, and your own FSSAI adviser should confirm what applies to your licence. We do not give legal advice.
- Green or brown veg and non-veg mark on every item
- Allergen icons with a legend (nuts, gluten, dairy, shellfish and so on)
- Calories per serving and serving size where the rule applies to you
- Your FSSAI licence number in the menu footer
Printing and placing QR codes so guests actually scan them
A QR code menu only works if phones scan it on the first try, in the lighting you actually have. Print it large, high-contrast and at eye-level distance, and test it on a cheap phone before ordering two hundred stickers.
We deliver print-ready artwork for table tents, stickers and wall posters, with your logo beside the code rather than stuffed into its centre. Dark code on a light background, a clear quiet margin around it, and a short line such as “Scan for menu · UPI accepted” work better than clever designs. Matte lamination avoids glare from overhead lights.
For ordering, every table gets a unique code with the table number printed in large text next to it, so staff can spot a misplaced tent. Stick codes down or use weighted stands, because a tent that wanders to the next table sends orders to the wrong bill. Check codes weekly for tampering; a stranger’s sticker placed over yours is a known scam elsewhere, and a quick glance at opening time prevents it.
Think about the path to the code, too. A QR on a wall poster by the entrance lets waiting guests browse before they sit, which shortens the time from seating to first order. A small QR on the takeaway counter and on delivery bags sends people to the same menu later, and it costs nothing extra because it is the same page.
Does a QR menu need an app download?
No, and it should not. Asking a hungry guest to install an app to read a menu loses most of them. A QR menu opens in the browser within a couple of seconds on 4G, and that speed is the whole design goal.
We keep the menu page light: compressed photos in modern formats, lazy loading for images below the first screen, no heavy scripts, and text that appears before photos finish. On a low-end Android phone on a weak signal, the dish names and prices should be readable almost immediately.
Regular guests can still keep your menu handy. The page can be installed as a progressive web app, which adds your icon to the home screen without an app store. That is also a neat base for a loyalty card or pre-ordering takeaway. If you later want a full branded app in Google Play and the App Store, that is a separate project from ₹40,000; our customer loyalty app page covers it.
Data use is part of the no-app promise. A view-only QR code menu for restaurant guests needs no login and collects nothing. Ordering needs only a table token; a phone number is asked for only if the guest wants an e-bill or loyalty points, with a one-line explanation of how it will be used.
How much does a QR code menu for a restaurant cost?
A view-only QR code menu for restaurant tables starts at ₹10,000 with us, and table ordering with a kitchen link and UPI payment starts at ₹60,000. The gap reflects real work: ordering needs sessions, security, a kitchen view, payments and testing under load.
What raises a view-only quote
Hundreds of items with individual photos, several languages, time-slot menus, and a design that must match an existing brand book.
What raises an ordering quote
Linking to an existing POS, many kitchen stations, split payments, table transfers, and loyalty or guest accounts.
What you pay others
Domain renewal, hosting (often small for a menu page), payment provider charges, and printing of table tents.
What you do not pay
No per-scan or per-table fee to us, and no monthly platform fee. Maintenance is free for two months, then optional from ₹8,000/mo.
Quotes for QR menus across the market vary a lot, mostly because some include ordering and payments and some are just a hosted PDF. Compare the level, not only the number. See our starting prices for every plan.
A useful way to judge value: count how many times a year you reprint menus today, add the staff minutes spent walking bills to tables in a busy week, and compare that with the one-time build. For a restaurant that edits prices monthly, even a view-only menu usually pays for itself quickly.
How long does it take to launch a QR menu?
A view-only QR menu is usually live in one to two weeks; a table-ordering system with pay-at-table takes six weeks or more, including a pilot. The menu data is the part that takes longest.
For a view-only menu, the first days go on collecting the menu sheet: item names, descriptions, prices, veg or non-veg, allergens and photos. We give you a spreadsheet template. Design and build follow, with a preview link to open on your phone at your own tables. Once approved, we connect your domain, generate the QR artwork and send it to your printer.
For ordering, add table mapping, kitchen screen setup, payment account connection, staff training and a pilot on a few tables during quiet hours. Running the pilot on part of the floor lets you compare order times and guest reactions before committing the whole restaurant.
Photos are the usual delay. Phone photos taken near a window in daylight are fine to begin with; you can swap them for professional shots later without touching the QR.
Launch on a weekday lunch rather than a Saturday night. The first service shows small things (a category in the wrong order, a missing modifier), and because the menu is a web page, we correct them from our side while you keep serving.
Can a QR menu help your restaurant show up on Google?
It can, if the menu is a real web page rather than a PDF or image. A menu built as HTML text on your own domain can be indexed, linked from your Google Business Profile, and marked up with Restaurant and Menu structured data from schema.org.
That matters because many people search for a dish plus a neighbourhood, or check a menu before choosing where to eat. When your menu lives on your domain with clear dish names and prices, search engines and AI answer tools have something concrete to read and cite. A PDF menu on a generator’s domain gives them little.
We add a clean URL per section, a link from the menu to your Google Business Profile listing, opening hours and address in structured data, and fast loading so Core Web Vitals pass on phones. Nobody can guarantee rankings, and a menu page alone will not beat strong competitors, but it removes a common weak spot. If you want ongoing local visibility work, our restaurant SEO service starts at ₹10,000/mo.
One small trick helps both guests and search: give the menu page a plain address such as yourrestaurant.in/menu/ and print it in small text under the QR. Guests who cannot scan can type it, and the same address works in your Instagram bio and Google listing.
Do guests like QR menus? Handling the ones who do not
Many guests like QR menus for speed and photos, and some dislike them, especially older diners and people whose phone battery is low. The practical answer is to offer both: the QR on the table and a few printed menus that a captain can bring without fuss.
The details that decide how guests feel are small. The menu should open on the dish categories, not a splash screen. Text should be large enough to read without zooming. Prices must be visible without tapping into each item. And there should be a “Call staff” button that alerts a captain’s phone, so ordering by QR never feels like being ignored.
Staff buy-in matters as much as guest reaction. Captains sometimes worry that QR ordering reduces tips or their role. Framing it as a tool that removes running back and forth for small orders, while they still greet the table and handle recommendations, makes adoption far smoother.
Accessibility is part of guest experience. We use readable font sizes, enough colour contrast for low vision, labels that screen readers can announce, and buttons large enough for shaky hands. A menu that works for a grandparent works for everyone at the table.
QR code menu for restaurant launch checklist
Use this list before you print anything. It takes about half an hour with your manager and prevents most first-week problems.
If you are setting up a QR code menu for restaurant tables for the first time, the three items people skip are the low-end phone test, the evening-light scan test and keeping paper menus. All three take minutes and save embarrassment on day one.
- Menu sheet complete: names, prices, veg or non-veg, allergens, photos
- Domain decided and in your name (for example menu.yourrestaurant.in)
- Menu opens in under three seconds on a low-end phone on mobile data
- Language switch tested with a guest who reads that language
- Sold-out and price edits tested by the manager, not only by us
- QR artwork tested from the farthest seat under evening lighting
- For ordering: one code per table, captain confirmation switched on
- For payments: a test UPI payment appears on the cashier screen
- A few printed menus kept for guests who prefer paper
Worked example: a beach café in Goa adds QR ordering for the season
This is a hypothetical scenario, not a client story, to show how the three levels fit together.
Say a 30-table beach café near Panaji serves Goan, continental and Israeli-style breakfasts to a mix of Indian and foreign tourists. In peak season, guests on the far tables wait to catch a server’s eye, and bills pile up at sunset. The owner also changes seafood prices daily, which makes printed menus useless by mid-week.
We would propose a level-1 menu first, on the static plan from ₹10,000: English, Hindi and one more language the owner provides translations for, with the day’s catch updated from the manager’s phone. For the season, level 2 and level 3 follow as a custom build from ₹60,000: table-wise codes, captain confirmation for the first order, a kitchen screen for the bar and main kitchen, and UPI or card pay-at-table with split bills. A pilot on the ten farthest tables runs for a week before the whole floor switches. International guests who cannot use UPI simply pay at the counter as before.
At the end of the season, the owner would compare order-to-serve times and bill queues on the pilot tables against the rest, then decide whether ordering stays on all tables or only on the far terrace. The menu itself stays live all year.
QR menus for restaurants and cafés across India
We set up QR menus remotely for restaurants anywhere in India. You send the menu sheet and photos, we share preview links on WhatsApp, and a local printer handles the table tents from our artwork. Calls are in English or Hindi.
City pages describe local business context for owners in Panaji, Jaipur, Udaipur, Puducherry, Mumbai, Delhi, Shillong, Mysuru and Thiruvananthapuram, among others. Tourist towns lean towards multilingual menus; big-city cafés more often want ordering and pay-at-table.
Payment is by UPI or bank transfer in stages, and international restaurant owners can pay in USD through Wise, wire or PayPal, with the menu plan from US$150. After launch, two months of maintenance are free, covering fixes and small changes you ask for.
Restaurant groups with outlets in several cities can run one menu system with outlet-wise prices and dishes, so a chain in Bengaluru and Chennai keeps a shared brand look while each kitchen shows only what it serves that day.