How to design a restaurant menu that sells

Written by Marco Azzari on 11 September 2026

A restaurant menu is a sales page written under rising food costs, 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: bistro, trattoria, neighborhood 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 9 p.m.

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 special, not as a permanent line that makes the menu look serious.

Neighborhood 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 the plain English your servers actually use. Keep the Italian, Spanish, or Japanese name if the kitchen is built on it and the floor can say it, then gloss it in a few words. A French poem over a barbecue kitchen is decoration. A guest who cannot pronounce the dish will not order it, and a server who has to translate every line will sell the two plates they can say in their sleep.

Drop empty adjectives. "Homemade" on a pasta line in a trattoria is noise. Origin, cut, and one concrete detail do more: the Gulf shrimp, the farm, the dry-aged strip. Same rule we will apply to wine-list language.

A price ladder, not a flat band

If almost every entrée sits within a few dollars, 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 theater. 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, on the menu price itself. US menu prices are pre-tax: state and local sales tax is added at checkout and the tip goes on top of that. Neither is yours, so neither belongs in your margin. Do not build a price that only works if you count the tax. Food and wine need different cost targets: food cost versus wine cost.

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 an entrée: 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 catalog, 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.