How to Write Menu Descriptions: Examples, Sensory Words and a Two-Week Test

If you're going through your menu line by line, each description has one job: tell the guest what arrives on the plate and why your version is worth ordering. A sentence or two is usually enough to name the dish, say how it's made and give the one detail that sets it apart. "Delicious" adds length and no information. A sensory word belongs in the line only if the guest can check it on the plate, and a story about the dish belongs on one or two signatures, not on every item. Allergens, sizes and serving hours go in their own fields. And before you rewrite the whole menu, try the new lines on a few items for two weeks and see whether orders actually move.

What goes into the line, and in what order

A guest scrolling a long menu on a phone tends to give each line a few words before moving on. Those first words have to say what the dish is, so "beef burger" or "lamb shoulder" comes before anything else. If the item name already says it, the description can start with the next part.

The next part is what makes your version different from the one the guest had somewhere else last week. That might be the cut, the cooking method, a sauce you make in-house or the bread you bake. After that, add anything that changes the decision. Served cold. Comes with one side, not two. Big enough for two. Takes 20 minutes from the kitchen. These look like small details on paper. At the table they aren't, because a guest who finds out after ordering that the soup is chilled or the steak needs 20 minutes is annoyed, and one clear line would have spared the server that conversation.

Leave out anything every dish on the menu could claim. A decent kitchen can call every plate it sends out fresh, delicious, carefully prepared and made with love, which is exactly why those words tell the guest nothing about this one.

Some items don't need a line at all. Espresso, fries and a house salad that is exactly what it says are already described by their names. If you write something for every item, the menu reads the same from top to bottom and the dishes you want noticed lose their contrast.

Sensory words and scene-setting: when they earn their place

Most menu writing advice tells you to use descriptive language. The catch is that plenty of descriptive language doesn't describe anything. The useful kind tells the guest something they'd notice on the plate and might choose on: crisp skin, a runny yolk, charred edges, a broth poured at the table, a dessert that comes out warm. Each of those is a fact about texture or temperature, and the guest can check it when the plate lands.

Praise words don't pass that check. "Mouth-watering" and "heavenly" describe how the writer hopes the guest will feel, and most guests have read both on more menus than they could count.

The second check happens in the kitchen on a full night. If the pork belly only comes out crackling when the oven isn't overloaded, the pass will sometimes send out a soft one, and that guest is the one likely to remember the word. So write the dish as it leaves the kitchen on its busiest service, not on its best one.

A short scene, such as where the recipe comes from or who raises the lamb, can work on one or two signature dishes. Give every item one and it stops working, because with forty stories on the menu the guest has no way to tell which dish the kitchen is proudest of.

Short lines and descriptive lines only pull against each other when the sensory word is added on top of a vague one. Use it as a replacement instead. "Slow-roasted lamb shoulder, falls off the bone" is about as long as "Delicious tender lamb, cooked to perfection", and every word in the first one can be checked on the plate.

Menu description examples, before and after

The table pairs five lines of the kind you'll find on plenty of menus with a rewrite of each. They're illustrations, not dishes from a real menu. Every rewrite follows the same order: what the dish is, what's different about it, and what changes the decision.

Most of the weak lines fail in one of two ways. In some, praise stands in for information. In others, allergens, calories and serving times have been typed into the sentence, because a printed menu had nowhere else to put them. A digital menu usually does have somewhere else, and that changes what the description needs to carry.

Allergens, sizes and serving hours belong in their own fields

A printed menu gave each dish one box, so everything went into the description. A digital menu typically has separate fields for allergens, nutrition, portion sizes and the hours an item is available, and each of them shows up in its own place on the guest's screen.

Putting that information back into the sentence costs you in three ways. The line gets longer. Allergen notes tend to end up worded a little differently on each item, so a guest checking for nuts has to read every sentence closely instead of looking for the same marker each time. And the data is stuck in prose, so it can't be shown, translated or updated anywhere else without editing each description by hand.

Serving hours are the easiest to move out. A breakfast item that comes off the menu at 11:00 doesn't need "served until 11am" in its text. On the morning you push the cutoff to 11:30, you change one setting instead of hunting through thirty lines. The guest reads all of this on the screen they opened from the table, and what changes for guests after the QR scan covers the rest of that view.

Every sentence you add gets translated too

Run the menu in more than one language and every sentence gets multiplied. A menu of 200 items in three languages is 600 descriptions, and when a recipe changes, the same edit has to happen in each language. A generous writing habit in the first language turns into a standing job for whoever maintains the others.

The sensory and scene-setting words also tend to be the first to lose their meaning. Think of a pun on the dish name, a regional nickname, or a word like "smashed" or "loaded" that carries a whole style of cooking in English. Machine translation renders the words and often drops what they meant. Before a translated menu goes live, have someone who reads that language fluently go through it, and rewrite a joke rather than translating it. Plain lines built from ingredient, method and one difference usually come through translation with their meaning intact.

Test a rewrite on a handful of items first

Everyone on the team will have a view on the new wording, and none of those views tells you whether orders moved. Measuring does, and the test fits into an ordinary two weeks:

1. Note views and orders for each item over the last two weeks. If guests order through a server, take order counts from your POS, because the digital menu records only the view.
2. Pick five to ten items that get opened often and ordered rarely.
3. Rewrite only their descriptions. Keep the price, the photo and the position on the menu the same.
4. Leave them for two weeks, so the comparison covers two weekends and two quiet Mondays.
5. Compare views and orders for the rewritten items against their own previous two weeks, and against a few items you didn't touch.

The untouched items are there so a busy fortnight doesn't pass for a successful rewrite. If they rose as much as the rewritten ones, something else was at work, the weather or a local event perhaps, and only the gap between the two groups can be put down to the descriptions.

Read views and orders together. When nobody opens an item, the cause is often its placement or its name, and that's worth fixing before you judge the description. When guests open it and don't order, something on that card is losing them. It could be the description, the price or the photo next to it, and that's where a rewrite is worth trying.

The test has limits. A small café that sells a dish three times a week won't learn much in two weeks, since a move from six orders to eight can easily be noise. Test on items that actually sell, or run the comparison longer. The bigger blind spot is how orders are taken. If guests read the menu on their phones but order through a server, the digital menu records the view and never the order. For those items, take order counts from your POS, or let guests order from the menu itself; the trade-offs of that are in online ordering for restaurants: benefits, do's and don'ts.

What a better description can't do

If an item keeps coming back half-eaten, the wording isn't the problem. Better copy only moves the disappointment from the menu to the table. Price works the same way: a good line can justify a price the guest already finds reasonable, but it won't make an unreasonable one land. If you suspect the dish rather than the copy, ask the guests who ordered it, and a few of these restaurant survey questions fit that job.

Take care with claims a guest can check. Organic, local, house-made, hand-cut and free-range are all things a guest can ask a server about. When the server has to answer "not exactly", you likely lose more trust than the word ever won. Write them only when they're true every day, including the days a supplier lets you down.

Writing and checking descriptions in FineDine

In FineDine's Menu Manager, the description is a field on the item's General tab. It's a rich text editor with an "Enhance with AI" option for a first draft, and AI features draw on your account's credits. Treat the draft as something to edit, because the facts in it are still yours to check.

Portion sizes live in Price Options, nutrition in Nutrition Info and serving hours in Availability, each a separate tab on the same item, so the description only has to say what the dish is and what sets it apart. On the guest's phone, the item card shows the name, the description, the price variants and allergen and diet icons. When the breakfast cutoff moves, you change the item's hours in Availability and leave its text alone.

Translation happens in the Translation Center. Each language sits beside the original with a completion percentage, and a filter shows only the untranslated items. AI auto-translate gives you a first pass to hand to a fluent reader. How many menu languages you can run depends on your plan, and the pricing page has the current breakdown.

For the two-week test, FineDine IQ (the AI Reports tab) shows Item Views and Orders side by side, along with Revenue and Avg Ticket, so you can compare the rewritten and untouched items over a 14-day comparison range. Ranges of 7, 28 and 90 days or a custom period are there too, and a Menu Performance tab sits in the same place. The classic Reports section also has an Item Report. The blind spot from the test still applies here: FineDine counts the orders placed through FineDine, so anything a server rings up on a separate POS has to come from that system.