QR menu or restaurant website: which one to build first

Owners often ask whether a QR menu restaurant setup is "the website" they need. It is not, but it is a useful part of one. The two tools meet the guest at different moments: the website when they are choosing, the QR menu when they are already sitting at your table.

Two moments, two tools

Think about the guest's evening.

At 18:30 someone in Kentron opens Google Maps and searches for "khorovats with terrace" or "brunch near Cascade". They see three or four places, tap through to websites and photos, check the menu and prices, and decide. A QR menu plays no part here, because it is not visible until you are at the table.

At 20:00 they sit down, scan the code on the table and choose dishes. Here a fast menu in their language matters more than any homepage design.

The cheapest smart setup

You do not need two separate systems. Build a website with a real menu page (HTML, not a PDF), make it fast on mobile, and print the QR code with that page's address. Then:

• Prices change in one place.
• Search engines index the same menu that guests see at the table.
• A guest who liked dinner can open the same page later to book again.

Many standalone QR services charge monthly and keep the menu on their domain. If you leave the service, the codes printed on your tables stop working. With your own site, the address stays yours, a point we cover in who owns your website.

What a good table menu page needs

1. Category tabs at the top: salads, khorovats, mains, desserts, drinks. Guests jump straight to what they want.
2. Language switch visible without scrolling: Armenian, Russian, English.
3. Prices in AMD, with portion size in grams where it matters for grilled meat.
4. Photos for the best sellers only. Twenty photos on a slow connection make the page heavy.
5. Notes guests ask about: spicy, vegetarian, contains nuts.
6. No login, no app download, no pop-ups.

Test it on mobile data, not your restaurant Wi-Fi. If it takes more than a few seconds, cut image sizes.

What the website adds on top

The menu page is only one part. The pages that bring new guests are the ones that answer pre-visit questions: where you are, how to park, whether you take groups, what the terrace looks like, how to book. Our restaurant website checklist lists twelve points in detail.

Booking is the action that turns a visitor into a guest. A short form or a Telegram bot for a restaurant sends requests to your staff chat, so nobody has to answer the phone during the dinner rush.

Do not forget your map listing either. Guests often see your Google profile before your site, so a Google Business Profile with a link to the menu page closes the loop.

When a QR menu alone is fine

• A small coffee point in a business center, mostly regulars.
• A food court stall where people decide by walking past.
• A pop-up or seasonal bar that runs for a few months.

In these cases, a simple menu page and a printed code are enough. Once you want bookings, banquets or tourists finding you, you need the full site.

Step-by-step plan

1. List all dishes with prices in AMD and translations in three languages.
2. Pick 6 to 10 dishes worth a photo.
3. Build a menu page on your own domain and check it on a phone with mobile data.
4. Print QR codes for tables with that address.
5. Add pages for booking, location, events and contacts.
6. Link the menu page from Google Maps and Instagram.

Cost at Kinto

See an example in our restaurant demo or read about restaurant websites.

Send us your current menu and we will suggest whether a one-page site is enough. Telegram: @kinto_am.