Design
How to design a restaurant menu in Italy
Build an Italian menu that the kitchen can hold, the guest can read, and the house can live on. Length, names, price ladder. Then the wine list.
Written by Marco Azzari on
A restaurant menu in Italy is a sales page written under 10% IVA, a coperto line, a tight kitchen, and a guest who can see the next place's prices on their phone. If you built yours from recipes and never looked at it as a page people buy from, this is the pass.
This article is for independent rooms: trattoria, osteria, bistro, neighbourhood restaurant. You are probably also the chef, or you stand next to the person who is. You do not need a consultant to write a menu. You need fewer dishes than pride wants, names the table can say, and a price ladder that gives the guest somewhere to go besides "the same plate at the same price."
Length the kitchen can hold
Every extra dish is a prep list, a waste risk, and a line the guest has to climb over to find what you actually cook well. A short menu that comes out clean beats a long menu that 86s by 21:30.
A practical test: list the plates that left the pass on a normal Thursday. Those are the menu. Everything else is a candidate to drop or to run as a piatto del giorno, not as a permanent line that makes the card look serious.
Italian rooms often keep a few "we have always had this" dishes for regulars. Keep them if they still move. If they sit, they are paying rent on the page.
Names in the language the table speaks
Write the dish in Italian, the language your kitchen and service actually use, then add English if your room sees visitors. A machine-translated line under every dish is decoration. A guest who cannot read the dish will not order it, and a waiter who has to translate every line will sell the two plates they can explain in their sleep.
Drop empty adjectives. "Fatto in casa" on a pasta line in a trattoria is noise. Origin, cut, and one concrete detail do more: the Cetara anchovies, the farm, the 30-month Parmigiano Reggiano. Same rule we will apply to wine-list language.
A price ladder, not a flat band
If almost every secondo sits within a few euros, you have given the guest one product at one price. The table that would have spent more tonight has nowhere to go. The table that is stretched has nothing that feels like a decision they can live with.
You do not need a luxury plate for theatre. You need a spread: a true entry, a middle that carries the house, a top that a celebration can land on. Menu engineering is the name for putting high-contribution plates where the eye goes. Do that after the ladder exists. Engineering a flat menu just moves identical problems around the page.
Price from true cost, IVA included. At the table, food and wine both sit at 10%, and so does the coperto. Bottles sold to take away are 22%. The wiki page is restaurant VAT (IVA) in Italy. Do not copy the 22% retail rate or a foreign rate into the costing sheet.
The menu is only half the page
You wrote the food on purpose. In a lot of rooms the wine list was never written. It accumulated from a distributor, a predecessor, and a guess.
The wine list is the second menu. Guests read it with the same fear they bring to a secondo: they do not want to look cheap, they do not want to look foolish, they do not want to stall the table. If that page is a catalogue, they will take a famous name or the second-cheapest bottle and you will call it taste.
When the food menu is stable, design the wine list against the three plates that go out every night, not against the distributor's open cases. Pairing is that job in detail.
About the author
Marco Azzari
Founder of Wine CFO · Wine List Engineer for restaurants in Italy
I help restaurants, hotels and bars in Italy earn more from the wine they already sell. I price lists wine by wine, cost by-the-glass programmes on their real yield, rebuild selections around the food menu, and rewrite lines so guests understand what they're ordering. Every Wine Profit Checkup goes across my desk personally.
More about Wine CFO