Restaurant Menu Template: What a Good Template Must Include (and When to Go Digital)

A menu template rarely fails on the day it is designed. It fails weeks later.

The kitchen swaps a sauce, and nobody updates the allergen line. A price changes on the till but not on the laminated card. A new dish has to fit into a column that was never built to stretch.

By then the template is no longer just a layout. It is a record the restaurant is accountable for, and every update is a chance for that record to drift away from what is actually served.

That is the idea behind this guide: a good template is designed for the update, not for the first print. Below you will find the structure that survives a busy service, the information EU rules require, and the clarity guests expect on allergens, prices and descriptions. Then we look at when a template stops being enough, and how to move to a digital menu without losing a service.

The Anatomy of a Restaurant Menu Template That Survives a Busy Service

Picture a Saturday at 8 pm. Guests skim the menu mid-conversation. Servers point at lines they know by heart. The kitchen needs every order to match a real dish.

Nobody reads the menu the way you designed it. They look for one thing at a time: a dish, a price, an allergen. A restaurant menu template earns its keep by giving each of those a fixed place, in the same order, after every update.

The non-negotiable blocks: header, sections, item, price, labels, footer

Every working food menu template, printed or digital, repeats the same six blocks. Think of them as the fields of a form: if a piece of information has no fixed place, someone will improvise one under pressure.

Branding (logo, colours, fonts) lives in the header. Whether you start from a menu design template or build your own, keep it consistent across print and screen versions, so guests recognise the menu wherever they meet it.

The item block needs one more thing: room for modifiers, add-ons and upgrades, such as extra toppings or a larger size. Without a slot for them, staff improvise prices and the bill becomes a negotiation. If your current template has no such slot, add it before the next price update.

Hierarchy: why guests read your menu like a book

Menu psychology loves confident rules. The best known is the “sweet spot”: the idea that a diner’s eyes land first on the upper right of a page.

The evidence for it is thin. One 2012 eye-tracking study by Sybil Yang, reported by White Hutchinson Leisure & Learning Group, found no support for the sweet spot. Diners read menus sequentially, the way they read a book.

It is a single study, not a law of nature. But it is a sounder basis for layout than folklore, and it leads to a simple rule: design for reading order.

In practice, order your menu sections the way the meal unfolds. Let typography and white space make the visual hierarchy follow that order: clear section headings, item names heavier than descriptions, and enough space to find your place again after a conversation. Keep menu prices in one consistent format and position, so the eye is not pulled from the dish to a column of numbers.

Where hotel and multi-outlet menus need extra fields

Hotels often run one kitchen and several menus. That adds fields a single café can skip: outlet name, serving hours, room-service availability and outlet-specific prices.

Illustrative example: a hotel kitchen serves the same club sandwich in the lobby bar and through room service, with a delivery charge on the second. If each outlet’s menu is a separate document, one price change means editing several files, and sooner or later one falls out of date.

The fix is structural. Keep shared item fields (name, description, allergens) in one place and a separate price per outlet. The dish is described once; each price changes only where it applies.

The Legal Layer: What an EU Menu Must Show and What Is Only Good Practice

Illustrative example: put three bistro menus side by side, from Dublin, Munich and Lyon. One spells out allergens in print. One carries numbered footnotes next to the sausages. One states where the beef comes from.

All three answer to the same EU regulation. The differences come from what Brussels left to national governments. That split, one EU rule plus national extras, is the key to a template that works in your country.

EU-wide: allergens are the only mandatory particular

The rulebook is Regulation (EU) No 1169/2011 on Food Information to Consumers, applied since 13 December 2014.

For unpackaged food, Article 44(1) makes only one item mandatory: allergen information, meaning the presence of any of the 14 EU allergens in a dish. Everything else in Articles 9 and 10 stays optional unless a Member State requires it.

For your template, that means one field is non-negotiable anywhere in the EU: allergen data for every dish.

National extras: Ireland, Germany, France as examples

Article 44(2) lets each Member State decide how allergen information is made available and, where relevant, its form and presentation. Three countries show how far that freedom goes.

Ireland asks for allergens in writing. Under S.I. No. 489 of 2014, as updated by S.I. No. 656 of 2024, allergen information must be written, easy to find and available before purchase without the customer having to ask. A “just ask your server” policy falls short.

Germany adds additive declarations. Under § 5 of the LMZDV, non-prepacked food must carry statements such as “mit Farbstoff”, “mit Konservierungsstoff” or “mit Geschmacksverstärker”. That is why German menus carry numbered footnotes.

France adds price display and meat origin. Each item must show its price with “boisson comprise” or “boisson non comprise”, and drinks are listed by type and serving size. Décret n° 2002-1465 requires restaurants to state the origin of beef. Décret n° 2022-65 of 26 January 2022 extended this to pork, sheep and poultry bought raw, as a temporary measure from 1 March 2022 to 29 February 2024. Décret n° 2025-141 of 13 February 2025 made that extension permanent from 19 February 2025.

The practical step: start with the EU allergen field, then add your country’s extras as fixed template fields rather than notes someone has to remember.

Recommended, not required: calories, alcohol strength, origin claims

Some details only feel mandatory.

Alcohol strength is one. Under Article 9(1)(k), alcoholic strength by volume is compulsory on prepacked drinks above 1.2% alcohol, but not for drinks poured at your bar.

Calories are another. Nutrition values have been mandatory on packaging since 13 December 2016, but they stay optional on a restaurant menu unless national law says otherwise.

Optional is not useless. Alcohol strength helps guests pace a tasting flight, and an origin line can justify a price. The condition is accuracy: every claim you choose to print is one you have to keep true.

National rules change, so check with your food authority. This overview is orientation, not legal advice.

Allergens on the Page: 14 Substances, Four Ways to Show Them

A guest who asks “anything with nuts in this?” wants an answer about one dish, not about the kitchen in general.

The Food Safety Authority of Ireland (FSAI) makes the same point. A generic line such as “Our food contains…” is not acceptable; allergens must be tied to the specific dish, as in “spaghetti bolognaise – contains milk, celery, wheat”.

The list of what to track is fixed. Annex II of Regulation (EU) No 1169/2011 names 14 categories: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame seeds, sulphur dioxide and sulphites, lupin and molluscs.

The audience is large. A 2023 systematic review of 110 studies by Spolidoro et al. in Allergy put self-reported lifetime food allergy prevalence in Europe at 19.9%, against 0.8% confirmed by food challenge. Confirmed or not, that is a lot of guests who will look for allergen information before they order.

Icons, numbered codes, a separate allergen matrix or a filterable digital menu

There is more than one acceptable way to show allergens, and Germany shows the range. Under § 4(3) LMIDV, allergen information for loose food may be offered in writing or electronically, if it is directly and easily accessible and a notice explains how guests get it. Under § 4(4), staff may answer orally only if a written or electronic allergen record exists, is available to authorities and guests on request, and a visible notice says so.

Look at the weak points together and a pattern appears: each method is only as reliable as the record behind it. And whichever you choose, a QR code menu that works as a web page still needs a visible notice saying where the allergen information lives.

The ‘may contain’ grey zone

Article 36(3)(a) of the same regulation foresees implementing acts on the unintentional presence of allergens. Until they exist, treat ‘may contain’ like an alarm: useful when it is rare, ignored when it sounds all the time.

Use it only where cross-contact is a genuine risk. Printed on everything, it stops meaning anything.

Keeping the allergen record current when a supplier changes

Typical scenario: a supplier swaps the pesto, and the new one contains cashews. The printed menu, the allergen matrix and the staff record are three separate documents, and each one needs the change.

This is where menu updates and version control matter. Keep one dated master record, change it first, then republish every format from it. The order is the point: if formats are edited one by one, sooner or later one is missed.

A digital menu shortens that chain, because one edit reaches every table.

Prices, VAT and Service Charges Without Surprises at the Table

Many arguments over a restaurant bill start with a line the guest never saw on the menu: a cover charge, a service percentage, a “plus VAT” note in small type. The amount may be small. The damage to trust is not.

The rule that prevents it is simple: every charge the guest will pay should be visible before they order.

The final price is the price: taxes included

Directive 98/6/EC on price indication defines the selling price as the final price including VAT and all other taxes.

The Unfair Commercial Practices Directive 2005/29/EC covers any goods or service, so menu prices fall within its scope. Its Article 7(4)(c) treats the tax-inclusive price, plus any additional charges, as material information in an invitation to purchase.

For a template, that means one VAT-inclusive price column. No net figures, and no arithmetic left to the guest.

Service and cover charges: say it on the menu, not on the bill

France offers the most precise model. According to CCI Paris Île-de-France, the arrêté of 27 March 1987, amended on 29 June 1990, requires prices including taxes and service, with “prix service compris” followed by the service rate in brackets. Menus and a drinks card must also be visible from outside during service.

Elsewhere, borrow the principle: reserve a fixed footer line for service and cover charges. Once the line is part of the template, the information no longer depends on whoever edits the file.

“A charge that first appears on the bill is a charge the guest remembers for the wrong reason.”

Currency signs and price formatting

One 2009 Cornell Center for Hospitality Research study by Yang, Kimes and Sessarego found that 201 diners spent on average $5.55, about 8%, more when prices appeared without a currency sign.

It is a single study, not a law of nature, so treat it as a hint rather than a lever. The safer lesson is consistency: plain numerals, consistent decimals and aligned columns, with the currency stated once beside the service note.

Descriptions and Dietary Labels That Inform Before They Sell

Before a guest looks at the price, they usually want two answers: what is on the plate, and can they eat it? A menu that answers both saves a trip to the kitchen.

What a good description does in 15–25 words

The best menu item descriptions do three jobs. They name the main ingredient, the cooking method and one detail that sets the dish apart.

An illustrative example: “Lamb shoulder roasted for six hours, served on white beans with salsa verde and charred lemon.” Ingredient, method and a distinguishing detail, all in 16 words.

There is evidence that this pays. McCall and Lynn (2008), reviewed by Spence in Foods (2018), found in a study with 160 participants that more complex descriptions raised perceived quality, expected price and purchase intention.

The catch: every adjective is a promise the kitchen must keep. Treat the rest of menu psychology with the same care. The popular “sweet spot” claim is not borne out by eye-tracking data, and individual price-format effects rest on single studies.

Menu photos can support a description, but they have a limit: a photo cannot show that the dressing contains mustard.

Dietary labels: a small, consistent legend

Dietary labels and icons (vegan, vegetarian, gluten-free) work like road signs. They help only when each one means the same thing on every page.

Keep the set small. Put each icon in the same place next to the dish name, and explain them once in a legend guests can find easily. Avoid overlapping variants such as “plant-based”, “vegan-friendly” and “V*” on the same menu.

These icons sit alongside allergen marking. They never replace it.

‘Gluten-free’ has a legal threshold; ‘vegan’ does not (yet)

The two labels look alike on a menu but carry different legal weight.

“Gluten-free” is a regulated claim. Commission Implementing Regulation (EU) No 828/2014 sets maximum gluten levels for “gluten-free” and “very low gluten” claims, measured in the food as sold. For a kitchen that shares flour and fryers, that is a real commitment. If you cannot guarantee it, leave the claim off, list the ingredients and flag the risk of cross-contact.

“Vegan” and “vegetarian” have no such numeric rule. Article 36(3)(b) of Regulation (EU) No 1169/2011 foresees implementing acts on suitability for vegetarians or vegans. Until they exist, your legend sets the definition, so write it down and apply it to every dish.

Menus for Guests Who Don’t Read Your Language

Typical scenario: on a busy terrace in a tourist location, the slowest table is the one holding a menu nobody at it can read. Guests point, ask the server to translate, then order the one dish they recognise.

The table is not slow because of the guests. It is slow because the menu was written for only part of the room.

Who is reading your menu in a tourist location

Across the EU, foreign guests now spend almost as many nights in tourist accommodation as domestic ones. A menu written in one language serves only part of that audience.

English does not close the gap, because fewer than half of Europeans speak it. Younger guests are more often multilingual, but they are rarely the whole table.

CSA Research’s “Can’t Read, Won’t Buy” study of 8,709 consumers in 29 countries found that 76% of online shoppers prefer products with information in their own language, and 40% never buy from websites in other languages. A menu is not a website, but the instinct is the same.

Why a second printed language column breaks the layout

Adding a language to a printed menu sounds like a copy-and-paste job. In practice, it changes the geometry of the page.

Translations often run longer, so names wrap, prices drift from their dishes and allergen markers lose alignment. A third language either shrinks the type or doubles the length. And every price change now has to be made in several places.

This is where a multilingual menu tends to move off paper. A digital menu opened from a QR code and built as a web page lets each guest switch language, while the printed copy stays clean.

Translating dish names vs explaining them

Menu translation is not word-for-word work. A literal translation of a regional dish name can mean nothing to a visitor, or the wrong thing.

A better pattern: keep the original name and add one line on what is on the plate, how it is cooked and what it contains. Guests know what they are ordering, and the dish keeps its identity.

Formats That Fit the Room: A4, A3, Table Tents and Boards

A menu that looks crisp on a designer’s screen can fail on a candle-lit two-top or a windy terrace. So decide on the object before you settle typography: what will the guest hold, and where?

Matching format to service style

ISO 216 fixes the paper sizes most European printers use: A4 is 210 × 297 mm, A3 is 297 × 420 mm and A5 is 148 × 210 mm, each half the area of the next size up.

That ratio is useful. A layout built for A4 scales cleanly to A3 for a window display, or down to A5 for table tents and small cards such as a dessert menu.

Each format trades space for discipline. A bifold gives room for sections and white space but invites skimming; a single page forces you to edit. Either way, send the printer a print-ready PDF, not an editable file.

Readability: font size, contrast, lighting

Restaurant lighting is rarely kind to thin fonts or grey text on cream paper. The simplest test costs nothing: print the menu and read it at your dimmest table.

Strong contrast and a generous font size help older guests and anyone reading in a second language.

The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 and covers services including e-commerce, so it bears on online ordering more than on paper. Microenterprises providing services (fewer than 10 persons, turnover or balance sheet total up to EUR 2 million) are exempt under Article 4(5). Even so, the Act’s principles remain a sensible benchmark for any menu.

Boards and daily specials

Typical scenario: a bistro chalks three lunch dishes on a board each morning. The board sits outside the template, yet guests still need allergen and price details for those dishes.

The fix is a matching printed insert or staff sheet that follows the same rules as the main menu.

Print, PDF or Web-Page Menu: What Each Format Really Costs You

A dish sells out. A supplier changes. A new invoice moves a price. Each change forces someone to reprint, re-export or simply edit, and the format you chose decides which of the three it will be.

Why a PDF behind a QR code is still a paper menu

A print-ready PDF is the natural end point of a printed menu, and putting it behind a QR code feels like going digital. Mostly, it is not.

Guests pinch and zoom through a page laid out for A4. Every correction means a new export and upload. Version control stays manual, as old files linger in shared links and screenshots. And the layout ignores on-screen font size and contrast, a weakness the European Accessibility Act has made harder to overlook.

In short, a PDF moves paper onto a screen without changing how the menu is updated.

What a web-page menu changes: updates, languages, allergen filters

A digital menu built as a web page fits the screen it is opened on. Menu updates happen in one place and reach the next guest who scans. Languages, allergen filters and menu photos sit on one page instead of in separate files.

The audience is online. Eurostat reported that in 2024, 93% of people aged 16–74 in the EU had used the internet in the previous three months. Under Regulation (EU) 2022/612, “Roam like at home” lets travellers use mobile data across the EU at domestic prices, within fair-use limits, so opening a QR code menu abroad no longer risks a surprise bill.

Some national rules accept screens for allergen information too, such as the German LMIDV provision described above.

Where print still wins

Paper needs no battery, no signal and no willingness to scan. It suits short set menus that rarely change.

That is why many venues choose a hybrid: a compact printed menu on the table and a web-page version for languages, allergens and daily changes.

Seven Signs Your Template Should Go Digital, and How to Migrate Without Losing a Service

Typical scenario: three months into the season, the printed sheet carries two crossed-out prices, a handwritten “sold out” and an allergen note stapled to the back.

Each mark tells the same story: the menu now changes faster than the template can follow.

The seven signs

Read them as a checklist. The more you recognise, the stronger the case for moving the fast-changing parts of your menu online.

First, you change dishes or prices more often than you reprint, so the table menu and the kitchen drift apart.

Second, version control has broken down. Nobody knows which file is current, and the PDF on your website is older than the laminate.

Third, allergen information for the 14 EU allergens lives in a binder rather than on the page guests read.

Fourth, language. As the tourism figures above show, foreign guests fill a large share of the room, and a translation that is a second, older printout is a multilingual menu problem, not a solution.

Fifth, daily specials never make it into print.

Sixth, you cannot see which dishes guests open or skip, so menu engineering is guesswork.

Seventh, reprints for small fixes have become routine.

Hybrid by design: what stays on paper

Going digital rarely means removing paper. A hybrid menu keeps the main list and a clear allergen notice in print, and moves the fast-changing parts to a QR code menu.

The law shapes that split. Ireland’s S.I. No. 489 of 2014 requires written allergen information before purchase, and Germany’s LMIDV accepts electronic information only with a clear notice. Neither rewards an unexplained QR code on a table, so check your national wording before relying on screens alone.

Migration in five steps: audit, structure, allergens and labels, languages, QR placement and fallback

A migration from template to digital menu works best between services, with the old printed version kept on hand until the new one has survived a full week. Each step builds on the record created in the one before, so take them in order.

A platform such as Platoo can host the web-page side, but the sequence matters more than the software. Get it right, and a menu update becomes a single edit instead of a reprint.

If you want one step to take this week, start with the audit. Gather every live version of your menu and check whether they agree. Each difference you find is an update your template failed to carry.

FAQ