Menu Jargon Guests Don't Understand: A Plain-Language Rewrite Guide

Why jargon accumulates

Culinary language enters a menu from three directions: the kitchen's own vocabulary, the chef's training, and the urge to make a simple dish sound more considered.

The first two are usually useful. A kitchen that calls a sauce by its real name is being precise, and a technique that changes the texture of a dish is information a guest may care about. The third is where menus go wrong. "Artisanal," "hand-crafted," "deconstructed," "elevated" and "seasonal" — used without specifics — tell the guest nothing they can picture, and they take up the space where a useful detail could have been.

The test for any term is simple: does it change what the guest expects to arrive? If yes, keep it and explain it. If no, cut it or replace it with a fact.

Terms that earn their place

Some words do real work, and removing them makes the menu less honest rather than more accessible.

• **A technique that changes the dish:** braised, grilled, cured, fermented, smoked, poached. A guest who knows they dislike smoke or vinegar is making a decision from that word.
• **Origin, when it is specific and verifiable:** the region of a cheese, the type of chilli, the variety of tomato. It tells the guest what the dish will taste like, not where the marketing department has been.
• **A word that prevents a surprise:** "spicy," "contains shellfish," "served cold," "bone-in," "comes with a knife." Guests rarely object to being told what to expect.

Terms that mostly confuse

Some words are worth replacing with the thing they mean.

• **Aioli** — say "garlic mayonnaise" unless the kitchen genuinely makes a traditional emulsion and the distinction matters to the guest.
• **Confit** — say "slow-cooked in its own fat" or "slow-cooked, tender" depending on what the guest will notice.
• **Deconstructed** — describe the components instead. The word tells the guest the dish will be arranged unusually, which is not the same as telling them what they are eating.
• **Market price** — give a range or an indicative price, or state the portion. A blank price is a reason to skip the dish.
• **Reduction** — say "concentrated sauce" or name the sauce.
• **House-made** — worth keeping only if it distinguishes the item from something the guest would otherwise assume is bought in.
• **Chef's selection** — fine for a tasting menu, confusing on a regular list where the guest is choosing for themselves.

Rewriting without flattening the dish

A plain-language rewrite is not a simpler dish. It is the same dish, described so the guest can picture it.

Work from the facts you have: the main ingredient, how it is cooked, what comes with it, and anything a guest might not expect. Then write the sentence in the order a guest eats it.

A practical method is to read the description and ask three questions. Could a guest picture the plate? Do they know the main ingredient and the format — sandwich, bowl, stew, salad? Is there anything that might surprise them, stated plainly? If any answer is no, the description is not finished, however elegant it sounds.

Keep descriptions roughly the same length across the menu. A single paragraph of forty words next to six items of eight words makes the long dish look expensive or overwrought, regardless of its price.

Spice, market price and trade terms

Three cases deserve their own rules.

Spice needs a scale, not an adjective. If your menu uses chilli, decide what "mild," "medium" and "hot" mean in your kitchen, use the same words everywhere, and make sure the floor agrees. A guest who orders "medium" in one restaurant and gets a different heat level has no way to calibrate.

Market price is honest only when the price is genuinely volatile. Even then, a range or an indicative price is more useful than a blank. If the price is stable, print it.

Trade terms that guests genuinely use — espresso, flat white, tasting menu, prix fixe, omakase — can stay, because the guest who wants them is looking for them. The test is whether the term is common in your market, not whether it is common in your kitchen.

Keeping translations consistent

If your menu runs in more than one language, the same rule applies with more force. Translate the description, not the jargon. A literal translation of a culinary term often lands as an unfamiliar word in the second language, which is worse than a plain description.

Build a short glossary for the terms you keep — one column for the term, one for the plain description in each language — and use it for the QR menu, the printed menu and the delivery listing. Inconsistent translations across channels are as confusing as inconsistent prices.

Worked rewrites

The examples below are illustrative.

Before: "Pan-seared sea bass, citrus beurre blanc, deconstructed ratatouille, micro herbs."

After: "Sea bass fillet, seared, with a lemon butter sauce and diced summer vegetables. Served hot."

Before: "Artisanal house burger, secret sauce, hand-cut chips."

After: "Beef burger with lettuce, tomato and house sauce, served with hand-cut fries."

Before: "Chef's daily market fish, market price."

After: "Today's fish, grilled or fried — ask your server for today's catch and price."

In each case, nothing about the kitchen's work is denied. The guest simply knows what is coming, which is what they need in order to order it.

Limitations and assumptions

This approach assumes you have accurate dish facts to write from: ingredients, preparation and what is included. Where those facts are missing, the rewrite becomes guesswork, and guessing on a menu creates allergen and accuracy risks that outweigh any readability gain. It assumes a general audience; a restaurant whose guests are culinary professionals can keep more trade vocabulary. Brand voice, translation quality and local usage all vary, and no rewrite removes the need for a final check that allergen, dietary and legal statements remain complete and unambiguous. Plain language should never simplify away a warning.