Most menus describe dishes one way: by listing what is inside. "Cod fillet, potato purée, spinach, butter sauce." The guest gets a table of contents, not a reason to order it.
The description is the cheapest change on the whole menu. It needs no new supplier, no print run and no pricing decision — just one sentence rewritten.
What a description does that an ingredient list does not
Three jobs, in this order:
- It answers what the guest does not know — how it is made, how big it is, whether it is hot.
- It separates the dish from the one next to it — if two items carry the same description in different words, the guest picks on price.
- It gives one concrete detail that stays in the head — a variety name, a cooking time, an origin, a way of serving.
Point three is the one usually missing. The rest is formality.
Four things that work
Method instead of adjective
"Delicious ribs" says nothing — every venue thinks its own are delicious. "Ribs baked 6 hours at low temperature" says how much work is inside, and explains the price at the same time.
The same mechanism: smoked over alder, aged 30 days, from a wood-fired oven, fried in clarified butter.
A specific instead of a generality
Instead of "blue cheese" — the name of the cheese. Instead of "local vegetables" — from where. Instead of "aromatic spices" — which ones.
A specific is credible because it can be checked. A generality sounds like hedging.
Information that removes hesitation
A guest does not order when there is something they do not know. The most common unknowns: how hot, how big, can it be made without something, how long is the wait.
One sentence in the description removes the question to the server and speeds up the decision. "Heat 2/3, can be toned down" or "portion for two" works better than enthusiasm.
A short line about origin, if it is true
The farm name, the region, the supplier. One condition: it has to be true and verifiable. An invented "from local farmers" with no name is noise the guest has stopped reacting to.
What not to do
Do not transcribe the recipe. A 40-word description with every ingredient takes longer to read than the decision takes. A 60-item menu written that way is fifteen minutes of reading.
Do not use the same adjectives across the menu. When "aromatic" and "succulent" appear at ten dishes, they stop meaning anything — and the menu starts reading like one paragraph.
Do not promise what the kitchen does not deliver. A description raises expectation. The gap between the description and the plate costs more than a flat description.
Do not translate descriptions literally. A regional stew rendered as cabbage stew puts people off; slow-cooked sauerkraut with three kinds of meat, 3 hours does not.
How long
The practical range is 60–140 characters per item. Below 60 you usually end up with the ingredient list again; above 140 the description starts competing with the decision.
The exception: the menu's heroes — the signature dish, a tasting, anything that needs explaining. There 200 characters is justified, because the guest will stop anyway.
Three rewrites
Before: Beef burger, cheddar, lettuce, tomato, sauce. After: Chuck minced on site, 12-month cheddar, mustard sauce. 180 g.
Before: Chicken salad. After: Grilled chicken, romaine, parmesan, sourdough croutons. Available gluten-free.
Before: Homemade cheesecake. After: Baked on a shortcrust base, no gelatine. From a family recipe, unchanged since we opened.
In each case we added one specific and one piece of information that removes a question. That is the whole operation.
Where to start when the menu has 80 items
Not at the beginning. The order that pays off fastest:
- The puzzles from your profitability analysis — dishes with a good margin that do not sell. Usually because of the description; the classes are explained in menu engineering.
- Items guests ask the server about. Every recurring question is a missing sentence in the description.
- Signature dishes — the ones somebody is meant to travel for.
The rest of the menu can stay as an ingredient list. Not every item needs a description.
Why this is easier on a digital menu
A description in print is a decision for the whole run of 40 copies: changing it costs another print, so nobody tests. On a digital menu you rewrite one sentence and a month later you see in the sales whether it worked.
That changes the nature of the work — from one-off copywriting to a series of small corrections. See QR menu and menu examples.
Frequently asked questions
Does every menu item need a description?
No. Descriptions are needed by non-obvious dishes, signature dishes, and those with a good margin that do not sell. An item like "chips" does not need a sentence.
How long should a dish description be?
60–140 characters for an ordinary item. Longer only for dishes that need explaining.
Should I list every ingredient in the description?
No — that is what allergens marked at the item are for. The description exists to give a reason to order; composition is a separate field.
How do I know whether a new description worked?
Compare the item's sales a month before and a month after the change, with the price and menu position unchanged.
