Automated COGS Calculator for Multi-Site UK Restaurants

Written by: JJ Tan, Founder, Jelly | Last updated: 30 September 2026

Key Takeaways

• Multi-site COGS requires more than summing individual site figures. Inter-site transfers, central kitchen production, and VAT-inclusive invoices all distort site-level data.
• Accurate group COGS follows six clear steps that cover consistent inventory valuation, VAT-exclusive purchases, transfer tracking, and elimination of internal movements at group level.
• An automated COGS calculator needs five core data inputs to work across multiple locations: sites, ingredients and suppliers, recipes, purchases and stock movements, and POS sales data.
• Variance between theoretical and actual COGS must link to specific causes such as waste, over-portioning, unrecorded staff meals, shrinkage, recipe errors, supplier price changes, and stock-count mistakes.
• Jelly automates invoice capture, transfer elimination, VAT handling, and real-time variance attribution for multi-site UK restaurants, pubs, and boutique hotels.

See how Jelly handles multi-site COGS

How to Calculate COGS Across Multiple Restaurant Sites

These six steps produce a defensible site-level COGS figure that you can then reconcile at group level.

1. Value opening inventory at each site using one consistent method, such as FIFO, weighted average, or most-recent-cost, applied identically across all sites and periods. Mixing valuation methods within a single period produces a COGS number that reflects methodology rather than actual consumption.
2. Add purchases at actual invoiced prices, net of VAT and minus credit notes. To extract the VAT-exclusive cost from a VAT-inclusive invoice at the standard 20% rate, divide the gross amount by 1.2.
3. Add net inter-site transfers in, which means transfers received minus transfers dispatched at each site, valued at the cost basis carried from the source location.
4. Add central kitchen production received, valued at transfer cost rather than retail price.
5. Subtract closing inventory, valued on the same basis as opening inventory.
6. Eliminate all internal transfers at group level so group COGS reflects only external purchases and not stock that has simply moved between your own sites.

Jelly handles unit conversions and transfer elimination automatically, removing the manual reconciliation step that breaks spreadsheet-based workflows at scale.

The Multi-Site COGS Formula With Transfers and Central Production

Jelly handles unit conversions and transfer elimination automatically, but seeing the full formula clarifies what the platform calculates. The standard single-site formula, Opening Inventory + Purchases − Closing Inventory, is insufficient for a group because it ignores stock moving between your own sites.

The site-level formula adds transfers and central kitchen receipts. The group-level formula then removes those internal movements so you are left with only external purchases.

• Site-level: COGS = Opening Inventory + Purchases + Transfers In − Transfers Out + Central Kitchen Receipts − Closing Inventory
• Group-level: Group COGS = Σ Site COGS − Σ Internal Transfers − Σ Central Kitchen Internal Receipts

Transferred stock is neither a purchase nor a sale; if inter-site transfers are not tracked separately, the receiving site’s purchases are overstated and the sending site’s closing inventory is understated, distorting COGS at both sites. At group level, those internal movements must be eliminated entirely so the consolidated figure reflects only what was bought from external suppliers.

Jelly applies this elimination automatically. When stock moves between your sites, the transfer is recorded at both ends and stripped from the group purchasing figure without manual journal entries.

The Five Data Inputs an Automated COGS Calculator Needs for Multi-Site UK Restaurants

The six calculation steps above only work when the underlying data is captured consistently. An automated COGS calculator needs five data inputs to make that possible across multiple sites.

• Sites: Each location registered with its own inventory, transfer records, and cost history.
• Ingredients and suppliers: A unified ingredient master linked to supplier SKUs, so a price change on one invoice updates every recipe that uses that ingredient.
• Recipes and bills of materials: Structured recipe cards that break each dish into ingredient quantities, yield factors, and wastage allowances. Automated recipe costing removes the 28 minutes of spreadsheet work that a single menu item typically requires.
• Purchases and stock movements: Every supplier invoice, credit note, inter-site transfer, and stock adjustment captured at line-item level as it occurs.
• POS sales: Item-level sales data from the till, linked to recipes, to generate theoretical COGS and enable variance attribution.

Jelly captures invoices via email or photo, which matters because supplier invoices arrive in inconsistent formats such as email PDFs, paper delivery notes, and portal downloads. Any automated capture system must handle multiple document types rather than a single standard format. Jelly’s invoice scanning handles this variation automatically, extracting quantity, SKU, price, and tax from every line item regardless of supplier format. It also integrates natively with Xero for accounting, with Sage coming soon, and with Square, EPOS Now, Toast, and Lightspeed for POS sales data.

Theoretical vs Actual COGS Variance: How to Attribute the £ Difference

Theoretical COGS is what the kitchen should have spent if every portion matched the recipe. It is calculated by multiplying recipe cost per item by units sold from POS data. Actual COGS is what the physical stock count shows was consumed. A positive variance, actual minus theoretical, means product left the kitchen that recorded sales cannot explain.

The variance breaks into named, additive causes.

• Waste and spoilage: Logged waste reduces unexplained variance. Unlogged spoilage inflates it.
• Over-portioning: A kitchen serving 180 covers per day at $0.48 over-portion per cover generates approximately $2,580 per month in unplanned food cost at a single site.
• Unrecorded staff meals and comps: Ingredients consumed without a corresponding sale register as unexplained loss.
• Shrinkage and theft: Identified by running item-level variance reports and isolating products where variance consistently exceeds what waste and portioning can explain.
• Recipe errors: Stale recipe costs, where the recipe card has not been updated to reflect the latest invoice price, understate theoretical cost and make variance appear artificially high.
• Supplier price changes: Across mid-size restaurant groups, the average number of ingredient price changes per month exceeds forty, which makes static recipe costs unworkable.
• Stock-count errors: A stocktake wrong by 3% in either direction can swing COGS percentage by a full point, and a single inaccurate count contaminates two months of data because closing inventory becomes the next period’s opening inventory.
• Unrecorded transfers: Inter-site movements not logged at both ends create phantom variance at the sending and receiving site simultaneously.

Two Jelly features address these causes directly. Price Alert flags every supplier price increase or decrease by ingredient and supplier the moment a new invoice is scanned, giving operators the evidence to negotiate credits before the variance compounds. Flash Report then delivers daily, weekly, or monthly GP margin by site, so a problem week is visible before it becomes a problem month.

How to Handle VAT on Supplier Invoices in COGS Calculations

UK supplier invoices for standard-rated goods arrive with 20% VAT included in the total. To extract the VAT-exclusive cost, divide the VAT-inclusive price by 1.2, for example a £180 VAT-inclusive purchase yields a £150 net cost and £30 reclaimable VAT. Using the gross figure in COGS calculations overstates ingredient cost and understates gross margin by the full VAT fraction.

Hot food and drink consumed on premises, hot takeaway food, alcoholic drinks, and catering services are all standard-rated at 20% VAT, while cold takeaway food not eaten on premises is zero-rated. For mixed supplies such as a meal deal combining standard-rated and zero-rated items, VAT must be apportioned correctly. Under Making Tax Digital, UK businesses must keep digital records and file VAT returns using MTD-compatible software, and manual entry of totals into HMRC’s portal is not permitted.

Jelly digitises every line item of every invoice including tax, stripping VAT before costing so that every margin figure in the platform reflects the true net cost of ingredients.

What Is a Good COGS Percentage for a UK Restaurant?

COGS benchmarks vary materially by segment, so a single industry range across all formats misreads margins. Segment benchmarks are:

• Quick-service restaurants (QSR): 25–31%
• Casual dining: 28–33%
• Fine dining: 30–38%
• Bars and beverage-led venues: 18–24% on beverages
• Central kitchens and commissaries: 35–42%

A 34% COGS is catastrophic for a QSR operator but perfectly normal for a fine-dining restaurant. For UK pubs, the correct GP formula uses net selling price, which means the till price with VAT stripped out, as the denominator; using VAT-inclusive till prices overstates pub drink GP by roughly seven percentage points.

Within a single group, the gap between the best-performing and worst-performing site is almost always wider than the gap between good and average operators across the industry, so a 12-site group might have one site at 27% COGS and another at 35%, with the aggregated group number hiding the problem entirely. That visibility problem is exactly where spreadsheets fail, because a spreadsheet COGS model breaks at the second site for three structural reasons.

Free Spreadsheet vs Automated COGS Calculator for Multi-Site Groups

A spreadsheet COGS model breaks at the second site for three structural reasons. First, inter-site transfers have no native transaction type in a spreadsheet, so teams either ignore them or adjust them manually, and both approaches introduce errors. Second, ingredient prices must be updated manually each time a new invoice arrives. A 6% jump from a main protein supplier caught the week it happens is a conversation with the supplier. Caught three months later, it becomes a margin hole to dig out of. Third, group-level reconciliation requires eliminating internal transfers and consolidating site COGS into a single defensible figure. That formula logic grows exponentially with each new site and breaks silently when a cell reference changes.

For a broader comparison of automated food costing software for UK hospitality, see Jelly’s dedicated guide. When you evaluate automation for a multi-site group, focus on five criteria: line-item invoice capture without manual entry, transfer elimination at group level, VAT-correct costing, real-time variance attribution by site, and POS integration for theoretical COGS. Jelly is built to meet all five for growing UK restaurants, pubs, and boutique hotels.

A Worked Group-vs-Site Reconciliation Example

This example shows why transfer elimination matters. The aim is to show that summing site COGS overstates the group figure until internal transfers are removed.

Consider a two-site group. Site A has opening inventory of £8,000, purchases of £12,000, and closing inventory of £9,000. It also transferred £1,500 of stock to Site B during the period.

Site A COGS = £8,000 + £12,000 − £1,500 (transfer out) − £9,000 = £9,500

Site B has opening inventory of £5,000, purchases of £7,000, received the £1,500 transfer from Site A, and has closing inventory of £6,000.

Site B COGS = £5,000 + £7,000 + £1,500 (transfer in) − £6,000 = £7,500

Sum of site COGS = £9,500 + £7,500 = £17,000

The group’s actual external purchases were £12,000 + £7,000 = £19,000. The £1,500 transfer has been counted once as a reduction at Site A and once as an addition at Site B, netting to zero at site level, which is correct. However, if the transfer had not been recorded at all, Site A’s closing inventory would be overstated by £1,500 and Site B’s purchases would appear understated, producing a group COGS figure that cannot be reconciled to the supplier invoices.

Group COGS = Σ Site COGS − Σ Internal Transfers = £17,000 − £1,500 = £15,500, which equals external purchases of £19,000 minus the net inventory build of £3,500. The internal transfer is eliminated and the group figure reflects only what was bought from external suppliers.

COGS-Well Alternatives UK and MarketMan vs Nory vs Jelly for Multi-Site COGS

The competitive landscape for multi-site COGS automation in the UK divides into three categories. Legacy platforms such as Kitchen Cut were built for large chains with dedicated office teams and carry the complexity and cost that implies. Newer all-in-one platforms such as MarketMan and Nory offer broader feature sets but are frequently described by operators as complex to onboard and expensive to run. Jelly occupies a distinct position, purpose-built for growing UK operators at the 2–5 site stage, with a flat rate of £129 per location per month, onboarding that generates value in the first week, and a user interface clean enough for the least tech-savvy chef to operate without training.

Square, EPOS Now, Toast, and Lightspeed are Jelly’s POS integration partners. Each delivers real-time, item-level sales data to Jelly the moment a transaction completes, enabling automatic theoretical COGS calculation and sales mix analysis without manual export. For detail on how inventory tracking integrates with food cost calculation in practice, see Jelly’s food cost calculator with inventory tracking guide. With the landscape clear, here is what Jelly actually does.

The Product: Introducing Jelly

Jelly is the automated COGS calculator for multi-site UK restaurants, pubs, and boutique hotels. It captures every invoice, eliminates internal transfers, handles VAT, and attributes variance in real time. That combination replaces the spreadsheet workflow that breaks at the second site.

Key features include:

• Automated invoice scanning via email or photo, extracting every line item including quantity, SKU, price, and tax
• Real-time dish costing with live GP margins that update automatically when a new invoice changes an ingredient price
• Price Alert flagging every supplier price increase or decrease by ingredient and supplier
• Flash Report delivering daily, weekly, or monthly GP margin by site
• Menu Engineering (Sales Mix) via POS integration with Square, EPOS Now, Toast, and Lightspeed
• One-click push to Xero with a 90% reduction in bookkeeping time, and Sage integration coming soon

The results are verified. Jelly customers cut food costs by 3% on average in the first three months, and gross margins increase by 2 percentage points. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue. Amber, a Mediterranean restaurant in East London, saves £3,000–£4,000 per month. That is approximately 68× ROI, driven by invoice automation, real-time costing, and Price Alert-driven supplier negotiations. Murat Kilic, Chef-Owner at Amber, says: “Jelly keeps my business alive.” Populu saw similar gains, lifting GP from 68% to 72% across 16 locations after connecting Jelly’s POS integration.

Stuart Noble, Head Chef at Cairn Lodge Hotel, says: “Price hikes were crushing our margins, I felt helpless. With Jelly, every dish cost is up-to-date at my fingertips. We slashed food costs by 5% in a month, it is a game changer!”

Jelly onboards in the first week and charges a flat £129 per month per location, with no variable charges per user or feature.

Start your first-week onboarding

Frequently Asked Questions (FAQ)

What COGS Percentage Should a Multi-Site UK Group Target?

Target COGS still depends on format, and the segment benchmarks above apply. The most important benchmark for a group is the gap between theoretical COGS and actual COGS. A persistent gap above 3–4 percentage points signals a systemic issue. Jelly’s Flash Report and real-time dish costing give you both figures without waiting for a month-end P&L.

How to Calculate Restaurant Inventory Across Multiple Sites?

Each site requires a consistent opening count, line-item purchase recording net of VAT, logging of all inter-site transfers in and out, and a closing count valued on the same basis as opening. At group level, internal transfers must be eliminated so the consolidated figure reflects only external supplier purchases. Jelly automates the purchase capture and transfer elimination steps, reducing the process from hours of manual reconciliation to a real-time dashboard.

Is There a Free Spreadsheet I Can Use for Multi-Site Food Costing?

Spreadsheets work at one site but break structurally at two. They have no native transaction type for inter-site transfers, require manual price updates every time a supplier invoice changes, and produce group-level reconciliation logic that fails silently when a cell reference breaks. For a single-site operator, a spreadsheet is a reasonable starting point. For a group, the hidden cost in margin erosion, missed credits, and management time typically exceeds Jelly’s flat £129 per location per month within the first quarter.

How to Do Accounting for a Multi-Site Restaurant Group?

Multi-site restaurant accounting requires site-level P&L visibility, consolidated group reporting, and a clean flow from operational data such as invoices, stock movements, and POS sales into the general ledger. The critical integration sits between the back-of-house platform and the accounting system. When a delivery is confirmed, the corresponding entry should post automatically. Jelly integrates directly with Xero, with Sage coming soon, pushing digitised invoices with one click, while operators or their teams can avoid spending 10–20 hours a week on manual data entry, price checking, inventory, and reconciling invoices.

How Do Inter-Site Stock Transfers Affect Group COGS?

If transfers are not recorded, the receiving site’s purchases are overstated and the sending site’s closing inventory is understated, which distorts COGS at both locations. At group level, uneliminated transfers cause the consolidated COGS figure to exceed actual external purchases, so the group appears to have spent more than it did. The correct treatment records the transfer at both ends at the source cost basis, then eliminates it from the group purchasing figure. Jelly handles this automatically, so group COGS reflects only what was bought from external suppliers.

Conclusion: The Definitive Automated COGS Calculator for Multi-Site UK Restaurants

Group COGS reflects more than the sum of your sites. Inter-site transfers, central kitchen production flows, VAT-inclusive invoices, and timing differences between purchases and sales all distort site-level figures in ways that a spreadsheet cannot reconcile automatically. By the time the month-end P&L arrives, the margin has already eroded and the window to act has closed.

Jelly is the automated COGS calculator built for this problem. It captures every invoice at line-item level, eliminates internal transfers at group level, strips VAT before costing, and attributes variance to its true cause in real time rather than four weeks after the period closes. At that flat rate with first-week onboarding, it is the simplest path from spreadsheet chaos to operational control for growing UK restaurants, pubs, and boutique hotels.

Start your first-week onboarding