Written by: JJ Tan, Founder, Jelly | Last updated: 22 June 2026
Key Takeaways for Pub Groups
- Centralised food cost percentage monitoring replaces isolated per-venue spreadsheets with a single HQ dashboard that aggregates invoice, recipe and POS data daily across all sites.
- Four sequential steps – standardised invoice capture, POS integration, central recipe database and Price Alerts – create daily visibility and remove hours of manual work per site.
- The food cost variance formula highlights the gap between theoretical and actual costs. Jelly calculates both automatically so groups can keep variance below 2–3 percentage points.
- Weekly short-form counts plus monthly full stocktakes, supported by a 90-day rollout plan, move pub groups from month-end reviews to proactive weekly variance management.
- Jelly delivers this infrastructure at £129 per site per month, with POS connections live in minutes. Book a demo to see how it centralises monitoring across your pub group.
How to monitor food costs across multiple sites
Daily visibility across a group comes from four clear steps that build on each other.
Step 1 — Standardise invoice capture. Every site must feed supplier invoices into one system. Jelly captures invoices via photo or dedicated email address, scanning every line item, including quantity, SKU, price and tax, without manual data entry. This removes the lag between delivery and cost visibility.
Step 2 — Connect your POS systems. Jelly integrates natively with Square, EPOS Now, Lightspeed and Toast via real-time API. Each integration takes approximately five minutes: open Jelly, click Integrations, sign in to the POS, grant permissions, then select which categories to sync. Once connected, item-level sales data flows into Jelly the moment a transaction completes. This automation replaces two to five hours of weekly manual work per site.
Step 3 — Build a centralised recipe database. In Jelly's Kitchen section, chefs build dishes by clicking on ingredients already populated from scanned invoices. The system handles unit conversions and wastage percentages automatically. Work that previously took 28 minutes per dish in a spreadsheet takes roughly three minutes in Jelly. Multi-site groups see the fastest results by first mapping recipes for the top 20% of menu items that generate 80% of revenue, then expanding to the full catalogue.
Step 4 — Activate Price Alerts. Jelly's Price Alert feature flags every ingredient price increase or decrease and shows which supplier raised it and by how much. Before using Jelly, Chef Murat Kilic of Amber relied on manual costing and spreadsheets. After activating automated invoice processing and price change alerts, the restaurant consistently saves £3,000–£4,000 per month.
Book a demo to see how Jelly connects your sites in under a week.
What is the food cost variance formula?
The formulas below show how to calculate theoretical cost, actual cost and the variance between them. This gives the mathematical foundation for daily monitoring.
Food Cost Variance Formula
Theoretical Food Cost % = (Recipe cost of items sold ÷ Total food revenue) × 100
Actual Food Cost % = (Opening stock + Purchases − Closing stock) ÷ Total food revenue × 100
Variance = Actual Food Cost % − Theoretical Food Cost %
Example: If your theoretical food cost is 30% and your actual food cost is 33%, your variance is +3 percentage points, representing £3,000 in unexplained loss on every £100,000 of food revenue.
Operators often target a variance of 2–3 percentage points or less. A 5% variance on £100,000 in monthly food sales represents £5,000 in lost profit.
In a multi-site pub group, variance accumulates silently across locations. When POS systems operate in isolation from inventory and recipe databases, groups cannot distinguish waste, over-portioning or theft because theoretical usage is never compared to actual consumption. Jelly's Flash Report calculates both figures automatically, pulling recipe costs from the Cookbook and sales from the connected POS, so variance becomes visible daily rather than at month-end.
How often should pub groups count stock?
Best practice combines two counting rhythms that work together.
- Weekly short-form counts focus on the top 20–30 high-value or high-velocity SKUs such as draught beer, proteins and premium spirits. These counts take 15–30 minutes per site and feed weekly variance reports.
- Monthly full counts cover a complete physical count of every SKU, reconciled against the theoretical usage calculated from POS sales and recipe data.
Operational oversight for multi-site groups should shift from month-end review to weekly variance checks so that recurring problems on high-value items or underperforming sites are identified before they become systemic margin issues.
Sushi Revolution's monthly stocktake using Jelly takes 5–20 minutes, down from 2–3 hours previously. At group scale, that efficiency compounds across every site every month. To achieve similar results across your pub group, follow the three-phase rollout plan below.
90-day rollout plan: three clear phases
Phase 1 — Foundation (Days 1–30)
Owner: Finance Manager / Operations Director
Actions: Set up a dedicated Jelly invoice inbox per site so that all future supplier invoices flow into one system automatically. Once the inbox is live, photograph or forward all existing supplier invoices to create a baseline cost database. With ingredient costs now visible, build recipes for the top 20% of menu items by revenue so the highest-impact dishes generate the first variance insights. Finally, connect at least one POS system per site to start matching sales data against recipe costs.
Outcome: Every site has live ingredient costs and a working Flash Report within the first week. Price Alerts are active from day one.
Phase 2 — Integration (Days 31–60)
Owner: Group Head Chef + Finance Manager
Actions: Complete the full recipe database for all menu items so that every dish has a live cost. Push digitised invoices into Xero using Jelly's one-click accounting integration to streamline accounts payable. Run the first weekly variance report across all sites to highlight problem areas. Establish a standard unit-of-measure convention across every location so that recipes, invoices and POS data speak the same language.
Outcome: Theoretical versus actual food cost variance becomes visible weekly. Standardised units of measure ensure POS sales correctly decrement buying units such as cases or kilograms, which removes phantom variances.
Phase 3 — Governance (Days 61–90)
Owner: Operations Director
Actions: Introduce weekly short-form stock counts at every site so high-value items stay under control. Set site-level GP targets in the Jelly dashboard to give managers clear goals. Review the Sales Mix report to identify low-margin, high-volume dishes for repricing or removal. Establish a monthly full-count schedule and hold sites accountable for completing it.
Outcome: Group-wide variance holds below 2%. Teams remove 10–20 hours of monthly admin. HQ gains daily GP visibility across every site without adding chef admin burden.
Pro Tip: Assign one "Jelly champion" per site, typically the sous chef or kitchen manager, to photograph invoices on delivery day. This single habit keeps cost data less than 24 hours old.
Common Pitfall: Before integrating POS with central recipe and stock systems, operators must clean POS data by removing duplicate buttons, archiving dead menu items and enforcing consistent naming conventions. Without this work, inaccurate mappings spread across all sites and inflate variance figures.
Multi-site dashboard that flags weekly outliers
Jelly's HQ dashboard displays real-time GP margins venue by venue. A red percentage appears on any dish whose margin has dropped, and a green one appears when it improves. Finance managers can compare any site against the group average and identify outliers, such as a pub running 38% food cost while the group average is 32%, without requesting reports from individual sites. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue after connecting their POS to Jelly. Populu lifted GP from 68% to 72% across 16 locations.
Schedule a chat to see the multi-site dashboard live.
UK-specific realities in 2026
The Food and Drink Federation forecasts at least 9% food inflation for the UK by the end of 2026. Pub groups face rising food and operating costs in 2026 that are hard to pass through to retail prices. In this environment, monthly reporting cycles move too slowly. A price increase that lands in week one of a period erodes four weeks of margin before anyone acts.
Margin pressure quickly flows into accounts payable and cash flow. Jelly's Xero integration addresses this side of the problem by pushing digitised invoices directly into Xero with one click. This reduces bookkeeping time by 90% and removes the risk of missed payments that damage supplier relationships. Many hospitality operators still rely on manual procurement processes, which creates a structural vulnerability when supplier prices move weekly.
Once POS systems are connected to Jelly, the Sales Mix report shows which dishes are most popular and most profitable across every site simultaneously. This combination of automated invoice capture, live recipe costing and POS integration creates the operational infrastructure that protects margins when the supply market is volatile.
Common Pitfall: Without centralised stock visibility, branch managers order from memory or rough estimates, leading to over-purchasing at some sites, stock-outs at others, and no audit trail explaining discrepancies. A centralised system removes this dependency on individual site judgement.
Typical pub-group food cost targets
The table below shows typical food cost percentage targets by pub concept. Use these benchmarks to set realistic site-level goals in your dashboard.
| Concept | Food Cost % Target | GP Margin Implied | Source |
|---|---|---|---|
| Gastropub / bar-forward | 20–28% | 72–80% | Vellin |
| Casual dining pub | 28–35% | 65–72% | LBH |
| Full-service restaurant | 28–35% | 65–72% | UKHospitality via Growyze |
| Fine dining | 28–35% | 65–72% | BusinessDojo |
A variance of 2–3 percentage points or less between actual and theoretical food cost is a realistic target for operational control.
Measurable success checklist
- ✅ Daily GP visibility across every site from a single HQ dashboard
- ✅ Weekly food cost variance held below 2% group-wide
- ✅ 10–20 hours of monthly admin eliminated per site
- ✅ Stocktakes completed in 5–20 minutes per site per month
- ✅ All supplier invoices digitised and pushed to Xero within 24 hours of delivery
- ✅ Price Alerts active so every supplier price movement is flagged the same week it occurs
- ✅ Sales Mix report identifying low-margin dishes for repricing or removal
Conclusion
Centralising food cost percentage monitoring for pub groups is an operational discipline made practical by the right platform. Replacing per-venue spreadsheets with one real-time system gives finance managers daily variance visibility, gives head chefs live dish margins without extra admin and gives operations directors the outlier alerts needed to act before margin erosion becomes systemic. In the 2026 UK supply market, that daily visibility separates operators who react to price volatility from those who absorb it silently. Jelly delivers this infrastructure at £129 per site per month, with POS connections live in minutes and initial value generated within the first week.
Book a demo and see how Jelly centralises food cost percentage monitoring across your pub group.
Frequently asked questions
How does Jelly handle food cost monitoring across sites with different POS systems?
Jelly integrates natively with Square, EPOS Now, Lightspeed and Toast via real-time API. Each integration follows the same five-minute setup process regardless of which POS a site uses. Once connected, item-level sales data flows into Jelly the moment a transaction completes, and the platform maps each POS item to a Jelly dish for accurate cost and margin calculations. A pub group where different sites run different POS systems can still consolidate all sales and cost data into one central dashboard without any manual reconciliation.
What is a realistic food cost percentage target for a UK pub group in 2026?
The appropriate target depends on the concept. Gastropubs and bar-forward operations typically aim for 20–28%. Casual dining pubs generally sit between 28–35%. The more important metric for a multi-site group is variance. The gap between theoretical food cost, which recipes define, and actual food cost, which invoices and stock counts confirm, should be 2–3 percentage points or less. A variance above 3% on a group turning £1 million in food revenue per month represents at least £30,000 in unexplained losses every month.
How long does it take to onboard a pub group onto Jelly?
Jelly generates initial value within the first week. Once suppliers begin sending invoices to a dedicated Jelly email address, or the team starts photographing invoices on delivery, Price Alerts and spending insights go live within 24 hours. POS integration takes approximately five minutes per site, as described earlier. Building the full recipe database for the top 20% of menu items by revenue typically takes one to two weeks with a group head chef involved. The full 90-day rollout plan described in this article takes a group from fragmented spreadsheets to daily GP visibility, weekly variance reporting and Xero integration.
Can Jelly replace our existing accounting software?
Jelly is not an accounting platform. It is the operational layer that sits between your kitchens and your accounts. The system digitises every invoice line item and pushes the data directly into Xero with one click, reducing bookkeeping time by 90%. Your finance team keeps Xero for statutory accounts while gaining daily food cost visibility that Xero alone cannot provide. Sage integration is also in development. The combination of Jelly for operational cost control and Xero for financial reporting gives pub-group finance managers both real-time margin data and clean accounts payable records.
How does Jelly help with supplier price negotiations across a pub group?
Jelly's Price Alert feature flags every ingredient price increase or decrease and identifies the specific supplier, the specific SKU and the exact percentage change. For a group head chef or operations director managing multiple suppliers across multiple sites, this creates a concrete evidence base for supplier conversations. Instead of suspecting that prices have crept up, you can present the data directly. Amber restaurant used this feature to recover the £3,000–£4,000 monthly savings mentioned earlier, demonstrating how Price Alerts support supplier credits, better buying decisions and tighter menu controls. At group scale, the same capability applied across every site compounds into significant annual savings.