Most restaurant operators know intuitively that some dishes make more money than others, but intuition rarely translates into a clear decision about which items to keep, reprice, promote, or remove. Menu engineering is the structured answer to that question. It is a framework that classifies every item on your menu by two dimensions: how much profit it generates per portion, and how often it sells. The result is a four-cell grid that tells you exactly which items are working, which are costing you money, and which are sitting in the middle waiting for a decision.
This guide explains how to run a menu engineering analysis for an Indian restaurant, how to calculate contribution margin per item, and what to do with each category of item once you have mapped them.
Every menu engineering calculation requires two numbers per item: contribution margin and popularity index.
Contribution margin is the selling price of an item minus its food cost. It is the amount of money that item puts into your pocket after ingredient cost, before labour and fixed overheads. A butter chicken that sells for three hundred and twenty rupees and costs ninety-five rupees to make has a contribution margin of two hundred and twenty-five rupees. A margherita pizza that sells for two hundred and eighty rupees and costs fifty-five rupees has a contribution margin of two hundred and twenty-five rupees as well, even though their food cost percentages look different.
Popularity index is the share of total covers that ordered a given item over a defined period, typically one month of sales data. If your restaurant served a total of three thousand portions across all items in a month and chicken tikka masala was ordered four hundred and twenty times, its popularity index is fourteen percent. You calculate this for every item and then compare each item against the average popularity across all items on the menu.
Once you have contribution margin and popularity index for every item, you plot each item against two thresholds: the average contribution margin across all items, and the average popularity index across all items. Each item falls into one of four cells.
Stars are the items every restaurant should protect. They sell frequently and contribute more than average profit per portion. These are the items you feature prominently on the menu, train your team to recommend, and never discontinue without strong evidence. In a full-service Indian restaurant, well-priced dal makhani, popular grilled starters, and signature cocktails often land in this cell. The strategic move with Stars is to protect them from cost creep: if your dal makhani supplier raises dal prices, you need to notice immediately, because a Star that quietly slides below average contribution margin becomes a Plow Horse, and that is a loss you feel at month end.
Plow Horses are popular but they do not pay well. They sell in volume but their contribution margin is below average. A classic example in the Indian restaurant context is a category anchor item such as plain rice, standard roti, or a basic soft drink. Guests expect it, order it frequently, but the margin is thin. The strategic question with Plow Horses is whether you can raise the selling price without hurting volume. A ten rupee price increase on a high-volume Plow Horse can shift it toward the Star cell without a proportional drop in orders, because guests who expect and want it will absorb a modest increase. Alternatively, look at whether you can reduce the portion size slightly or substitute one ingredient for a lower-cost equivalent without changing the perceived experience.
Puzzles make good money when they sell, but they do not sell often enough. This can happen for several reasons. The item may be poorly positioned on the menu, visually buried in a section that guests skip. The name may not communicate enough about what the dish is, leaving guests reluctant to order something unfamiliar. The price may signal a premium that guests are not ready for without a supporting story. Or the item may simply not be something your particular customer base wants regardless of how it is presented.
For Puzzles, the intervention depends on the diagnosis. If the item is visually buried, test repositioning it to the top of its section or adding a brief description. If the name is unclear, rename it with language that describes the flavour or occasion rather than just the ingredient list. If the item genuinely does not resonate with your guests despite repositioning, it is a candidate for removal and replacement with something that fits the same high-margin slot but with more inherent appeal.
Dogs are items that neither sell well nor contribute meaningful profit when they do sell. The natural response is to remove them, and in most cases that is the right call. Dogs consume kitchen preparation time, add inventory complexity, and often have high wastage because they sit in the cold store between infrequent orders. However, there are two exceptions worth considering before removing a Dog. First, some items are ordered by a specific table type, such as a family that orders a particular dish for children, and removing it would affect the overall experience for that segment. Second, some items are on the menu for completeness reasons, such as a vegetarian option in a predominantly non-vegetarian menu, and their value is not captured by their individual contribution margin. If neither exception applies, remove the item and replace the kitchen prep time and inventory slot with something that belongs in a higher cell.
The threshold for high versus low contribution margin is the weighted average contribution margin across all items on the menu. To calculate it, multiply each item's contribution margin by the number of times it was sold in the period, sum all those products, and divide by total portions sold. This weighted average ensures that high-volume items influence the threshold more than rarely-ordered items.
The threshold for high versus low popularity is simpler. If you have forty items on the menu, the average popularity index is two point five percent (one hundred divided by forty). Items sold at a higher rate than this are popular. Items sold at a lower rate are not. Some practitioners use seventy percent of the average as the low-popularity threshold to avoid classifying items as low-popularity when they are close to average but slightly below, which can shift a few borderline items from Dog to Puzzle. Either approach is valid as long as you apply it consistently.
Start with one month of point-of-sale data. Export the total quantity sold per item and the selling price per item. If you do not have digital POS records, use your purchase registers and kitchen order ticket tallies for the month. The data does not need to be perfect; even approximate counts will reveal clear Stars and clear Dogs.
For each item, calculate the food cost from your standard recipe card. A standard recipe card specifies the exact ingredient quantities and their market prices. If you do not have recipe cards, estimate food cost as your known food cost percentage multiplied by the selling price for that item category. Biryanis in most Indian restaurants run at a food cost of thirty to thirty-eight percent, while kebab and grilled items often run lower at twenty-four to thirty percent, and desserts lower still.
Subtract food cost from selling price to get contribution margin per item. Calculate the weighted average contribution margin. For each item, note whether its contribution margin is above or below the average, and whether its popularity index is above or below the threshold. Assign each item to its cell.
Consider a restaurant in Hyderabad with twenty-eight items on the dinner menu. After one month of analysis, the weighted average contribution margin is two hundred and fifteen rupees per portion. The popularity threshold is three point six percent of total portions. The Hyderabadi chicken biryani lands at a contribution margin of two hundred and forty-five rupees and a popularity index of eighteen percent: a Star. The plain steam rice has a contribution margin of ninety rupees and a popularity index of twenty-two percent: a Plow Horse, so the owner tests a ten-rupee price increase the following month. A signature lamb raan has a contribution margin of three hundred and eighty rupees but a popularity index of only one point two percent: a Puzzle, so it gets repositioned to the top of the menu with a two-line description of the marinade and cooking time. A paneer dish added six months earlier shows a contribution margin of one hundred and fifty rupees and a popularity index of one point eight percent: a Dog, removed from the menu and replaced with a new preparation that tests as a Puzzle candidate with higher inherent appeal.
Menu engineering is most useful when run quarterly. Running it monthly creates noise from short-term sales fluctuations. Running it annually means you are making menu decisions on data that is up to a year old. A quarterly rhythm lets you make two to three menu changes per year based on patterns that are statistically meaningful, while keeping the analysis manageable enough that it actually gets done.
Always run the analysis after a price change, a seasonal menu update, or a significant change in raw material costs. A biryani that was a Star before rice prices increased by thirty percent may have quietly become a Plow Horse. Menu engineering makes these shifts visible before they compound into a margin problem.
Menu engineering measures items against each other using your own sales data. It does not tell you whether your overall price level is competitive with nearby restaurants. It does not account for items that drive table selection at the consideration stage, such as a signature dish that is the reason a group chooses your restaurant even if that dish is not always ordered. It does not replace a sensory review of food quality or a guest satisfaction assessment. Menu engineering is a financial lens, not a complete view of the product. Use it alongside a quarterly competitive price check and an honest review of which dishes guests talk about, not just which ones they order.
Track contribution margin, food cost, and weekly P&L across every item category in one structured format. The Restaurant P&L Tracker includes a monthly item-level cost sheet, weekly revenue tracking, and GST-compliant margin calculations built for the Indian restaurant format.