Written by: JJ Tan, Founder, Jelly | Last updated: 17 June 2026
Key Takeaways for UK Multi-Site Operators
- UK multi-site restaurants operate on tight 3–6% net margins, so undetected cost increases across sites can wipe out weekly profit before anyone reacts.
- A centralised margin analysis dashboard connects real-time invoice, POS, and delivery data to calculate CM1 and CM2 at dish, site, and group levels, replacing slow monthly reports with daily visibility.
- Operators are moving from manual spreadsheets to automated systems that use invoice scanning, POS integration, and unified data layers for accurate, comparable performance tracking across every site.
- Key trade-offs when choosing a dashboard include cost versus control, automation versus manual work, real-time versus monthly updates, and how well the system handles multi-site complexity.
- See how Jelly gives UK groups daily CM1 and CM2 visibility with automated insights tailored to multi-site operations.
CM1 versus CM2: the two margin layers that matter
Multi-site operators need to see how delivery channels erode profitability in ways that traditional gross profit tracking cannot show. The table below illustrates how a single dish’s profitability changes once delivery commissions are included.
| Margin layer | What it measures | UK delivery example |
|---|---|---|
| CM1 (Contribution Margin 1) | Revenue minus direct food and beverage cost (Cost of Goods Sold) | A £14 dish with £4.20 food cost = CM1 of £9.80 (70%) |
| CM2 (Contribution Margin 2) | CM1 minus variable channel costs such as delivery platform commission | Same dish on Deliveroo at 30% commission: CM2 = £9.80 − £4.20 = £5.60 (40%) |
Sushi Revolution uses Jelly to set separate target gross profits on dine-in and delivery menus, accounting for 30% delivery commissions, achieving actual gross profits 2–3% higher on average, because CM2 is tracked as a distinct layer rather than blended with dine-in revenue.
Running multiple sites without daily CM1 and CM2 visibility? See how Jelly surfaces both margin layers automatically in a live walkthrough.
How UK operators are moving from spreadsheets to centralised dashboards
Most growing UK groups still rely on per-site spreadsheets updated manually after invoices arrive. Consolidating stock and margin data from multiple spreadsheets into a single report can take days, so the trading week has already finished before anyone reviews performance.
Three architectural changes drive the move to centralised dashboards. First, invoice scanning replaces manual data entry, so invoices arrive by email or photo, every line item is digitised automatically, and ingredient costs update in real time. Second, POS integration supplies the sales side of the margin equation without manual export. Third, a unified data layer joins cost and sales data so that each system stops giving only a partial picture, and site-by-site comparison becomes straightforward.
Centralised dashboards in multi-unit operations unify metrics including labour percentages, average check size, and net profit into one view, enabling instant performance comparisons between locations. For UK operators, the core integrations are Xero for accounting, Square and ePOSnow for POS, and Deliveroo or Uber Eats for delivery channel margin.
Key considerations when choosing a margin dashboard
Four trade-offs help operators decide which margin dashboard approach fits their group.
Cost vs control. Custom hospitality BI development for mid-sized multi-property projects typically starts from £1,000+ for basic dashboards, with larger one-time budgets for complex integrations. Purpose-built platforms charge a recurring subscription but remove development risk and ongoing maintenance.
Manual vs automated. Using static recipe costs in spreadsheets is a major operational risk because supplier prices change frequently due to food price inflation, and manually updating hundreds of recipes is impractical. Automated invoice scanning keeps recipe costs current without extra chef time.
Single-site vs multi-site complexity. Multi-site restaurant operators face extra margin leakage when individual sites order from different suppliers at different prices, increasing cost variability across the estate. A dashboard must normalise those differences into comparable site-level metrics.
Once these trade-offs are clear, the next step is to check whether your operation can adopt a real-time margin dashboard without friction.
Assess your readiness for real-time margin analysis
Five dimensions determine whether your operation can implement a real-time margin dashboard smoothly. The first two, data quality and supplier coordination, control whether cost data flows automatically into the system. The next two, Xero readiness and POS integration, determine whether the system can calculate accurate margins by joining cost and sales data. The final dimension, team adoption, decides whether the system will be used consistently during busy service.
- Data quality: Are supplier invoices consistently received by email or available for photo capture at every site?
- Supplier coordination: Can suppliers be directed to forward invoices to a dedicated inbox without significant resistance?
- Xero readiness: Is the business already on Xero, or is migration planned within the implementation window?
- POS integration: Does the current POS (Square, ePOSnow, or equivalent) support API-level sales data export?
- Team adoption: Are head chefs willing to use a mobile-first tool for recipe costing, or will adoption require structured onboarding?
Operators who can confirm all five are ready for a phased rollout within weeks. Those with gaps in supplier coordination or POS compatibility should resolve those dependencies first, because the dashboard is only as accurate as the data feeding it.
Unsure where your group sits on this readiness scale? Get a no-obligation readiness review from the Jelly team and clarify your next steps.
Implementation roadmap: four phased workstreams
Phase 1: Data layer. Direct all supplier invoices to a dedicated email address or set up a photo-capture workflow at each site. Jelly digitises every line item, including quantity, SKU, price, and tax, within 24 hours of receipt, which removes manual entry from day one.
Phase 2: Costing layer. Build dish recipes using ingredients already populated from scanned invoices. Work that previously took 28 minutes per dish in a spreadsheet takes about 3 minutes in Jelly, because unit conversions and wastage calculations are handled automatically.
Phase 3: Insight layer. Activate Flash Reports for daily, weekly, or monthly GP margin views, Price Alerts to flag every supplier price movement, and Sales Mix reports that link POS data to dish-level profitability. Jelly’s Price Changes feature provides real-time insights into ingredient price fluctuations, enabling pricing decisions, ingredient substitutions, and better supplier deals.
Phase 4: Decision layer. Use Price Alert data to enter supplier negotiations with documented evidence of price creep. Push digitised invoices to Xero in one click, which cuts bookkeeping time by about 90%.
UK integration checklist: Xero for accounting, Square or ePOSnow for POS, Deliveroo and Uber Eats for delivery channel margin, and supplier email forwarding for invoice automation.
Common margin leaks and how dashboards surface them
Operational leakage can cost UK restaurant businesses 5% or more of revenue, so a group turning over £1 million may lose £50,000 in avoidable costs each year. The most common sources appear below.
Delayed invoice data. Without automated scanning, price increases sit undetected in paper invoices for weeks. Without three-way invoice matching, restaurants commonly pay for items never received, such as a delivery arriving 15% short on high-cost ingredients while the invoice reflects the full order quantity.
Inconsistent units and recipe drift. The static-cost problem described earlier shows up as recipe drift. When a supplier changes pack size or price without the spreadsheet being updated, the recipe cost stays frozen and the displayed margin becomes fiction.
Chef adoption barriers. Complex systems that demand heavy manual input are abandoned under service pressure. Jelly’s interface allows non-technical chefs to complete dish costing in under five minutes, which keeps adoption high.
Missed price alerts. Failing to compare theoretical and actual food costs leaves operators blind to losses caused by waste, theft and portioning errors, with best practice targeting a variance of 2% or less.
These leaks explain why the right dashboard characteristics matter so much for multi-site operators.
Best-practice characteristics of an effective multi-site dashboard
An effective multi-site margin dashboard shares five characteristics, and each one addresses a specific failure in traditional spreadsheet-based approaches. The first two, simplicity and timeliness, determine whether the system is used and whether it provides data that teams can act on quickly.
Simplicity. Non-technical chefs must be able to use the system without training beyond initial onboarding. Complexity kills adoption.
Timeliness. Monthly P&L reporting functions as archaeology rather than a real-time decision tool when trading conditions can shift within a week. Daily or weekly refresh is the minimum viable frequency.
The next two characteristics, site-by-site visibility and repeatability, ensure that comparisons across the estate are meaningful.
Site-by-site visibility. Modern financial software enables automated weekly P&L reviews that allow multi-unit operators to compare unit performance side-by-side and immediately investigate outliers such as significantly higher food costs.
Repeatability. The same metrics must be tracked in the same way at every site so that comparisons stay valid. Ad hoc spreadsheets per site undermine this completely.
The final characteristic, ease for non-technical chefs, focuses on real-world behaviour under service pressure.
Ease for non-technical chefs. The Howard Arms owner Ruth Seggie reports: “After using Jelly, we reached 80% gross profit. Now I sleep better knowing my costs are under control and can react instantly, not weeks later.”
Want to see these characteristics in a live environment? Walk through a real multi-site Jelly setup and see how each element works in practice.
Build versus buy: decision framework for UK operators
The table below compares three approaches across the factors that matter most for multi-site margin tracking: onboarding speed, automation level, multi-site visibility, and total cost over time.
| Attribute | Spreadsheets | Custom BI (Power BI / Tableau) | Jelly |
|---|---|---|---|
| Onboarding time | Immediate but manual | Weeks to months for complex integrations | Initial value within first week |
| Real-time invoice data | No, manual entry only | Possible with custom connectors | Yes, automated scanning |
| Multi-site comparison | Manual consolidation taking days | Yes, with development effort | Yes, built-in site-level views |
| Flat-rate pricing | Free, with hidden time cost | £1,000+ implementation plus licensing | £129/month per site |
What is the average profit margin for restaurants in the UK?
Most UK restaurants operate with average net profit margins between 2% and 6%, with full-service restaurants typically at 3–6% and bars and pubs at 7–10%. A net margin of 6% or higher is considered healthy for the majority of UK restaurants. Gross margins sit significantly higher.
What is a good EBITDA margin for restaurants?
UK-specific EBITDA benchmarks for restaurants are not widely published at sector level. US data from Damodaran’s dataset reports an average EBITDA margin in the high teens, a figure that reflects the inclusion of large publicly listed chains with significant scale advantages. UK independent and small-group operators should treat this as an upper-bound reference rather than an operational target, because structural cost differences between US and UK hospitality markets are material.
What is the best accounting method for restaurants?
Accrual accounting is the standard for UK restaurants with turnover above the VAT threshold, because it matches costs to the period in which they are incurred rather than when cash moves. For operational margin analysis, accrual-based invoice data integrated directly with a platform like Jelly, then pushed to Xero in one click, provides the most accurate daily cost picture. Cash-basis reporting, while simpler, hides the true cost of goods in any period where invoice payment timing differs from delivery timing.
2026 trends in restaurant margin reporting
A weekly trading dashboard that includes revenue versus target by day, gross margin at category or site level, labour cost as a percentage of revenue, and written commentary on material movements is becoming the baseline expectation for professionally managed UK hospitality groups in 2026, so it now functions as a hygiene factor rather than a differentiator.
Anomaly detection now represents the next frontier. Back-office modules that auto-reconcile supplier invoices and flag cost variances are increasingly standard in purpose-built platforms, replacing manual price-checking that previously consumed 10–20 hours of chef or manager time per week. Delivery Performance Dashboards that centralise net sales, margin and average order value broken down by virtual brand, geography and individual site are also gaining traction as delivery channel mix becomes a material margin variable for UK groups.
Frequently Asked Questions
What is the difference between CM1 and CM2 in a restaurant context?
CM1, or Contribution Margin 1, is revenue minus the direct cost of food and beverage, so it functions as gross profit at dish or category level. CM2, or Contribution Margin 2, deducts variable channel costs from CM1, most commonly delivery platform commissions. For a UK restaurant selling through Deliveroo at a 30% commission rate, a dish with a 70% CM1 may have a CM2 closer to 40% once the commission is included. Tracking both layers separately is essential for multi-site operators running mixed dine-in and delivery channels, because blended reporting hides which channel actually generates profit.
How quickly can a multi-site UK operator expect to see value from a margin dashboard?
With Jelly, operators typically gain access to Price Alerts and spending insights within 24 hours of photographing invoices or directing suppliers to forward invoices to a dedicated email address. Full dish costing and live GP margin visibility are usually operational within the first week. Jelly customers report an average reduction in food costs of 3% within the first three months, and gross margins increase by an average of 2 percentage points over the same period. The Amber restaurant case study documents savings of £3,000–£4,000 per month from the first months of use.
Who should own the margin dashboard within a multi-site hospitality group?
Ownership usually sits with the finance manager or operations director at group level, while head chefs at each site handle recipe costing and invoice capture. The critical design principle states that the system must not depend on chefs performing significant manual data entry, because adoption breaks down under service pressure. Jelly’s architecture addresses this by automating invoice scanning so that cost data updates without chef intervention, while giving management direct dashboard access to verify figures independently.
What integrations are essential for a UK multi-site margin dashboard?
The minimum viable integration set for a UK multi-site operator includes a POS system, usually Square or ePOSnow in the Jelly customer base, for sales data, an accounting platform such as Xero for financial reconciliation, and an invoice capture mechanism, either email forwarding or photo upload, for cost data. Delivery platform integration with Deliveroo and Uber Eats becomes important once delivery revenue exceeds roughly 15–20% of total revenue, because CM2 margin tracking requires accurate commission data at order level.
How does Jelly’s pricing compare to building a custom dashboard?
Jelly charges a flat rate of £129 per month per site with no per-user or per-feature charges. Custom BI solutions built on Power BI or Tableau typically require a one-time implementation budget starting from £1,000 for basic dashboards, plus ongoing licensing and maintenance costs, and several weeks to months of integration work before delivering real-time invoice-driven data. For a two-to-five site UK group, Jelly’s total cost over a 12-month period is materially lower than a custom build, and the time to first value is measured in days rather than months.
Conclusion
For UK multi-site restaurant, pub, and hotel operators, the shift from monthly spreadsheet reports to daily invoice-driven margin analysis has become an operational necessity rather than a technology experiment. With the tight margins documented earlier, a single undetected supplier price increase or a delivery channel running at untracked CM2 erosion can eliminate a week’s profit before anyone notices.
The practical path forward follows a four-phase implementation: automate invoice capture first, build live dish costing second, activate daily flash and price alert reports third, and use the resulting data to drive supplier negotiations fourth. Jelly delivers all four workstreams at £129 per site per month, with integrations covering Xero, Square, ePOSnow, Deliveroo, and Uber Eats, and an interface simple enough for non-technical chefs to use from day one.
Ready to move from spreadsheets to daily margin visibility across every site? See Jelly running on a live multi-site setup and decide whether it fits your group.
