AI Prompts for Restaurants and Food Businesses

TL;DR: These are copy-paste AI prompts for restaurants and food businesses: menu descriptions, daily specials, review replies, staff shift notes, supplier emails, and seasonal menu ideas. Every prompt uses bracketed placeholders for the facts that matter, and none of them invent an allergen, a nutrition number, or a food-safety claim. You verify those; AI only handles the wording.

How Is a Restaurant Prompt Different From a Generic Marketing Prompt?

A generic "write me a menu description" prompt has no idea what's actually in the dish, whether a customer with a nut allergy can safely order it, or what your kitchen calls "spicy." It fills those gaps with something plausible, and plausible is exactly the wrong quality for food information. The prompts below are built the same way every time: role (who's writing), task (what needs to happen), format (length and shape), constraints (what to leave as a placeholder or never invent), and tone. That last piece, the constraints line, is doing more work in a food-business prompt than in almost any other industry on this site, because the cost of a model confidently filling a gap is higher here than in most other jobs an AI assistant helps with.

This applies whether you run a sit-down restaurant, a bakery, a food truck, or a catering business — the fields change (a menu board instead of a printed menu, a delivery-app listing instead of a website), but the same rule holds everywhere a dish gets described in words: the description can be creative, the facts underneath it cannot be guessed.

If you run a different kind of local, appointment-driven business, the same structure applies with different nouns, and our companion piece on AI prompts for local service businesses and trades covers that version; for gyms and fitness studios specifically, see AI prompts for gyms and fitness businesses.

Where Does Allergen and Ingredient Information Actually Have to Come From?

Your recipes, checked by you, every time, not a chat window. This is the one rule on this page that isn't negotiable. Allergen labelling is a real legal obligation, it varies by country and often by region, and it is never something to delegate to a model that has never seen your kitchen. Nothing below states a specific temperature, cites a specific food-safety regulation, or claims one country's rule applies everywhere; if you need the actual legal requirement for your jurisdiction, that's a conversation with your local health authority or a food-safety consultant, not an AI chat.

The same caution applies wherever a dish description travels once it's written — a printed menu, a chalkboard, your website, and a third-party delivery app listing can all carry the same sentence, and a mistake copied across four places is four places that need correcting, not one.

1. Pre-publish allergen and ingredient verification checklist

Role: quality-control assistant for a [TYPE OF FOOD BUSINESS, e.g. restaurant, bakery, food truck].
Task: read the draft menu description below and produce a checklist of every
food-related claim in it that must be verified against our actual recipe
before publishing — allergens named or implied, ingredients mentioned,
preparation methods, and any dietary claim (vegan, gluten-free, halal, etc.).
Draft: [PASTE THE DRAFT DESCRIPTION]
Format: a numbered checklist, one claim per line, no more than 15 items.
Constraints: do not confirm or deny whether any claim is accurate — only list
what needs checking. Do not add new claims that aren't already in the draft.
Tone: precise, no filler.

What to change: this prompt never touches the actual facts — it just makes sure you don't skim past a claim that snuck into the draft. Run it before every new menu item goes live, not just the ones that feel risky, and keep a copy of the checklist alongside the recipe once it's confirmed.

How Do You Write a Menu Description That Sells Without Guessing at Ingredients?

The gap between "grilled chicken sandwich" and a description someone actually wants to order is usually a handful of sensory details: how it's cooked, what it's served with, what makes your version different. None of that requires inventing a fact — it requires describing the real dish well, which is exactly what these prompts are for. The same description usually needs to work in more than one place too: a printed menu can afford a longer line than a delivery-app listing with a character limit, so it's worth asking for both lengths up front rather than rewriting the same dish twice.

2. New dish description, allergens and nutrition left blank on purpose

Role: menu copywriter for a [CUISINE TYPE] restaurant.
Task: write an appetizing menu description for [DISH NAME], based on these
real details: [LIST ACTUAL INGREDIENTS, COOKING METHOD, AND WHAT IT'S SERVED WITH].
Format: 25-40 words, matches the tone of our other menu items.
Constraints: use only the ingredients and details I listed — do not add,
imply, or guess at any ingredient, allergen, or dietary label I didn't
mention. Do not state a calorie count or nutrition figure.
Tone: appetizing, specific, no generic food-blog adjectives like "delicious"
or "mouthwatering" doing the work instead of a real detail.

What to change: if the same dish also needs a shorter version for a delivery app, run the prompt again with "under 15 words" in the format line rather than trimming the long version by hand — a fresh short draft usually reads better than a truncated long one.

3. Rewrite an existing description to sound less generic

Role: menu editor tightening an existing description.
Task: rewrite the description below so it sounds specific to this dish
rather than any dish, without changing what the dish actually is.
Existing description: "[PASTE CURRENT DESCRIPTION]"
Actual ingredients and method, for reference only: [LIST]
Format: keep it within 10 words of the original length.
Constraints: do not add an ingredient, technique, or claim that isn't in the
original description or the reference list.
Tone: match our existing menu voice — [DESCRIBE IT, e.g. "warm, a little playful"].

What to change: this works well as a batch job. Paste in five tired descriptions one at a time and you'll usually spot the same one or two generic adjectives repeating across your whole menu, which is worth fixing everywhere at once.

4. Menu translation, first draft only

Role: bilingual menu translator, [SOURCE LANGUAGE] to [TARGET LANGUAGE].
Task: translate the menu section below, preserving dish names where they're
recognized internationally and translating descriptions naturally rather
than word-for-word.
Menu section: [PASTE SECTION]
Format: same structure as the source (dish name, then description).
Constraints: flag, rather than silently resolve, any dish name or allergen
term you're not fully confident about, so a fluent speaker can check it.
Tone: natural, as if written by a native speaker, not a literal translation.

What to change: treat this as a first draft only. A wrong word in a translated allergen term is exactly the kind of small error that matters far more than it looks — have a fluent speaker check it before it goes to print, especially anything involving allergens or dish names that don't translate literally. Our guide to prompting AI in languages other than English covers the general pattern if you're translating more than a menu.

How Do You Turn Today's Specials Into Something Staff and Customers Actually Read?

A special that only exists as a scrawled note on a whiteboard or a rushed verbal handoff at pre-shift gets forgotten, mispriced when a server describes it, or skipped entirely on a slow table. Two prompts turn the same rough note into something a server can repeat accurately and something worth a social post, without either one drifting from what's actually on the plate.

5. Pre-shift special blurb for servers

Role: kitchen manager briefing front-of-house staff on today's special.
Task: turn the rough note below into a short, accurate blurb a server can
repeat to a table from memory.
Note: [PASTE ROUGH NOTE ON THE SPECIAL — INGREDIENTS, PRICE, PORTION]
Format: under 50 words, plain spoken language, not menu-copy language.
Constraints: include the price only if I gave you one; leave [PRICE] as a
placeholder otherwise. Do not add an ingredient I didn't list.
Tone: clear and easy to repeat out loud, not a sales pitch.

What to change: read the output back out loud before pre-shift, not just on screen — a line that scans fine written down can still trip up a server saying it to a table for the first time.

6. Social post for a limited-time special

Role: social media voice for a [CUISINE TYPE] restaurant.
Task: write a short post announcing today's special, based on: [DISH,
INGREDIENTS, WHY IT'S SPECIAL, e.g. "first of the season", AVAILABILITY WINDOW].
Format: under 60 words, 1-3 relevant hashtags maximum.
Constraints: describe only what's true about the dish and its availability —
no invented scarcity ("almost gone!") unless it's actually true today.
Tone: appetizing but not hyped past what's actually true.

How Do You Reply to a Bad Review Without Sounding Defensive or Fake?

A one-star review almost always contains something specific: a wait time, a wrong order, a cold plate, a rude interaction. A generic "we're sorry for your experience, please contact us" reply reads as a template because it is one, and it does nothing to reassure the next reader who's deciding whether to book a table. These prompts require the real complaint as input, on purpose, and give a model no room to guess at what actually happened on the shift.

7. Reply to a review about slow service or a long wait

Role: owner responding publicly to a review about slow service.
Task: write a reply that acknowledges the specific wait described below,
without excuse-making, and states one concrete thing being done about it if
I've given you one.
Review: "[PASTE THE ACTUAL REVIEW TEXT]"
What we're actually doing about it, if anything: [DESCRIBE, OR LEAVE BLANK]
Format: under 90 words.
Constraints: do not invent a reason for the wait or a fix we aren't actually
making. If I left the "what we're doing" line blank, don't fill it in with
something plausible — just acknowledge the wait and invite them back.
Tone: calm, specific, not defensive.

What to change: paste the actual review text, not a summary of it. A reply that references the specific detail the customer complained about reads as genuine; a reply to a paraphrase reads as slightly off, in a way most readers notice without being able to say why.

8. Reply to a review claiming a wrong or missing item

Role: owner responding publicly to a review about an order mistake.
Task: write a reply that takes the mistake described below seriously without
disputing the customer's account, and offers a concrete next step.
Review: "[PASTE THE ACTUAL REVIEW TEXT]"
Next step we can actually offer: [e.g. "email us and we'll make it right", or
leave blank]
Format: under 80 words.
Constraints: do not argue with what the customer says happened, even if you
suspect it's wrong — that argument, if it needs to happen, happens off the
public review. Do not invent a policy or a next step I didn't give you.
Tone: taking it seriously, not performative.

How Do You Ask Happy Customers for a Review Without Sounding Pushy?

Asking for a review is fine on virtually every platform; what most platforms explicitly prohibit is tying an incentive, like a discount, to leaving one, changing one, or removing a negative one. Check your own review platform's current terms before offering anything in exchange for a review — the prompts below only ever ask, never trade, and the timing of the ask matters almost as much as the wording.

9. Post-visit review request text

Role: [RESTAURANT NAME] following up after a customer's visit.
Task: write a short text or email asking for a genuine review, sent after a
good visit.
Context: [ANYTHING SPECIFIC ABOUT THE VISIT WORTH REFERENCING, OPTIONAL]
Format: under 50 words, one clear link placeholder [REVIEW LINK].
Constraints: ask for an honest review; do not offer a discount, freebie, or
any other incentive in exchange for leaving one.
Tone: warm, brief, not needy.

What to change: send this while the visit is still fresh, ideally within a day, and only to a table your staff genuinely thought had a good time — a request sent to every table regardless of how the visit went reads as automated even when the wording isn't.

10. Thank-you note after a catering or private-event job

Role: [RESTAURANT NAME] following up after catering or hosting a private event.
Task: write a thank-you message referencing the actual event below, closing
with a genuine (not incentivized) ask for a review.
Event details: [EVENT TYPE, DATE, ANYTHING SPECIFIC THAT WENT WELL]
Format: under 100 words.
Constraints: reference only the details I gave you; do not invent specifics
about the event. No discount or incentive tied to the review ask.
Tone: personal, specific to this client, not a form letter.

How Do You Keep Shift Handoffs and Schedule Changes From Getting Lost in Texts?

A closing shift's notes for the opening shift, or a last-minute schedule change, usually lives in someone's memory or a half-read group chat by the time it matters. These prompts turn a rushed voice note or a scribbled list into something the next person actually reads, instead of skims past at the start of a busy shift.

11. Closing-shift handoff note

Role: closing manager writing a handoff note for tomorrow's opening shift.
Task: turn the rough notes below into a clear, scannable handoff.
Notes: [PASTE ROUGH NOTES — WHAT RAN LOW, WHAT NEEDS FOLLOW-UP, ANYTHING
UNUSUAL FROM TONIGHT]
Format: short bulleted sections (Inventory, Follow-up, Anything unusual),
under 150 words total.
Constraints: include only what's in my notes — do not infer a cause for
something running low unless I told you the cause.
Tone: plain, no filler.

What to change: dictate the rough notes into a voice-to-text app on your way out the door rather than typing them — the prompt handles turning a messy voice transcript into a clean handoff just as well as a typed list, and it's faster at the end of a long shift.

12. Last-minute schedule change text to staff

Role: manager sending a last-minute shift change to the team.
Task: write a short group text announcing the change below and asking who
can cover.
Change: [WHAT CHANGED, e.g. "Friday 5-close needs one more cover"]
Format: under 40 words, one clear way to respond.
Constraints: state only the change I described; don't add a reason unless I
gave you one.
Tone: direct, no guilt-tripping about the ask.

How Do You Draft a Supplier Email When You're Short Mid-Shift?

Running low on an ingredient mid-week, or needing to push back on a price increase, both need a fast, clear email that says exactly what you need without a half-hour of rewriting a template from an old thread. The two prompts below are deliberately short, because a long email is the thing that doesn't get sent when the walk-in fridge is the actual problem.

13. Urgent early-delivery request

Role: [RESTAURANT NAME] kitchen manager emailing a regular supplier.
Task: write a short, direct email requesting an earlier or additional
delivery of [ITEM], because we're running low ahead of [WHEN, e.g. the
weekend].
Format: under 80 words, clear ask in the first line.
Constraints: state only the item and timing I gave you — do not invent a
reason for the shortage or promise a future order size I haven't confirmed.
Tone: direct, professional, not apologetic.

What to change: put the ask in the subject line too, not just the first line of the email — a supplier scanning an inbox mid-morning is more likely to act on "Need early delivery Thursday: [item]" than on a subject that just says "Quick question."

14. Pushing back on a price increase

Role: [RESTAURANT NAME] owner responding to a supplier's price-increase notice.
Task: write a reply acknowledging the notice below, asking whether a smaller
increase, a locked-in rate for a set period, or an alternative product tier
is possible.
Their notice: [PASTE OR SUMMARIZE THE PRICE-INCREASE NOTICE]
Format: under 100 words.
Constraints: don't invent a competing quote or offer I don't actually have —
ask the question directly instead of implying leverage I don't have.
Tone: firm, respectful, relationship-preserving.

How Do You Brainstorm a Seasonal Menu Without Copying the Restaurant Down the Street?

A seasonal special that starts from "what's actually in season, and what do we already do well" reads differently from one that starts with a competitor's Instagram. These prompts use your own ingredients and your own strengths as the starting point, which also means the resulting dish is one your kitchen can actually execute at volume, not just plate once for a photo.

15. Seasonal special brainstorm from what you already have

Role: chef brainstorming a seasonal special.
Task: suggest 5 seasonal dish concepts using primarily these ingredients,
which are in season or already in our regular supply: [LIST INGREDIENTS].
Build on techniques we already use well: [LIST 2-3 THINGS YOUR KITCHEN DOES WELL].
Format: 5 short concepts, one line each (dish idea + why it fits), no full
recipes.
Constraints: use only the ingredients I listed as the core of each concept —
you can suggest one or two common pantry additions per idea, clearly marked
as suggestions to confirm, not as facts about what's in the dish.
Tone: practical, kitchen-ready, not a food-blog fantasy list.

What to change: treat the five concepts as a shortlist to test on a slow night, not a finished menu decision — the one that reads best on the page and the one your line can actually turn around during a rush are not always the same dish.

16. Limited-time item announcement

Role: [RESTAURANT NAME] announcing a new limited-time menu item.
Task: write a short announcement for [social post / email — specify], based
on: [DISH, WHY IT'S LIMITED, AVAILABILITY WINDOW].
Format: under 70 words.
Constraints: state the availability window only if I gave you one — do not
invent an end date or a reason for scarcity.
Tone: excited but accurate.

What Should Your Local-SEO Description Actually Say?

What you serve, where you serve it, and what's genuinely different about your kitchen, in words a customer would actually use to search. That's a different job from menu copy, and it's worth writing separately rather than reusing a menu blurb as your business description — a description built to sell one dish reads oddly as the summary of an entire restaurant.

17. Business profile description

Role: writer drafting a business profile description for [RESTAURANT NAME].
Task: write a factual, specific description covering cuisine type, what
makes us different, and neighborhood/area, based on: [CUISINE, NEIGHBORHOOD,
2-3 GENUINE DIFFERENTIATORS].
Format: under 750 characters, no bullet points, plain prose.
Constraints: use only the details I gave you — no invented awards, no
"award-winning" or similar claims unless I stated one, no promotional
language dressed up as fact.
Tone: honest, specific, written for a real customer deciding where to eat.

What to change: let the neighborhood and cuisine details appear naturally in a sentence rather than as a stacked list of keywords at the end — a description that reads like a real paragraph works for the human reading it and for search, without needing to choose between the two.

18. "About us" story for the website

Role: writer turning rough founder notes into an "about us" page.
Task: turn the notes below into a short story about why this restaurant
exists.
Notes: [PASTE ROUGH NOTES ON WHY YOU STARTED, WHAT MATTERS TO YOU, ANY REAL
HISTORY]
Format: 150-200 words, first person or third person — [SPECIFY].
Constraints: use only the history and details in my notes — do not invent a
founding year, an award, or a detail about the food that isn't in my notes.
Tone: [DESCRIBE YOUR ACTUAL VOICE, e.g. "warm and a little informal"] — see
our guide to [building a brand-voice context](/blog/67-brand-voice-ai-context)
if you want every prompt to default to this voice without retyping it.

What Should You Never Let AI Decide for a Restaurant?

Three things, specifically, and they're worth repeating because they're the easiest ones to let slide once a draft reads well: any allergen or ingredient claim, any nutrition or calorie figure, and any food-safety or labelling statement presented as universal fact. Allergen labelling is a real legal obligation and it genuinely varies by country and region — treat every draft above as a first pass that needs your own recipe and your own local rules applied before it goes anywhere public, whether that's a printed menu, a chalkboard, a website, or a listing on a third-party delivery app. A model that sounds confident about any of these three things is not evidence that it's correct, and the more polished the sentence, the more worth double-checking it actually is.

Does the Free Plan Cover This?

Mostly, yes, for occasional use. Every prompt above is plain text and runs in ChatGPT, Claude, or Gemini exactly as written, no extra tool required. Prompt Architects is an optional layer: a Chrome extension that puts a structured-prompt sidebar inside the AI chat you already use, so you're filling in brackets instead of retyping a full prompt from a notes app between orders.

The Free plan includes 5 prompt generations a day, forever, no credit card required, and it works the same way inside ChatGPT, Claude, or Gemini through the extension — enough to run a handful of the templates above on a quiet shift. Note that the current /pricing page doesn't display a Free plan card even though the plan is active; the daily-generation figure comes from the FAQ page. What Free doesn't include: saving your own copies as a reusable template with tags and search, or a personal context library where your cuisine type, standard tone, and go-to disclaimers live once instead of being retyped into every prompt. Those are Pro-plan features, at $4.99/month at the time of writing — verify current pricing on /pricing, since it runs on a promotion that won't stay in place forever. For a single kitchen running these a few times a week, Free may genuinely be enough; Pro earns its keep once the same three or four templates get reused every week and you don't want to hunt for them in old chat threads.

Speed on specials, honesty on reviews, and a blank bracket everywhere a fact belongs instead of a guess. That's most of what separates a prompt that gets reused from one that gets abandoned the first time it invents an allergen nobody checked. Copy what's useful, delete what isn't, and keep the ones you reach for every week somewhere you can find them again with sauce on your hands and three tickets still up.