Menu Copy with AI: Appetizing Wording Without Getting a Cease-and-Desist Letter
"Cheese spätzle with fried onions" is an ingredient list. "Homemade egg spätzle, generously baked under sharp mountain cheese and crowned with golden-braised onions" is a reason to order it. That difference costs you twenty minutes per dish.
For a menu with thirty items, that's ten hours. On text. In a profession where you're actually supposed to be cooking.
Why most menus sound boring
Not because restaurant owners can't write. It's that by the twelfth dish, you can't find a new way to say "delicious" anymore. The vocabulary runs dry, the sentences start to sound the same, and by the end "homemade" appears thirty times.
This is exactly where AI is strong. Its vocabulary never runs dry. You give it the ingredients, the preparation method, and a special feature, it delivers three wording suggestions, you choose.
Input: "Dish: pumpkin soup. Ingredients: Hokkaido pumpkin, ginger, coconut milk. Special feature: regional pumpkin from the farm next door. Tone: cozy, autumnal."
And now the part the AI doesn't know
A menu isn't just marketing copy. It's a document with legal obligations attached. And the AI knows neither your recipe nor food law.
Allergens and additives
The EU Food Information Regulation (LMIV) requires that the fourteen major allergens be labeled. Additives too. If the labeling is missing, fines are possible, and in a worst case you put guests at risk.
Never let the AI add or estimate allergens. It doesn't know your recipe. If it suggests an allergen label, it's a guess. You do the labeling yourself, based on your actual recipes.
Health-related claims
The EU Health Claims Regulation governs which health-related claims about food are permitted. The short version: almost none.
"Boosts the immune system," "makes you slim," "good for digestion," "anti-inflammatory." All of that is prohibited without an approved claim, even on a menu. And AI likes to write sentences like these, because they appear in recipe blogs.
Write explicitly into your prompt: "No health-related claims. Describe only taste, preparation, and origin." That significantly cuts down on the editing work.
Origin claims
"Regional pumpkin," "organic egg," "pasture-raised beef" are factual claims. If they aren't true, that's misleading advertising under the UWG. The AI takes claims like these straight from your input without questioning them. Check every origin claim in the finished text.
The workflow that saves time and stays safe
- Jot down the dish, main ingredients, preparation method, and a special feature.
- Ask the AI for two to three sentences, explicitly without health claims.
- Read the suggestion. Cut anything you can't back up.
- Add allergens and additives yourself, based on your actual recipe.
- Check origin claims against your delivery slips.
Twenty minutes become five. With thirty dishes, that's seven and a half hours you don't spend at a desk.
Where else AI carries weight in hospitality
The menu comes up once a quarter. Social media, reviews, and guest inquiries come up daily. The same principle applies to all three: the AI delivers the draft, you check it and send it.
It's especially worth it for reviews. The first impulse after a bad review is to justify yourself, and justification always reads badly. An AI doesn't have a bruised ego.
What remains
AI doesn't write a menu. It writes wording suggestions for a menu. You're liable for the recipe, the allergens, the origin claims, and legal soundness.
Whoever keeps that distinction wins a lot of time. Whoever doesn't risks a fine because a language model once read in a recipe blog that ginger is anti-inflammatory.
This article is not legal advice. For questions about labeling requirements, the LMIV, or health claims, contact your local food safety authority or a specialist lawyer.
Want to go deeper?
Our guide "AI for Hospitality" gives you ready-made templates to copy, usable right away.
See the guide →