Lavu POS for UK pubs: Does it actually work?

Last updated: 11 April 2026

Most EPOS comparisons you’ll read are written by people who have never managed a bar on a Saturday night when the card machine crashes and you’ve got a queue out the door. Lavu POS is cloud-based, affordable, and technically impressive on paper — but cloud-based systems have a completely different set of failure modes than traditional tills, and that’s what actually matters when you’re trading. This review is based on real-world testing and operator feedback, not vendor demos. You’ll learn whether Lavu is genuinely suitable for a UK pub, what actually happens when your internet fails, and how its costs stack up against the switching time you’ll lose in week one.

What is Lavu POS?

Lavu is a cloud-based point of sale system designed for food and beverage venues. It’s iPad-based, which means you’re using tablets instead of traditional fixed terminals, and everything is stored in the cloud rather than on an on-premises server. The system was originally built for restaurants in the US and has expanded to international markets including the UK.

The headline appeal is straightforward: cloud systems promise lower upfront costs, easier updates, and access from anywhere. You’re not buying expensive hardware. You’re paying a monthly subscription. The Lavu dashboard shows sales data in real time, and technically you can view it from your phone. For a restaurant doing table service with iPad ordering, that’s genuinely useful. For a wet-led pub, the picture is more complicated.

Lavu positions itself as an alternative to traditional pub EPOS systems like Eposnow or Tevalis, but that’s misleading. It’s built on a different architecture with different assumptions about how you operate. Understanding that distinction is critical before you consider switching.

Performance During Peak Trading

The real test of any EPOS system isn’t how it performs during a quiet Tuesday afternoon — it’s Saturday night with a full house. When I was evaluating systems for Teal Farm Pub in Washington, Tyne & Wear, we deliberately tested each system under genuine peak conditions: a packed bar, multiple staff hitting terminals simultaneously, card-only payments running through, kitchen tickets printing, and tabs being settled all at the same time. That’s when you see which systems are genuinely built for a pub and which are pretending to be.

Lavu’s cloud architecture means every transaction, every inventory update, and every terminal command travels across your internet connection. On a fast, stable connection with good bandwidth, that’s not a problem. But pub WiFi rarely meets those conditions. Most pubs have WiFi designed for punters scrolling social media between rounds, not 17 staff processing 200 transactions per hour.

The critical weakness during peak trading is lag. Multiple staff trying to process payments simultaneously can cause noticeable delays at the terminal. It’s not a complete failure, but when you’ve got a queue and three bar staff are trying to close bills, even a two-second lag per transaction is multiplied across dozens of payments. That’s lost throughput and frustrated customers.

Additionally, Lavu’s iPad interface, while intuitive, isn’t optimised for speed in a high-volume bar environment. A traditional pub till with dedicated buttons for common items (pint of bitter, vodka and coke, etc.) will always be faster than navigating a touchscreen menu. If you’re shifting 200+ drinks per hour, that difference compounds.

Real Costs: What You’ll Actually Pay

Lavu’s pricing is transparent on the surface but deceptive in practice. The monthly subscription typically ranges from £39 to £89 depending on features, plus payment processing fees (usually 1.5–2.2% per transaction for card payments). Hardware is extra — iPad, receipt printer, card reader, stand — easily adding £800–£1,500 upfront.

But here’s what actually costs you money: the first two weeks after go-live. Your staff don’t know the system. Orders take longer to process. Mistakes happen more frequently. You’ll need someone senior on shift to troubleshoot. You’ll lose revenue because throughput drops. You’ll also lose sales because customers don’t like waiting for staff to figure out how to ring up a round of drinks.

When you’re calculating whether to switch from your current till, don’t just look at the Lavu monthly fee. Use a pub profit margin calculator to estimate what a 10–15% revenue drop over two weeks actually costs you in lost profit. Then calculate pub staffing cost calculator for the extra hours senior staff will need to spend learning and coaching. That’s the real financial picture.

On the positive side, once staff are trained, Lavu’s cloud dashboard does genuinely save time on reporting. You can see sales broken down by product, time period, and staff member without manually exporting data. That’s valuable. But it’s not valuable enough to offset a bad peak trading experience.

Integration Problems You Need to Know

Most EPOS systems worth their salt integrate with accounting software, stock management, and third-party services. Lavu has integrations, but they’re limited and often incomplete.

QuickBooks integration exists but requires manual setup and doesn’t automatically sync inventory adjustments. If you’re using EPOS QuickBooks integration for UK hospitality, you’ll find Lavu’s version is surface-level. You can export sales data, but cellar management — the live stock count that actually matters in a pub — doesn’t sync in real time. That means you’re still doing manual stock counts, which defeats one of the main reasons to switch EPOS systems.

If you use third-party booking or loyalty systems, check compatibility before committing. Many UK pub loyalty platforms (particularly those used by tied houses) have limited Lavu support.

Additionally, if your pubco (if you’re a tied tenant) has mandated a specific EPOS system or requires certain features for compliance, Lavu might not qualify. This is a common blocker that catches people by surprise.

What Happens When the Internet Goes Down

This is the question that separates operators who understand their own business from those who don’t. Every pub landlord should ask it of any cloud-based system: What happens to my till when the WiFi fails?

Lavu has offline functionality, but it’s limited. The iPad can continue taking orders and storing them locally for a short period — typically a few hours depending on device storage. But payment processing requires an internet connection. You cannot take card payments offline. If your connection drops during a Saturday night, you can take cash payments only. That’s a real revenue problem if you’re running a card-heavy venue.

Most wet-led pubs in 2026 process 60–80% of transactions by card. If your connection fails for even 30 minutes on a busy night, you’ve either stopped trading or you’re forced to only accept cash. That’s not a minor inconvenience — it’s a business continuity risk.

A traditional on-premises EPOS system doesn’t have this problem. The till works regardless of internet connectivity because the whole system runs locally. This is one of the genuinely valid reasons older operators still prefer traditional systems, and Lavu’s cloud architecture can’t overcome it.

Tied Pub Tenants: Check Pubco Compatibility First

If you’re a tied pub tenant (which covers roughly 40% of UK pubs), you don’t have complete freedom to choose your EPOS system. Your pubco agreement may mandate specific systems or require pre-approval before you install anything.

Before you seriously consider Lavu, contact your pubco directly and ask: Is Lavu POS approved for our tenancy agreement? Don’t assume it is. Some pubcos have negotiated preferential rates with specific EPOS vendors. Some have compliance requirements around payment processing that limit which systems you can use. Some have direct integration requirements with their own accounting systems that Lavu doesn’t meet.

I’ve seen operators waste time and money evaluating systems only to discover they weren’t contractually permitted to use them. That’s not a Lavu problem — it’s a tied tenancy problem — but it’s a real blocker you need to clear before even starting a trial.

The Honest Assessment: Is Lavu Right for Your Pub?

Lavu works well for casual dining restaurants with iPad ordering, where customers are seated and willing to wait a few extra seconds for orders to be processed. The cloud dashboard is intuitive. The support is reasonable. The initial cost looks attractive.

For a wet-led pub with high-volume card transactions, a small team working behind a busy bar, and the need for rock-solid offline capability? Lavu is not the best choice.

You should consider Lavu if:

• You’re already using Square or Toast and want a similar cloud-based philosophy
• You’re food-led (more than 40% of sales from kitchen) with table service
• Your pub operates quiet to moderate trading levels (under 100 covers or 150 drinks per night)
• You have fast, stable WiFi and reliable broadband backup
• You’re willing to invest time in staff training and accept a temporary dip in service speed

You should look elsewhere if:

• You’re wet-led (primarily draught and spirits, minimal food)
• Your pub is busy (regular Friday/Saturday nights with 300+ transactions)
• You have unreliable WiFi or live in an area with patchy broadband
• Your pubco has mandated a specific EPOS system
• You need real-time inventory sync with your cellar management

For context on what you actually need, explore whether UK pubs really need EPOS systems and pub IT solutions guide to understand your broader infrastructure requirements.

For more information, visit pub drink pricing calculator.

For more information, visit pub staffing cost calculator.