Written by: JJ Tan, Founder, Jelly | Last updated: 22 June 2026
Key Takeaways
- Multi-site pub groups in 2026 face margin leakage from disconnected systems, supplier price volatility, and delayed reporting that widens with each new location.
- Central inventory accuracy, offline resilience, rollout speed, three-year TCO, and food or wet-led suitability determine whether an EPOS platform genuinely supports multi-site operations.
- Enterprise platforms such as Zonal and Access/Evo offer robust features for larger estates but require longer implementation timelines and dedicated IT resource.
- Kobas and EPOS Now provide faster deployment options for 3–15 site groups, with EPOS Now, Lightspeed, Square, and Toast integrating natively with back-office automation tools.
- Pairing any EPOS with Jelly delivers real-time invoice scanning, dish costing, and price alerts that close the margin control gap in under five minutes per site.
What multi-site EPOS requirements actually means
A multi-site EPOS requirement goes beyond having the same software on every till. It describes a system architecture that allows a head-office team to view, control, and report across all locations from a single account. This removes the need for site managers to manually consolidate data.
Five criteria define whether an EPOS platform genuinely meets multi-site pub requirements in 2026:
- Central inventory accuracy, with consolidated stock visibility, inter-site transfer workflows, and theoretical depletion from recipe and sales data.
- Offline resilience, with the ability to trade without internet connectivity and sync cleanly on reconnection.
- Rollout speed and onboarding, with realistic timelines for high-turnover bar teams that have minimal technical resource.
- 2026 total cost of ownership (TCO), covering hardware, software, add-ons, payment processing, and contract exit terms over a three-year horizon.
- Food-led versus wet-led suitability, based on whether kitchen display, recipe costing, and tab management features match the venue’s primary revenue mix.
Central inventory and stock accuracy across every site
Operations leaders at multi-site groups need to view current stock positions at every location from a single group account dashboard rather than logging into separate site accounts. Platforms that deliver this natively, instead of through bolt-on modules, reduce the administrative overhead that typically falls on area managers.
A recipe costing integration is critical because it enables theoretical depletion calculations from sales data. Without that link, variance reporting is limited to physical-count gaps rather than expected-versus-actual usage. Healthy stock variance benchmarks for restaurants sit at 2–3%. Variance above that level indicates potential issues.
Multi-location stock management that covers inter-site transfers, recipe costing integration, and POS connections often takes several weeks for pub groups to implement. Operators should factor this timeline into any rollout plan.
Zonal and Access/Evo include stock control modules within their hospitality suites. Kobas offers centralised stock management designed specifically for pub groups. However, when EPOS connects to stock management, product sales automatically adjust inventory counts in real time, and the accuracy of that data depends entirely on whether invoices and supplier price changes also feed the system. That gap is where most EPOS platforms stop and where a back-office automation layer becomes essential.
Offline resilience for thick-walled UK pubs
Real-time stock accuracy only matters when the system can record transactions during connectivity drops. Victorian brickwork, basement bars, and rural locations make offline resilience a non-negotiable for UK pub operators. A system that freezes during a connectivity drop on a Saturday night creates both revenue loss and reputational damage.
| Platform | Offline mode | Sync behaviour | Deployment model |
|---|---|---|---|
| Zonal | Full trading via on-premise component | Reconciled centrally on reconnection | Hybrid cloud/on-premise |
| Access/Evo | Local server fallback available | Cloud sync on reconnection | Hybrid |
| Kobas | Offline mode supported | Syncs on reconnection | Cloud-based |
ICRTouch, worth noting for rural venues, is available as a one-time permanent licence rather than a subscription. That model can materially change TCO for operators in low-connectivity areas.
Rollout time and onboarding for high-turnover bar teams
Fast rollout and simple onboarding keep high-turnover bar teams productive. Any EPOS that requires a week of classroom training per site creates ongoing operational drag. Platforms best suited to 3–15 site pub groups offer role-based access, intuitive till interfaces, and remote configuration from a central admin panel so that new starters can be productive within a single shift.
Zonal and Access/Evo are enterprise-grade platforms with corresponding implementation timelines. Rollouts typically take several weeks per estate and need dedicated project management. Kobas is designed for pub groups and positions itself on faster deployment.
Operators also need to account for the back-office layer. Jelly’s POS setup takes approximately five minutes across all supported integrations. Open Jelly, click Integrations, sign in to the POS, grant permissions, and select categories to sync. This sequence makes Jelly one of the fastest back-office onboarding experiences available for multi-site groups.
See the five-minute setup in action. The team will walk through the exact integration steps for your EPOS.
2026 pricing and total cost of ownership realities
The Epos Now 2026 buying guide recommends calculating three-year TCO, covering initial hardware, 36 months of subscriptions, and hidden fees, rather than focusing only on upfront pricing. That advice applies to every platform in this comparison. EPOS hardware typically costs £300–£1,000+ upfront, software subscriptions £30–£100+ per month, and support and maintenance a further £30–£85+ per month. Common paid add-ons include multi-site management, accounting integrations, and loyalty programmes, and paid extras can more than double monthly fees.
Platform-specific indicators for 2026:
- Zonal pricing is bespoke, based on sites and modules required, covering supply chain, reservations, and stock control.
- Access/Evo offers modules including kitchen display systems and Menu Manager. Customers have reported automatic contract roll-overs without sufficient notice.
- Kobas pricing is available on request for multi-site deployments.
EPOS contracts may include automatic price increases, hidden fees, and clauses allowing providers to remotely disable systems if payments are missed. Requesting a full cost breakdown before signing remains essential.
Food-led versus wet-led suitability by venue type
Food-led pub groups that derive more than half of revenue from kitchen covers need kitchen display system integration, recipe-level stock depletion, allergen management, and course-by-course ordering. Zonal and Access/Evo are well established in this space, with modular kitchen management built into their hospitality suites. Kobas handles both food and wet-led operations and is used across managed pub estates.
Wet-led operations prioritise tab management, round ordering, cellar stock tracking, and fast transaction throughput. Zonal’s tab-linked reservations and Kobas’s cellar management features support these needs. For operators running a mixed estate, the ability to configure each site independently within a central account becomes the deciding factor.
EPOS Now, Lightspeed, Square, and Toast each serve food-led venues effectively and integrate natively with Jelly. Operators on these platforms can add real-time dish costing and invoice automation without changing their till infrastructure.
Head-to-head comparison: Zonal, Kobas, Access/Evo and EPOS Now (2026)
| Criterion | Zonal | Kobas | Access/Evo | EPOS Now |
|---|---|---|---|---|
| Central inventory | Centralised reporting, data reconciled after reconnection | Built-in multi-site stock management | Optional stock control add-on | Multi-site management add-on at ~£25/month |
| Offline resilience | Hybrid cloud/on-premise, full trading offline | Offline mode, cloud sync on reconnection | Local server fallback, hybrid deployment | Cloud-based with offline mode |
| Rollout speed | Enterprise implementation, weeks per estate | Designed for pub groups, faster deployment | Project-managed rollout, scalable pricing structure | Self-serve setup, hardware bundles from £149 |
| 2026 indicative cost | Bespoke per site or module | Contact for multi-site pricing | From £316/month (1 site, 2 terminals) | From ~£25/month/terminal, hardware £799 |
| Food or wet-led fit | Strong food and wet, tab-linked reservations | Both, cellar management included | Strong food-led, KDS and Menu Manager modules | Food and wet, 100+ app integrations |
| Integration ecosystem | Bespoke integrations, purchase-to-pay module | Open API, third-party integrations | Optional CRM and stock add-ons | Xero, Sage, Deputy via integration hub, Jelly native integration |
EPOS is only half the story with margin control
EPOS platforms in this comparison record what was sold. None of them automatically scan supplier invoices, update dish costs in real time, or alert the kitchen when a price increase erodes margin. Jelly closes that gap.
Jelly is a £129/month flat-fee back-office automation layer, with one price per site and no per-user charges, that connects to EPOS Now, Square, Lightspeed, and Toast via real-time API. Setup takes approximately five minutes. Once connected, every invoice scanned by photo or email updates ingredient costs across all live dish recipes automatically. The Flash Report delivers a daily GP view calculated from actual costs and POS sales. The Price Alert feature flags every supplier price movement, giving operators the evidence to negotiate credits or switch suppliers before the damage compounds.
The results are measurable. Amber, a Mediterranean restaurant in East London, saves £3,000–£4,000 per month through Jelly’s invoice automation, price alerts, and real-time costing, which equates to approximately 68× ROI. Chef-Owner Murat Kilic states: “Jelly keeps my business alive.” One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue. Populu lifted GP from 68% to 72% across 16 locations. On average, Jelly users add 2 percentage points to gross margins in the first three months.
For multi-site pub groups already running Zonal, Kobas, or Access/Evo, Jelly operates as a complementary back-office layer rather than a replacement till system. For groups on EPOS Now, Square, Lightspeed, or Toast, the native integration delivers item-level sales data the moment a transaction completes. The Sales Mix report then shows which dishes are most popular and most profitable across every site simultaneously.
Connect your EPOS in under five minutes. The team will show you the native integration for your platform.
Multi-site rollout checklist for pub groups
- Confirm central admin access for the head-office team across all site accounts, so you can control locations from a single dashboard.
- After confirming access, audit offline resilience requirements by site, noting building type, connectivity history, and peak trading periods, because these factors shape the deployment model that will work.
- With infrastructure needs clear, map existing integrations such as accounting software (Xero, Sage), labour scheduling, and any stock tools, so the new EPOS does not create duplicate data entry.
- Using that information, request a full three-year TCO breakdown from each EPOS vendor, including add-ons, payment processing, and exit clauses.
- Pilot one site before full estate rollout and measure variance reporting accuracy against the healthy benchmark noted earlier.
- Connect Jelly to the EPOS at the pilot site and confirm invoice scanning, price alerts, and the Flash Report are live within the first week.
- Train site managers on Jelly’s Price Alert and dish costing features. Average onboarding time sits under one hour.
- Roll out remaining sites sequentially and use the central Jelly account to monitor GP across the estate from day one.
EPOS Now vs Zonal for 3–15 site pub groups
Choosing between EPOS Now and Zonal for smaller estates
EPOS Now suits independent and growing pub groups that want a self-serve, lower-entry-cost platform with a broad app ecosystem. The platform integrates natively with Jelly for real-time back-office automation. The trade-off is that EPOS Now ties hardware and software to lengthy contracts that are difficult to exit, which becomes a meaningful TCO variable for groups processing high card volumes.
Zonal is an enterprise-grade platform built specifically for UK hospitality groups. Its hybrid cloud/on-premise architecture delivers full offline trading resilience, and its purchase-to-pay supply chain module addresses procurement visibility at scale. Pricing is bespoke, which makes Zonal better suited to groups with dedicated IT and operations resource to manage implementation. For groups of 3–6 sites without that resource, the implementation timeline and cost can outweigh the feature advantage over a simpler platform paired with Jelly.
Best EPOS choices for 3–15 site UK pubs
No single EPOS suits every pub group in this size range. The right choice depends on wet-led versus food-led revenue mix, building connectivity, existing accounting infrastructure, and available IT resource for rollout.
Zonal and Access/Evo serve larger, more complex estates with dedicated operations teams. Kobas is purpose-built for managed pub groups and offers faster deployment. EPOS Now, Lightspeed, Square, and Toast serve growing groups that want a lower-cost entry point and faster self-serve setup. All four integrate natively with Jelly, so the back-office automation layer is available from day one without additional integration work.
Regardless of EPOS choice, the margin control gap around real-time dish costing, automated invoice scanning, and live GP visibility requires a dedicated back-office tool. Jelly fills that gap at £129/month per site with the five-minute POS connection mentioned earlier and no per-user fees.
Conclusion: pairing EPOS with the right automation layer
The five criteria in this guide, covering central inventory accuracy, offline resilience, rollout speed, three-year TCO, and food or wet-led suitability, provide a consistent evaluation lens for any EPOS decision in 2026. Apply them to vendor proposals, request full cost breakdowns, and pilot before committing to an estate-wide rollout.
The more important decision for multi-site pub groups is recognising that EPOS data alone does not deliver margin control. Automated invoice scanning, live dish costing, and real-time price alerts require a back-office layer that sits alongside the till system rather than replacing it. Jelly provides that layer, remains compatible with the leading EPOS platforms, can be operational within a week, and consistently delivers measurable GP improvements across growing pub and restaurant groups.
See how Jelly works with your EPOS. The team will show you the integration for your current or planned platform.
Frequently asked questions
What is the difference between an EPOS system and a back-office automation tool like Jelly?
An EPOS system records transactions at the point of sale, capturing what was sold, at what price, by which staff member, and at which time. It provides sales data and, in many cases, basic stock depletion based on what was rung through the till. A back-office automation tool like Jelly operates on the cost side of the business. It scans supplier invoices line by line, updates ingredient costs in real time, calculates live dish and menu GP margins, and alerts operators when supplier prices change. The two tools are complementary. EPOS provides the sales data, and Jelly provides the cost and profitability intelligence, giving multi-site pub operators a complete picture of margin performance without manual data entry or monthly accountant reports.
How long does it take to roll out a new EPOS system across a 5–10 site pub group?
Timelines vary significantly by platform and estate complexity. Enterprise platforms such as Zonal and Access/Evo typically involve project-managed implementations that can run to several weeks across a full estate. Purpose-built pub group platforms such as Kobas are designed for faster deployment. Full implementation of multi-location stock management that covers inter-site transfers, recipe costing integration, and POS connections typically takes six to twelve weeks for groups of five to twenty locations. Operators should factor training time for bar teams into any rollout plan, particularly given high staff turnover in the sector. Jelly’s back-office layer can connect to a supported EPOS in approximately five minutes per site and generates initial value, including price alerts and spending insights, within the first week.
What should a multi-site pub group look for in EPOS offline resilience?
Offline resilience means the system can continue processing transactions, including card payments, tab management, and kitchen orders, without an active internet connection. For UK pubs in older buildings or rural locations, this is a baseline requirement rather than a premium feature. Key questions for any EPOS vendor include whether the system uses a local on-premise component or relies entirely on cloud connectivity, which specific functions are unavailable during an outage, and how transaction data syncs when connectivity is restored. Hybrid cloud or on-premise architectures, such as those used by Zonal, provide strong offline resilience for high-volume trading environments. Cloud-based platforms with offline modes offer a reasonable middle ground for most pub groups, provided the offline mode covers card processing and not just cash transactions.
How does Jelly improve gross profit margins for multi-site pub groups?
Jelly improves GP through three mechanisms. First, automated invoice scanning captures every supplier price change at the line-item level and triggers a Price Alert, giving operators the data to negotiate credits or switch suppliers before the margin impact compounds. Second, live dish costing means that every recipe’s GP percentage updates automatically when ingredient costs change. Operators see a red flag on any dish that has dropped below its target margin without waiting for a monthly review. Third, the Sales Mix report, generated by connecting Jelly to a supported EPOS, shows which dishes are both popular and profitable, enabling menu engineering decisions based on real data rather than intuition. On average, Jelly users add 2 percentage points to gross margins in the first three months. Amber restaurant in East London demonstrates these savings in practice, as detailed earlier in the article.
Is Jelly a replacement for an EPOS system?
No. Jelly is a back-office automation layer that works alongside an existing EPOS system, not a replacement for one. It does not process transactions, manage tables, or handle front-of-house operations. Jelly connects to EPOS Now, Square, Lightspeed, and Toast via real-time API to pull item-level sales data, which it combines with invoice cost data to produce live GP margins, Flash Reports, and Sales Mix analysis. For pub groups running Zonal, Kobas, or Access/Evo, Jelly operates as a complementary profitability tool that addresses the invoice-to-margin workflow those platforms do not automate. The two systems serve different functions and are designed to be used together.