Menu Descriptions for AI Assistants: Examples and Checklist
Write menu descriptions your guests and AI assistant can use. See dish examples, a field-by-field checklist and checks for ingredients and serving details.
A product name that is obvious to your kitchen may not tell a guest which plate to expect. A menu assistant cannot turn details absent from the description into reliable information either. Good product descriptions offer concrete features that help people choose instead of dressing a dish in exaggerated adjectives. This work also makes your menu easier to read independently of the chat experience.
Contents
Pair a creative name with an understandable description
A name such as 'From the Garden' may suit your brand, but alone it does not explain whether the product is a salad or a sandwich. State the main product type in the short description. For a fictional dish, 'Grilled vegetable sandwich, served with baked potatoes' provides more usable information than 'An unforgettable, unique flavor'. Adapt the ingredients and serving arrangement in this example to your actual recipe.
Use natural phrases the menu assistant can draw on in searches; do not repeat the same keyword in different forms. Filling a product with 'coffee, hot coffee, coffee drink, café coffee' makes its description harder to read. The name, category and description should complement one another instead of repeating the same text in every field.
Prioritize a few details that affect the choice
When writing a description, ask the service team what guests most often ask before choosing the product. Whether it is served hot or cold, its main ingredient or its accompaniment may be common needs. Verify these details with the kitchen and put the most important one in the first sentence. You do not need to describe the entire preparation process, but do not bury a detail that changes the meaning behind poetic wording.
If a sauce's composition, the number of portions or suitability for a particular dietary preference has not been verified, do not guess. Interpretations based on a photograph or product name are not the same as recorded information. Leaving details open for guests to ask the team is more useful than a full-looking but incorrect description.
| Field | Useful information | Approach to avoid |
|---|---|---|
| Name | A name that makes the product recognizable | An internal team code alone |
| Description | Verified ingredients and serving details | General praise |
| Nutrition information | A recorded, verified value | Guessing from the dish name |
Do not hide structured information inside the description
Repeating the price in a description means updating a second field when the price changes. The same problem can occur with nutrition values and feature labels. If your system has dedicated fields, manage verified information there; let the description explain serving style and distinctive product features. This makes it easier for the guest card and assistant response to use a shared record.
In Orvunai, product price, availability and recorded nutrition values are managed in their own fields. Writing 'now 250 TL' in the description while leaving a different price in the price field creates an inconsistency. Similarly, if a description calls a product vegan while business labels conflict, check the source information before publication.
Test the description against real questions
Open a product and ask a colleague to describe the dish using only its recorded description. List the questions they cannot answer. Do not add every question to the description; distinguish details important to selection from special details requiring staff verification. Then ask the menu assistant a natural question aimed at finding the product and check that the displayed information matches your record.
When a recipe changes, review the product name, description, photograph and any language versions within the same task. An ingredient that has been removed but remains in the description can affect both the ordinary menu and the chat. Having the content owner review these four areas together is a stronger habit than assuming the update is complete after changing one screen.
Explore the relevant Orvunai product guide to put these steps into practice with your own menu.
Explore AI restaurant menu and Luca AI waiter