Menu Views
Day, hour, weekday — the when and how much of your traffic. Today / 7 days / 30 days comparison as standard.
Menu views, category clicks, item depth, hourly load, device split — live numbers, evidence-based menu decisions.
Each layer answers its own question: which category is opened, which item is read longest, which hour peaks, which device your guest uses, which question keeps coming back.
Day, hour, weekday — the when and how much of your traffic. Today / 7 days / 30 days comparison as standard.
Which categories open, which item detail is read — the real menu heat. The top-clicked item shows on the panel's first card.
Time spent on an item + session depth (how many items browsed) — quality of interest, beyond click count.
Mobile / tablet / desktop split; came via QR or direct link — the traffic source translates into a design decision.
Which language guests read in (32 languages) — tourist profile, month by month, clear.
Guests ask "is this vegan?", "does it contain peanuts?" — repeat concerns are cues for the menu text.
The panel scans each period and hands you the standout movements in one sentence. Approve; the Action Centre takes you to the right screen.
Avocado Toast increased views by 600% in the last 30 days — consider featuring it in the menu.
Espresso is down 80% over the last 30 days — a photo or description update may help.
Which hours did the menu open? A seven-day × twenty-four-hour grid makes your service moments visible. Staff planning and campaign design start from this grid.
This is the actual panel view — restaurant name masked.
Mobile-heavy — keep menu cards concise; desktop-heavy — depth can be increased. The QR / direct-link split shows the yield of your printed QR campaigns.
Unique sessions reaching each stage — visitors don't have to follow this order. The lost step is the position to improve.
For restaurants with the Takeaway module enabled, "Add to Cart" and "Order Confirmed" join this funnel. In a standard menu, item detail reading is the last step — the QrMenum menu does not need a cart; it's designed for a fast information + decision flow.
Most-clicked item to first position; never-opened items removed or rewritten. Menu health starts here.
High clicks + long detail reads — demand is solid; price-rise test is worth running. Low clicks — position or copy problem; try sequence + description changes.
In the Chain program, outlet-to-outlet comparison: which outlet gets 2× more views on the same item, at which hours — the head office sees it in one screen.
The Q Assistant's frequent questions surface missing information in the menu — add "contains: peanuts" next revision, and the same question drops off.
In the panel demo we'll walk through the analytics screen of a real menu together. Reach us on WhatsApp; 15 minutes to a live walkthrough.