The margin you cannot see

If you asked most multi-site operators how their margins are doing they’ll probably give you a group number. Drinks gross profit of 72%. Food cost at 29%. Numbers that look fine, sit comfortably inside plan, and give nobody a reason to dig further.

The problem with a group number is that it’s an average, and averages are where problems hide.
Take that 72% drinks GP. Break it down by site and you might find one venue running cocktails at 60% against a theoretical 80%. Twenty points of margin, gone. On its own it barely moves the group figure, so nothing flags. But it has been happening every week for months, and nobody can tell you why because answering “why” means putting till data next to pour data next to waste logs, and those three things live in three different systems.

This scattered data is what’s causing the issue, operators want to know their margins but the data needed to explain margin is spread across systems that were never designed to talk to each other.

Front of house knows what sold. Back of house knows what it cost. Nobody is holding both.

Your POS is very good at one thing: recording what customers bought and what they paid. What it can’t tell you is what those sales actually cost you last Tuesday, because ingredient prices moved, one supplier short-delivered, a keg was written off, and portion sizes on the new dish have drifted since the chef who designed it moved sites.

Meanwhile the back of house data that answers all of that, the deliveries, invoices, stock counts, recipe costs and waste, is being captured somewhere else. Often, still, in spreadsheets.

So the two halves of the margin equation never meet in a form anyone can act on. And that has four expensive consequences:

Leakage that never surfaces. The gap between what a dish should cost and what it did cost is where margin quietly disappears. If nothing compares the two, there may be gaps you don’t know about, so can’t manage.

Decisions made on last month’s facts. By the time the month-end pack lands, the shift where things went wrong was three weeks ago.

Menu engineering by guesswork. Pricing a dish on a cost you calculated in January, when your supplier has raised the price twice since, isn’t menu engineering. Some of your best sellers may be your worst performers.

Buying blind. Procurement decisions get made without a clear view of what is actually being consumed, wasted or overcharged across the estate, so the group loses the one advantage its scale should give it.

Closing the loop is a data problem

The instinct is usually to push harder: more stocktakes, tighter portion control, another spreadsheet consolidating the sites. That treats a structural problem as a diligence problem, and it doesn’t hold because it depends on someone finding the time every week, forever.
What actually closes the loop is two things working together.

First, back of house data captured accurately at the point it happens, not reconstructed later. This is exactly what growyze does: purchasing, deliveries, three-way invoice validation, barcode stocktakes, live recipe costing, waste logging. It is the trusted layer underneath everything else.

Second, somewhere that data meets the rest of the business. That is the job of our XMS Business Intelligence product, and growyze data flows into it automatically: operational detail sitting alongside sales, labour, bookings and customer data, so a margin question can actually be answered rather than estimated. XMS BI then turns it into reporting that refreshes regularly, built for operators rather than analysts.

Accurate operational data feeding real-time intelligence. That is the whole idea, and it is why we work with growyze.

Where to start

You don’t need a transformation programme to make progress this quarter. Start with one question: can you show, by site, the gap between theoretical and actual GP for last week?
If the answer is “not without a day of spreadsheet work,” you have found the thing worth fixing first. Everything else like menu engineering, supplier negotiation, benchmarking… gets easier once that number exists on a screen instead of in someone’s head.

We help businesses hit their plan by replacing disconnected systems with connected data and actionable intelligence. Talk to us about your data and see how XMS BI can help and find out how growyze handles the operational layer.