Updating menu items and prices

The whole point of a digital menu: changes take effect everywhere, instantly, and the printed codes on your tables never change. Here's the day-to-day workflow.

Making changes

1. Go to Menus and open the menu.
2. Edit anything in place — names, descriptions, prices save when you click away from the field.
3. Click Publish when you're ready. Until then, customers keep seeing the previous version — the status pill reads "Unpublished changes" to remind you.

Made a mess of it? Revert changes restores the last published version.

86ing an item mid-service

The one exception to "publish when ready": each item's availability switch is built for speed. Flip it off when the kitchen runs out — the item shows a "Sold Out" badge (or drops off the menu entirely, depending on the page's menu element settings). Flip it back on tomorrow.

Seasonal and rotating menus

Two patterns that work well:

• One menu, edited in place — simplest when the menu evolves gradually.
• Multiple menus, swapped on the page — build "Summer Menu" and "Winter Menu" as separate menus, and switch which one the page's menu element points to when the season turns. Old menus can be retired (the Active toggle) so they can't accidentally appear anywhere, without deleting their contents.

What never changes

The QR codes. Whether you edit items, swap whole menus, or redesign the page, the printed codes keep pointing at the same page and always open the current published version. Print once; change forever.