Lavu hospitality POS for UK pubs in 2026

Last updated: 11 April 2026

Lavu is a US-built cloud EPOS system marketed as a flexible solution for hospitality venues across multiple territories — but UK pubs face a specific problem with it from day one. Most cloud EPOS systems are designed around restaurant workflows, not the real pressures of a wet-led pub during last orders on a Saturday night. I’ve personally tested systems like this across Teal Farm Pub in Washington, Tyne & Wear, managing 17 staff during peak trading with simultaneous card payments, kitchen tickets, and bar tabs — and the gaps in Lavu’s design for UK pub operations become obvious fast.

This guide cuts through the vendor marketing and shows you what Lavu actually delivers for UK hospitality, where it genuinely helps, and — honestly — where it will frustrate you. You’ll know by the end whether it’s worth your time to trial, or whether you need a system built for pubs from the ground up.

What Is Lavu and How Does It Work?

Lavu is a cloud-based point of sale system owned by Square (acquired in 2018) and designed primarily for restaurants, bars, and hospitality venues. The core architecture is SaaS-delivered — all data lives in the cloud, and you access the system via iPad, Android tablets, or terminal devices connected to the internet.

The system focuses on speed of transaction, kitchen integration via display screens, and mobile ordering. On paper, it looks flexible. In practice, the design assumptions baked into Lavu are American — high table turnover, tipping at checkout, reliance on card payments, and minimal offline resilience.

For a UK pub context, this matters immediately. We work differently. Cash is still meaningful in many venues. Bar tabs run all night and settle at close. Kitchen requirements are often simpler than restaurant workflows. And when the internet drops during last orders — it happens more than cloud vendors admit — you need a till that doesn’t pause.

Why Lavu Struggles With UK Pub Requirements

No Native Cellar Management

I’ve watched licensees spend two weeks manually counting stock because their EPOS didn’t talk to cellar systems. Lavu has no built-in cellar management module — you’ll need a separate system or manual tracking, which defeats the purpose of integrated software. Systems like Zonal and Tevalis address this because they were designed in the UK for wet-led venues. Lavu assumes you’re a restaurant with a small wine list, not a pub managing 12 draught lines, 30 cask ales in rotation, or spirits inventory across bottle and optic.

This isn’t a minor inconvenience. Cellar management integration matters more than most operators realise until they’re doing a Friday stock count manually. If you’re a wet-led only pub with no food, this gap alone should make you think twice.

Pubco Compatibility Unknown

If you’re a tied tenant under a pubco like Marston’s, Greene King, or Stonegate, you need EPOS approval. Most pubcos maintain approved EPOS lists. Lavu is not widely approved across major UK pubcos because it doesn’t integrate with their systems the way tied pubs require. You’ll need to check directly with your pubco before spending any money. This is a hard blocker for many licensees and most EPOS comparison sites miss it entirely.

Bar Tab and Running Credit Workflow

UK pubs don’t close the till every 30 minutes like restaurants. Drinkers run tabs, settle at close, and often pay cash or card after multiple drinks. Lavu’s tab system exists, but it’s designed for table service settlement, not the open-running bar model. Staff have told me the process feels clunky — tabs don’t close intuitively, and the interface assumes faster payment cycles than bar culture demands.

Payment Processing and Card Fees

Lavu processes payments through Square Payments. This is transparent, but it means you’re locked into Square’s card fee structure (typically 1.75% + 20p in 2026) and you can’t negotiate with Worldpay or other processors some pubs prefer. For a low-margin pub doing high card volumes, this compounds costs quickly. Using a pub profit margin calculator to model your actual throughput against payment fees is essential before committing to Lavu.

Real-World Performance: Peak Trading Scenarios

I tested various EPOS systems at Teal Farm Pub during peak trading — specifically a Saturday night with a full house, card-only payments, kitchen tickets, and bar tabs running simultaneously. This is the real test. Most systems that look good in a demo struggle when three staff are hitting the same terminal during last orders.

Lavu’s performance under this load depends entirely on your internet connection quality. If you have solid WiFi and tablets on a modern network, it’s reasonably fast. If your connection drops or stutters — common in older pub buildings with thick walls and poor infrastructure — the system becomes sluggish or unresponsive.

Kitchen Display Screen Performance

This is Lavu’s strongest feature. Kitchen display screens save more money in a busy pub than any other single feature. Lavu’s KDS integration is fast, clear, and the order flow from bar to kitchen is intuitive. If you serve food alongside drinks, this alone might justify the platform. Orders appear on the kitchen screen instantly, items are marked as prepared, and the bar sees completion status in real time. Compare this to paper tickets or shouting over the bar — the time saved is measurable.

Tablet Stability During Service

Tablets can crash. Battery drain is real. Screen responsiveness under pressure varies by device quality. If you’re relying on iPads as your till, you need spares, charging docks, and backup tablets ready. This adds hardware cost that often isn’t factored into budget discussions. When you’re managing 17 staff across FOH and kitchen using real scheduling systems daily, losing a terminal during service isn’t theoretical — it’s a business problem.

Offline Capability and Internet Dependency

This is the critical question every pub operator asks: what happens when the internet goes down?

Lavu has a limited offline mode. Transactions can be processed locally on the device, and they sync to the cloud when connectivity returns. The offline capability exists but is restricted — you can take payments, but certain features don’t work offline, including kitchen orders, customer history, and some reporting. This is better than nothing, but worse than systems built with offline-first architecture.

Here’s the real risk: internet outages don’t happen when you’re quiet. They happen on Friday and Saturday nights when you’re busiest and your internet provider is most likely to have issues. A cloud-dependent system puts you in a precarious position. The alternative — systems like Tevalis that sync data locally and push to cloud when available — is fundamentally more resilient for UK pub environments.

If your broadband is stable and you have a backup connection (4G hotspot), Lavu’s risk profile drops. If you’re in a rural area with patchy connectivity, avoid it.

Integration Support and Third-Party Software

QuickBooks and Xero Integration

Lavu doesn’t have native integrations with UK accounting software. Integration with QuickBooks integration for UK hospitality works through third-party tools like Zapier, not direct API connections. This means data syncs happen on a schedule (not in real time), and if something breaks in the chain, your accounts and till records may not reconcile cleanly. You’ll need to verify that your bookkeeper or accountant is comfortable with this workflow before you buy.

Staff Scheduling and Payroll

Lavu has basic staff management built in — clock in/out, simple shift tracking. But it doesn’t integrate deeply with dedicated payroll software or advanced scheduling tools. If you use a pub staffing cost calculator to plan rotas and labor budgets, you’ll need to export Lavu data manually or use a workaround. This is time-consuming and error-prone when managing 17 staff.

Inventory and Third-Party Stock Systems

As mentioned earlier, cellar management integration is weak. If you use inventory software like MarginEdge or similar, Lavu’s integration is limited. You’ll be managing stock in two places, which defeats the purpose of EPOS integration.

The True Cost of Lavu in 2026

Lavu’s pricing is opaque in its marketing. Let me break down what you’ll actually pay:

Monthly Software Fee

Lavu’s base pricing typically starts around £50–100 per month for a single-location venue (2026 rates). This is reasonable on the surface. But this is only the software license.

Hardware Costs

You need tablets (iPads minimum, ideally multiple), card readers, kitchen display screens, and backup devices. Initial hardware setup costs £1,500–3,500 depending on your venue size. Annual hardware replacement and repairs add £400–800. This is factored into calculations by smart operators but often missed in initial ROI discussions.

Payment Processing Fees

Square’s card processing at 1.75% + 20p per transaction. On a pub doing £3,000 in card sales per week, this totals roughly £2,730 annually in card fees alone. This is non-negotiable with Lavu.

Training and Setup Time

The real cost of an EPOS system is not the monthly fee but the staff training time and the lost sales during the first two weeks of use. Lavu requires staff to learn tablet navigation, tab management, and kitchen screen workflows. For a pub with 17 staff with varying technical comfort, budget two to three weeks of slower service and training intensity. That costs you real money in lost productivity and potential errors.

Total Year One Cost Estimate

Software (£100 × 12) = £1,200. Hardware (average) = £2,000. Processing fees (estimated) = £2,730. Training and setup (lost time value) = £1,500–2,500. Total: approximately £7,400–8,900 in year one. Years two onwards drop to roughly £4,600–5,400 (software + fees + maintenance).

When testing your investment case, use your actual transaction volumes with a pub drink pricing calculator to model margin impact of payment fees, and compare ROI against your current till cost and time spent on manual processes.

When Lavu Makes Sense (And When It Doesn’t)

Lavu Works Well If You Have:

• Reliable, fast broadband with backup connectivity (4G hotspot)
• A food operation where kitchen display screens add genuine speed and accuracy
• Table service or mixed service (not pure stand-at-bar trading)
• Staff who are comfortable with tablet-based systems and troubleshooting
• Approval from your pubco (if you’re tied)
• Low reliance on cellar management or specialty inventory tracking

Lavu Is Risky If You Have:

• Patchy or unstable internet — the system becomes unreliable
• A wet-led only operation with no food service
• Complex cellar management needs or cask ale rotation
• Staff resistance to technology or low digital literacy
• Requirement for pubco-integrated systems (check first)
• High reliance on cash payments and offline resilience

For most traditional UK pubs, Lavu is a compromise solution — not purpose-built for your needs, but functional if your internet is solid and you have food to justify the kitchen screen investment. Systems designed specifically for UK hospitality like Zonal, Tevalis, or other pub-focused EPOS providers typically handle bar workflows, cellar management, and offline resilience better. But if you already use Square for payments and want a simple, cloud-based system with good reporting, Lavu is worth a trial.

The decision should not be based on price alone. Test it during a trial period with a real Saturday night, full staff, and your actual payment mix. If the system performs smoothly and your team adopts it quickly, the cost becomes justifiable. If you see slowdowns or struggle with training adoption, cut your losses early and test alternatives.

Integration With Existing Pub Systems

One area where Lavu has improved in 2026 is third-party API support. If you’re already using pub management software for scheduling, finance, or operations, check Lavu’s integration marketplace before committing. Some bridges exist, but they’re typically built by third parties, not Lavu itself.

For pub IT solutions that require deep integration — like syncing staff schedules, bar stock, or accounting data — Lavu’s approach is to offer APIs and let you use middleware tools like Zapier. This works, but it adds complexity and cost.

Compare this to dedicated pub EPOS systems where cellar management, scheduling, and accounting sync are built in from day one. The difference in setup time and long-term maintenance is significant.