Every scan, browse and search on your Scanqur menu leaves a trace: which dishes get attention, which categories carry the load, when your guests look and from where. Analytics turns those traces into the clearest picture of your business you’ve ever had.
Kumo Ramen
This week · 412 views
For as long as menus have existed, merchants have guessed. Which dish do people consider and reject? Is the new category getting found? Did the price change scare anyone off? A paper menu absorbs all of these questions silently. Even most digital menus only tell you they were opened, not what happened inside.
Because a Scanqur menu is structured (categories, products, languages), it can report at the same resolution: views per product, per category, and visitors over time. There is no tracking setup and no analytics account to connect. If your menu is live, your data is already accumulating.
The dashboard keeps the metrics deliberately few and legible:
Anyone who changes their menu more than never. Restaurant owners deciding what to cut, cafés timing their specials, shops seeing which product families draw browsers, and multi-role teams where the manager reads reports while the kitchen runs service.
Without view counts, the dish nobody considers survives on nostalgia, occupying menu space, prep time and inventory.
Raising a price without knowing a dish’s popularity is a coin flip. Raising it on your most-viewed dish is a strategy.
Hours spent photographing and describing dishes guests never open, while the actual crowd-pleaser sits with no photo at position nine.
Analytics starts working the moment your menu is live. No pixels, no tags, no third-party analytics account.
See which dishes get viewed most, and cross-check against orders to spot the "much looked at, rarely bought" dishes whose price or photo needs work.
Know which sections carry your menu and which are dead weight, before you reorganise.
Counts and trends, not personal profiles. Your guests browse a menu, not a surveillance system.
Analytics only pays when it changes something. This is the loop.
Publish your menu and resist conclusions for a fortnight. You want typical weeks, not opening-night curiosity spikes.
Open Analytics: views, unique visitors, top products, top categories. Write down the one thing that surprises you, there is always one.
Tip: The most common surprise: the dish the owner considers "the star" is rarely the most-viewed one.
Set your top-viewed items against what actually gets ordered. High views with low orders means the price, photo or description needs work. Low views with loyal orders means a regulars’ favourite that new guests never find, so move it up.
Promote a dish, cut a dead one, rename a category. One change at a time is what keeps cause and effect readable.
Did the change move the numbers? Keep it or revert it, then pick the next experiment. Merchants who run this loop monthly compound small wins into a visibly better menu by year’s end.
Judge trends, not days
A rainy Tuesday proves nothing. Week-over-week and month-over-month movements are where truth lives.
Watch peak hours
When views cluster tells you when decisions happen, useful for timing specials, staffing and even when to post on Instagram.
Check analytics after every menu change
Every price move, photo or reorder is an experiment. The numbers two weeks later are its result, collect it.
Don’t equate views with sales
Views measure attention. The gap between attention and orders is exactly where the actionable insight sits, mind the gap, don’t ignore it.
Don’t change five things at once
If views jump after you changed the theme, three prices and the category order, you learned nothing about anything.
Don’t let a dashboard override the dining room
Data narrows the questions; your kitchen and your regulars still answer some of them. Use both.
Kenji assumed his tonkotsu, the house classic, first on the menu, was the star. Analytics disagreed: the most-viewed item was his spicy miso, sitting seventh in the list without a photo, and the "Sides" category was drawing almost no visits at all.
He made two changes: moved spicy miso to the top with a proper photo, and folded the failing "Sides" category into "Ramen add-ons" attached to what people actually browsed.
The next month’s numbers told the story: spicy miso views up sharply and now matched by orders, add-ons finally getting seen, and, the part he didn’t expect, evening view counts revealed a 22:00 browsing spike from people planning tomorrow’s lunch. He now posts his daily special at 21:45.
Total time invested: two five-minute reading sessions and one photo.
#1
spicy miso, from position 7
2×5 min
analytics time per month
22:00
the browsing spike he never knew about
Analytics tells you what to change, these features are where you change it.
Complete or cancel with a reason, keep every order on file, and read revenue, average order value and cancellation rate monthly.
Read articleStructure your catalog, hide sold-out dishes in seconds and keep every price current, all from your phone.
Read articleReplace your paper menu with a digital one: add your dishes, pick a theme, print the code. The complete guide, free.
Read articleYour menu is already collecting the answers. Open your Scanqur analytics and make next month’s menu the informed one.
Scanqur tracks millions of menu views for merchants worldwide.