Observation Centre

Evidence, not guesswork.
One panel, your data.

Menu views, category clicks, item depth, hourly load, device split — live numbers, evidence-based menu decisions.

Six measurement layers, one panel.

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.

Menu Views

Day, hour, weekday — the when and how much of your traffic. Today / 7 days / 30 days comparison as standard.

Category & Item Clicks

Which categories open, which item detail is read — the real menu heat. The top-clicked item shows on the panel's first card.

Item Detail Depth

Time spent on an item + session depth (how many items browsed) — quality of interest, beyond click count.

Device & Entry Point

Mobile / tablet / desktop split; came via QR or direct link — the traffic source translates into a design decision.

Language Preference

Which language guests read in (32 languages) — tourist profile, month by month, clear.

Q Assistant Questions

Guests ask "is this vegan?", "does it contain peanuts?" — repeat concerns are cues for the menu text.

This period's insights, generated automatically.

The panel scans each period and hands you the standout movements in one sentence. Approve; the Action Centre takes you to the right screen.

auto-generated

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.

Hourly load — week × hour.

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.

Hour
00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Mon
Tue
Wed
Thu
Fri
Sat
Sun

This is the actual panel view — restaurant name masked.

Device + entry point — where does the guest arrive from?

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.

Mobile %31
Tablet %0
Desktop %69
%9
1 outlet
%91
10 outlet

Menu journey.

Unique sessions reaching each stage — visitors don't have to follow this order. The lost step is the position to improve.

Total Visits
11 sessions
%100 all visitors
Home
11 sessions
%100 of visitors
Menu Discovery
1 sessions
%9 of visitors
Category Browse
1 sessions
%9 of visitors
Item Detail
2 sessions
%18 of visitors

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.

Turn data into decisions.

Menu order is no longer a hunch.

Most-clicked item to first position; never-opened items removed or rewritten. Menu health starts here.

Prove your pricing calls.

High clicks + long detail reads — demand is solid; price-rise test is worth running. Low clicks — position or copy problem; try sequence + description changes.

Compare outlets.

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.

Cues for the menu copy.

The Q Assistant's frequent questions surface missing information in the menu — add "contains: peanuts" next revision, and the same question drops off.

Analytics & Observation — FAQ

  1. Whose data is this? Does it go to a third party like Google Analytics?
    The data is yours. QrMenum collects it on its own infrastructure and shows it in the panel. Google Analytics 4 integration is optional — but not required; the data in the QrMenum panel is complete.
  2. Is it GDPR-safe?
    Yes — no personal data collected; anonymous interactions (view, click, language) counted. IPs kept truncated, cookies only for language preference. Detailed report available to your legal team.
  3. Can I export reports?
    Monthly reports export as PDF and CSV. Weekly email summaries can be turned on.
  4. How does outlet comparison work in the Chain program?
    The cross-outlet dashboard shows every outlet's metrics on one screen: ranking, delta (vs. last week), top-clicked item. No need to browse them one by one.
  5. Is the heatmap real-time?
    Views and clicks land in the panel with ≤5-minute delay. Live tracking during service peaks (lunch/dinner) is practical.
  6. How does the AI Nutrition Assistant connect to reports?
    The Q Assistant's FAQ list merges with the Menu Health layer: which item has missing nutrition and low clicks at once — the panel presents both signals together, with an action suggestion.

Would you like to see the numbers?

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.

WhatsApp'tan yazın Ortalama yanıt: 10 dk