Menu Engineering With Current Ingredient Costs: A Better Way to Price Dishes

The matrix everyone knows, the input everyone fakes

Stars, plow-horses, puzzles, dogs — every operator has seen the menu-engineering matrix. Popularity on one axis, contribution margin on the other. The framework is sound. The problem is the margin axis: most restaurants compute it once, from costs that were true when the menu launched, and never again.

A dish costed in January is a different dish in July. If the matrix runs on stale costs, you will promote yesterday's star that has quietly become a dog.

Current costs change the questions you can ask

• Which plates lost the most margin this month? Not "which have low margin" — which are moving.
• Is the bestseller still worth its menu placement? Volume on a shrinking margin is a leak with good PR.
• Where does a price increase actually stick? Reprice the dishes where cost rose, not everything by 5% across the board.

Pair cost data with sales mix — covered in what operators need from weekly sales-mix reporting — and the matrix becomes an operating tool instead of an annual consulting exercise.

Pricing with a margin floor

The practical discipline: set a margin floor per category, and let current costs tell you when a dish breaches it. When the alert fires, you have four moves — reprice, re-portion, re-source, or redesign the plate. The right answer differs by dish; the wrong answer is not knowing the breach happened. For the fire-drill version, see stress-testing menu margin the same week.

Where HAUS-SYNC fits

HAUS-SYNC keeps every recipe priced against the latest invoice-observed ingredient costs, shows margin by dish alongside sales mix, and lets you run what-if scenarios (price change, portion change, substitution) before you commit the reprint. The matrix stops being a quarterly spreadsheet and becomes the Tuesday-morning screen.