QR Menu Maker for Restaurants: Update Prices Without Reprinting

What good QR menus need

Mobile-first type, clear categories, allergens, and instant updates from one source of truth.

Keep categories short enough to scan on a phone: Starters, Mains, Desserts, Drinks. Keep the price on the same line as the dish so it does not wrap badly on narrow screens. List major allergens in plain words next to the dish. Use one project as the source of truth for both QR and print, so a mid-week edit does not create two versions.

Before you print, confirm three things:

• Hosted URL, not static file
• Works on slow 4G
• Matches print brand

How the hosted edit loop works

1. Open /build to reach the current Studio. Prepare a menu with sections, dishes, prices and descriptions, then verify every item.

2. Publish the approved menu file to a share link and download its QR. Export the matching PDF for paper menus.

3. When something changes, prepare and approve a new file version, then publish that version to the existing share link. The QR points to the published version, not an unpublished draft. Regenerate the PDF and replace any paper copies with changed prices.

4. Test the printed code at its real size before the next service.

No reprint of QR tents for a price change. No new QR for a sold-out item.

Example: a mid-service sold-out fix

Illustrative example: a small bistro sells out of sea bass on a busy Friday and features salmon instead. Staff prepare a revised menu marking sea bass as sold out, confirm the salmon price and review the new description. After they publish the approved file to the existing share link, guests scanning the same table tent see that version. Staff regenerate the counter PDF and replace outdated paper copies before using them.

The workflow is illustrative; actual steps follow the current /build editor.

Phone-readability, 4G and print-size checks

A QR menu is only as current and accessible as the page behind it.

Test the printed code at its real size, distance, lighting, and placement. Scan from a seated position, not just up close. Verify the destination on common phones and slower connections. Keep body type large, contrast high, and the QR destination lightweight — avoid forcing a large PDF download over the QR link. Keep a printed or staff-assisted alternative for dead batteries, no signal, or guests who prefer paper.

Practical rule: print one tent, place it on a real table, and scan it under warm dining light. If it takes more than a couple of seconds to focus, make the code larger, add quiet margin around it, and avoid glossy glare.

AI descriptions + live prices

Generate dish copy, review the facts, publish the approved file and regenerate the print PDF. Check both versions before service.

Use the menu description generator to draft short, specific copy — ingredients, cooking method, portion cue — then edit for accuracy. A live editor does not verify prices, availability, allergens, recipes, privacy, or local disclosure requirements. You confirm what is true before you publish.

MenuCrafters

Build at /build, export PDF, publish QR from the same project.

Limitations and assumptions

Test the printed code at its real size, distance, lighting, and placement; verify the destination on common phones and slower connections; and keep a printed or staff-assisted alternative. A live editor does not verify prices, availability, allergens, recipes, privacy, or local disclosure requirements.