Set the decision boundary before using the numbers
Inputs and records to align
- □A defined menu, sales channel and observation period. (not complete)
- □Units sold after voids and refunds for each item. (not complete)
- □Net price and included ingredient, packaging and channel cost per item. (not complete)
- □A consistent definition of contribution per item and total contribution. (not complete)
- □Preparation minutes, station constraint, waste or complexity evidence where operational burden matters. (not complete)
- □Availability and promotion notes so low sales are not mistaken for low demand. (not complete)
Build one transparent decision model
Item contribution = (net item price - included variable cost per item) × units sold; menu contribution = sum of item contributions
- net item price
- Recorded revenue per item after included discount and refund treatment (CU per item) — sales record
- included variable cost
- Recipe, packaging, fee and other item-level costs inside the declared boundary (CU per item) — recipe, purchase and contract record
- units sold
- Fulfilled item quantity for the same period (items per period) — point-of-sale record
Do not average away item differences. Popularity thresholds and operational burden are separate classifications and should remain visible beside contribution.
- Reconcile item sales, price and included cost on one period.
- Calculate contribution per item and total item contribution.
- Classify observed demand without treating it as stable future popularity.
- Add preparation time, bottleneck and waste evidence beside the financial view.
- Choose one item-level change and identify possible substitution across the menu.
- Review the whole-menu result after the test rather than celebrating one item in isolation.
Worked example: compare two items without a verdict shortcut
Invented period: Item A sells 120 units at 8 CU contribution each; Item B sells 60 units at 15 CU contribution each.
| Line | Calculation | CU |
|---|---|---|
| Item A total contribution | 120 × 8 | 960 |
| Item B total contribution | 60 × 15 | 900 |
| Combined contribution | 960 + 900 | 1,860 |
| Contribution difference | 960 - 900 | 60 |
| Case | Changed input | Result | Decision signal |
|---|---|---|---|
| Base Item B | 60 units × 15 CU | 900 | Inspect lower demand |
| Price test | 60 units × 17 CU | 1,020 | Test demand and execution |
| Demand test | 70 units × 15 CU | 1,050 | Check capacity burden |
Review the operational trade-offs before acting
- Ranking by revenue, food-cost percentage or units alone.
- Using median popularity as a universal performance target.
- Ignoring stockouts, promotion, availability and menu placement.
- Removing a low-volume item without checking bundles, substitution or strategic role.
- Increasing price without modelling possible volume and mix changes.
- Calling a descriptive matrix proof of causation.
Decision questions
- Should every low-popularity item be removed?
- No. Check contribution, availability, substitution, customer promise and operational burden before choosing an action.
- Can I use food-cost percentage to rank items?
- Not by itself. Contribution per item and total contribution answer different questions, and capacity or waste can change the decision.
Sources and methodology
- Restaurant Menu Profitability methodology — Margin101: Item contribution, observed demand and operational-burden decision contract.
- Product Mix Profit methodology — Margin101: Whole-mix contribution mechanics and scenario boundaries.
Test the editable scenario
- Restaurant Menu Profitability Planner
Choose menu items and pricing from item-level contribution, popularity and operational burden
- Menu Pricing Planner
Set a menu price from recipe yield and loaded portion cost
- Product Mix Profit Planner
Compare contribution when the volume mix changes across products