Written by: JJ Tan, Founder, Jelly | Last updated: 29 September 2026
Key Takeaways For Pub Group Finance And Ops Teams
- Centralised menu costing software links supplier invoices to menu profitability across every pub site. It replaces spreadsheets with a single source of truth that updates in real time.
- The full invoice-to-menu traceability workflow needs digitised invoices, automatic recipe updates, real-time GP recalculation, native POS integration, and direct accounting sync to deliver actual versus theoretical margins.
- Pub groups face separate wet and dry costing challenges. Most platforms handle kitchen recipes well but overlook keg yields, line cleaning losses, and draught waste that can erode 8–12% of bar revenue.
- Operators should demand native EPOS integrations, multi-supplier price tracking, sub-recipe support, VAT handling, and site-level overrides during demos to confirm the platform truly serves multi-site estates.
- Jelly delivers centralised menu costing for pub groups with automated invoice scanning, real-time dish costing, Price Alert, Flash Report, and POS integrations at a flat £129 per month per location.
See The Full Invoice-To-Menu Workflow
The Invoice-To-Menu Traceability Workflow Every Platform Must Pass
Centralised menu costing software for pub groups must complete the following loop across every site in the estate, not just at one location.
- A supplier invoice arrives by email or photo into a dedicated address.
- Every line item is digitised, including quantity, SKU, unit price, and tax.
- Ingredient prices update automatically across all recipes and dishes.
- Dish costs and GP margins recalculate in real time.
- POS sales data from Square, EPOS Now, Lightspeed, or Toast maps to dishes for actual versus theoretical GP.
- Digitised invoices push to accounting software such as Xero, with Sage coming soon.
This six-step loop is the minimum viable workflow, and the later steps are where most platforms fail. A platform that completes steps one to four but breaks at step five because it lacks a native POS integration cannot deliver actual versus theoretical GP. Even if it clears that hurdle, a platform that completes steps one to five but requires manual CSV exports for accounting adds back the admin burden the software was meant to remove. That is why every vendor should be evaluated against the complete loop, not just the early steps.
Test Your Vendor Against The Checklist
Wet And Dry Costing Challenges Specific To Pub Groups
Pub groups manage two separate costing problems. Dry costing covers kitchen recipes, ingredients, wastage, and trim. Wet costing covers keg yields, draught waste, cask line cleaning, and pour cost. Most centralised menu costing software handles dry well but treats wet as an afterthought, which creates a serious gap for any estate with meaningful bar revenue.
The gap between theoretical and actual yield is where wet margin disappears. A standard 11-gallon keg holds 88 pints in theory, but real-world yield is typically around 84 pints. Line cleaning, foam, and spillage account for the difference, so operators should budget for 8–12% loss on keg beer. Line cleaning wastes approximately half a pint per line per clean. For a 12-tap pub cleaning weekly, that is over 300 pints lost per year before a single pint is over-poured.
The scale of the wet and dry margin gap makes separate tracking essential. UKHospitality and Christie & Co’s Benchmarking Report 2022, based on actual P&L accounts from 4,791 managed outlets, reports gross profit margin on food sales at 67% and on wet sales at 66% across the whole survey. Within wet margins, tied pubs ran at 61.2% wet GP versus 68.9% for commercial operators. That gap of nearly eight percentage points is driven largely by purchasing constraints and yield management. UK pub valuation guidance formally splits trading into wet and dry elements, valuing drinks net of VAT separately from food sales net of VAT. This reflects how the trade is assessed at the highest level.
Beer line cleaning losses typically account for 2–3% of draught throughput, so operators must price draught beer on true yield rather than theoretical yield. A gap of 2–3 percentage points between target GP and actual GP on a draught-heavy bar is normal. A widening gap indicates a problem with a clear start date. A pub-group-ready platform must handle both wet and dry because GP accuracy across a mixed estate depends on it. For a deeper look at how food and drink costing differ structurally, see Pub Menu Costing Vs Restaurant Costing: 2026 UK Guide.
Questions To Use In A Centralised Costing Software Demo
The questions below separate real centralised platforms from glorified recipe software. Take this checklist to every vendor demo.
- How do you handle pack-to-unit conversions such as case to each or kilogram to gram?
- Can one ingredient have multiple suppliers with different prices?
- Do you support sub-recipes and yields?
- How are wastage and trim percentages applied?
- Can I see full supplier price history per SKU?
- Do you report actual versus theoretical GP, and at what frequency?
- Which EPOS systems do you integrate with natively, and is it a real-time API or a batch export?
- How is allergen management handled across the estate? Under Natasha’s Law, any UK food business producing prepacked for direct sale food must label it with the name of the food and a full ingredients list, with allergenic ingredients emphasised, so your costing software must support this workflow.
- How do you handle UK VAT on food and drink lines, including standard 20% on catering and hot takeaway and zero-rated cold takeaway with exceptions?
- Is there a full audit trail of who changed what and when?
- Can sites override the central recipe master without breaking group reporting?
- What does onboarding actually look like in the first 30 days?
Vendors that cannot answer questions 6, 7, and 11 with specifics are not operating a genuinely centralised platform.
How Jelly Delivers Centralised Menu Costing For Pub Groups
Jelly completes all six steps of the invoice-to-menu loop across every site in a pub estate. Invoices arrive by email or photo, and Jelly digitises every line item, including quantity, SKU, price, and tax, without manual data entry. Ingredient costs update with every new invoice, so the gross profit margin for every dish stays live. A red percentage flags a dish that has dropped margin, and a green one confirms it has grown.
Price Alert flags every supplier price increase or decrease, which gives pub groups hard evidence to negotiate better rates and claim credit notes. The Flash Report delivers a daily, weekly, or monthly GP margin view calculated from invoice costs and POS sales. Menu Engineering (Sales Mix) shows which dishes are most popular and most profitable across the estate, so group leaders can make data-driven menu decisions.
POS integrations with Square, EPOS Now, Lightspeed, and Toast all operate via real-time API. They deliver item-level sales data the moment a transaction completes, and each integration is set up in under five minutes. All four work alongside Jelly as complementary tools. Digitised invoices push to Xero in one click, with Sage coming soon, which removes the manual bookkeeping step entirely.
Jelly is priced at a flat £129 per month per location, with no variable charge per user or feature. That simplicity is reflected in the results.
- Populu lifted GP from 68% to 72% across 16 locations.
- One operator improved GP from 65% to 72% within 12 weeks on approximately £500,000 in revenue.
- Across the user base, Jelly customers cut food costs by 3% on average in the first three months and add 2 percentage points to gross margins.
For a detailed breakdown of the multi-site costing system Jelly supports, see Centralised Menu Costing System For Multi-Site Pub Groups and Food Cost Reduction Strategies For Multi-Site UK Pub Groups. Jelly is not the only option, however. The right choice depends on estate size and complexity, so the comparison below sets out how the main tiers differ.
Honest Platform Comparison By Estate Size And Complexity
The right platform depends on estate size and how much configuration your team can absorb. The tiers below map loosely to the six-step loop and the demo checklist, so you can see which category fits your estate.
Enterprise options such as Fourth and Kitchen CUT suit large chains with dedicated office teams. They carry the feature depth to match that complexity, but implementation timelines are long and implementation costs for platforms in this tier typically run $3,000 to $15,000 or more depending on scope before subscription fees begin.
All-rounders such as MarketMan and Apicbase offer broader feature sets, including purchasing, inventory, and cost reporting in a single platform. That breadth comes with greater setup complexity and longer time to value. MarketMan charges $200 to $350 per location per month on standard plans, with onboarding fees of $500 to $1,500 depending on complexity.
UK-native and wet-led options such as growyze and WISK work well for estates where bar management and pour cost tracking are the primary need. WISK in particular supports bar-specific workflows including cocktail costing and batch recipes.
Lighter costing-first tools, with Jelly as the clearest example, prioritise fastest time to value and the simplest interface. They suit growing pub groups that need the invoice-to-menu loop closed quickly. For groups at 2–20 sites that have outgrown spreadsheets but do not yet need a full ERP, this tier often delivers the highest return in the shortest time.
Calculating Menu Costs Across Multiple Pub Sites
Multi-site menu costing at group level requires a central recipe master, automated invoice data, and POS-linked sales mix. Manual per-site calculation cannot keep up with supplier price changes across an estate. When a supplier increases the price of a key ingredient, that change must flow automatically to every dish containing it across every site. The resulting GP impact must appear immediately. A spreadsheet updated by a site manager once a week cannot achieve this.
The practical answer is a platform that digitises every invoice line, holds a central recipe master with site-level overrides, and maps POS sales to dish costs in real time. For the full methodology, see Centralised Menu Costing System For Multi-Site Pub Groups and Pub Menu Costing: The 7-Step System To Hit 28–35% Food Cost.
Onboarding And Time-To-Value Realities
Enterprise systems take months to set up because they require configuring accounting, purchasing, inventory, and integrations at the same time. A full ERP rollout can take months, and implementation cost and uncertainty about where to start were cited by nearly a third of non-adopters as reasons they had not adopted new restaurant technology. Some solutions require months of structured implementation, often with an outside partner, and two to four weeks of active setup before food cost reporting becomes meaningful.
Jelly generates initial value in the first week. Price alerts and spending insights are live once suppliers send invoices to a dedicated email address, or less than 24 hours after invoices are photographed into Jelly. There are no implementation fees, no configuration projects, and no waiting for an outside partner to complete a data migration before the platform becomes useful.
Below are the questions pub groups ask most often when evaluating centralised costing software.
Frequently Asked Questions (FAQ)
Can Centralised Menu Costing Handle Site-Specific Menus?
Yes. A central recipe master with site-level overrides separates real centralisation from rigid standardisation. Jelly supports site-level overrides for seasonal specials, regional pricing, or site-specific dishes without breaking group-level reporting. Operations directors retain a consolidated view of GP across the estate while individual sites keep the flexibility they need.
Does It Work With Our Existing EPOS?
Jelly integrates natively with Square, EPOS Now, Lightspeed, and Toast via real-time API, as described above. Setup takes approximately five minutes across all four systems. These are complementary tools that Jelly works alongside, and connecting them does not require middleware, custom development, or a support ticket.
How Long Does Onboarding Take?
As covered above, Jelly generates initial value in the first week. Price alerts and spending insights go live as soon as suppliers start sending invoices. Enterprise systems in the same category typically require months of structured implementation before delivering comparable visibility. That difference determines whether you react to a supplier price increase this week or discover it in next month’s accountant report.
What Does It Cost Per Site?
Jelly is a flat £129 per month per location. There is no variable charge per user, per feature, or per invoice volume. For a five-site pub group, Jelly costs £129 per location per month, which equals £645 per month for the full platform. That price includes automated invoice scanning, real-time dish costing, Price Alert, Flash Report, Menu Engineering, POS integrations, and Xero accounting sync. The real cost can be higher than the headline, however, because POS integration costs from £15 per location where available and a one-time per-site setup fee applies.
Conclusion: Why Pub Groups Move To Jelly
Per-site spreadsheets and generic restaurant software cannot complete the invoice-to-menu loop across a pub estate. They fail to update dish costs the moment a supplier invoice arrives, and they cannot separate wet and dry GP in a way that reflects how pub trade actually works. By the time a monthly accountant’s report surfaces a margin problem, the opportunity to act has already passed.
Jelly closes the loop. The features described above, including automated invoice scanning, real-time dish costing, Price Alert, Flash Report, POS integrations, and one-click Xero sync, come at a flat £129 per month per site, with first-week value rather than months of setup. For growing pub groups that have outgrown spreadsheets and need a central source of truth across every site, Jelly provides a proven system.
