Digital menu
Discuss publishing a QR food menu and editing prices without reprinting. Verify publishing delay, caching and the guest view; instant updates have not been measured.
Illustrative screens with sample data.
Who this is for
Restaurant managers and staff updating the guest-facing food offer.
Daily workflow
Illustrative scenario — not a customer case study
The manager updates dishes and prices; staff check the guest-facing QR before service; guests browse on their phones. A menu view alone does not identify a guest or establish marketing consent.
Preparation checklist
- 01
Organize food items and current prices; give the kitchen and editor one correction route.
- 02
Test the QR destination and readability on a small guest phone before printing more codes.
- 03
Before each service, check changed dishes and retain a staff-assisted way to explain the offer.
Questions before you decide
Does a QR menu visit identify the guest?
No. Anonymous menu browsing is not a known guest record or marketing consent. Treat any personal-data link as a separate permission and scope question; marketing campaigns are coming soon.
Where can I verify the price and billing unit?
Use the published pricing page for listed modules and packages. HR is per organization; other listed modules are per establishment. Unlisted scope and integrations require a quotation, not an assumed package inclusion.
Availability and scope
Listed in the public offering. Confirm actual availability, permissions and your exact workflow in a demo before ordering.
Limits to check
Publishing a menu is not ordering, checkout or an allergen-compliance guarantee. Have responsible staff verify food information and do not infer consent from a page view.
Start simply.
Digital menu