Start with the four questions guests actually ask
Every restaurant page that lives behind a menu QR is really a self-service answer to a small set of questions. The list is shorter than it looks. What is on the menu today. When are you open. Where are you, and how do I get there. And the one that matters most, how do I get in touch if I want to ask about a booking, change a plan, or check an ingredient. If those four are answered quickly, the QR is doing useful work and the front-of-house team can focus on the people in the room.
A useful way to prepare the page is to imagine a guest reading it on a phone with one hand, in low light, while standing on the pavement. Short lines, big enough text, no carousel of slides that needs swiping. The menu in plain text or as a clear list. The address with a map link. The phone, email, and any external booking link on the same screen, not hidden behind a separate tab. When the four questions fit on one view, the page feels calm, which is exactly what a guest wants when deciding where to eat.
QREasy hosts these small restaurant sites through editable templates, so the same page can be opened, edited, and republished from a browser without touching the printed QR at all.
- Menu, hours, location, and one clear enquiry channel on the first view.
- Plain text or a simple list beats a slideshow that needs swiping.
- Keep the booking link or phone number where it cannot be missed.
A hosted page that can be updated without reprinting
A printed menu can already carry contact details, hours and an address, so the case for a page behind the QR is not about adding information the paper cannot hold. The case is that a hosted page can be edited and republished without reprinting the QR. A dish that sells out, a price that moves, a new set menu, or a corrected opening hour can be reflected on the page the same day, and the QR that points at that address keeps on working. The address stays fixed, the content underneath moves.
This is the practical edge of running a small site behind a QR. A static URL QR encodes a fixed address, so the same QR can keep pointing at the page while the menu changes. Only changing the encoded address itself would require a new QR. That separation between the printed QR and the content it shows is what makes the page worth maintaining in the first place, especially for kitchens where the menu drifts week to week.
- The page can be edited and republished without reprinting the QR.
- Only changing the encoded address would require a new QR.
- Update the menu and hours as often as the kitchen changes them.
Menu, hours and location that read well on a phone
For the menu itself, the most useful format is the one that reads well on a phone. A short text list grouped by starters, mains, desserts, with prices clearly aligned, is friendlier to read than a photographed page in a dim PDF. Mark the daily special in the same style, not as an afterthought. If there are dietary details that the kitchen can speak to with confidence, suggest that guests call or message for the latest detail, since recipes drift and only the kitchen knows what is in the pan today. The hours and the address belong near the menu, with a tap-to-open map link for the address, and a small note about the last seating if the kitchen closes earlier than the door.
Sections on a hosted page can be ordered to match common guest questions. Menu near the top helps when a guest is checking what you serve, hours and address below when they confirm logistics, and Contact afterwards when they decide to reach you.
- Group the menu in short sections with prices in line.
- Mark daily specials in the same style as the rest of the menu.
- Place the map link and hours close to the menu.
Enquiry channels and what they actually mean
This is where many restaurant pages go wrong. The QR opens a page that looks like a booking page, but it is really a contact page. Restaurant and similar templates usually offer phone, email, WhatsApp or an external booking link as enquiry channels, and these fall into two different categories. Phone, email and WhatsApp enquiries are requests that the restaurant team follows up on; a message through any of these channels is not itself a confirmed booking and the page should say so plainly. An external booking service linked from the page is a different kind of integration: it may confirm a booking directly under its own rules, independent of how the restaurant handles phone, email or WhatsApp enquiries. The honest way to phrase this matters. For the request-based channels, a line like call us to reserve, or message us on WhatsApp to ask about availability; we will reply to your request, sets the right expectation. Example response wording should be shaped to match the restaurant's actual practice. Phrasing phone, email or WhatsApp enquiries as if a message is a confirmed booking creates friction for the guest and extra work for the team when reality has to catch up, while a linked external booking service can be presented on its own terms as a separate reservation path.
The practical move is to set the enquiry channels apart as their own short section, label each one with what it actually does, and link out to any external booking platform the restaurant already uses as the dedicated reservation path. The page itself can carry phone, email and WhatsApp as the catch-all for everything else, from a birthday request to a question about a gluten-free option. A call placed through the phone link, an email sent through the email link, and a WhatsApp message sent through the WhatsApp link are all requests the team follows up on rather than automatic reservations. An external booking service linked from the site can confirm a booking under its own rules, since QREasy does not provide native booking and does not determine what that separate service is able to do on its own platform.
- Treat enquiries as requests, not as confirmed bookings.
- Link out to the external booking platform already in use.
- A short contact section beats a form that pretends to be a booking system.
A small layout that holds together
Templates designed for restaurants tend to follow a familiar shape for a reason. A hero image of the room or a signature dish, a short story about the kitchen or the family behind the place, the menu, the location with a map link, and the contact section. The order matters more than the visual styling. The image earns the first second of attention, the menu answers the practical question, the story answers the emotional one, the location confirms logistics, and the contact section closes the loop. None of these need to be long, and a single tidy page works well for a single location.
A useful suggestion for the layout is to write the page in the same voice as the staff. If the team is warm and chatty on the phone, the page can be warm and chatty too. If the team is quiet and formal, the page should match. Tone that does not match the room creates a small disappointment for guests who arrive expecting one thing and meet another. The page is part of the welcome, even before the door opens.
- Hero image, menu, story, location, contact, in that order, is a reliable shape.
- A single tidy page suits a single location.
- Write in the same voice as the front-of-house team.
Choosing the right template for the page
The choice between the Simple restaurant template and the restaurant template is a content choice first. The Simple restaurant template is available on the free plan and covers menu, location and hours, which suits a small place that needs one tidy page behind the QR. The restaurant template requires Lite SME or Business, independently of whether a Wallet card is created, and gives the page more room to carry a fuller menu, a longer story about the kitchen, or a fuller gallery of the room. That decision can sit alongside the QR, rather than ahead of it, since the QR points at the page regardless of plan.
- The Simple restaurant template is free and covers the essentials.
- The restaurant template needs Lite SME or Business and gives the page more room.
- Pick the template that fits the content first, then match the plan.
