Menu Engineering Dashboard | Real Minds AI
Retail & Hospitality /Document Generation live field guide · 9 min

Menu Engineering Dashboard

Combines POS sales with cost-of-goods to score every menu item by margin and velocity, classifies them star/plow-horse/puzzle/dog, and recommends what to feature, reprice or cut — for the manager to check against the data before changing the menu.

theater/demos/retail-hospo_menu-engineering.html · sandbox · read-only
Open
FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads each menu item's sales count and food cost, plots it on the popularity-versus-margin matrix, and surfaces a ranked list of reprice, feature and cut suggestions for a venue manager to approve before any change reaches the menu.

Input 01
The sales export + cost cards

A trading period's POS sales by item — order count and price — plus the current cost-of-goods for each dish, so margin can be worked out per item rather than guessed at the category level.

Agent 02
Classifies, ranks, suggests

Works out contribution margin and sales velocity for every item, places each in the star / plowhorse / puzzle / dog quadrant, and ranks the reprice, feature and cut candidates by projected weekly impact.

Output 03
A ranked action list, working shown

A suggested-actions list — feature this, reprice that, replace this dog — each with the numbers behind it, for the venue manager to approve, edit or reject. Nothing changes on the menu on the tool's say-so.

Where it works well

It does the per-item margin-versus-popularity maths across the whole menu, every period, in full.

  • Done by hand it is a spreadsheet job that gets deferred for months, so the menu drifts on yesterday's costs while supplier prices move under it.
  • Best for a venue or F&B manager reviewing a 30-plus-item menu periodically: end of month, seasonal menu change, after a supplier price rise.
  • For a multi-venue operator, the recaptured hours go into standardising the highest-margin dishes across sites and into the guest experience, not into rebuilding the same spreadsheet four times.

The slow, invisible problem is that the best-selling dish and the most-profitable dish are almost never the same one — and you cannot see the gap from the till total. A high-volume seller carried at a thin margin quietly drags the whole menu, while a high-margin dish nobody orders sits buried at the bottom of page two.

Where it works badly

It is confidently wrong when the cost cards are stale or incomplete — and a clean-looking quadrant hides it.

  • Weak where the cost card is missing wastage, prep loss or the labour-heavy items — a slow-cooked dish costed on ingredients alone looks far better than it is.
  • A reprice suggestion is a margin calculation, not a market call — it does not know your local price ceiling, your competitor down the road, or that the item is a loss-leader you keep on purpose.
  • If your menu is small and stable and you already know your numbers cold, the dashboard tells you what you already knew.
The honest test

If you cannot say, right now, when each dish's cost card was last updated against real invoice prices, this tool makes your wrong costing look rigorous — it does not make it right.

Feed it a recipe cost that hasn't been updated since the last produce price rise and it places a dish as a "star" that is actually being sold at a loss. The chart looks authoritative; the cost behind it is months out of date. That is the trap.

What it doesn't do — and shouldn't

It suggests. A person approves. That boundary is deliberate.

WHAT IT DOES
Surfaces the contribution margin and order count behind each item's placement
Shows the projected weekly impact figure behind every suggested action
Flags the dogs and plowhorses as candidates for a human decision
WHAT IT WON’T
Change a price, pull a dish, or republish the menu
Judge whether a reprice respects your local market or a loss-leader you keep on purpose
Account for award penalty rates, surcharge disclosure or food-safety scope on its own

A menu change ripples past margin. Repricing interacts with how you handle weekend and public-holiday surcharges — and the Australian Consumer Law, enforced by the ACCC, requires the displayed price to be the real total a diner pays, with any day-specific surcharge clearly disclosed on the menu. Cutting or changing dishes can touch your food-safety scope under the FSANZ Food Standards Code, and rostering for a busier featured item runs into the Restaurant Industry Award. The manager stays on the decision because those consequences land on the venue, not the tool.

What your data has to look like

Accurate per-item costs and clean per-item sales counts — not category totals.

44%
Typical readiness
across orgs we see, before the first job
Current recipe cost cards per dish
Needs shaping
POS sales broken out by individual item
Usual weak point
Selling price as actually charged
Usual weak point
A consistent trading period to compare
Usually ready
Item names that match between POS and recipe file
Needs shaping
The real first job

The recipe cost cards are usually the weak point — built once at opening and never re-costed as supplier prices moved, or never split out from a rolled-up food-cost percentage at all. Fixing how dish costs and per-item sales are captured and kept current is usually the real first job — bigger and more valuable than the dashboard on top. Once the costs are honest, every menu review after that is fast and right by default.

Right fit if…
You run a 30-plus-item menu and review it periodically — month end, seasonal change, after a price rise
You keep recipe cost cards and update them against real invoice prices
Your POS breaks sales out by individual item, not just by category
You operate several venues and want to compare and standardise the highest-margin dishes
Walk away if…
Your menu is small and stable and you already know every dish's margin cold
Your dish costs are a single rolled-up food-cost percentage with no per-item cards
Cost cards were built at opening and never re-costed since
You want a tool that sets prices for you rather than showing you the numbers
Open questions

The worried-buyer questions, answered straight

It can suggest a wrong move — which is why nothing changes on its say-so. Every suggestion shows the contribution margin, the order count and the projected weekly impact behind it, and a venue manager approves, edits or rejects each one. It does not know your local price ceiling or a loss-leader you keep on purpose, and it does not handle surcharge disclosure: under the Australian Consumer Law, enforced by the ACCC, the price you display has to be the real total a diner pays, with any weekend or public-holiday surcharge clearly stated on the menu. The tool surfaces the maths; the person makes the call.
It works from per-item costs and per-item sales, so a single rolled-up food-cost percentage gives it nothing to place on the matrix. If a dish’s cost card is stale or missing its wastage and prep loss, the tool plots it confidently in the wrong quadrant — it can’t tell an out-of-date cost from a current one. Getting recipe costs and POS item sales into clean, current form is usually the first piece of work, and the piece that pays off across every menu review after.
No. It does the spreadsheet maths a manager would do if they had a clear day — margin and velocity for every item, ranked by impact — so their judgement goes to the calls that need it: whether a price respects the local market, whether a dog stays for menu balance, whether a featured dish can be rostered for under the Restaurant Industry Award. The menu is still theirs. The capacity it frees goes back into the food and the floor.
Current to the period you’re reviewing. Produce and supplier prices move, so a recipe cost card that hasn’t been re-costed since the last price rise will place a loss-making dish as a star. Point it at last quarter’s costs and it gives you a clean, professional chart built on numbers that no longer hold. The honest test: can you say when each dish’s cost card was last updated against real invoice prices?
The analysis runs against your own POS export and cost data within the controls you set — nothing is published, sent or actioned without a manager approving it. Sales and recipe data is commercially sensitive, so we scope where it sits, how long it’s kept and who can see it as part of the build, rather than pooling it anywhere shared. The demo here runs entirely on fabricated data — Chicken Parma, Mushroom Risotto and the rest are invented menu items, not a real venue’s figures.
No, and it shouldn’t pretend to. It is a margin-and-popularity tool. It does not roster staff under the Restaurant Industry Award, set surcharges under the Australian Consumer Law, or scope your food-safety obligations under the FSANZ Food Standards Code — all of which a real menu change can touch. It surfaces which dishes are worth a closer look and what the margin maths says; the manager weighs those other obligations before acting.
What it takes to build
3–4 weeks · 4 phases
Reused from template~70%
Bespoke to this skin~30%
stack · Claude · POS connectors · analytics dashboard · review UI
What it would cost

Fixed scope, fixed price, fixed dates.

01
Bite-sized first piece
One contained change, low risk
02
Pilot build
Most builds land here
03
Embedded support
Scale on proof

Considering this for your venue?

The honest place to start is a bite-sized first piece — one menu, one trading period, low risk. Tell us where it hurts; we'll play it back, scope it, and show you what's possible.

More in Retail & Hospitality
Review-Response Drafter
View →
Council Enquiry Assistant
View →
Order Intake Sorter
View →
Missed-Call Rescue & Booking Agent
View →
How We Work Proof Talk to us
How We Work Proof Talk to us
Ask us anything