How to write menu descriptions that sell (with before/after examples)

Guests choose a dish by reading, not by tasting. Between "Mushroom pasta" and the same line written well sit different order counts and — when the description earns the price — different bills too. The good news: writing descriptions that sell doesn't take a copywriter. It takes a few rules, applied to every line of the menu.

What a description does (when it works)

A well-written description works on three fronts:

• It lets the guest picture the dish. They should "see" it before it arrives: texture, cooking method, what's actually on the plate.
• It justifies the price. An ingredient with a name and an address — the Hereford rib-eye, the day-boat scallops, the single-farm cheddar — explains why this dish costs more than its anonymous twin.
• It builds trust. A menu that states ingredients and allergens clearly says, between the lines: we know what goes on the plate here.

Sensory yes, gushing no

Sensory language works when it describes facts: the cooking ("braised for 12 hours"), the texture ("crisp outside, molten inside"), the temperature, the origin. It stops working when it describes opinions: "delicious", "mouth-watering", "irresistible" are verdicts that belong to the guest, and on a menu they sound like the landlord praising his own beer.

The practical rule: every word must tell the guest something they didn't know. "Tasty" fails the test. "Finished with brown butter" passes.

Provenance earns the price

Between "Grilled beef — 24 €" and "28-day dry-aged Hereford sirloin, grilled over charcoal — 24 €" the price is identical, but only in the second case does the guest understand why. Name the origin when it's true and when it's a merit: the PDO, the local farm, the day boat. If a premium ingredient is in the dish, writing it down isn't vanity: it's the only way the guest can know. And if you're still deciding what the dish should cost, start from the numbers with the food-cost calculator — a description justifies a price, it doesn't invent one.

Two lines. No more

The right length for a description is about two lines: enough for one image and one reason to order, not enough for an essay. Under one line you're listing; over three the guest skips to the next item. The dish name is the headline, the description does the rest: don't repeat in the text what the name already says.

The mistakes that cost you

• Adjective soup. "Delicious fragrant pasta with fresh tasty mushrooms": four adjectives, zero information.
• "Delicious" and its cousins. If it's written on half the menu, it means nothing on all of the menu.
• ALL CAPS. On a menu it just shouts: harder to read, no extra authority.
• Prose poetry. "A journey of flavours that cradles the palate": the guest wants to know what they're eating, not where they're travelling.
• Decorative jargon. Technical terms only if your guests understand them; "pan-roasted" is fine, "en demi-glace au jus" on a pub menu is not.

Allergens: clarity that sells

Declaring allergens legibly isn't just an obligation under EU Regulation 1169/2011: it's part of the description. A guest with an allergy picks the restaurant where they don't have to cross-examine the server; the line "Contains: gluten, milk" under a dish is, for them, the most persuasive sentence on the menu. Legal clarity and commercial clarity coincide here.

Before and after: three rewrites

Example dishes, invented purely to show the mechanism:

Before: "Mushroom pasta — delicious pasta with fresh tasty mushrooms"
After: "Hand-rolled tagliatelle, sautéed porcini, aged pecorino. Contains: gluten, milk"

Before: "Grilled beef — tender grilled meat with a side"
After: "28-day dry-aged Hereford sirloin, grilled over charcoal, rosemary potatoes"

Before: "CHEF'S SPECIAL OCTOPUS — AN EXPLOSION OF FLAVOURS!"
After: "Charred octopus on rosemary chickpea purée, smoked paprika oil. Contains: molluscs"

The mechanism never changes: verdicts out, facts in — technique, origin, allergens.

Rewriting the whole menu without reprinting it

Rewriting thirty descriptions on a printed menu means a reprint; on a digital menu it means half an hour on your phone. With Menudetto you edit descriptions in chat or by voice ("rewrite the pasta description like this...") and the change is live at once — the QR on the table stays the same. And if the menu runs in several languages, the descriptions' translations stay aligned across all 6: you rewrite in English, and the German guest reads the updated version in theirs.

Descriptions are also the raw material of menu engineering: a high-margin dish nobody orders is often just a badly described dish — the menu engineering guide shows how to spot them, and the one on menu pricing psychology how to present the price next to the description.

A checklist before you publish

Reread each description and ask:

• Is there at least one fact the guest didn't know (technique, origin, pairing)?
• Does it fit in two lines?
• Does it pass the "delicious" test? If a word could sit under any dish on the menu, it isn't saying anything: replace it or cut it.
• Are the allergens declared and legible?
• Does the price next to it have a why — does the description earn it?

Five yeses: publish. One no: rewrite that single line. It's two minutes, not an afternoon — and on a digital menu there's no reprint waiting for you either.

In short

A description that sells is two lines of facts: cooking technique, ingredients with their origin, allergens declared. Out with the verdicts ("delicious"), the adjective soup and the capitals; in with what the guest doesn't yet know and what earns the price. If you want to overhaul the whole menu, the digital menu guide shows where to start — or create your menu free and rewrite your first three descriptions tonight.