Inventory planners
Set practical stock policies using demand and lead-time evidence.
Restaurant Inventory Tools
Classify menu items as Stars, Plowhorses, Puzzles or Dogs using popularity and contribution margin from CSV or Excel data.
Classify menu items using sales popularity and contribution margin.
Upload a CSV or Excel file to begin.
Business context
Menu engineering compares item popularity with contribution margin. It helps classify dishes as Stars, Plowhorses, Puzzles or Dogs so pricing, placement, promotion and recipe decisions use both demand and profitability evidence.
This guidance is designed for people who need to use menu engineering analyzer results in a real approval, planning or operational workflow.
Set practical stock policies using demand and lead-time evidence.
Identify slow, excess and high-priority stock for action.
Protect availability while controlling working capital.
Input guide
| Column | Purpose | Example |
|---|---|---|
| Menu Item * | Unique dish or product name. | Grilled Chicken Bowl |
| Units Sold * | Quantity sold during a consistent review period. | 420 |
| Selling Price * | Net selling price per item. | 12.50 |
| Recipe Cost * | Current standard ingredient cost per item. | 4.10 |
Mapping note: Use consistent dates, currencies, units and definitions. A correct calculation based on inconsistent inputs can still lead to a poor decision.
Use the analysis as a controlled decision-support step: prepare reliable data, review the exceptions, verify the cause and document the action taken.
Clean the source data and confirm the required fields and reporting period.
Run the tool and prioritise the most important menu engineering results.
Validate the cause with contracts, transactions and operational evidence.
Assign actions, export the report and measure improvement in the next cycle.
Decision support
These actions are practical review priorities. Apply your organisation's approval limits, tolerance rules and contractual requirements.
Immediate
Start with records that have the greatest financial, service or operational effect. Confirm the source data before taking action.
Next
Separate genuine performance or demand movement from data quality, timing, unit, currency and process issues.
Monitor
Run the analysis on a consistent schedule, record decisions and compare whether corrective actions improve the next period.
Practical examples
The same result can require a different response depending on product criticality, shelf life, contract terms, service impact and available alternatives.
A high-volume dish has a below-average contribution margin.
Expected outcome: The operator reviews portion cost and price before changing its strong menu position.
A profitable speciality drink has low sales.
Expected outcome: Menu placement, naming and staff recommendation are tested.
Menu engineering combines customer demand with contribution margin. It supports informed decisions about placement, pricing, promotion, portion design and removal while protecting strategically important dishes.
No. Supported CSV and Excel analysis runs locally in your browser.
No. It provides transparent decision support and should be reconciled with approved POS, purchasing and stock records.
Recipe and menu analysis should follow meaningful price or menu changes. Usage and waste analysis is commonly reviewed weekly or by accounting period.