A menu that machines can read, and why it fills tables
The format decides whether the menu is read at all. A menu published as text on a page can be read on a phone, quoted by an assistant answering a question and checked against dietary needs, while a PDF is a download that many people will not open. The content is the same, the reach is not.
What a PDF costs you
Three things. It has to be downloaded, which many people will not do on a phone with a weak connection. It is laid out for paper, so reading it means zooming and panning. And it is a poor source for anything answering a question about you, because the text sits inside a layout rather than in the page.
That last point has grown teeth. 45 percent of consumers used an AI tool to find a local business in 2026 against 6 percent a year earlier, and the systems that answer those questions work from readable page text.
Meanwhile the questions people bring to a menu are specific: is there something for a vegetarian, what does a main course cost, do you have a children's option. Each of those is one line of text and none of them survive being locked in a layout.
A PDF also ages badly. The version on the site is from last season, the one at the door is current, and nobody notices until a guest quotes a price that no longer exists.
What a text menu has to contain
The dishes, the prices and the date it applies from. Prices are subject to the same rule as anywhere else: the total price includes VAT and other price components, and where a price is itemised the total has to be highlighted.
Structure it the way a reader scans it: 3 to 5 groups, each with the dishes underneath, rather than one long list. A guest looking for a starter should reach it in 1 movement of the thumb.
Then mark the two or three properties people actually filter by. Whether something is vegetarian, whether it contains the common allergens you are required to declare, and whether a smaller portion exists. Those three answers convert more enquiries than a paragraph about the philosophy of the kitchen.
| Property | Text on a page | |
|---|---|---|
| Readable on a phone | With zooming | Directly |
| Quotable by an assistant | Poorly | Yes |
| Updated in | A design tool | One file |
| Findable by a search | Rarely | Yes |
| Ages | Silently | Visibly, so it gets fixed |
How to keep it current
Change the page when the kitchen changes, not at the end of the season. A menu page is 1 file, and editing it takes less time than printing anything.
And keep the PDF if you want, as a second copy for people who like it. Just do not let it be the only version, because the only version should be the one that can be read by everybody and everything.
Count what that saves. A menu of 30 dishes in 5 groups is 1 page, edited in 2 minutes, against a design file, an export, an upload and a link that has to be replaced. Four steps become one.
Questions and answers
Can I keep the PDF as well?
Do prices on a menu follow the total price rule?
How should the menu be structured?
What should be marked?
Sources
- Section 3 Preisangabenverordnung (PAngV) The total price duty that menu prices follow
- BrightLocal, Local Consumer Review Survey 2026 The growth in AI use for local search
