Written by: JJ Tan, Founder, Jelly | Last updated: 22 June 2026
Key Takeaways for Multi-Site Food Cost Control
- A repeatable, centralised operating model controls food costs across multiple restaurant sites better than disconnected spreadsheets.
- The 8-step system standardises recipes, automates supplier price monitoring, reconciles theoretical versus actual costs, and gives daily GP visibility across all locations.
- UK multi-site operators can save 10–20 hours of weekly manual work with structured, automated food costing processes.
- With food prices projected to rise 3%–5% in Q1 2026, variance above 3% of weekly food spend signals systemic issues that need immediate action.
- Book a demo with Jelly to see how this 8-step system protects margin and removes manual admin from your teams.
Why Multi-Site Food Costing Is Now Non-Negotiable
Food and beverage prices are projected to rise 3%–5% in Q1 2026 and 3%–4.5% in Q2 2026, remaining elevated for the next 9–12 months, with beef at record highs and no relief anticipated until 2027–2028. At the same time, the UK hospitality sector loses £3.2 billion annually to food waste. A food cost percentage that drifts from 28% to 34% can erase a venue’s entire net profit.
For groups running two or more sites, that drift compounds silently across every location until a monthly report finally surfaces the damage, weeks too late to act. Variance above 3% of weekly food spend signals something systemic is wrong. A structured, automated operating model applied consistently across every site provides the only reliable fix.
The Complete 8-Step Operating Model for Multi-Site Groups
| Step | Owner | Frequency | Jelly Automation Benefit |
|---|---|---|---|
| 1. Centralised recipe database with live costing | Executive Chef | Ongoing | Invoice scans update ingredient costs in real time, dish GP recalculates automatically |
| 2. Approved supplier lists and price alerts | Operations / Chef | Ongoing | Price Alert flags every increase or decrease by SKU and supplier |
| 3. Theoretical vs actual variance tracking | Finance / Chef | Weekly | Flash Report compares POS sales data against invoice costs automatically |
| 4. Inter-site inventory transfer management | Site Managers | As needed | Transfers logged in Jelly, stock values adjust across both sites instantly |
| 5. Cross-site benchmarking dashboards | Operations / Finance | Weekly | Consolidated GP% and spend data visible across all locations in one view |
| 6. Portion control and waste logging | Head Chefs | Daily | Standardised recipe cards enforce portions, POS integration validates yield |
| 7. Monthly and quarterly review cadences | Owner / Finance | Monthly / Quarterly | Historical cost and margin data exportable for supplier and menu reviews |
| 8. Menu engineering and sales mix analysis | Owner / Chef | Monthly | Sales Mix report identifies highest-margin, highest-volume dishes by site |
Step 1 – Build a Centralised Recipe Database with Live Costing
Every recipe card must include portion sizes in grams and millilitres and be accessible to all kitchen staff. This forms the baseline for every theoretical cost calculation across the group. In Jelly’s Cookbook, chefs build dishes by clicking on ingredients already populated from scanned invoices. The system handles unit conversions and wastage percentages automatically.
What previously took 28 minutes per dish in a spreadsheet now takes under three minutes in Jelly. Ingredient costs update with every new invoice, so the GP margin for every dish stays live. A red percentage appears when a dish drops below target and green when it improves, which prompts immediate action.
Step 2 – Lock In Approved Suppliers and Automated Price Alerts
Centralising purchasing with group-wide prices from a select list of approved suppliers increases buying power and consistency across locations. With the commodity volatility and sustained price increases outlined earlier expected to persist through 2026, passive monitoring no longer protects margin.
Jelly’s Price Alert feature flags every price increase or decrease by SKU and supplier the moment a new invoice is scanned. Chefs and operations managers receive hard data to challenge suppliers, claim credit notes, or switch to an approved alternative before the impact compounds across sites.
Step 3 – Track Theoretical vs Actual Costs Within the 2–3% Threshold
Industry best practice keeps the variance between theoretical and actual food cost at 2% or less. Anything beyond that directly indicates waste, inconsistent portioning, unrecorded items, or shrinkage. Staying within the 2–3% variance threshold mentioned earlier requires daily visibility into the gap between theoretical and actual costs.
Jelly’s Flash Report compares POS sales data against invoice costs automatically on a daily, weekly, or monthly basis. Teams no longer need manual reconciliation. Weekly tracking and variance analysis can drive a 3–6% improvement in food cost within a single quarter.
Step 4 – Record Every Inventory Transfer Between Sites
Untracked inter-site transfers create one of the most common sources of phantom variance in multi-site groups. When Site A sends surplus protein to Site B without a formal log, both sites report inaccurate stock values. The group-level food cost figure then becomes unreliable.
Every transfer should be recorded at the time it occurs. The sending site reduces stock and the receiving site increases it at the same cost value. Use this checklist as a minimum standard:
- Date and time of transfer
- Sending site and receiving site
- Item name, SKU, and unit of measure
- Quantity transferred and cost per unit (from most recent invoice)
- Authorised by (name and role)
- Received and confirmed by (name and role at receiving site)
Jelly logs transfers within the platform so stock values adjust across both sites instantly. This removes the manual spreadsheet step that usually delays reconciliation by days.
Step 5 – Use Weekly Cross-Site Dashboards to Spot Outliers
Weekly benchmarking highlights which sites perform above or below group GP targets before variance turns into a monthly problem. The following KPI template provides a practical weekly dashboard for any multi-site group:
- GP% by site (target vs actual)
- Food cost % by site
- Top 5 spend categories by site
- Variance from theoretical food cost by site
- Number of price alerts triggered (by supplier and site)
- Waste log total by site
Jelly’s consolidated view surfaces all of this data across locations in one place. Teams replace hours of pulling figures from individual site spreadsheets and manually combining them.
Step 6 – Tie Portion Control and Waste Logs to Measurable KPIs
Portion inconsistency quietly erodes margin in multi-site operations. A 10g over-portion on a protein dish served 200 times per week across five sites creates a material cost variance that never appears as a single identifiable event.
Standardised recipe cards with gram-level specifications, calibrated scales at every station, and daily waste logs act as the operational controls that prevent over-portioning at the point of service. These controls only work when teams can verify that theoretical yields match actual sales volumes. Jelly’s POS integrations connect item-level sales data directly to recipe costs, so yield assumptions can be validated against actual sales volumes in real time rather than estimated at month end. Portion control then shifts from a kitchen discipline to a measurable, trackable KPI.
Step 7 – Run Monthly and Quarterly Reviews with Live Data
Quarterly menu pricing reviews based on live supplier costs, combined with sales-data-driven PAR levels, keep stock lean, reduce spoilage, and prevent cash from being tied up in excess inventory. Monthly reviews should assess GP% by site against group targets, identify dishes where ingredient cost increases have eroded margin below threshold, and flag suppliers with repeated price creep.
Quarterly reviews should include formal supplier performance meetings using Jelly’s Price Alert history as the evidence base. They should also include a full menu engineering exercise using the Sales Mix report to retire low-margin, low-volume dishes.
Schedule a chat to see how Jelly structures these reviews for multi-site groups.
Common Multi-Site Food Costing Failures and Fixes
Untracked transfers: Stock moves between sites without documentation, which creates phantom variance at both locations. Fix: mandate the transfer checklist above and log every movement in a centralised system on the day it occurs.
Inconsistent stock counts: Different sites count on different days, use different units, or skip categories. Fix: standardise count sheets, count days, and responsible roles across all sites. Use short-form weekly counts on high-value categories instead of full counts that get skipped due to time pressure.
Delayed data: Finance receives monthly reports from accountants after the period has closed, which makes corrective action impossible. Fix: connect invoices and POS data to a live platform so GP is visible daily, not monthly. Jelly’s Flash Report delivers this without waiting for an accountant.
Recipe drift: Chefs at individual sites modify recipes without updating the central database, which breaks the link between theoretical and actual cost. Fix: lock recipe cards in a centralised system and require authorisation for any change that affects cost by more than 0.5%.
Manual vs Automated Food Costing Across Your Sites
The time savings and margin gains from automation compound across every site in a multi-site group. The table below shows the weekly time investment for each core process under manual spreadsheet management versus Jelly’s automated approach, and links those savings to direct margin impact.
| Process | Time per week (manual) | Time per week (Jelly) | Margin impact |
|---|---|---|---|
| Invoice entry and price checking | 5–8 hours | Under 30 minutes | Price alerts recover credits and prevent unnoticed cost creep |
| Recipe costing (per dish) | ~28 minutes per item | ~3 minutes per item | Live GP on every dish, red/green margin flags trigger immediate action as described in Step 1 |
| Theoretical vs actual reconciliation | 3–5 hours | Automated via Flash Report | Enables the quarterly improvement range cited in Step 3 |
| Cross-site GP reporting | 4–6 hours (manual consolidation) | Real-time consolidated dashboard | 2–3 percentage point GP lift; one operator improved GP from 65% to 72% within 12 weeks on ~£500,000 revenue |
How Jelly Delivers This 8-Step System in Practice
Jelly is built for UK restaurant, pub, and boutique hotel groups at the £500k+ revenue stage that have outgrown spreadsheets. Invoices are captured by photo or email, and Jelly scans every line item, including quantity, SKU, price, and tax, then populates the ingredient database automatically. Recipe costs update in real time as new invoices arrive.
The Flash Report delivers daily, weekly, or monthly GP visibility by combining invoice costs with live POS sales data from Square, EPOS Now, Lightspeed, and Toast. The Price Alert feature flags every supplier price movement the moment it appears on an invoice. The Sales Mix report highlights which dishes drive margin and which erode it.
Jelly charges a flat rate of £129 per site per month with no per-user fees and no hidden charges. Onboarding generates initial value within the first week. Price alerts and spending insights go live as soon as suppliers send invoices to a dedicated Jelly email address, or within 24 hours of the first photo upload. Customers cut food costs by an average of 3% in the first three months and see an average 2 percentage point improvement in gross margins. Amber restaurant in East London saves £3,000–£4,000 per month, approximately 68× ROI, using Jelly’s invoice automation, price alerts, and live recipe costing.
Book a demo and get the 8-step system running across your sites within a week.
Frequently Asked Questions
How long does onboarding take with Jelly?
Jelly is designed to generate value in the first week, not after months of setup. Once suppliers send invoices to a dedicated Jelly email address, price alerts and spending insights go live immediately. For operators who prefer to photograph invoices, the same data becomes available within 24 hours of the first upload.
Connecting a supported POS system such as Square, EPOS Now, Lightspeed, or Toast takes approximately five minutes. Full recipe costing and live GP reporting typically become operational within the first week of use.
What does £129 per site per month include?
The £129 flat rate covers all of Jelly’s features for that location. These include automated invoice scanning, the Insights Dashboard, Flash Report, Price Alert, Sales Mix report, Cookbook with live dish costing, delivery menu creation, and accounting integration with Xero. There are no per-user charges and no feature tiers, so every site on the platform accesses the full feature set at the same price.
How accurate is automated food costing compared with manual spreadsheets?
Automated costing via Jelly is more accurate than manual spreadsheets because ingredient prices update with every scanned invoice. Manual spreadsheets rely on a team member to re-enter figures, which rarely happens in real time. Spreadsheet-based costing is only as current as the last manual update, so dish costs can be weeks out of date during periods of supplier price volatility.
Jelly’s live costing means every dish GP reflects the most recent invoice price at all times. This accuracy underpins the 2–3 percentage point GP improvements seen across Jelly’s customer base.
Can we still negotiate directly with our suppliers using Jelly?
Teams continue to negotiate directly with suppliers, and Jelly makes those negotiations more effective. The Price Alert feature creates a complete, timestamped record of every price increase and decrease by SKU and supplier. This gives chefs and operations managers concrete evidence for supplier meetings, including exact dates, exact amounts, and the cumulative cost impact across the group.
Customers consistently use this data to claim credit notes and secure better rates. The negotiation relationship with suppliers remains entirely in the operator’s hands, while Jelly provides the data that makes those conversations more productive.
How does Jelly handle food costing across sites with different menus?
Each site in Jelly maintains its own recipe database and menu, while the group-level dashboard consolidates GP and spend data across all locations. Sites sharing common dishes benefit from centralised recipe cards that update automatically when ingredient costs change, so a price increase on a shared protein updates the dish cost at every site simultaneously.
Sites with unique menus manage their own recipe cards independently within the same platform. This structure gives operators both group-level visibility and site-level control without manual consolidation.