Maximize Sales with QR Menu Analytics Data Insights
A modern QR menu in 2026 captures eight categories of data, all anonymous, all GDPR-friendly when handled properly:
TL;DR — Key Takeaways
A modern QR menu surfaces five categories of data: per-dish view rates, language splits, time-on-menu, peak-scan windows and exit points. Each one drives a different operational decision.
The single most actionable metric is theview-to-order ratio: dishes that get viewed often but ordered rarely are description, photo or pricing problems with clear fixes.
Allergen filter usage tells you about your guest population in ways no other data point can — including, often, that you have far more allergic guests than you assume.
All of this isGDPR-compliant by designwhen handled correctly — restaurant menu analytics work with anonymous engagement data, not personal identifiers.
Operators who review their QR menu analytics weekly typically lift average check size 8–14% within 90 days, purely from data-driven menu engineering.
What data can I get from a QR menu?
A modern QR menu in 2026 captures eight categories of data, all anonymous, all GDPR-friendly when handled properly:
1. Scan count and timing.How many guests scanned the QR, broken down by hour, day, and location (which printed asset they scanned). Tells you about traffic patterns and which placements are pulling weight.
2. Per-dish view rate.How many menu visitors actually looked at each dish (clicked, hovered, scrolled past). The underused goldmine of menu engineering.
3. View-to-order ratio.Per-dish view rate divided by per-dish order rate (when integrated with a POS or order-pay system). The single most actionable diagnostic on your menu.
4. Time on dish.How long guests linger on each item. Long lingering on an unordered dish often signals decision friction — the description isn't selling it, the price feels off, or the photo isn't there.
5. Language split.What percentage of scans use which language. Tells you whether your multilingual investment matches your actual guest mix.
6. Allergen filter usage.Which allergens are most-filtered. Tells you about your guest population (more nut-allergic than you thought, more vegan than you thought, more gluten-free than you thought).
7. Section navigation flow.Which categories guests move between and where they drop off. Tells you whether your menu structure matches your guest's mental model.
8. Exit points.Where guests close the menu. If 40% exit at the price column, your perceived-value problem is at pricing.
These metrics are useless to you in raw form. They're powerful when interpreted, and they should be reviewed weekly — not quarterly.
Which menu items get viewed but not ordered? Why does that gap matter?
This is the most actionable question QR menu analytics can answer.
A "high view, low order" dish is one that gets attention but doesn't convert. There are five common causes:
1. The description doesn't sell the dish.A dish titled "Grilled Branzino" with a description of "Mediterranean sea bass with seasonal vegetables" is technically accurate but doesn't communicate why a guest should order it. Rewrite to highlight what makes it distinct: "Whole branzino, salt-baked tableside, served with charred lemon and a Sicilian salmoriglio sauce."
2. The price feels off relative to the description.If a dish reads as "comfort food" but is priced at the high-end of the menu, guests view but don't buy. Either reframe the dish (premium ingredients, technique, region of origin) or reprice.
3. There's no photo.This is the easiest fix. Photos lift conversion 25–30% on average. AI-generated dish photography (available in platforms likeIntermenuat near-zero marginal cost) closes this gap immediately.
4. The dish has a competing dish nearby on the menu.If a guest is choosing between two similar dishes, view rate goes up on both but order rate concentrates on whichever wins the comparison. Differentiate the descriptions.
5. The dish has an allergen or dietary marker that excludes the guest population.If 30% of your guests are filtering for "no shellfish" and your octopus dish has high views, the issue is structural — those views are guests confirming what they can't eat.
The diagnostic workflow: pull the top 5 "high-view low-order" dishes from your analytics each month, hypothesize the cause, change one thing per dish, run another month, see what moved. This is the classic A/B testing rhythm — and it's what menu engineering looks like in 2026.
Can I track peak ordering times by table?
Mostly yes, with caveats.
What you can track:scan timing per QR code, which (if you have one QR per table) effectively gives you a per-table view of menu engagement timing. You can see that table 7 scanned at 7:42pm and stayed on the menu for 6 minutes.
What you can't track without integration:the actual order from that table — that data lives in your POS system. Modern QR menu platforms increasingly integrate with major POS systems (Toast, Square, Lightspeed, Revel) so the menu engagement data and the order data join in one place.
What this enables operationally:
Identify which tables are slow to convert (long menu time, late order) — often a sign of ambiguous menu content.
Identify which tables convert quickly (short menu time, fast order) — often a sign of repeat guests or strong menu clarity.
Spot patterns in service quality by section — if a server's tables consistently take longer to order, the bottleneck might be service, not menu.
The per-table data also helps with capacity planning. If your dinner service consistently shows a 6-minute average decision time on Friday nights but only 3 minutes on Tuesdays, your Friday service planning needs to account for the longer menu phase.
How do I A/B test menu changes with QR analytics?
The three most useful menu A/B tests:
Test 1: Dish description.Run two versions of a dish description for two weeks each, see which lifts the view-to-order ratio. Sample size needed: at least 200 views per version for statistical confidence.
Test 2: Dish position.Move a high-margin dish from third in its section to first. Most QR menus have section-position effects similar to printed menus — items at the top of a section get more attention.
Test 3: Photo vs no photo.The simplest and highest-impact test. Add a photo to a dish that didn't have one and watch the order rate move. The lift is typically 25–30% in the photographed dish.
The mechanics in modern menu platforms: many support "experiment mode" where 50% of scans see version A and 50% see version B, with results summarized in the dashboard. Without this feature, you can run sequential tests (version A for two weeks, then version B for two weeks) — slightly less rigorous but still informative.
Intermenusupports both sequential and split testing modes within the same menu, so a description rewrite or a new photo can be tested against the original without exporting data into a separate analytics tool.
Is QR menu data GDPR compliant?
Yes — when handled correctly. The compliance frame is simpler than most operators expect.
What QR menu analytics typically collect:
Anonymous scan events (timestamp, language, device type)
Anonymous interaction events (which dish was viewed, time on page)
Anonymous filter usage (which allergens were filtered)
What QR menu analytics should NOT collect without explicit consent:
Email, name, phone number
Precise GPS location
Cross-site tracking identifiers
What you need to do for GDPR compliance:
Privacy notice on the menu page.A short, clear paragraph explaining that anonymous engagement data is collected to improve the menu. Most platforms include this template.
Cookie/consent banner if you use any tracking that requires consent.Default analytics (anonymous, no PII) typically don't require a banner. Ad-platform tracking pixels do.
Data retention policy.Most platforms default to 12-24 months of retention; this is fine for GDPR purposes.
A way for guests to opt out.Usually a "do not track" link in the footer.
For most independent restaurants using a reputable hospitality platform, GDPR compliance is handled by default — the platform sets the right cookie behavior, the retention policy, and the privacy notice. For enterprise hotel groups, additional compliance documentation (DPIAs, processor agreements) may be required.
Don't let GDPR concerns scare you off menu analytics. Anonymous engagement data is exactly what GDPR was designed to permit. The compliance hard part is the personal-data-tracking the menu shouldn't be doing in the first place.
What's the right data to look at weekly vs quarterly?
Weekly review (5 minutes):
Total scan count vs the same week last month
Top 5 most-viewed dishes (any change?)
Top 5 high-view-low-order dishes (any to address?)
Any technical issues (slow load times, scan failures, error rates)
Monthly review (30 minutes):
Per-language scan distribution (is your translation investment paying off?)
Allergen filter usage trends (is your guest population shifting?)
Section navigation flow (where are guests dropping off?)
A/B test results from the prior month
Average check size per language (the highest-leverage data point in tourist-area restaurants)
Quarterly review (2 hours):
Full menu engineering review using view-to-order ratios
Print signage placement performance (which QR placements are pulling weight?)
Year-over-year scan growth
Strategic decisions: language additions, allergen visibility upgrades, photo coverage gaps
The weekly cadence is the one that compounds. Most operators do a quarterly review and miss most of the value. The 5-minute weekly check catches small problems before they become permanent menu features.
What's a "good" QR menu engagement rate?
Benchmarks from cross-restaurant data, useful as rough comparisons:
Metric Below average Average Excellent Scan rate per cover <40% 60–75% >85% Avg time on menu <90 sec 2–4 min 4–6 min Multilingual usage rate (tourist areas) <15% 25–35% >40% View-to-order ratio (median dish) <0.4 0.5–0.7 >0.7 Allergen filter usage <3% 5–10% >10% Photo coverage (% of dishes with photo) <30% 50–70% >85%
These are rough benchmarks. Your specific numbers depend on your cuisine, your guest mix, and your dining context (a fine-dining restaurant with paper menus alongside QR will have lower scan rates than a casual restaurant on QR-only — this is fine).
How to use analytics to drive a 10% AOV lift in 90 days
The standard analytics-driven AOV lift workflow:
Days 1-7:Set up your menu analytics dashboard. Configure the metrics above. Verify scan tracking works across all your QR placements.
Days 8-30:Pull your top 10 "high view, low order" dishes. Hypothesize causes. Make one change per dish (rewrite description, add photo, adjust price, reposition).
Days 31-60:Measure impact. Some changes will work, some won't. Roll back failures. Identify your top 5 successful changes; replicate the pattern across other dishes.
Days 61-90:Apply pattern to the next layer of dishes. Run an A/B test on the highest-margin dish to optimize its description.
By day 90, most operators see a 8–14% lift in average check size, driven entirely by menu engineering decisions backed by data. The work is 30 minutes per week, not 30 hours.
Frequently Asked Questions
What data can I get from a QR menu?Scan count, per-dish view rate, view-to-order ratio, time on dish, language split, allergen filter usage, navigation flow, and exit points. All anonymous, GDPR-friendly.
Which menu items get viewed but not ordered?This is the highest-value diagnostic. High-view, low-order dishes are usually description, photo, or pricing problems with clear fixes.
Can I track peak ordering times by table?Yes, with one QR per table. Combined with POS integration, this gives a full picture of timing per table.
How do I A/B test menu changes?Most modern menu platforms support split testing (50/50 traffic) or sequential testing (run version A for two weeks, then B). 200+ views per version is the rough threshold for statistical confidence.
Is QR menu data GDPR compliant?Yes, when collected anonymously. Standard QR menu analytics use no personal data and require no consent banner. Reputable platforms handle compliance by default.
See Your Menu's Hidden Bestsellers
If you've been running a QR menu for a year and never opened the analytics, there are dishes in your menu costing you money quietly — viewed often, ordered rarely, fixable in 10 minutes.
Intermenuopens this layer of insight in the dashboard from day one — per-dish view rates, language splits, allergen filter trends — alongside the multilingual menu and AI dish photography that often drive the fixes.
Open your menu's analytics and find your 3 quick-win dishes →