How to read a dish profitability report without getting it wrong
A dish profitability report is the most misread document in hospitality, and the two classic errors both come from looking at one number in isolation.
Key takeaways
- Percentage and cash margin together, never one alone.
- Multiply margin by units sold; that is what pays the rent.
- Some dishes exist to bring people in or to complete a menu.
- Change the recipe or the price before removing a dish.
- A dish selling twice a week is a data question, not a profitability one.
The two-number rule
The percentage is useful for comparing similar items and for spotting a dish whose cost has drifted. It is actively misleading as a menu management tool, because a business pays its rent in pounds rather than in percentages.
So every line carries both, and the report is sorted by total cash margin: margin per dish multiplied by how many sell. That ordering answers the question most people are actually asking.
Popularity and margin together
- Compute
- Machine learning
- Analytics
The second lane
A popular dish with a poor margin is the single largest opportunity on most menus, because a small change is multiplied by a large number of covers. Twenty pence off the cost of something that sells forty times a week is four hundred pounds a year from one adjustment.
The changes available are a smaller portion of the expensive component, a different supplier for it, a garnish that adds perceived value cheaply, or a price rise. All four are less drastic than removing a dish people evidently want.
Dishes that exist for other reasons
Before removing anything, ask what it is for
- The signature dish that people come for and then bring three friends who order other things.
- The menu completer: the vegetarian option, the children’s option, the thing that means a group of six can all eat here.
- The anchor: the expensive item that makes everything else look reasonable, and which does not need to sell much.
- The one that uses the trim from something else, and whose removal makes another dish more expensive.
- The staff favourite is not a business reason, and it is worth saying so plainly.
- None of these are visible in the numbers, which is why the report proposes nothing.
The fourth item is the one a costing system can actually help with, and it is worth checking automatically: removing a dish that consumes the trim from another ingredient changes the yield credit on that ingredient and makes the other dish more expensive. That interaction is invisible unless something is looking for it.
The dish that sells twice a week
- Compute
- Management
- Analytics
Greying out or annotating low-volume lines stops the report from generating a monthly conversation about a dish whose numbers are noise, which is otherwise where a good deal of the attention goes.
What the system does not do
It does not recommend a price, it does not recommend removing anything, and it does not compute an optimal menu. Those all require knowing what dishes are for, what the competition charges, and what the room will bear, none of which are in the data.
What it does is make the arithmetic correct and current, decompose every change, and put the two numbers that matter next to each other. The decisions stay with whoever knows the restaurant.
Next: what all of this costs to run.
All posts