“Our chef’s exceptional dish made with the finest ingredients” sounds like a description but does little to help someone order. Guests still do not know what is in it, how it is prepared or what the price includes. Useful writing removes those uncertainties while keeping the venue’s character. It does not require a poetic story for every item or a fixed word count. It requires verified facts from the kitchen and information that genuinely distinguishes dishes. The examples below are for adaptation, not declarations about your recipes.
1. Gather the facts from the kitchen first
For each item, establish the main ingredient, preparation, included accompaniments and available options. Check the recipe rather than relying on the editor’s memory. A bought-in sauce may contain ingredients its everyday name does not reveal. If portions or sets vary by day, agree how the menu will explain that. Write the sentences only after gathering these facts. A description should match the actual dish, not an idealised version of it. A short conversation before publishing is more useful than explaining discrepancies at the table.
2. Let the name identify and the description distinguish
A name should give newcomers something to recognise. “Pasta with roasted tomatoes” usually explains more than “Chef’s favourite”. If a signature name matters to your brand, keep it and add the type of dish. The description need not repeat the full name. Use it for the next question: which sauce, accompaniment or cooking method? W3C’s web-writing guidance recommends plain language and short, clear sentences. That is a useful starting point for a menu read on a phone.
3. Four before-and-after examples
These are fictional editing examples. Use an ingredient or quantity in your own menu only if it matches what you actually serve. The examples are not complete allergen information. Notice that the improvement is not the addition of “delicious” or “perfect”. Each revision resolves a specific uncertainty about the dish, accompaniments, preparation or serving size.
| Before | After | What becomes clearer |
|---|---|---|
| Chef’s burger. Our best! | Beef burger. Cheddar, onion and mustard sauce in a bun. Served with fries. | The meat and included side |
| Special risotto | Roasted beetroot risotto. Arborio rice, goat’s cheese and toasted seeds. | Flavour, main ingredients and finish |
| Dessert of the day with extras | Vanilla cheesecake. Baked on a shortcrust base and served with raspberry sauce. | The dessert and how it is served |
| Homemade lemonade | Lemon and rosemary lemonade. Made with sparkling water. 1-litre jug. | Ingredients, carbonation and size |
4. Shorten for meaning, not a magic word count
There is no single ideal description length for a coffee, burger and multi-part set. An espresso may only need its size, while an unfamiliar dish needs a short explanation. QRelay’s description field holds 300 characters: a technical limit, not a target to fill. Keep the key ingredient and the difference from other items. Remove repeated names and empty adjectives. If important details will not fit, simplify the wording and check the complete public display rather than hiding the issue behind abbreviations only the kitchen understands.
5. Explain the price and option alongside the dish
Portion information should agree with the price beside it. Make clear if the amount is for a small pizza, a jug of drink or an extra. Do not write “with fries” if fries require a supplement that is not visible with the item. QRelay displays the price as entered by the owner, so the unit and currency belong in that text. It does not automatically convert dish prices for guests from another country. Agree a consistent way to show sets and supplements, then read each item as a first-time visitor.
6. Keep allergen information separate from marketing claims
An ingredient description helps people choose, but does not establish that allergen information is complete. The European Commission notes that allergen information also applies to non-prepacked food, including in restaurants and cafés. Check the obligations relevant to your venue. Never label a dish gluten-free, vegan or free from an ingredient based only on a name or photo. Verify the recipe, supplier products and actual preparation. Resolve uncertainty with the kitchen before publishing. A general invitation to ask staff does not replace checking the information.
7. Check understanding and language consistency
Show two similar dishes to someone unfamiliar with them and ask what makes them different. If they must guess, improve the distinguishing detail. In translation, preserve ingredients, portions and included sides rather than translating a signature name literally without explanation. QRelay does not automatically translate owner-entered content. If you use two languages in one item, remember the shared field limit and readability on a small screen. Review every version when the recipe changes. Updated Polish wording and an older foreign-language description may describe different dishes.
8. An editing checklist before publishing
Do not judge a description only by how appetising it sounds. Compare it with the recipe, price display and phone view. Check items across categories to catch inconsistent units and names. Assign someone to approve changes. After publishing, note recurring guest questions: they may reveal missing information, but are not automatic proof of a rise or fall in sales.
- The name identifies the type of dish.
- The description adds information rather than repeating the name.
- Ingredients, option and portion match kitchen practice.
- The price clearly identifies what is included and any supplements.
- Allergen information and dietary labels have been verified.
- The complete text fits the field and remains readable in the public menu.