Smart Menu Engineering: How to Price and Place Dishes for Profit
Classify every dish by popularity and margin, then reprice, reposition or remove it. A step-by-step menu engineering guide for Indian restaurants.

Most restaurant menus grow by accident: a dish added for a festival, another because a chef liked it, a third because a competitor had it. Smart menu engineering replaces that guesswork with a simple method: measure how often each dish sells and how much it earns, then decide what to promote, reprice, rework or remove. Done regularly, it is one of the cheapest ways to improve margins without cutting quality.
This guide walks through the method, the numbers you need and the changes that usually make the biggest difference.
The two numbers that matter: popularity and contribution margin
Menu engineering looks at every dish through two lenses:
- Popularity: how many portions sold in a period, compared with the other dishes in the same category.
- Contribution margin: selling price (excluding GST) minus the plate cost of ingredients. A paneer tikka selling at ₹320 with a plate cost of ₹95 contributes ₹225.
Food-cost percentage alone can mislead. A dish with 40% food cost that earns ₹400 per plate may be worth more than one with 20% food cost that earns ₹120. Contribution in rupees is what pays rent and salaries.
For accurate plate costs, you need standard recipes with exact quantities and current purchase prices. If ingredient prices change often, as they do with vegetables, dairy and meat in India, your costs must update with them.
For wider context on costs and trends across the sector, the National Restaurant Association of India publishes industry reports worth reading. Inside your own restaurant, though, smart menu engineering starts with your own sales and recipe data.
Classify every dish into four groups
Compare each dish against the average popularity and average contribution of its category (starters with starters, mains with mains). That gives four groups:
|
Group |
Popularity |
Margin |
What to do |
|---|---|---|---|
|
Stars |
High |
High |
Protect quality, give prime menu position, avoid discounting. |
|
Ploughhorses |
High |
Low |
Raise price slightly, reduce portion cost, or pair with high-margin sides. |
|
Puzzles |
Low |
High |
Rename, redescribe, move to a better spot, train staff to recommend. |
|
Dogs |
Low |
Low |
Rework or remove, unless they serve a clear purpose. |
A common rule for "high popularity" is selling at least 70% of what an equal share would be. If a category has 10 dishes, an equal share is 10% of sales, so any dish above 7% counts as popular.
How to run a menu engineering review step by step
- Pick a period: use four to eight weeks of sales so one busy weekend does not distort the picture. Avoid mixing festival weeks with normal weeks.
- Pull item-wise sales: export quantities sold and net revenue per dish from your POS, by outlet if you run more than one.
- Update plate costs: check recipes against current purchase prices, including garnish, oil and packaging for delivery.
- Calculate contribution: net price minus plate cost, then multiply by quantity to see total contribution per dish.
- Classify: place each dish in one of the four groups within its category.
- Decide actions: agree one action per dish with the chef and the floor manager.
- Measure again: review the same numbers after four to six weeks to see what changed.
Run the review separately for dine-in and delivery. Prices, packaging costs and commissions differ, so a star on the dine-in menu can be a ploughhorse on Swiggy or Zomato.
Pricing and layout changes that move the numbers
Price with care
- Small increases of ₹10 to ₹30 on popular dishes are rarely noticed but add up quickly.
- Drop the ₹ symbol and trailing zeros on printed menus where it suits your style; it keeps attention on the dish.
- Avoid lining prices up in one column, which invites guests to scan for the cheapest item.
- For ideas on adjusting prices by time or demand, read our dynamic pricing guide.
Use the menu layout
- Place stars and puzzles where eyes land first: the top of each section and the top right of a two-page menu.
- Use a box, a short story or a chef's recommendation tag on one or two dishes per section, not ten.
- Keep sections short. Seven to ten items per category is easier to choose from than twenty.
- On QR and digital menus, put high-margin items first in each category and add photos only where they help.
Write better descriptions
Specific words sell: "slow-cooked Chettinad chicken with roasted kalpasi" works harder than "chicken curry". Mention origin, technique or a signature ingredient, but keep it to one line.
Train the floor team
Staff recommendations shift sales more than most layout changes. Tell servers which dishes are stars and puzzles each month and give them one sentence to describe each.
Keep it going: menu engineering as a monthly habit
Ingredient prices, seasons and guest tastes change, so a one-time review fades fast. Treat smart menu engineering as a monthly or quarterly routine. Watch for:
- Dishes whose plate cost has risen because a key ingredient went up.
- Stars losing popularity, which can signal a quality or consistency problem.
- Dogs that keep surviving reviews because nobody wants to remove them.
- Menu items that slow the kitchen down at peak hours without earning much.
Smart menu engineering works best when the data is already in one place. If sales, recipes and purchase prices live in separate tools, the review becomes a spreadsheet exercise that nobody has time for. For a wider view of how menus and stock connect, see how AI is shaping menu strategy.
How Digitory helps
Digitory keeps the numbers for menu engineering in one platform:
- Item-wise sales: the Digitory POS records dine-in, takeaway, QR and delivery-app orders together, so you can compare each dish across channels and outlets.
- Live recipe costing: Digitory Inventory links recipes to purchase prices, so plate costs update when vendors change rates, and variance reports show where actual use differs from the recipe.
- AI alerts: Digitory AI flags vendor price jumps and sudden sales drops, so you know when a dish needs attention.
- Plain-language questions: with DigiTalk, ask "which mains had the lowest margin last month?" and get an answer without building a report.
- Chain-wide menus: head office can update menus and prices across all outlets from one place.
Frequently asked questions
How often should I review my menu?
Monthly for fast-moving menus and delivery brands, and at least quarterly for the rest. Review again whenever a major ingredient price changes.
Should I remove every low-selling, low-margin dish?
Not always. Some dishes serve a purpose, such as a Jain or vegan option that brings in a group. Keep them if they earn their place, but simplify them where you can.
Do I need special software for menu engineering?
You can start with a spreadsheet, but it takes hours. A POS linked to recipe costing gives you item-wise sales and plate costs automatically.
Does menu engineering work for delivery menus?
Yes. Run it separately, including commissions and packaging in plate cost, because delivery margins differ from dine-in.
Start with your next review
You do not need a new menu to improve profits; you need to know which dishes earn their place. Pull your sales, update your costs, classify your dishes and act on the results. To see how Digitory brings sales and recipe costs together, book a demo.



