Food, Menu & Beverage Costing

Menu Engineering Calculator

Classify menu items as Stars, Plowhorses, Puzzles or Dogs using menu mix and contribution margin. Includes the classic threshold method and example.

Audited formula No live data required Browser-only calculation
Last reviewed Sep 22, 2026 Source set reviewed Sep 22, 2026 Next review Sep 22, 2027

Interactive calculator

Enter your assumptions

Example values are prefilled. Replace them with your own figures, then calculate.

Menu item rows: name, selling price, food cost, quantity sold
Selling priceFood costQuantity soldActions

Use this calculator to estimate menu engineering calculator from your own assumptions. The calculation runs locally in your browser, and the formula, example, scope, and source are visible below.

How to use this calculator

  • Menu item rows: name, selling price, food cost, quantity sold: enter the value for the same scenario and period as the other inputs.
  • Optional category/period: enter the value for the same scenario and period as the other inputs.
  1. Replace the example values with values from one consistent scenario.
  2. Select Calculate and review the primary and supporting results.
  3. Change one assumption at a time when comparing scenarios, then verify material decisions against the governing source or a qualified professional.

Formula and method

contribution_i = selling_price_i - food_cost_i
menu_mix_i = units_sold_i / total_units_sold
equal_share = 1 / number_of_items
popularity_threshold = 0.70 * equal_share
weighted_average_CM = sum(contribution_i * units_sold_i) / total_units_sold
popular_i = menu_mix_i >= popularity_threshold
high_CM_i = contribution_i >= weighted_average_CM
Star = popular & high_CM
Plowhorse = popular & not high_CM
Puzzle = not popular & high_CM
Dog = not popular & not high_CM

The implementation uses the audited A12 — Restaurant / Recipe Cost method. Intermediate values retain calculation precision; the interface formats values only for display unless the formula itself specifies a rounding rule.

Worked example

Inputs: A: $20 price, $8 cost, 100 sold; B: $18/$7/50; C: $15/$9/30

Result: CMs=$12/$11/$6; Mix=55.56%/27.78%/16.67%; Popularity threshold=23.33%; Weighted-average CM=$10.72; A=Star, B=Star, C=Dog

This is the baseline audited scenario used to check that the page, formula, and displayed result remain aligned.

How to interpret the result

The calculator reports Contribution margin/item; menu mix %; 70%-of-equal-share popularity threshold; weighted-average CM threshold; quadrant. Treat the output as a scenario estimate: it changes when the entered scope, time period, fee basis, or cost definition changes. It does not establish a universal benchmark or guarantee a business outcome.

Assumptions and limitations

  • CORRECTED: classic Kasavana/Smith popularity threshold is 70% of equal-share popularity, not raw 1/N. Profitability threshold is weighted-average contribution margin.

  • Results are informational planning estimates, not accounting, tax, legal, employment, valuation, or investment advice.

  • Values are processed in the browser and are not submitted to an application server.

Common mistakes

  • Analyze comparable menu sections.

  • total units=0.

  • tiny sample periods.

  • document any alternative threshold method.

  • CORRECTED: classic Kasavana/Smith popularity threshold is 70% of equal-share popularity, not raw 1/N. Profitability threshold is weighted-average contribution margin.

  • Rounding intermediate values before completing the formula can change the final result.

  • A worked example is not a default recommendation; replace every assumption that does not match your case.

Frequently asked questions

What inputs should a restaurant include in the Menu Engineering Calculator?

Use the same period and units for these inputs: Menu item rows: name, selling price, food cost, quantity sold; Optional category/period. Keep optional assumptions at their example values only when those values match your scenario.

How is Menu Engineering calculated?

The calculation applies this audited method: contribution_i = selling_price_i - food_cost_i menu_mix_i = units_sold_i / total_units_sold equal_share = 1 / number_of_items popularity_threshold = 0.70 * equal_share weighted_average_CM = sum(contribution_i * units_sold_i) / total_units_sold popular_i = menu_mix_i >= popularity_threshold high_CM_i = contribution_i >= weighted_average_CM Star = popular & high_CM Plowhorse = popular & not high_CM Puzzle = not popular & high_C… Display rounding is applied after the calculation rather than to intermediate values unless the rule explicitly requires it.

Which labor, overhead or tax items are excluded unless entered?

Use the same period and units for these inputs: Menu item rows: name, selling price, food cost, quantity sold; Optional category/period. Keep optional assumptions at their example values only when those values match your scenario.

How should I interpret the result for my own restaurant?

Read Contribution margin/item; menu mix %; 70%-of-equal-share popularity threshold; weighted-average CM threshold; quadrant as a planning estimate for the assumptions entered. Compare scenarios using the same scope and period; the calculator does not establish a universal target or guarantee an outcome.

How this calculator was created and tested

  • Formula basis: the public formula is generated from the audited implementation specification for this calculator, not inferred from a search snippet or an AI answer.
  • Validation coverage: 2 of 2 release test vectors are marked Audited for this calculator. The suite covers a normal scenario plus boundary or invalid-input behavior where defined.
  • Regression behavior: build checks compare expected outputs, validation states, route integrity, structured data, internal links, and release blockers before publication.
  • Automation and AI: automation or AI may assist drafting, organization, and regression work, but it is not treated as an authoritative source and does not override the audited formula, official rate registry, or release blockers.
  • Editorial responsibility: MIASIN S.R.O. controls publication, source policy, corrections, and release decisions. No named individual expert review is claimed unless a page explicitly identifies one.

Read the full Methodology, Editorial Standards, and Corrections Policy.

Sources and freshness

Sources are ordered by authority: government or official sources first, then first-party platform sources, educational references, and finally supporting industry references.

Last reviewed: September 22, 2026
Source set reviewed: September 22, 2026
Next scheduled review: September 22, 2027
Review cadence: Formula stable; external benchmarks only when explicitly sourced