HorecaHire
Restaurant menu engineering compares what guests actually order with the contribution each dish generates after its standardized direct recipe cost. It helps restaurant owners identify popular items worth protecting, high-margin items that need better visibility and weak dishes needing closer analysis. This original HoReCaHire guide explains the traditional Stars, Plowhorses, Puzzles and Dogs matrix using consistent Indian-rupee calculations, a copy-ready worksheet and practical next steps. It is complementary to—but not a substitute for—accurate recipe costing.
Menu engineering vs food-cost percentage
A food cost percentage asks how much ingredient cost compares with the dish’s net selling price. Contribution margin per dish instead asks how many rupees remain after direct recipe cost: net selling price − standard plate cost. That amount still needs to cover labour, rent, utilities, distribution costs, tax-related treatment, overhead and profit. Neither number by itself is a complete P&L.
| Measure | Formula | Why it matters |
|---|---|---|
| Plate contribution per unit | Net menu selling price − accurate plate cost | Shows contribution in rupees |
| Item popularity share | Units sold for item ÷ units sold for all comparable items × 100 | Shows sales mix in defined category |
| Total item contribution | Contribution per unit × units sold | Quantifies category contribution |
| Category’s sales-weighted average contribution | Sum of item total contributions ÷ sum of units sold | Benchmark for high/low margin matrix |
| Illustrative popularity threshold | (100% ÷ number of items) × 70% | Traditional menu engineering convention, not mandatory policy |
Worked menu engineering matrix: four fictional dishes
Training setup: One restaurant’s hypothetical category contains four menu items sold during the same reporting month. Prices and recipe costs are illustrative net-of-tax values in rupees; actual supplier or menu prices are not being claimed. Total units sold = 60 + 100 + 20 + 20 = 200 portions.
| Menu item | Net price | Plate cost | Contribution | Units sold | Popularity |
|---|---|---|---|---|---|
| Paneer Bowl | ₹260 | ₹80 | ₹180 | 60 | 30% |
| Dal Rice | ₹150 | ₹65 | ₹85 | 100 | 50% |
| Salad Bowl | ₹240 | ₹75 | ₹165 | 20 | 10% |
| Soup | ₹120 | ₹60 | ₹60 | 20 | 10% |
| Total | — | — | — | 200 | 100% |
Total category contribution = (₹180 × 60) + (₹85 × 100) + (₹165 × 20) + (₹60 × 20) = ₹10,800 + ₹8,500 + ₹3,300 + ₹1,200 = ₹23,800. Sales-weighted average contribution = ₹23,800 ÷ 200 = ₹119 per portion. With four dishes, the conventional popularity cutoff is (100% ÷ 4) × 0.70 = 17.5%. This threshold is an illustrative application of a traditional convention; some operators choose their own meaningful benchmarks.
The four categories explained
| Category | Popularity | Contribution | Item and possible action |
|---|---|---|---|
| Star | High | High | Paneer Bowl: protect quality and availability; avoid unnecessary discounting |
| Plowhorse | High | Low | Dal Rice: investigate ingredient cost and portion consistency without surprising guests |
| Puzzle | Low | High | Salad Bowl: test description, placement or staff familiarity before cutting price |
| Dog | Low | Low | Soup: review operational purpose and guest needs before removal |
In this example, high popularity means at least 17.5% of category units, and high contribution means at least ₹119. Stars, Plowhorses, Puzzles and Dogs are common menu engineering labels, not value judgments about cooks or customers. A soup classified as a Dog may still be important for dietary choice, multi-course sales or guest expectations.
Copy-ready restaurant menu engineering worksheet
| Column | Enter or calculate | Example |
|---|---|---|
| Item and category | Comparable items from the same menu period | Main-course category |
| Units sold | POS quantity after confirmed voids/returns | 60 |
| Net selling price | Verified per-item price under matching tax rules | ₹260 |
| Standard plate cost | Recipe cost including approved components | ₹80 |
| Unit contribution | Net price − plate cost | ₹180 |
| Item mix % | Item units ÷ category units × 100 | 30% |
| Weighted total contribution | Unit contribution × units sold | ₹10,800 |
| Margin classification | Compare with sales-weighted category average | High |
| Popularity classification | Compare with selected popularity cutoff | High |
| Action and owner | Specific test, approved change and review date | Protect recipe consistency |
Seven-step menu engineering process for restaurant managers
- 1. Choose a fair comparison set: do not mix all beverages and mains without thinking about different purchase intent.
- 2. Select a consistent period: compare units, selling prices and plate costs across the same date range.
- 3. Clean the POS data: review voids, promotions, combos and return treatment before counting demand.
- 4. Verify the recipe cost: include sauces, garnishes and actual usable yields rather than guessed food-cost percentages.
- 5. Calculate weighted contribution and mix: use the agreed category definition and formulas.
- 6. Select cautious actions: test descriptions, station readiness, portion accuracy or approved pricing before major redesign.
- 7. Measure after change: compare subsequent actual sales, guest feedback, waste, workload and broader profitability.
What to do with each menu engineering category
Stars: retain reliability
Check availability, recipe execution, supplier consistency and service times. A Star may lose its status if rising ingredient costs or inconsistent quality reduce repeat sales. Avoid assuming constant high demand.
Plowhorses: protect guest value
Review measured portions, negotiated ingredient costs and operational effort before testing a carefully explained price change. A popular low-margin item may attract repeat customers or complementary purchases; removing it can damage demand elsewhere.
Puzzles: test how people discover the dish
Check whether the description is accurate, staff can explain the dish, the menu location is visible and the recipe meets guest expectations. Do not invent “limited-time” claims or pressure servers into misleading upsells.
Dogs: understand strategic purpose
Review whether an item supports special dietary needs, a contracted menu, seasonal demand or groups before changing it. Low unit sales in a short period may not reflect a stable long-term pattern.
Mistakes that can invalidate the matrix
- Using gross selling prices but ingredient costs recorded under a different tax convention.
- Calculating a simple unweighted average contribution across dish titles when volumes differ.
- Comparing seasonal dishes against full-period items with unequal selling days.
- Treating discounted combos as full-price individual item sales.
- Using recipe costs from last year even though supplier prices changed.
- Calling contribution margin “profit” before labour, fees, rent and overhead.
- Ignoring food safety or guest expectations to increase contribution.
- Changing a menu based on one week with unusually low sample size.
Monthly menu engineering review meeting: 10-minute agenda
| Minute | Question | Decision record |
|---|---|---|
| 1–3 | Are POS units, prices and plate costs correct? | Data issues to correct |
| 3–5 | What moved between categories and why? | Actual demand and cost drivers |
| 5–7 | Which limited changes are safe to test? | Named owner and guest/food-safety check |
| 7–9 | How will the test be measured? | Sales mix, contribution and complaints |
| 9–10 | When will we review the results? | Date and responsibility |
An important operational limitation
The traditional matrix evaluates contribution and popularity within a defined menu group. It does not directly reflect kitchen bottlenecks, wastage during service, labour intensity, digital-platform commissions, food-safety needs, capital investment or all cross-selling effects. Treat it as one input into a thoughtful menu decision, not an automated instruction to raise prices or delete dishes.
Related HoReCaHire restaurant management resources
Use the Restaurant Manager checklist, Executive Chef responsibilities, Food and Beverage Director scorecard and restaurant chef hiring guide to connect analysis with operations. Employers can post relevant restaurant jobs.
Frequently asked questions
Is a menu item with 20% food cost always better than one at 30%?
No. Compare the rupee contribution, actual units sold and broader profitability. A higher selling price can generate more rupee contribution even with a higher percentage food cost.
What is the popularity threshold for four menu items?
Under the common 70%-of-equal-share convention, 100% ÷ 4 × 70% = 17.5%. Set comparisons within a consistently defined category.
Should restaurants remove every Dog item?
No. Examine seasonality, dietary options, operational value and the cause of low sales before removing or redesigning the dish.
Research and methodology: Original HoReCaHire rupee examples follow the principles described in the open educational resource “Basic Kitchen and Food Service Management—The Principles of Menu Engineering,” including sales mix and per-item contribution. The figures are invented teaching values, not live restaurant performance data or a guaranteed pricing recommendation.
