The hospitality & catering value tree
Hospitality margin is decided per dish, per cover, per outlet, every day — and reported per month, by which time the decisions that made it are three weeks old.
01 The same tree, this industry
Where the money is made and lost here
The structure does not change: value is profit plus how well that profit becomes cash, profit is revenue minus cost, and revenue is price times quantity. What changes is which drivers sit underneath each branch, and which system holds them. If you have not read the general version, start with the Enterprise Value Tree and come back.
This tree has the shortest feedback loop and the slowest reporting in the set. Food is bought, prepared and wasted within days; labour is rostered a week ahead against demand that moves hourly. Anything that arrives as a monthly P&L is a post-mortem, not a control.
Every driver below names the metric it lands on. Follow one and you get its formula, the system the number lives in, and the ways it is commonly misread.
02 Price
What decides the price you actually get
Menu pricing and engineering
Not what a dish costs plus a margin — what it contributes, against how often it is ordered and what it displaces.
Contribution margin (net_revenue − variable_cost) ÷ net_revenuePriceSpend per head
Covers times average spend. The second half is a service and merchandising outcome, not a price-list one.
Average order value net_revenue ÷ ordersPriceChannel and commission
Delivery aggregators and OTAs take a share that turns a healthy dish margin into a marginal one.
Cost to serve (delivery + service + returns + order_handling) ÷ customers or ordersPricePromotions and packages
Volume bought with margin, evaluated on covers rather than on contribution.
Price realisation net_revenue ÷ list_revenuePriceContract catering rates
Fixed rates against variable food cost, where inflation lands on you unless indexation was written in.
Price realisation net_revenue ÷ list_revenuePriceUpsell and attachment
Sides, drinks and desserts: the highest-margin part of the bill and the most operationally driven.
Attach rate orders_containing_the_attached_item ÷ eligible_orders03 Quantity
What decides how much you sell
Covers and footfall
How many people you served, by outlet and by daypart. The base every other number divides by.
Active customers count(distinct customers with at least one purchase in the window)VolumeSeat turns and occupancy
Utilisation of a perishable resource. An empty table at eight o'clock cannot be sold later.
Capacity utilisation actual_output ÷ practical_capacityVolumeOutlet and daypart mix
Breakfast, lunch and dinner have completely different economics in the same space.
Contribution margin (net_revenue − variable_cost) ÷ net_revenueVolumeDelivery channel volume
Incremental covers with a different cost structure and a different customer you may not own.
Purchase frequency orders_in_period ÷ active_customersVolumeRepeat and loyalty
The base that survives a competitor opening across the street.
Customer retention rate customers_retained ÷ customers_at_startVolumeContract sites
In contract catering, the estate under management and its renewal profile.
Net revenue retention (starting_revenue + expansion − contraction − churn) ÷ starting_revenue04 Cost
What it takes to operate
Food cost and wastage
Theoretical against actual consumption. The gap is portioning, spoilage, over-production and theft — four problems in one number.
Scrap and yield scrapped_quantity ÷ total_produced (yield is the inverse)CostLabour against demand
Rostered a week ahead on last year's pattern, paid against this week's covers.
Capacity utilisation actual_output ÷ practical_capacityCostProcurement price variance
The same item bought at different prices across sites, invisible without one item master.
Price realisation net_revenue ÷ list_revenueCostDelivery commission
A cost per order that varies by platform and by promotion, rarely allocated to the dish.
Cost to serve (delivery + service + returns + order_handling) ÷ customers or ordersCostEnergy per cover
Kitchens run whether they are busy or not, so intensity moves with volume as much as with efficiency.
Energy per unit energy_consumed_kWh ÷ units_producedCostStock losses and shrinkage
Beverage and high-value items, where a small percentage is a large number.
Inventory turns cogs ÷ average_inventory_value05 Cash
Where the cash actually sits
Perishable stock cover
Days of cover on items that expire. Too much is waste; too little is a menu you cannot serve.
Stock cover current_stock ÷ average_daily_demandCashSupplier terms
Fresh produce bought on short terms while receivables in contract catering run long.
Days payables outstanding (accounts_payable ÷ cogs) × days_in_periodCashContract receivables
B2B catering paid monthly in arrears against daily cost.
Days sales outstanding (accounts_receivable ÷ net_revenue) × days_in_periodCashDeposits and prepayments
Events and functions paid before delivery — negative working capital, if it is tracked.
Cash conversion cycle dso + dio − dpoCashFit-out capex
Committed per site, recovered over a lease term, and rarely revisited per outlet.
Capex intensity capital_expenditure ÷ net_revenueCashInventory turns
How hard the same stock investment works across a multi-site estate.
Inventory turns cogs ÷ average_inventory_value06 Where the numbers live
The systems behind the branches
A value tree is only usable once each box maps to a system and a record. These are the six that matter most in hospitality & catering: what each one is actually for, the records inside it the tree depends on, and which branch it feeds.
| System | What it holds | Key records | Feeds |
|---|---|---|---|
| POS | Every item sold, by outlet, daypart and server — the only record of what the guest actually chose. | Check, Line item, Outlet, Daypart, Server | Price, quantity |
| Inventory and recipe management | Recipes, theoretical consumption, stock counts and the variance between them. | Recipe, Ingredient, Stock count, Variance | Cost, cash |
| Procurement | Purchase orders, supplier prices and the item master that lets one site's price be compared with another's. | Item, Supplier, Purchase order, Price list | Cost, cash |
| Rostering and time attendance | Planned shifts against actual hours worked, by outlet and daypart. | Employee, Shift, Clock event, Skill | Cost |
| PMS / booking or contract system | Occupancy, reservations, events and the contracted scope in B2B catering. | Reservation, Event, Contract, Cover forecast | Quantity, price |
| Finance | The outlet P&L, which arrives weeks after the decisions that shaped it. | GL account, Cost centre, Outlet, Period | Cost, cash |
Almost every hard question in hospitality & catering needs two of these joined. That join — not the calculation — is the work.
07 Where it leaks
Value lost between two systems
These are the losses that no single system can see, because the evidence is split across two of them. Each one is a real number that stays invisible until the join exists — which is why the tree is an integration exercise before it is an analysis one.
| Where value leaks | Why it happens | The join that finds it |
|---|---|---|
| Waste counted, never costed | Kitchens record what was thrown away in units while the value sits in the recipe and purchase price. Waste is discussed as a percentage and never as a margin line. | Join waste records to recipe cost and purchase price, per site per day |
| Theoretical against actual consumption | The recipe says one portion uses 180g; the stock count says otherwise. Without the join, over-portioning is invisible and permanent. | Join POS items sold x recipe to stock movements, weekly |
| Labour rostered on last year | Rosters are built from historical patterns while bookings and weather predict this week. The variance is paid as overtime or lost as service. | Join the roster to forward bookings and actual covers by daypart |
| The same item at four prices | Each site buys under its own code, so procurement cannot compare, negotiate or standardise. | One item master across the estate, resolved from local codes |
| Delivery orders costed like dine-in | Commission, packaging and the discount that won the order are absorbed centrally while dish margin is judged on the recipe. | Join channel commission and packaging cost to the order and the dish |
08 Worked example
From "how much did we sell?" to "what makes money?"
Revenue was up and contribution was flat. The tree separates it: wastage sat well above the theoretical recipe cost, labour was rostered against last year rather than forward bookings, delivery grew at a commission that dish margins never accounted for, and the same core ingredients were bought at four different prices across sites.
| Component | Effect | What sits behind it |
|---|---|---|
| Covers | +€1.8m | Growth weighted to delivery and lunch |
| Food wastage | −€0.7m | Actual consumption above recipe theoretical |
| Labour variance | −€0.5m | Rostered on last year, paid on this week |
| Delivery commission | −€0.4m | Channel mix shift, dish margin unchanged |
| Purchase price variance | −€0.2m | One item, four site prices |
| Net | +€0.0m | More covers, the same contribution |
Illustrative figures, shown to demonstrate the split. The point is the shape of the walk, not the numbers — on your own data the same bridge is built from your ledger.
09 Diagnostics
Six questions to ask in hospitality & catering
Ask them of your own team before anyone asks them of you. In most organisations at least two of these cannot be answered without a manual exercise, and those two are the plan.
- Can you see food cost variance by site and by dish this week, or only in the monthly P&L?
- What did you throw away yesterday, and what did it cost?
- Is the same ingredient bought at the same price across every site?
- Is your roster built from forward bookings or from last year's pattern?
- What is the contribution of a delivery order after commission, packaging and promotion?
- Which dishes are popular and unprofitable — and when did you last change one?
10 The metrics behind it
Definitions for every box
11 Questions
Frequently asked
Why is monthly reporting such a problem here?
Because the decisions are daily. A P&L that arrives three weeks after month end describes ninety-plus service periods that can no longer be changed. Daily cost visibility per site is the whole difference between reporting and managing.
What is the fastest win in a multi-site operation?
One item master and purchase price variance across sites. It needs no behaviour change from the kitchens and usually pays for itself before the menu is touched.
How should delivery channels be evaluated?
At order level, after commission, packaging and promotional discount. Delivery is often incremental volume at a fraction of the contribution, which is a fine trade if it is a decision rather than a surprise.
Is wastage really the biggest lever?
It is usually the largest recoverable one, because it is pure loss rather than a trade-off. Cutting it does not reduce covers, service or quality — which is not true of most other cost lines in this tree.
See this tree on your own data
Connect the systems above, define each box once, and the tree stops being a slide.