wowprompt

Menu engineering from restaurant item sales and margins

Sorts every dish on a menu into stars, plowhorses, puzzles and dogs using sales count and contribution margin, then suggests price, placement and recipe changes. Use it before reprinting a menu or when food cost is rising and profit is not.

A table of menu items with units sold, food cost, contribution margin and class, followed by a menu matrix summary and changes for each class
The output this prompt produced, unedited.

The prompt

Goal

Know which dishes earn their place on the menu and what to change for each one.

Inputs

  • Restaurant type and service: [e.g. cafe with dine-in and delivery, North Indian family restaurant]
  • Period: [e.g. last 30 days]
  • Items: [one row each with menu section, item name, selling price, food cost per plate and units sold]
  • Delivery commission, if items sell on apps: [e.g. 25% on delivery orders, or none]
  • Constraints: [e.g. signature dishes we will not remove, kitchen station limits]

Steps

  1. Compute contribution margin per item: selling price minus food cost (and commission where it applies).
  2. Compute each item's share of units sold within its menu section.
  3. Mark popularity as high when the share is at least 70% of an equal share (100% divided by the number of items, times 0.7).
  4. Mark margin as high when it is at or above the section's weighted average margin.
  5. Classify: star (high, high), plowhorse (popular, low margin), puzzle (high margin, unpopular), dog (low, low).

Output format

  • | Section | Item | Price | Food cost | Margin | Units | Popularity | Margin level | Class |
  • Count of items in each class per section.
  • Actions: stars (protect, keep prominent), plowhorses (small price rise or cheaper garnish), puzzles (rename, move up, staff recommendation), dogs (rework or remove).
  • The three changes with the largest monthly profit effect, with the arithmetic.

Check before answering

  • Every figure comes from the pasted rows.
  • Sections are analysed separately; desserts are not compared with main courses.
  • Price suggestions are small steps, not jumps that change the dish's position on the menu.
  • Removing a dish is never the only option offered.
menu engineeringrestaurant menu analysisdish profitabilityfood cost analysiscafe menu pricingcontribution margin

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity