Menu analytics and reporting

A paper menu tells you nothing

You can count plates leaving the kitchen. You cannot count the guests who read the dessert page and ordered nothing, or the ones who searched for a vegetarian dish you do not serve and put the phone down.

The demand you never see is the demand you never meet, and a menu is redesigned on a feeling because there was nothing else to redesign it on.

Counted where the menu is served

The counting happens on Zabuno's side, as the menu is served. Your guests are not handed to an advertising network in order for you to learn that forty people opened the menu.

The reports are also allowed to say "not yet". The dish report and the trend view withhold their figures below a minimum number of distinct visitors rather than dress up three people as a pattern, because a report that is wrong once is never read again.

How it works

Five events, named once Scan, menu opened, dish viewed, search with no result, order sent. The list is fixed in code, so a typo cannot quietly split a report in two.
Recorded by the server Guest events are posted to a rate-limited endpoint on your own domain and written to your workspace's rows.
Visitors are summarised, not identified A visitor is represented by a derived key that cannot be turned back into a person. Six opens from one table are not six guests.
Read as a summary or a shape One request answers "how much in this period", another answers "what shape did the period have" - by day, by hour, and against the period before it.
Turned into menu decisions The menu report ranks dishes by how many different people opened them and lists the ones nobody opened at all.

What the reports answer

How many scanned, how many opened: Both counts, plus the ratio between them, so a code that is scanned but never opens tells you something is wrong with the code or the connection.
Roughly how many people: An approximate count of distinct visitors, which is a different question from how many times the menu was opened.
Which branch and which code: The same period broken down by location and by individual QR code, so a quiet corner of the room is visible as a quiet corner.
Day by day, and against last time: Daily buckets across the range and a comparison with the previous period of the same length.
Which hours are busy: An hour-by-hour view of when menus are opened. Cells with too few visitors to be meaningful are withheld and counted, not shown as zero.
Which dishes people actually look at: Dishes ranked by distinct viewers, and the dishes nobody opened, so the menu can be shortened on evidence instead of instinct.
What guests looked for and did not find: Search terms that returned nothing, counted by how many different people searched them. This is the only demand a menu cannot show you any other way.

What you need

A plan that includes reporting	Analytics belongs to a paid plan. Without it the menu, the codes and the guest page keep working; only the reports are closed.
Permission inside the workspace	A team member needs the analytics permission. Without it the report is not merely empty, it is not there.
Enough visitors for the menu report	The dish report needs at least five distinct visitors in the range before it shows figures, and says so instead of showing zeros.
Scripts, for part of the picture	Scans and menu opens are recorded by the server. Dish views and searches are reported by the guest's browser, so a guest who blocks scripts still reads the menu but leaves no dish or search row.

What it does not do

Three ranges only Today, the last seven days and the last thirty days. There is no custom date range and no month-by-month history.
No revenue or sales reporting Reports count attention, not money. There is no turnover figure, no average spend and no best-selling list.
No export Reports are read on screen. There is no spreadsheet or document download.
Nothing about who the guest is No age, no gender, no location, no returning-visitor history. A visitor is a derived key inside one workspace and nothing more.
No automatic recommendations The reports show what happened. Deciding what to do about it is still your job.

Questions owners ask

How far back can I look?

Today, the last seven days, or the last thirty. Those are the three ranges the reports accept.

Why does the report say there is not enough data?

Because fewer than five different people opened dishes in that range. Three visitors are not a pattern, and a number built on them would send you rearranging the menu for nothing.

Can I see how much money the menu made?

No. Analytics counts scans, opens, dish views, searches and orders sent. It does not report turnover.

What is the most useful report?

Usually the searches that returned nothing. It is the only place a menu can tell you about a dish you do not serve.

Are my guests tracked by an advertising network?

These counts are recorded by Zabuno on your own domain and stay inside your workspace. A visitor is a derived key, not a person.

Analytics