Written by: JJ Tan, Founder, Jelly | Last updated: 9 November 2026
Key Takeaways
- Multi-site restaurant groups face specific costing challenges such as site-level supplier pricing, sub-recipe drift, central kitchen transfers, and per-site variance that spreadsheets and single-site tools cannot reliably manage.
- Essential capabilities include a central recipe library with site-specific pricing, automatic recosting from real invoices, sub-recipe and yield handling, and POS-driven theoretical-versus-actual reconciliation by site.
- Buyers should run a three-recipe demo test using their own invoices from two different sites before signing any contract to validate vendor performance.
- Transparent, per-location flat pricing such as Jelly's £129 per month per location makes budgeting and board sign-off straightforward compared to quote-based enterprise tools.
- Jelly is the best recipe costing software for multi-site UK restaurants because it onboards in the first week, keeps dish costs live from scanned supplier invoices, and charges a flat £129 per month per location with no per-user or per-feature charges.
What Multi-Site Changes About Recipe Costing
Single-site recipe costing is mostly arithmetic. At multi-site scale the arithmetic is easy, and the hard part is keeping data accurate across every location. The same dish and recipe can behave very differently when four sites buy the same ingredient from four suppliers at four prices, and a group average hides that spread.
Central Recipe Library With Site-Specific Ingredient Pricing. A group needs one authoritative recipe for every dish. That recipe must then be costed against each site's actual invoice prices. A chicken breast bought through a national contract at Site A may cost materially less than the same product sourced locally at Site B. Multi-site groups must cost recipes using the actual price each site pays per ingredient because otherwise one location can appear artificially efficient or inefficient. Software that holds only one price per ingredient will silently misstate margins at every site that pays a different rate.
Sub-Recipes And Prep-Yield Drift. Sauces, stocks, and prep items costed as sub-recipes are where margin often leaks without warning. If a kitchen portions a sauce at 95g instead of 80g, or a yield drops because of a new prep team, the parent dish cost drifts and no one sees it in time. When a supplier invoice price changes, four things must happen. Match the invoice, update the product cost, then recost every recipe and sub-recipe using that product. Finally, update theoretical food cost and menu GP for every site selling those items. Software that does not handle sub-recipes and automatic recosting breaks this chain at the first price change.
Central Kitchen And Commissary Transfers. When a central kitchen ships prepped items to sites, the transfer must carry its cost. If it does not, the receiving site understates its COGS while the central kitchen overstates its own. A site moving roughly $2,800 of stock a week in from another location can see its food cost percentage shift by around 3.5 points if that stock arrives priced wrong. Blended group figures can hide that distortion for an entire period.
Theoretical Versus Actual Variance By Site. Comparing what recipes say a dish should cost with what was actually used and sold, site by site, is how groups find leakage. One multi-site restaurant group held a steady 63% gross profit margin for months, yet a quarterly deep-dive found two sites running at 55–57%, propped up by stronger locations. Those sites bought at higher prices the recipe cost model never captured, and POS-driven sales-mix reconciliation per site was the only way to surface the gap.
The wider trading picture makes this work urgent. UHY research published in October 2026 found that the UK's Top 100 restaurant groups saw profits fall 44% year on year, from £365 million to £204 million, despite combined turnover rising from £12.9 billion to £13.3 billion. At the same time, UKHospitality reports that in multi-site hospitality businesses, risk and margin leakage often stem from fragmented buying, inconsistent supplier choices and varying commercial terms, and that without a consolidated view of spend, pricing pressure and working capital drag can accumulate unnoticed until they appear in financial results.
For a deeper grounding in the fundamentals, see How Recipe Costing Improves Restaurant Profit Margins and Recipe Costing Software For Restaurants: How To Choose.
Ranked Shortlist: Best Recipe Costing Software For Multi-Site UK Restaurants
This shortlist ranks tools against a clear use case. A UK group running 2–10+ sites needs fast rollout, live costing from real invoices, and pricing it can explain to a board.
1. Jelly — Best Overall For Fast-Rollout Live Costing For Growing UK Groups. Jelly is the fastest route from real invoices to live dish costs. Suppliers email invoices to a dedicated address or you photograph them in the app, and Price Alert plus spending insights go live within 24 hours, often in the first week of onboarding. Automated invoice scanning captures every line item by photo or email so dish costs and gross-profit margins update as invoices land. The Price Alert feature flags each supplier price movement and gives operators the evidence to negotiate credits or switch suppliers. Sales Mix menu engineering shows which dishes are most popular and most profitable. Native POS integrations with Square, Lightspeed, Epos Now and Toast connect in approximately five minutes each. Xero accounting integration is live, with Sage coming soon. Populu lifted gross profit from 68% to 72% across 16 locations using Jelly, and Amber saved £3,000–£4,000 per month. Across the customer base, Jelly users cut food costs by around 3% in the first three months and add roughly 2 percentage points to gross margins.
2. Access Procure Wizard Evo (The Access Group) — Best For Enterprise Procure-To-Pay. Access Procure Wizard Evo is fundamentally a purchase-to-pay platform with recipe management attached, connecting to 15+ named EPOS systems and providing PPDS-compliant allergen and nutrition labels. Published pricing is Essential at £900/month and Professional at £1,490/month, both on a 36-month minimum term, which creates a significant commitment and reduces flexibility for smaller groups or operators wanting to validate site-level costing before a long contract. It suits larger estates with dedicated procurement teams.
3. Apicbase — Best For Production Planning And Theoretical-Versus-Actual Variance Depth. Apicbase is built specifically for multi-site operators, offering strong recipe and food-cost controls, good stock-counting tools and detailed purchasing functionality. Its Growth plan starts from five outlets, and pricing is quote-based and billed annually, which introduces a minimum-site threshold and annual contract commitment that makes piloting harder for groups with fewer than five sites. Verified users note the system is "easy to use once it's running". That qualification signals an implementation and configuration burden before the system becomes effective. For a growing UK group shortlisting now, Jelly offers speed and pricing transparency that Apicbase's quote-based, implementation-heavy model cannot match. The flat £129 per location, first-week onboarding, five-minute POS connections and automatic dish-cost updates from scanned invoices are the evidence.
4. MarketMan — Best For Purchasing-Led Operations. MarketMan is a specialist back-of-house inventory and food-cost platform. MarketMan has no native POS and requires a sales enquiry for pricing, which adds another system to an operator's existing technology stack and makes cost comparison harder.
5. Kitchen CUT — Best For Chef-Led Legacy Systems. Kitchen CUT is an older, more static system typically targeted at large chains with dedicated office teams to run them. It lacks the dynamic, real-time invoice-driven updates that growing groups need when supplier prices move weekly.
For a broader view of the market, see Best Recipe Costing Software For Restaurants: 2026 UK Guide and Best Recipe Costing Software: A UK Operator's Guide For 2026.
What Should Multi-Site UK Restaurants Look For In Recipe Costing Software?
Those rankings rest on seven capabilities that matter more at multi-site scale than at single-site. Any vendor that cannot demonstrate all seven against your own data in a demo should leave the shortlist.
- A Central Recipe Library That Can Be Pushed To Every Site. Each dish needs one authoritative recipe, accessible and enforceable across all locations. Chefs should not maintain parallel versions in separate spreadsheets.
- Site-Specific Ingredient Pricing From Actual Supplier Invoices. The system must cost each recipe against the real invoice price at each site. Group averages or manually entered price lists drift away from reality.
- Automatic Recosting When Supplier Prices Change. Every time an invoice lands with a new price, every affected dish and sub-recipe must recost immediately. Manual recosting or scheduled updates leave margins exposed.
- Sub-Recipe And Prep-Yield Handling. Sauces, stocks, and prep items must exist as costed sub-recipes that roll up into parent dishes. Yield percentages should apply so portioning changes appear in the cost instead of hiding in variance.
- Menu Engineering And Sales-Mix Analysis. Knowing which dishes are most popular and most profitable by site guides pricing and menu decisions that protect margin. Guesswork does not.
- Allergen And Recipe Documentation. Natasha's Law compliance requires accurate, up-to-date allergen information on every dish. The system must manage this centrally and reflect sub-recipe allergen inheritance automatically.
- POS Reconciliation Of Theoretical Versus Actual Usage. Sales data from the POS must drive a comparison of what recipes say should have been used against what was actually consumed, site by site. That view makes leakage from over-portioning, waste, or unrecorded transfers visible and actionable.
POS Integrations And The Xero Connection
Recipe costing only works when sales and purchase data stay live. A system that holds accurate recipes but receives stale sales data or manually entered invoice prices will produce numbers no one trusts.
Jelly integrates natively with four POS systems via real-time API: Square, Lightspeed, Epos Now and Toast. Each integration delivers item-level sales data the moment a transaction completes. Lightspeed is Jelly's closest POS partner, with Jelly listed on the Lightspeed marketplace. These tools sit alongside each other so connecting them automates two to five hours of weekly work and delivers real-time margins and sales-mix data.
POS setup follows the same flow across all four systems and takes approximately five minutes. Open Jelly, click Integrations, sign in to the POS, grant permissions, then select which POS categories to sync. POS-to-dish linking only surfaces items sold since the integration was connected, which keeps mapping clean and free of legacy menu clutter. The only common friction point occurs when the user lacks admin access to their POS account, and Jelly flags this requirement upfront.
On the accounting side, Jelly's one-click push of digitised invoices into Xero removes manual data entry and cuts bookkeeping time by around 90%. Sage integration is coming soon. Xero is named best overall among the leading accounting platforms for UK restaurants and hospitality in a 2026 buyer's guide, alongside QuickBooks and Sage, which makes Jelly's native Xero integration directly relevant to most UK multi-site operators.
One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue after connecting their POS through Jelly. For chef-specific guidance on getting the most from these integrations, see Best Recipe Costing Software For UK Restaurant Chefs.
Pricing Reality
Integrations decide whether the data is live, and pricing decides whether you can commit. Jelly charges a flat £129 per location per month with no per-user or per-feature charges. A monthly plan carries no minimum contract and can be cancelled at any time; an annual plan is 10% cheaper but commits for 12 months. For a group with five sites, the recurring software cost is £645 per month, which is a figure you can model, present to a board, and defend without a sales call.
The contrast with enterprise alternatives is material. Access Procure Wizard Evo publishes pricing at £900/month (Essential) and £1,490/month (Professional), both on a 36-month minimum term. Apicbase, MarketMan, Nory and Fourth all require a sales enquiry for pricing, which makes cost comparison and budgeting harder for buyers. For Apicbase, pricing depends on sites, modules, integrations, training and rollout complexity, so buyers should request a detailed commercial breakdown rather than relying on a per-site headline price.
A total-cost-of-ownership model should cover recurring subscription, annual increases, integration or middleware fees, implementation, data migration, training, support, workflow changes, and the cost of maintaining workarounds. Think beyond the headline subscription. Build in annual increases, integration or middleware fees, implementation, data migration, training and support. Then add the cost of workflow changes and the workarounds you will maintain in the meantime. On that basis, Jelly's transparent flat rate, first-week onboarding, and native integrations remove several cost categories that quote-based enterprise tools introduce.
The Demo Test: How To Evaluate Vendors
The most reliable way to shortlist recipe costing software is to bring your own data to the demo. Take three recipes, covering one simple dish, one with a sub-recipe, and one sold across multiple sites. Ask each vendor to cost them using your actual supplier invoices from two different sites.
Ask every vendor these questions during the session:
- How do you handle different ingredient prices per site?
- How quickly does a supplier price change flow through to dish margin?
- How are sub-recipes and yields managed?
- How does POS data reconcile theoretical versus actual usage by site?
- How long until we see value?
A vendor that cannot cost your three recipes against your real invoices from two sites in the demo is signalling how the system will perform in production. Jelly's onboarding delivers initial value in the first week, and the three-recipe test should take minutes rather than days of configuration.
Common Pitfalls
Choosing the right vendor is half the job; the other half is avoiding the operational mistakes that undo it. The most expensive mistakes in multi-site recipe costing are operational rather than technical. Relying on spreadsheets that drift, where one site's version of a recipe diverges from another's without anyone noticing, is a common cause of unexplained margin variance. Capturing invoices inconsistently across sites, where some locations photograph invoices promptly and others batch them weekly or monthly, means recipe costs always lag reality.
Waiting for monthly accountant reports before reacting to supplier price changes creates a structural problem. According to the NIQ and Prestige Purchasing Foodservice Price Index, July 2026 foodservice inflation was described as modest but volatile, with climate-related disruption fuelling market volatility. In those conditions, a month's delay in reacting to a price change can cost thousands. Choosing enterprise software that takes months to onboard creates a different problem because the group continues bleeding margin during implementation while paying for a system it cannot yet use. Failing to reconcile POS sales with recipe costs by site then leaves the group guessing which location is underperforming and why.
Conclusion: Why Jelly Is The Best Recipe Costing Software For Multi-Site UK Restaurants
Multi-site recipe costing works when there is a central recipe library, site-specific pricing from real invoices, automatic recosting, and POS reconciliation, all visible by site. Without those four elements, margin leakage stays invisible until it appears in financial results.
Jelly is the best recipe costing software for multi-site UK restaurants because it onboards in the first week, keeps dish costs live from scanned supplier invoices, and charges a flat £129 per month per location with no per-user or per-feature charges. Populu lifted gross profit from 68% to 72% across 16 locations. Amber saved £3,000–£4,000 per month. The Howard Arms reached 80% gross profit after their accountant said 60% would be lucky. These outcomes come from a system that runs within days rather than months, and the Populu and Amber results above show what that speed looks like in practice.
Book a demo, bring your three recipes and your invoices from two sites, and run the test with your own numbers.
Bring Your Three Recipes To A Demo
Frequently Asked Questions
How Do I Calculate The Cost Of A Recipe Across Multiple Sites?
To calculate recipe cost accurately across multiple sites, each site's version of the dish must be costed against the ingredient prices that site actually pays. The calculation for each site is straightforward. Sum the cost of every ingredient, using quantity multiplied by the price per unit from the most recent supplier invoice for that site. Include any sub-recipes at their own costed rate and any yield or wastage adjustments. Divide the total recipe cost by the number of portions to get cost per portion, then divide by the net selling price, excluding VAT, to get food cost percentage. Jelly automates this by scanning supplier invoices and updating every affected dish cost in real time so the figure stays current without manual recalculation.
What Is The Q Factor In Recipe Costing?
The Q factor, or quotient factor, is a multiplier applied to the raw ingredient cost of a dish to cover incidental costs that are difficult to cost individually. These include condiments, garnishes, cooking oils, seasoning, and similar items used across many dishes but not tracked per portion. Operators typically express it as a small percentage added to the calculated recipe cost, for example 5–10%, to give a more realistic total dish cost. In multi-site operations, the Q factor may vary by site if condiment usage or wastage differs between locations. Most recipe costing software, including Jelly, handles this through wastage percentages applied at ingredient level rather than a blanket multiplier, which gives more granular control.
How Do I Calculate Food Cost In A Restaurant With Several Locations?
Food cost for a multi-site group is calculated at two levels, per site and for the group. At site level, actual food cost for a period is: opening stock plus purchases received plus transfers in, minus transfers out and closing stock, then divided by net sales for the period. Theoretical food cost is calculated by multiplying the number of each menu item sold, from POS data, by its current recipe cost per site, summing the totals, and dividing by net sales. The gap between theoretical and actual is the variance, and it must be measured per site because a strong site can mask a weak one in blended figures. Jelly's Flash Report provides a daily, weekly or monthly view of gross profit margin, calculated from invoice costs and POS sales data.
What Is Theoretical Versus Actual Food Cost Variance By Site?
Theoretical food cost is what a site should have spent on ingredients based on the recipes for every dish sold, assuming perfect portioning and no waste. Actual food cost is what the site demonstrably spent, derived from stock counts and purchases. The variance between the two, expressed as a percentage of sales, reveals leakage from over-portioning, unlogged waste, unrecorded transfers, POS items not mapped to recipes, or theft. A theoretical-versus-actual variance of around 2% or under is presented as a working benchmark for a well-run site, though the exact target varies by cuisine and how tightly recipes are managed. A site at 4% is roughly double that, and the gap usually marks where stock leaks between the count and the recipe. Measuring this by site is essential because the same dish can carry a different expected cost depending on local purchasing and central kitchen transfer arrangements, and group averages hide the effects of supplier prices, portioning, waste, and sales mix.
Does Recipe Costing Software Integrate With UK POS Systems?
Recipe costing platforms for UK restaurants do integrate with the major POS systems used in the market. Jelly connects natively to Square, Lightspeed, Epos Now and Toast, as covered in POS Integrations And The Xero Connection above, so item-level sales data lands the moment a transaction completes and dish costs update as invoices are scanned. Xero is supported for accounting, with Sage integration coming soon. These integrations mean that sales data flows directly into gross-profit and sales-mix calculations without manual export or re-entry, giving operators a live view of margin by dish and by site.
How Much Does Recipe Costing Software Cost For A Multi-Site UK Restaurant Group?
Pricing varies significantly by vendor and model. Jelly's flat £129 per location per month, with no per-user or per-feature charges, is detailed in Pricing Reality above and is the only published per-site rate on this shortlist. Access Procure Wizard Evo's published rates, quoted above, sit on a 36-month minimum term, which is the longest commitment on this shortlist. Apicbase, MarketMan, Nory and Fourth are all quote-based, with Apicbase's Growth plan starting from a minimum of five outlets. When comparing total cost of ownership, buyers should factor in implementation time, onboarding fees, POS integration costs, and the cost of delayed value. A system that takes three months to onboard means three months of continued margin leakage at the old rate.
