The 3 Reports Every Restaurant Owner Must Run Weekly

Why Your Weekly Reports Aren’t Stopping You Losing Money

Most restaurant owners check sales figures weekly, but the reports they run don’t answer the questions that cost them money. A turnover number tells you how much you’ve made, not how much you’ve kept—or where the leaks are. The three reports below don’t just show you the numbers; they highlight the specific workflows, menu items and staff behaviours that are burning cash every week. Run these, and you’ll spot a £500 labour overrun or a 15% food-cost spike before it becomes a problem. Skip them, and you’re flying blind on the decisions that decide your margin.

The key is to focus on contribution margin—not gross profit, not net profit, but the cash left after direct costs (food, packaging, delivery fees) for every sale. A £20 burger might look profitable, but if the food cost is £8, packaging £1.50 and the marketplace takes £3, your contribution is just £7.50. That’s the number that tells you whether scaling that item or pushing it harder is worth your time.

These reports assume you’re using a system that tracks costs by channel (dine-in, delivery, marketplace) and by item. If you’re still pulling data from spreadsheets or PDFs, you’re already three weeks behind. Reports & Analytics does this automatically—no manual entry, no reconciling.

Report 1: Contribution Margin by Item and Channel

What it tells you: Which menu items are actually making money after their direct costs, and which channels (dine-in, delivery, marketplace) are draining your margin.

How to use it:

• Filter by channel first. A £10 pasta dish might contribute £4 in the restaurant but only £1.50 on a marketplace order (after fees and higher packaging costs). That’s not a pricing problem—it’s a channel problem. If your margin on marketplace orders is consistently 10% lower than dine-in, you’re either pricing delivery wrong or taking orders you shouldn’t.
• Spot the ‘losers’. If a bestseller’s contribution margin drops below 30% for a week, investigate. Is the food cost creeping up? Are you over-serving sides? Or is the marketplace suddenly taking a bigger cut? For example, say your signature burger contributes £6 in the restaurant but £3 on a delivery app. That £3 loss per order adds up to £300 a week if you do 100 of them. Cutting 20% of those orders (by reducing app visibility or raising prices slightly) could save you £600 a month—without losing customers if you redirect them to your own website or loyalty scheme.
• Compare to last week. A sudden drop in contribution for a specific item? Check portion sizes, supplier prices or staff wastage. A rise? You might be able to push that item harder in promotions.

What breaks if you ignore it:

• You keep promoting or scaling items that are secretly unprofitable.
• You assume all sales are equal, so you don’t adjust for the hidden costs of delivery or marketplace orders.
• You miss opportunities to reprice or reposition items that could add £500–£2,000 a month to your bottom line.

Example: A café in London ran this report and found their ‘Build Your Own Bowl’ was contributing just £2.50 on marketplace orders (after £1.20 in food, £0.80 in packaging and 20% marketplace fee). They stopped listing it on apps and moved it to their website with a £1.50 surcharge for delivery. Result: same sales volume, but an extra £1,200 a month in contribution.

Report 2: Peak-Hour Labour Efficiency

What it tells you: How many staff you actually need during peak times—and where you’re over- or under-staffing by the hour.

How to use it:

• Break sales into hourly buckets. If your busiest hour is 7–8pm but you’ve got three staff on for the whole evening, you’re paying for idle time. Use this report to see which hours need extra hands and which don’t. For example, if your kitchen can handle 40 covers an hour with two chefs but you’ve got three on at 9pm, you’re burning £15–£20 an hour in unnecessary labour.
• Compare to last week. Did a promotion or weather change your peak hours? If your usual 6–8pm rush shifts to 5–7pm after a new happy-hour deal, you’ll need to adjust staff rotas to avoid paying for downtime.
• Calculate your ‘ideal’ labour cost. Aim for labour to be 25–30% of sales during peak hours. If it’s creeping above 35%, you’re overstaffed. Below 20%? You’re risking service drops and remakes.

What breaks if you ignore it:

• You pay for staff to stand around during slow patches in peak hours.
• You understaff and lose sales to walkouts or slower service.
• You assume ‘peak’ means all evening, when it might be just two hours—and you’re paying for the whole shift.

Example: A pizza restaurant in Manchester used this report to find their labour cost was 40% of sales at 8pm—double what it should be. They reduced staff by one during the 7–9pm slot and retrained the remaining team to work faster. Labour cost dropped by £800 a week, and customer complaints about wait times fell by 30%.

Pro tip: If your system doesn’t track labour by the hour, use a timer to log when staff start and finish tasks (e.g., prep, service, cleaning). Berryin’s Reports & Analytics does this automatically, pulling from your POS and kitchen display.

Report 3: Food-Cost Variance by Supplier and Item

What it tells you: Where your food costs are creeping up—and whether it’s because of portion sizes, supplier price changes or staff theft.

How to use it:

• Track variance by supplier. If your chicken portions cost 5% more this week than last, was it a price hike from your supplier or are your chefs taking larger cuts? Set a 2% weekly variance limit as your red line. Anything above that needs investigating.
• Compare to your cost targets. If your target food cost is 30% but this week’s report shows 35%, dig into the items driving the spike. Is it a single dish (like a risotto with expensive cheese) or a general trend (e.g., staff over-serving sides)?
• Flag ‘shrinkage’. Missing stock isn’t always theft—it could be spoilage, spills or incorrect portioning. But if your variance report shows a consistent 3% shortfall on a high-turnover item (like fries or salads), assume it’s being taken until proven otherwise.

What breaks if you ignore it:

• You don’t notice supplier price hikes until they’ve eaten into your margin for months.
• You assume ‘food cost’ is a fixed number, when it’s a weekly leak that adds up to thousands.
• You miss opportunities to negotiate better deals or switch suppliers before a small increase becomes a crisis.

Example: A cloud kitchen in Sydney found their food cost had risen from 28% to 34% over four weeks. The report pinpointed two causes: a 10% price increase from their seafood supplier (unnoticed until now) and staff taking extra portions of sides. They renegotiated with the supplier (saving £400 a week) and introduced portion-controlled trays for sides, cutting waste by £300 a week.

How to fix it:

1. Set weekly targets. If your ideal food cost is 30%, aim for a ±1% variance. Anything outside that needs action.
2. Assign ownership. Give one manager the job of reconciling the variance report every Friday. Their bonus could depend on keeping it under 2%.
3. Act fast. If an item’s cost spikes, pull it from the menu or adjust the recipe until you find the cause.

How to Run These Reports Without Losing Your Mind

You don’t need a data scientist to run these—just a system that gives you the numbers by item, channel and hour. If you’re still using spreadsheets or paper logs:

• Manual entry = outdated data. By the time you’ve compiled last week’s figures, it’s already Tuesday. Decisions based on Tuesday’s data are made with yesterday’s problems.
• Human error = hidden leaks. A missed entry in a spreadsheet could hide a £200-a-week labour overrun for months.
• No benchmarks = no action. If you don’t compare this week to last, you’ll never spot the slow bleed.

What you need:

• A POS that tracks costs by item and channel (not just sales).
• A report that updates in real time (or at least daily).
• Alerts for variance over your set limits (e.g., food cost >32%, labour >35%).

Berryin’s Reports & Analytics does all three. It pulls data from your POS, kitchen display and delivery channels, then surfaces the numbers that matter—contribution margin, peak-hour labour efficiency and food-cost variance—in a dashboard that updates as orders come in.

The Hidden Cost of Not Running These Reports

Most restaurants lose 3–5% of turnover to avoidable leaks—wasted food, overstaffing, unprofitable menu items and hidden marketplace fees. That’s £3,000–£5,000 a year for a £100k-turnover café, or £15,000–£25,000 for a £500k restaurant. The reports above don’t just show you the leaks; they tell you how to plug them before they become a crisis.

Example of what you’re missing without them:

• A £1 price increase on your most unprofitable menu item could add £800–£1,500 a month to your bottom line.
• Cutting 15 minutes of idle labour in peak hours saves £500–£1,000 a week.
• Stopping one high-cost marketplace order a day could save £2,000–£4,000 a year in fees.

None of these require a genius—just weekly discipline and the right reports.

Frequently asked questions

How do I know which reports my system actually does?

Check your dashboard for contribution margin by item, hourly labour cost and food-cost variance. If you can’t pull these in three clicks or less, your system isn’t giving you the answers you need. Ask your provider for a demo of these three reports—if they can’t show you how to run them easily, they’re not built for operators.

What if my food cost is already high—can these reports still help?

Absolutely. If your food cost is 35% now, these reports will show you which items are the worst offenders and whether it’s portion sizes, supplier prices or theft. For example, you might find that one dish (like a truffle pasta) is costing you 60%—far higher than your average. Either remove it or adjust the recipe until it fits your target.

Do I need to run these reports every week, or can I do them monthly?

Weekly. Food costs, labour needs and menu performance change every week. A monthly check means you’re flying blind for 26 days out of 30. If you can’t commit to weekly, set up automated alerts for when variance exceeds your limits—then investigate only when something’s wrong.

What if my staff resist using these reports?

Frame it as their problem to solve. For example: “The variance report shows our chicken portions are running 8% over weight—can you check portion sizes this week?” Tie bonuses to hitting targets, and make the reports part of your weekly huddle. If they’re not using them, they’re not protecting their own wages.

Can I use free tools like Google Sheets to run these?

You can, but you won’t get real-time data or automated alerts. A spreadsheet is a lagging indicator—by the time you’ve entered last week’s figures, it’s already Tuesday. For these reports to work, they need to update as orders come in, not after you’ve spent an hour reconciling data.

Start by running these three reports for the next four weeks. Note the leaks you find, then pick one to fix first—usually the biggest margin drain. Once you’ve plugged that, move to the next. The goal isn’t perfection; it’s stopping the bleeding so you can focus on growing what works.