A QR code opens a destination; it is not the menu itself. That destination can be a PDF or a mobile web menu. Choose the format based on how easy it is to read on a phone and how your business will keep dishes and prices current.
The QR code and the menu do different jobs
The printed code takes a guest to a web address. The page or file at that address contains the menu. This distinction matters when you make changes: replacing content at the same stable destination can avoid reprinting every table card.
If the destination address changes, the printed code may need to change too. Agree who owns the destination and how it will be kept available. A link that depends on a paid service may also depend on keeping that subscription active.
Choose for the guest’s phone
A PDF can be a reasonable starting point if you already have an approved, readable menu and it is easy to keep up to date. A large print-layout PDF may require zooming and sideways scrolling on a small phone.
A responsive web menu can rearrange categories and text for the screen size. It also lets you plan dishes, prices and navigation around phone browsing. That comes with website setup and a decision about hosting and updates.
- Choose a PDF when the existing file is clear on phones and simple replacement is enough.
- Consider a web menu when you need phone-friendly categories, individual descriptions and a layout designed for scrolling.
- For either format, check contrast, readable type, image size and how quickly guests can reach the information.
- Keep an alternative available for guests who cannot access the digital menu.
Prepare one approved menu source
Before design begins, collect the menu in an editable document or spreadsheet. Each dish should have its name, category, description and approved price. Include sizes or variants so guests do not need to guess.
The restaurant supplies and approves dietary and allergen information. Design work cannot establish whether a dish is suitable for a particular dietary need. Agree the wording and responsibility before publishing.
Decide who updates it after launch
A menu can become inaccurate when the team that knows about price changes cannot update the published version. Choose a managed update arrangement or an editing tool as part of the scope.
The same menu link can be used on the table card and in an Instagram bio. Check both after changing the content. Avoid maintaining several separate copies unless someone is responsible for keeping them consistent.
- Who approves a price or dish change?
- Who makes the edit, and what does an update cost?
- Who owns and renews the domain or hosting?
- How will you check the published change?
A browsing menu does not automatically take orders
Ordering, payment, delivery and point-of-sale integrations are separate features. They introduce their own business rules, costs, access requirements and testing. Write them into the brief if guests need to complete those actions.
Eightweave’s core QR menu service covers the agreed browsing menu, a QR code linked to the published destination and table-card design. Menu size, languages, hosting, updates and additional features are discussed in the quotation.
Test the printed result at the table
Scan a final-size printed proof using more than one phone. Test in the lighting guests will actually use and confirm that the destination opens, prices are current and text can be read comfortably.
The QR graphic shown in Eightweave’s service illustration is a visual example, not a working code. A production code is generated for the actual published menu link and should be checked before a print run.
Plan the right scope for your business
Explore qr menus for restaurants & cafés for deliverables, what we need from you and what is scoped separately.
Prepare your project brief
