Restaurants and cafés

QR menu: the code on the table opens the live menu on your site

Short answer

A QR menu is a digital menu that opens on the guest's phone when they scan the code on the table. ALTAI Digital builds it as a page of the restaurant's own website, not as a separate app. The menu is edited in one place, and the website and the table code show the same page. Every dish has fields for category, description, price, allergens and a photo. The menu can run in English and Dutch. No menu subscription is needed; the build takes four weeks.

In many restaurants the QR menu is a link handed out by a menu app. Scanning the code opens a page on the app's domain, in the app's design. The restaurant's own website sits elsewhere, and its menu is often out of date. When a price changes, two places need editing and one gets forgotten. A guest sees one price on Google and another at the table. If the subscription lapses, every code on every table stops working.

We build the QR menu as a page of your website. The code opens the menu on your own domain. You edit the menu in one screen, and the change appears on the site and at the table at the same moment. Changing a price takes a minute and needs no technical knowledge. Staff get a half-hour walkthrough at handover. The domain and hosting are registered to the restaurant, so the address behind the code does not depend on anyone's subscription.

The menu page is written so that search engines can read it. Google reads the menu on your own site, and the menu link in your Business Profile points to that page. A guest who finds you on the map lands on the same menu. The page loads fast on a phone, and photos are resized before upload. Allergen information sits next to each dish. EU and UK food information rules name 14 allergens; the fields cover all of them, and your kitchen supplies the content.

Below you will find the scope of a QR menu build, the steps and the questions we hear most. The menu can be part of a full restaurant website or a single page added to your current site. We work from Rotterdam and Istanbul and deliver in English, Dutch or Turkish. Pricing is given after the discovery call, once the size of the menu and the number of languages are clear.

What happens today

What goes wrong today

  1. 01

    Two menus, two prices

    The QR menu lives in an app and the website menu lives somewhere else. A price changes in one and not the other. A guest arrives expecting one price and sees another at the table. The difference turns into a conversation at the bill.

  2. 02

    The code opens someone else's domain

    The code from a menu app points to the app's domain. Google does not count that page as your site. If the subscription ends, every table card opens an empty page and has to be reprinted.

  3. 03

    A PDF menu is hard to read on a phone

    A scanned copy of the printed menu is tiny on a phone. Guests pinch and zoom and cannot jump between sections. Updating the PDF means another job for the designer, and the old file stays on the tables for weeks.

  4. 04

    Visitors cannot read the menu

    In a city with many visitors, a menu in one language sends guests to the waiter with questions. During the busiest hour those questions hold tables up. A second-language menu kept in a separate file means prices are edited twice again.

  5. 05

    Allergen questions go to the kitchen

    A guest asks which allergens a dish contains. The kitchen knows, but the menu does not say. The waiter walks to the pass and back, and the table waits. The same question comes up at several tables every evening.

  6. 06

    Sold-out dishes stay on the menu

    The fish of the day runs out halfway through service. Removing it means logging into an app, and nobody has time. A guest orders it and then learns it is gone.

What we build

Scope of the build

One menu, edited in one place

The menu is managed in a single screen. The menu page on the website and the code on the table open the same page. A change to a price, a description or a photo shows on both at once. A sold-out dish is hidden with one tap and brought back the next day.

The code points to your own domain

The code opens the menu page on the restaurant's own domain. The domain and hosting are registered to the restaurant. Because the address does not depend on a subscription, the table cards stay valid for years.

Category, allergen and photo fields

Every dish has a category, description, price, allergen field and photo. Allergens appear next to the dish. Photos are resized before upload, so the menu stays fast on a phone.

English and Dutch, or English and Turkish

Both languages are edited in the same screen. The price is entered once and shows the same in each language. Guests switch language with a button on the page. A third language can be added in the same way.

Google and Business Profile link

The menu page is marked up with restaurant structured data. The menu link in your Google Business Profile points to it. Guests reach the same menu from the map, from search and from the table.

Table card and code design

The code comes as a table card in your restaurant's style, with a print-ready file. Because the address never changes, the cards do not need reprinting when the menu changes.

Booking and WhatsApp link

Under the menu sit a booking link and a WhatsApp link. A guest who looks at the menu from the map can reserve from the same page. The request arrives by WhatsApp or email and is confirmed with one tap.

How it runs

How the build runs

  1. 01

    Discovery (1 week)

    We collect the menu, prices, photos and allergen details. We measure your current site and Business Profile and agree the languages.

  2. 02

    Build (2 weeks)

    We build the menu page and editing screen, enter the dishes and prepare both languages. You test the menu on a phone at a review session.

  3. 03

    Print and launch (1 week)

    We hand over the table card file, publish the menu and give your staff a half-hour walkthrough.

  4. 04

    Connect and measure

    We link the Business Profile menu and Search Console. After the first month you get a report on visits to the menu page.

Key concepts

Terms used on this page

QR menu
A digital menu that opens when a guest scans the code on the table; it is the same page as the menu on the restaurant's website.
QR code
A square code that opens a web address when scanned with a phone camera.
Editing screen
The screen where dishes, prices, allergens and photos are updated without technical knowledge.
Menu link
The address in a Google Business Profile that shows the restaurant's menu; it points to the menu page on the restaurant's own site.
Restaurant structured data
Markup on the page that Google reads to show the menu, opening hours and location in search results.
Frequently asked

qr menuFrequently asked questions

The guest scans the code on the table with the phone camera, and the menu page on the restaurant's website opens. No app download is needed. The menu is edited in one screen and changes on the site and at the table together.

No. The menu runs on your own website. The domain and hosting are registered to the restaurant, and the address behind the code does not depend on a menu app.

You do. Prices and dishes are changed in the editing screen, with no technical knowledge needed. Staff get a half-hour walkthrough at handover. If you prefer, updates can be part of a monthly maintenance plan.

Yes. It can be added as a single page. We first measure the speed and structure of your site. If it is slow on phones or built on old technology, a new menu page is often quicker; we decide together on the discovery call.

That depends on your own obligations and guests. Check the rules that apply to your premises before removing printed menus. The QR menu also works alongside a printed one, as the copy that is always up to date.

Yes. Each dish has an allergen field covering the 14 allergens named in EU and UK food information rules. Your kitchen supplies the information; the build makes sure it sits in the right place in every language.

Yes. The menu page is readable by search engines, and the menu link in your Business Profile points to it. Guests reach the same menu from the map, so there is only one menu to maintain.

Four weeks: one for discovery, two for the build and one for printing and launch. If the menu, photos and allergen details arrive in the first week, the schedule holds.

Alparslan UnalMert Can Gundogdu
The founders take the call, not a sales team
Next step

The process first, the proposal after

In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.

30 minutes · no preparation needed

Chat on WhatsApp