Build a QR Code Menu for a Restaurant With AI
Build a QR code menu for a restaurant with AI: the one URL decision that saves reprinting, a simple data model, allergen rules and a print test.
To build a QR code menu for a restaurant with AI, make one decision before you write a single prompt: the QR code must point at a permanent address you control, such as your own domain followed by /menu, and never at a file or a temporary preview link. Everything else on the page can change daily. The printed card on the table cannot.
That one choice is what separates a menu you maintain in two minutes from one that needs a reprint every time the soup changes.
Build a QR code menu for a restaurant with AI: decide the address first
A QR code is just a printed web address. If it points at a long, auto-generated link from a builder or file host, then moving the menu later means every card is wrong. Do this instead:
Own a domain, or a subdomain of the restaurant's existing one, and fix the path:
yourplace.com/menu.Generate the QR code from that exact address, once.
Build the menu page behind that address and change what it shows as often as you like.
If the app is not yet on your domain, moving an AI-built app to a custom domain covers the steps, and you can do that before you print anything.
The menu data, kept boring on purpose
Ask the AI to build the page from a simple table rather than hard-coded text. A workable set of fields:
Field | Example | Why it exists |
|---|---|---|
name | Lamb shoulder | The dish |
section | Mains | Groups the page |
price | 24.50 | Stored as a number, formatted on display |
description | Slow-cooked, mint salsa | One line |
allergens | milk, celery | A list the owner types in |
available | true | Hides a sold-out dish without deleting it |
sort_order | 3 | Controls the order within a section |
The available switch is the feature staff will use most. Sold out at 8pm should take one tap, not an edit to the menu text.
A short admin screen, not a CMS
The owner needs three actions: change a price, toggle availability, add a dish. Ask for a password-protected page with exactly those, using a list view with inline editing. Do not ask for a general content editor, which you will spend a week debugging. If you want a larger picture of what to request from an AI builder for this kind of business, the best AI app builder for restaurants and AI tools for restaurants cover the options.
Allergens: a person enters them, the AI does not guess
Let the AI draft descriptions and tidy wording. Never let it infer allergens from a dish name or generate them from a recipe summary. A wrong or missing allergen is a real safety problem, not a typo. The rule that holds up: allergens are typed by someone who knows the recipe, shown on the page in plain text, and the page carries a line telling guests to ask staff about any allergy. Keep that line even if the data is perfect.
Print-ready QR codes: a few facts and a test
QR codes carry built-in error correction, so a code can still scan when part of it is dirty or damaged. According to Denso Wave, the developer of the QR code, there are four error correction levels, and Level M, which restores about 15 percent of the code, is the one most frequently selected. Level Q restores about 25 percent. Higher correction means a denser pattern, which needs more print area to stay reliable, so more is not automatically better for a small table card.
Before you print 40 cards, run this test:
Print one at actual size and scan it with at least two different phones, one older.
Scan it from the distance a guest holds the phone, at a seated angle.
Scan it in the dim light of the evening service.
Scan it with a thumb partly over a corner and with a drop of water on it, to see how it copes.
Hold the card in the sun by a window, since glare defeats cameras faster than damage does.
The page itself
Tell the AI the menu is read on a phone, one-handed, usually in poor light and on mobile data. That means large text, high contrast, no popups, and no account or app download. Section links near the top let people jump to desserts without scrolling past 40 mains. Keep photos small, see optimising images in an AI-built app, because a menu that takes ten seconds to load gets abandoned for a waiter.
Make the page readable without scripts if you can, and offer a printed menu on request for guests who do not use phones. A QR menu that is the only option excludes people, and some of them are your regulars.
For the wider picture of what AI can do for a small venue, start from AI for small business.
A digital menu makes it easy to change dishes often, and a weekly specials routine with AI covers how to choose them.
Frequently asked questions
How do I make a QR code menu for free?
You can host a simple page on a free hosting plan and generate the QR code from its address. Use your own domain path if possible, so the code never has to change.
Do QR code menus need to be updated when prices change?
No, if the code points at a permanent address. The code stays the same and you edit the menu data. Only the page content changes.
What QR code error correction level should a menu use?
Level M is the most commonly selected and suits most table cards. Consider Q if cards get wiped, spilled on or handled a lot, and test the print size.
Should the QR menu be a PDF?
A mobile web page is better. A PDF is slow on phones, hard to read without zooming, and you cannot hide a sold-out dish without uploading a new file.
How did this land?
About the author
Developer Advocate
Steve builds something with Swarmz every week and writes up what worked, what broke, and what he'd do differently. Tutorials and hands-on guides are his lane.
