Written by: JJ Tan, Founder, Jelly | Last updated: 19 September 2026
Key Takeaways
- Inventory software choice for UK multi-site pubs should start with pub type (wet-led vs food-led) and existing EPOS before feature lists.
- Groups with 2–5 sites need speed and simplicity. Groups with 5–20 sites need central purchasing, inter-site transfers and cross-venue GP benchmarking.
- Wet-led pubs need separate draught, packaged and spirits variance tracking plus line-cleaning waste logs. Food-led pubs need recipe costing and dish-level GP.
- EPOS integration is essential for real-time GP calculations. Jelly connects natively with Square, EPOS Now, Lightspeed and Toast.
- Jelly delivers automated invoice scanning, Price Alerts and Flash Reports that give pub groups immediate GP visibility across sites without lengthy implementation.
See Jelly In Action For Your Pub Group
The Problem: Why Most Pub Groups Shortlist the Wrong System
Most pub groups shortlist inventory software on feature lists. They compare dashboards, count integrations and read case studies from restaurant chains. Six months later they discover that the tool cannot handle cask fill levels, has no workflow for inter-site transfers, or does not connect to the EPOS already running across their estate.
UKHospitality warns that without a consolidated group-wide view of spend, pricing pressure, supplier dependency and working-capital drag can accumulate unnoticed across sites, with risk accumulating centrally while commercial decisions are made locally. That is precisely what happens when the wrong system is in place. Stock moves between sites without records, supplier price rises go unnoticed until the monthly P&L, and GP performance across venues can only be compared through manual spreadsheet work.
The organising principle is straightforward: start with your pub type and your EPOS. The software decision follows from those two answers. Ask these two questions before any vendor shortlist:
- Is the operation primarily wet-led or food-led?
- Which EPOS system is already running across the sites?
Getting this wrong has a measurable cost. Fragmented multi-site operational systems produce duplicate data entry between procurement and finance, poor forecasting, stockouts during peak service, over-ordering of perishables, delayed visibility into food cost variance, and weak control over transfers between sites. Admin time compounds, GP visibility is delayed by weeks, and margin leaks between sites without anyone knowing where.
Walk Through A Multi-Site Workflow With Jelly
The Wet-Led vs Food-Led Decision
Wet-led and food-led pub operations have fundamentally different stock control mechanics. A system built for one will frustrate operators running the other.
A wet-led pub’s margin is driven by keg and bottle yields, legally defined measures and wastage control. Draught beer losses are legitimate and legal in a wet-led UK pub. They arise from head allowance, line cleaning and pull-through at the start of a week, the first pint off a new keg, fobbing when the cellar runs warm, and samples poured for reps. A single blended variance percentage across all liquor stock hides a genuine spirits problem behind a normal draught allowance, or makes an ordinary week look like a crisis. Draught, packaged and spirits should each be measured separately. Pub stock control software UK therefore must handle cask fill levels, optics, line-cleaning waste logs, draught versus packaged variance and bottle-level counts as distinct categories.
A food-led pub’s margin is driven by recipe costing, yield and wastage, menu engineering and dish-level GP. Because wet-led pubs may run food near cost to drive drink sales, menu and recipe costing discipline matters more in food-led pubs than in wet-led pubs, where margin is driven by keg and bottle yields and wastage instead.
An 8-site wet-led community pub group and an 8-site gastropub group are not the same buyer. The wet-led group needs cellar-level control, draught variance reporting and line-cleaning waste logs. The food-led group needs recipe costing, yield tracking and dish-level GP by site. A system optimised for one leaves the other flying blind on the metrics that matter most.
What Wet-Led Bars Need From An Inventory System
For UK wet-led bars and pubs, the right inventory system separates draught, packaged and spirits variance, logs line-cleaning waste as a distinct category, and tracks cask fill levels rather than relying on estimated keg weights. EPOS software cannot replace a physical keg reading: the till tells you what was sold or voided but cannot tell you how much beer remains in a sealed keg, whether a delivery was short, or whether last night’s line clean was logged. For bars running food alongside drinks, the system also needs to connect invoice costs to dish-level GP in real time. Jelly meets both requirements. Automated invoice scanning keeps ingredient costs live, and the Flash Report gives daily, weekly or monthly GP margin visibility.
Site-Count Tiers: 2–5, 5–20 and 20+ Sites
Pub type is the first filter. The second is how many sites you run, because the operational demands shift sharply at each tier.
2–5 Sites: The owner or operations manager is still close to the operation. The priority is speed and simplicity. At this size the owner is often doing the ordering and the stocktakes, so a system that takes weeks to configure will not get used. What matters is that it onboards in the first week, needs no dedicated IT resource, and shows invoice costs and GP straight away. Complexity at this stage kills adoption before the system has a chance to prove itself.
5–20 Sites: Central purchasing, inter-site transfers and cross-venue benchmarking become essential. Moving from one venue to three does not triple inventory complexity but grows it by an order of magnitude, with different par levels, internal transfers, central purchasing, store-level variance and consolidated reporting all hitting at once. At this tier, the system must surface supplier price changes across the whole estate, record stock movements between sites with a proper audit trail, and let head office compare GP performance by venue without manual spreadsheet consolidation.
20+ Sites: Dedicated office teams and legacy systems come into play. Enterprise procurement platforms, ERP integrations and bespoke reporting become relevant. The shortlist at this scale looks materially different from the 5–20 tier, and the onboarding timeline is measured in months rather than days.
The EPOS Ecosystem Constraint
The EPOS a pub group already runs shapes the inventory shortlist more than any other single factor. Multi-site pub EPOS integration is the mechanism by which sales data flows into GP calculations in real time. Without it, margin reporting is always retrospective.
Jelly integrates with Square, EPOS Now, LightSpeed and Toast, which are complementary integration partners rather than competitors. There is a significant capability gap between entry-level EPOS systems, which offer only basic stock counts and simple alerts, and advanced EPOS platforms, which provide multi-location tracking and detailed margin reporting.
Jelly integrates natively via real-time API with four POS systems: Square, EPOS Now, Lightspeed and Toast. Each integration delivers item-level sales data the moment a transaction completes. Connecting any supported POS takes approximately five minutes, and the flow is identical across all four: 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, keeping the mapping clean and free of legacy menu clutter. Jelly works alongside these systems as a complementary integration partner. They handle the transaction, and Jelly handles the back-of-house intelligence.
For pub groups running Zonal or ICRTouch, Jelly’s invoice automation, Price Alert and Flash Report still deliver immediate value on the cost side. POS integration can be added when the group migrates to a supported system.
The Solution: How Shortlisted Platforms Compare
With the EPOS constraint established, the shortlist narrows to a handful of platforms. The table below shows how they compare on fit for wet-led or food-led operations and typical group size.
| Platform | Indicative Fit For A 5-Site Group | Best Fit |
|---|---|---|
| Jelly | Flat per-site subscription with week-one onboarding and no per-user charges. | Growing pub groups (2–20 sites, £500k+ revenue) needing fast onboarding, automated invoice scanning, real-time GP and EPOS integration. |
| MarketMan | Subscription pricing with paid onboarding and higher configuration effort. | Procurement-heavy restaurant and bar groups. More feature-rich with longer onboarding and higher complexity. Many UK operators searching for MarketMan alternatives report that it feels over-engineered for wet-led operations. |
| WISK | Subscription plus setup fee with structured onboarding. | Larger venues and groups with dedicated bar management teams. US-originated, so measure conventions and support may not align with UK pub operations. |
| Apicbase | Enterprise-style commercial terms agreed case by case. | Large food-led hospitality groups and contract catering operations with complex recipe and allergen management requirements. |
| Kitchen CUT | Enterprise-style commercial terms agreed case by case. | Large chains with dedicated office teams. A legacy system with static architecture that lacks real-time invoice-to-dish-cost automation for growing pub groups. |
| Zonal | Enterprise licensing negotiated for large estates. | Large managed pub estates with Zonal EPOS already embedded. Often considered at the 20+ site tier, where complexity and cost match larger groups. |
| ICRTouch StockCheck | Commercial terms set via ICRTouch resellers. | Pub groups already running ICRTouch EPOS who want native stock control within the same ecosystem. Capability varies by reseller configuration. |
Cellar and Line-Level Control for Wet-Led Sites
Industry guidance for wet-led pubs commonly puts draught shrinkage at 5 to 10% where control is loose, and at 2 to 4% where counts, pouring and cellar discipline are tight. The gap between those two figures, on a site doing £150,000 of draught beer annually, is between £4,500 and £9,000 a year on draught alone.
The main sources of cellar and line-level variance in a wet-led pub are:
- Cask fill levels estimated by tilt or feel rather than measured. Because kegs are opaque and under pressure, many operators estimate remaining volume by weight of hand, a shake, or “it feels about half”, a guess that is one of the biggest sources of variance between recorded sales and actual stock.
- Line cleaning and pull-through not recorded as waste. Line cleaning and pull-through that is not recorded is counted as loss in pub stocktakes.
- Cellar temperature driving fobbing. Poor cellar temperature drives cask wastage through fobbing and wasted liquid down the drain, and the cellar temperature log should be checked before checking staff.
- Head allowance. Up to 5% of every draught measure served in a UK pub can legitimately be head, per British Beer and Pub Association guidance on head of beer, meaning that liquid never reaches the customer’s glass, never rings through the till as volume, and will show up in a stocktake as gone.
- Optics and free-pour on spirits. Spirits are where a small consistent over-pour compounds fastest because the unit is small and the price is high.
How To Manage Inventory Across Multiple Channels
For wet-led multi-site pub groups, effective multi-channel inventory control treats each site’s cellar as a distinct stock location with its own draught, packaged and spirits variance tracked separately. Head office then holds a consolidated view of supplier pricing and inter-site stock movements. Unrecorded inter-branch movements are the single biggest source of phantom variance in multi-site groups, because a branch borrowing stock from a neighbouring site creates a variance at both locations that traces to nothing. Every transfer between sites must be recorded as a formal movement that is raised, submitted and received, with stock adjusting automatically on both ends only when the destination confirms receipt.
How To Manage Stock Across Multiple Pub Sites
Central purchasing and supplier price tracking for pub groups rely on three operational disciplines that most growing groups do not have in place when they reach five or more sites.
First, supplier price changes must be visible at the moment they occur, not when the monthly P&L is closed. A common cause of divergence between food cost percentage and P&L COGS is a lag between supplier price changes and recipe cost updates. Procurement may negotiate new pricing while recipe cards still reflect last quarter’s costs. Jelly’s Price Alert feature flags every price increase or decrease on the day it appears on an invoice, giving operators the evidence to challenge suppliers and claim credit notes before the margin damage compounds.
Second, inter-site stock transfers must be recorded formally. Stock transfers between locations create a procurement-inventory boundary that many systems handle poorly: when one site has surplus stock and another is short, the transfer must be logged accurately both to maintain inventory accuracy and to assign COGS to the correct cost centre, and groups tracking this manually describe it as “just writing it down in the log”, which creates reconciliation headaches at month-end.
Third, GP performance must be comparable across venues without manual consolidation. Questions to ask any vendor in a demo:
- Can I see GP by site on a single screen without switching logins?
- Does the system record inter-site stock transfers with a full audit trail?
- How quickly does a supplier price change flow through to dish-level GP?
- What is the onboarding timeline for a five-site group?
- Which EPOS systems does it integrate with natively, and how long does setup take?
- Is pricing flat per site, or does it scale by user, feature or transaction volume?
Why Jelly Is The Right Inventory Software For Growing UK Pub Groups
Jelly is built for growing pub groups in the 2–5 site tier and scales comfortably into the 5–20 tier. It uses flat-rate pricing, a one-week onboarding timeline and a feature set that covers the full invoice-to-GP workflow without a dedicated IT team or a months-long implementation project.
Key features:
- Automated Invoice Scanning: Capture invoices via email or photo. Jelly digitises every line item, including quantity, SKU, price and tax, and updates ingredient costs in real time.
- Price Alert: Flags every supplier price increase or decrease the moment it appears on an invoice, with the evidence needed to negotiate credits or switch suppliers.
- Flash Report: Daily, weekly or monthly view of GP margin, calculated from invoice costs and POS sales data.
- Menu Engineering (Sales Mix): Via POS integration with Square, EPOS Now, Lightspeed and Toast, shows which dishes are most popular and most profitable.
- Cookbook and Live Dish Costing: Build recipes from scanned invoice ingredients. As invoice prices update, dish GP margins update automatically. What used to take 28 minutes to cost now takes 3 minutes.
- Delivery Menu Creation: Duplicate existing menu items and factor in delivery commission overheads to build a separate, profitable delivery menu.
- Xero Integration: One-click push of digitised invoices into Xero, with Sage integration coming soon.
- Flat Per-Site Pricing: Simple per-location subscription with no per-user or per-feature charges.
Verified outcomes across Jelly’s customer base:
- 10–20 hours of admin saved per month
- 2 percentage points added to gross margins on average in the first 3 months
- 3% food cost reduction on average in the first 3 months
- 90% reduction in bookkeeping time
Named results: Amber (East London) saves £3,000–£4,000 per month, approximately 68× ROI. Populu lifted GP from 68% to 72% across 16 locations. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue.
“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’s a game changer!” — Stuart Noble, Head Chef, Cairn Lodge Hotel
“Our accountant said we’d be lucky to hit 60% gross profit. After using Jelly, we reached 80%! Now I sleep better knowing my costs are under control and can react instantly, not weeks later.” — Ruth Seggie, Owner, The Howard Arms
Get Your GP Visibility In Week One
Demo Question Checklist For Pub Group Operations Directors
Use these questions when evaluating any inventory platform for a multi-site pub group:
- Can I see GP percentage by site on a single dashboard, in real time, without switching between logins or exporting to a spreadsheet?
- How does the system record a stock transfer between two of my sites, and what does the audit trail look like?
- Does stock update at both ends only when the receiving site confirms receipt?
- Does the system separate draught, packaged and spirits variance, or does it report a single blended liquor figure?
- How does a supplier price change on an invoice flow through to dish-level GP, and is it automatic?
- What is the realistic onboarding timeline for a group of our size, in days or months?
- Which EPOS systems does it integrate with natively, and how long does the POS connection take to set up?
- Is pricing flat per site, or does it scale by number of users, features or transaction volume?
- Can line-cleaning waste and cask pull-through be logged as a distinct category so they do not appear as unexplained variance?
- Does the system flag supplier price increases automatically, or do I need to run a report to find them?
Frequently Asked Questions
What Is The Best Inventory System For Bars?
For UK wet-led bars and pubs, the best inventory system separates draught, packaged and spirits variance rather than reporting a single blended figure, logs line-cleaning waste and cask pull-through as distinct categories, and connects invoice costs to GP in real time. For bars running food alongside drinks, the system must also link recipe costs to dish-level GP and update automatically when supplier prices change. Jelly covers both requirements. Automated invoice scanning keeps ingredient costs live across every site, and the Flash Report gives daily GP visibility without manual consolidation.
How Long Does It Take To Onboard Inventory Software Across Multiple Pub Sites?
Onboarding timelines vary significantly by platform. Enterprise inventory and multi-location restaurant systems such as Zonal and Kitchen CUT typically take 8 to 12 weeks to implement, with the timeline driven by data standardisation and process preparation rather than the vendor’s install. Jelly onboards in the first week. Operators gain access to Price Alerts and spending insights as soon as suppliers are sending invoices to a dedicated email address, or within 24 hours of photographing invoices into the platform. POS integration with any of the four supported systems takes approximately five minutes. For a five-site pub group, the realistic timeline from sign-up to live GP data across all sites is days, not months.
Conclusion: Choosing The Right System For Your Pub Group
The core challenge for growing UK pub groups is not a lack of inventory software options. The challenge is shortlisting on features rather than fit. A wet-led 8-site group and a food-led 8-site group need different tools. A group running EPOS Now has a different shortlist from one running Zonal. A group at 5 sites has different priorities from one at 25.
Jelly is built for the 2–20 site tier. It is simple enough for non-tech-savvy bar and kitchen teams, fast enough to generate value in the first week, and priced at the flat per-site rate described above. Automated invoice scanning, real-time Price Alerts, the Flash Report and native POS integration with Square, EPOS Now, Lightspeed and Toast give operations directors the GP visibility they need across every site, without waiting for a monthly accountant’s report.
Talk To Jelly About Your Sites



