The main job of a menu description is to tell the guest what arrives on the plate, clearly and briefly. The decisions that matter more are which information stays in the description, which is kept in a field of its own, and how a change gets measured afterwards.
What Should Be in the Description?
The most practical opening is to name the item directly: if it is a burger, the first words say what kind of burger. In a long menu especially, the first few words should carry what the dish is.
After that, two kinds of information are worth adding: what makes this version different from the one they had somewhere else, and anything that changes the decision. House-made, charcoal-grilled, served cold, comes with one side rather than two. Everything else is decoration and costs you the reader's patience.
For dishes whose names already explain them, a description is not required. If something sets your version apart, a line still earns its place. Writing one for every item is how a menu ends up speaking at the same length from top to bottom.
What Belongs in a Field Instead
On a digital menu not every piece of information belongs inside the description. Allergens, nutrition and portion variants are separate fields, each with its own place in the guest's view. Cramming them into the description does three things at once: it lengthens the sentence, it hides the information from anyone filtering for it, and it leaves the data unusable everywhere else.
Some of these fields are more specific than people expect. There is a caffeine field on the price option, per variant, which matters for a cafe with three sizes of the same drink. Availability sits on its own too, so a breakfast item can disappear at eleven instead of carrying "until 11am" in its text forever.
| Information | Where it belongs | Why not in the description |
|---|---|---|
| What the dish is | Description | This is the description's job |
| Allergens | Allergen field | Guests filter by it; buried in text it cannot be filtered |
| Calories, nutrition | Nutrition field, per variant | Changes with portion size; text cannot |
| Portion or size prices | Price options | A sentence cannot be selected and added to a cart |
| Serving hours | Availability | Text goes stale; a schedule does not |
| What sets this version apart | Description | This is where the context that affects the choice belongs |
Length Costs More Than You Think in a Multilingual Menu
If your menu runs in more than one language, description length compounds. Every sentence you add is a sentence someone translates, checks and maintains, and the same edit has to happen once per language every time the recipe changes. In a menu with, say, 200 items and three languages, a generous writing habit turns into a standing obligation.
The practical rule that comes out of this: write the shortest line that says what the dish is and what sets this version apart.
How to Tell Whether the Rewrite Worked
Opinions about what makes a good description come easily; understanding the effect on sales takes measurement. So it is worth setting up a small comparison before you touch anything.
- Read your menu out loud in the order a guest reads it. The items that make you pause are the ones to rewrite.
- Start with a small group of items rather than the whole menu. Five to ten is a manageable test group. Where you can, leave price, photo and menu position unchanged on those items; if three things change at once, the effect of the description cannot be separated out.
- After two weeks, compare item views with orders for the same period. An item that gets looked at and not ordered has a different problem from one nobody opens.
That last distinction is the useful one. Low views can point to placement or naming. High views with low orders can point to the description, the price or the photo beside it, and that is where rewriting is worth trying.
A Description Does Not Solve Everything
A description cannot fix a dish. If an item is being sent back or quietly ignored, better wording moves the problem later in the visit rather than solving it. The same applies to price: a sentence can justify a price the guest already finds plausible, and it cannot make an implausible one land.
It is also worth being careful with claims. Words like organic, house-made and local are checkable, and a guest who checks and finds otherwise remembers the menu rather than the meal.
Frequently asked questions
- How long should a menu description be?
- Long enough to say what the dish is and what makes this version worth ordering. In practice that is usually one line. Length becomes a real cost when the menu is translated, because the sentence is written once and maintained in every language.
- Should every item have a description?
- No. Items whose names are self-explanatory read better without one, and a menu where everything carries a sentence is harder to scan than one where descriptions mark the dishes that need them.
- Do I put allergens in the description?
- Better in the allergen field. Guests who need that information usually filter for it, and text buried in a sentence cannot be filtered. Keeping it structured also means it stays correct when the description is rewritten.
- Does AI-generated wording work for menu descriptions?
- It works as a first draft and struggles with the part that matters: what sets your version apart. Without the specific ingredient, cooking method and difference, the result easily turns into generic text describing the category.
- How do I know which descriptions to rewrite first?
- Look for items with plenty of views and few orders. Those are the ones where the guest arrived, read, and decided against it, which is the only place a description is likely to be the deciding factor.
Managing Description, Allergens and Translation in One Menu
In FineDine the description sits in a rich editor alongside the fields discussed above, with a drafting assistant for the first version, translation handled per language, and item-level view and order figures in the reports. To see how description, allergens, variants and translation would separate out in your current menu, look at the demo.
