Menu contribution margin grid & item prioritizer

Quick hunger

Find which menu items actually earn you money, which drain margins, and which deserve promotion, rework, or removal. This tool walks you through the calculations, gives a clear way to classify items into the four menu-engineering quadrants, and offers pragmatic actions and an A/B test plan so you can change the menu without breaking guest satisfaction or revenue.

What you'll need

• For each menu item: price (menu price), ingredient (food) cost per portion, direct labor cost per portion (if tracked), any other variable cost per portion (packaging, condiments), and units sold for a recent period (week or month).
• Sales data from your POS for one representative period (7–30 days). If you have multiple locations, do this per location.

Step 1 — Calculate contribution margin (per portion)

Contribution margin (per portion) = Menu price − (Food cost + Direct labor + Other variable costs)

Contribution margin % = (Contribution margin ÷ Menu price) × 100

Example:

Menu price = $15; Food cost = $4.50; Labor = $1.50; Other costs = $0.50 → Contribution margin = 15 − (4.5+1.5+0.5) = $8.5 → Margin% = 8.5 ÷ 15 = 56.7%

Step 2 — Measure popularity

Use units sold in the same period. Convert to relative popularity if helpful: % of total units sold across all menu items, or average daily units.

Step 3 — Choose thresholds (practical options)

There is no single universal cutoff. Two practical methods:

1. Median-based: Mark items with contribution margin above the median as “high profit”; units sold above the median as “high popularity.”
2. Percentile-based: Top 25% by margin = high profit; top 25% by sales = high popularity. Use this when you want a stricter definition of “star” items.

Pick a method, and apply the same thresholds consistently for comparison over time.

Step 4 — Classify items into the menu contribution matrix

Quadrants and what they mean:

• Stars — High profit, high popularity. Protect supply, feature on menus and specials, consider upsells and pairing suggestions.
• Plowhorses — Low profit, high popularity. Adjust cost or price carefully: rework recipe, reduce portion variance, renegotiate supplier price, or increase price slightly if guest tolerance allows.
• Puzzles — High profit, low popularity. These may be opportunities to promote, reposition on the menu, test better plating, or bundle with sides.
• Dogs — Low profit, low popularity. Consider retiring, testing at a different price, or offering as a limited-time special to clear inventory; avoid removing without small tests if they have loyal fans.

Worked example (small table)

Step 5 — Prioritize actions (practical guidance)

• Start with Plowhorses and Puzzles—these are the highest-leverage opportunities.
• Plowhorses: reduce variable cost (trim, portion control, supplier changes), revise plating to reduce waste, test a modest price increase paired with improved description or pairing suggestion.
• Puzzles: promote (server suggestions, menu placement, photos), reposition as a special, adjust portion/price combo to encourage trial, or add a limited-time promotion with monitoring.
• Stars: protect consistency (SOPs, inventory priority, supplier contracts), create upsells (add-on sides), or slightly increase price only if guest sensitivity is low.
• Dogs: test low-cost experiments before removal—limited-time discounts, repositioning, or recipe rework. If no improvement after testing, remove to free menu space and kitchen complexity.

A/B test plan template (safe, measurable changes)

Before permanently changing or removing items, run small, time-boxed tests.

1. Hypothesis: Example — “Promoting Steak Special on the menu header will increase units sold by 30% without reducing average check.”
2. Metric: Units sold, revenue per item, average check, contribution margin per item, guest satisfaction (if available).
3. Variant: Control (current placement/price) vs Treatment (prominent placement + server upsell script).
4. Duration & sample: Run until at least 2 full business cycles for the item (e.g., two weeks), or until you reach a minimum sample size (e.g., 100 potential exposures or 40–100 item sales depending on volume). Track by shift and day of week to avoid skew from a single busy day.
5. Acceptance criteria: Statistically and operationally meaningful improvement—e.g., ≥20% increase in units sold and no more than 5% drop in average guest satisfaction, with positive contribution margin impact.
6. Implementation notes: Train servers on the script, document the change, and monitor inventory to be sure increased promotion doesn't create stockouts that harm the guest experience.
7. End & decide: If successful, roll out and monitor. If unsuccessful, revert and document lessons.

Prioritization checklist before making changes

• Do we have reliable sales and cost data for the period used?
• Have we calculated full variable costs (not just food cost) for each recipe?
• Is this item important to a specific customer segment or event (e.g., local favorite, dietary option)?
• Can we test the change with a small experiment rather than immediate removal?
• Do front-line staff understand the change and how to talk to guests about it?

Printable worksheet (copy and paste into a spreadsheet)

Columns: Item name, Price, Food cost, Labor cost, Other variable cost, Contribution $, Margin %, Units sold, Notes, Quadrant, Proposed action, Test planned?

Common mistakes to avoid (mal-hunger guardrails)

• Removing items without guest testing—this can lose loyal customers and hurt reputation.
• Using food cost alone—ignore labor and other variable costs at your peril; contribution margin is the full picture.
• Reacting to a short-term spike or dip—use a representative period and account for seasonality.
• Setting thresholds without consistency—always document and reuse the same method for longitudinal improvement.

Next steps & how to make this a living process

1. Run the worksheet for one representative period and classify items.
2. Pick one Plowhorse and one Puzzle to improve with a short A/B test each month.
3. Capture results, update recipes/SOPs for successful changes, and repeat quarterly.

Image search phrase: menu engineering matrix