Guide
How to update a restaurant menu
6 min read
To update a restaurant menu, edit the source once and let every format update from it: a hosted QR page changes instantly, and a print-ready PDF regenerates in seconds. This beats reprinting, which is slow, costly, and leaves stale prices on tables for weeks. The right setup turns a menu change from a project into a two-minute task you can do mid-service.
Why reprinting is the wrong default
Printed menus freeze your prices the day they leave the printer. When food costs move or a dish is discontinued, the menu lies until the next print run, and reprinting is expensive enough that operators delay it. A hosted menu removes that lag entirely: the page guests scan always shows the current truth, and the QR code never has to change.
What to update and how often
Menus drift in predictable ways, and a short routine keeps them honest. Review the high-impact changes on a regular cadence rather than waiting for a guest to point out a wrong price.
- Prices when ingredient costs shift meaningfully.
- Sold-out or 86'd items, marked the moment they run out.
- Seasonal additions and retirements at each rotation.
- Descriptions and allergen notes when a dish changes.
Edit the source, not each copy
The mistake is maintaining several disconnected versions — a PDF here, a printout there, a third on the website. Keep one source of menu data and publish every format from it. Change a price once and the hosted page, the QR link, and the downloadable PDF all reflect it, with no risk of a stale copy surviving on a table or a third-party listing.
Handle sold-out items in real time
Running out of a dish mid-service is routine; letting guests order it anyway is avoidable friction. A hosted menu lets a manager mark an item unavailable from a phone, so the next scan shows it as 86'd. That single edit prevents disappointed orders, saves the server an awkward correction, and keeps the floor moving during a rush.
Keep the QR code stable across changes
A well-built QR menu points to a fixed URL, so the printed code on your tables stays valid no matter how often the menu behind it changes. You never reprint table tents to fix a price. Update the data, and every existing code now resolves to the new menu — the link is permanent even as the content stays fluid.
Quick steps
- 1
Open the menu source
Edit the single hosted menu rather than any individual printed or PDF copy.
- 2
Make the change
Adjust prices, swap dishes, or mark items sold out in the editor.
- 3
Publish
Republish so the hosted page, QR link, and PDF all reflect the change at once.
- 4
Verify on a phone
Scan the existing code to confirm the live menu shows the update.
Frequently asked questions
- Do I have to reprint my QR code when I change the menu?
- No. A hosted QR menu points to a fixed URL, so the printed code stays valid. You edit the menu behind it, and every existing code resolves to the updated version.
- How do I mark a dish as sold out during service?
- With a hosted menu, a manager can mark an item unavailable from a phone, and the next guest scan shows it as 86'd. No reprint, and no crossing out by hand.
- How often should I update menu prices?
- Review prices whenever ingredient costs shift meaningfully, and at each seasonal rotation. A hosted menu makes the change quick enough that there is no reason to let prices fall out of date.