Know your numbers

Your menu has opinions. Analytics lets it speak.

Every scan, browse and search on your Scanqur menu leaves a trace: which dishes get attention and which categories carry the load. The free plan shows the essentials over 30 days; Pro adds busiest hours, where visits come from, languages read and a year of history.

By Mariem AUpdated on November 6, 2026 6 min read

  • Built in, no setup
  • Privacy-friendly
  • Free to start
Menu analytics: see what guests browse, love and ignore in the Scanqur dashboard, for the Chez Léon example business

The basics

What Scanqur analytics shows you

The four numbers that matter

The dashboard keeps the metrics deliberately few and legible:

  • Views: how often your menu is opened, day by day
  • Unique visitors: how many different people that represents
  • Top products: the dishes guests actually look at most
  • Top categories: where attention concentrates across your menu

Who gets value from it

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.

Step-by-step guide

From numbers to a better menu

Analytics only pays when it changes something. This is the loop.

  1. 1

    Let two normal weeks accumulate

    Publish your menu and resist conclusions for a fortnight. You want typical weeks, not opening-night curiosity spikes.

  2. 2

    Read the four numbers

    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.

  3. 3

    Compare attention with sales

    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.

  4. 4

    Change exactly one thing

    Promote a dish, cut a dead one, rename a category. One change at a time is what keeps cause and effect readable.

    Organize products and categories that sell

  5. 5

    Re-read next month and keep the loop going

    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.

Reading data well

Analytics best practices

Do this

  • 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, which is useful for timing specials, staffing and even posting on Instagram. Busiest hours are part of Pro’s statistics.

  • 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.

Avoid this

  • 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.

The Scanqur way

Analytics a busy merchant will actually read

  • Zero-setup tracking

    Analytics starts working the moment your menu is live. No pixels, no tags, no third-party analytics account.

  • Product-level attention

    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.

  • Category insight

    Know which sections carry your menu and which are dead weight, before you reorganise.

  • Privacy-friendly by design

    Counts and trends, not personal profiles. Your public menu loads no advertising or analytics cookies; your guests browse a menu, not a surveillance system.

Illustrative example

A ramen bar promotes its hidden bestseller

A fictional business, to show how the pieces fit together.

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, the busiest-hours chart in Pro 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.

Common questions

Menu analytics, answered

Stop guessing what your guests want

Your menu is already collecting the answers. Open your Scanqur analytics and make next month’s menu the informed one.

Menu statistics are included in the free plan, over 30 days.

  • Item-level insight
  • Privacy-friendly