Stars
Signal: High popularity and high contribution margin.
Playbook: Protect the experience, preserve visibility, and avoid discounting what already works.
The operator's guide
Menu engineering software for restaurants
Menu engineering turns item-level sales and costs into a decision system: see which dishes are popular, which ones carry margin, and what to test next. This guide explains the established method and points you to practical tools for putting it to work.
The framework
How the Kasavana–Smith method works
Formalized by Michael Kasavana and Donald Smith in 1982, menu engineering plots every item on two axes: popularity, measured by menu mix, and profitability, measured by contribution margin. The result is a matrix that gives each item a practical role instead of treating the menu as one average number.
Popularity asks what guests choose. Contribution margin asks what remains after the item-level food cost is subtracted from the selling price. Read together, those measures help an operator decide whether to protect, improve, feature, or rethink a dish.
The thresholds are comparison lines, not universal targets. Re-run the matrix for a comparable period and investigate items near either line before making a lasting price, portion, placement, or removal decision.
Two inputs, one useful view
- Popularity
- Menu mix percentage: an item's share of units sold in the comparison period.
- Profitability
- Contribution margin: menu price minus the item-level food cost you provide.
- Decision
- Use the quadrant as a prompt for a test, not as a promise about future revenue.
The playbooks
Four quadrants, four practical playbooks
The quadrant names are shorthand for a next question. Pair the signal with your restaurant's guest promise, execution reality, and observed results.
Crowd Pleasers
Signal: High popularity with a below-average contribution margin.
Playbook: Test a measured price, portion, or cost improvement while watching demand and guest value.
Hidden Gems
Signal: High contribution margin with lower popularity.
Playbook: Improve the description and placement, then give the team a relevant prompt to earn attention.
Leftovers
Signal: Lower popularity and lower contribution margin.
Playbook: Check execution, demand, and the item's role before removing or reinventing it.
Put it to work
Choose your next menu decision
Start with the smallest useful question, then move to a full matrix or a product comparison when the evidence calls for it.
- Run a full menu matrixPaste item sales and costs into the free browser calculator for a classified menu and action plan.
- Check one dish's food costEstimate ingredient-only food cost, contribution margin, and a target menu price.
- Use the menu teardown worksheetReview layout, margin, and three concrete menu fixes with a printable worksheet.
- Compare with meezSee where a menu-engineering-first workflow differs from recipe and ingredient costing.
- Compare with MenuMaxCompare browser-based POS data and a live matrix with a desktop recipe-costing workflow.
- Compare with Toast and xtraCHEFReview the boundary between menu engineering and Toast-native recipe or inventory operations.