EPOS for Tied Pub Tenants: Payment, Compliance & Rights

Last updated: 23 April 2026

Most tied pub tenants assume they can install any EPOS system they want. They’re wrong. I’ve watched three pub operators in my area buy systems that looked perfect in the demo, only to discover mid-installation that their pubco payment processor wasn’t compatible—which technically breaches their tenancy agreement. One of them spent £3,000 ripping it out and starting again. That’s not a small problem for a wet-led pub running on tight margins.

The real issue isn’t the technology itself. It’s the invisible layer underneath: pubco approval, payment processor compatibility, and the specific trading patterns of tied pubs. These are things you won’t find in generic EPOS comparison articles, because most comparison sites don’t understand the difference between running an independent pub and running a tied pub on a pubco agreement.

When I evaluated EPOS systems for Teal Farm Pub—a 180-cover wet-led operation on Marston’s CRP serving Washington, Tyne & Wear—the critical test wasn’t how the system looked in a showroom. It was whether it could handle peak Saturday night: card-only payments, kitchen tickets, bar tabs, and quiz night entries running simultaneously, all while staying compatible with my pubco’s payment infrastructure. That real-world pressure test is what this guide is built on.

By the end of this article, you’ll understand the compliance rules tied tenants face, which payment processors actually work with your pubco, how to avoid costly mistakes, and what happens if you choose the wrong system. Most importantly, you’ll know your actual legal rights as a tenant.

Why Tied Pubs Need Different EPOS Rules

The fundamental difference between tied and independent pubs is payment infrastructure. When you run an independent pub, you choose your payment processor. When you run a tied pub, your pubco typically dictates which payment processors you can use, which ones integrate with their systems, and which ones they’ll actually support if something goes wrong.

This isn’t the case for food-led pubs alone—wet-led pubs have completely different EPOS requirements to food-led pubs, and most comparison sites miss this entirely. A wet-led pub like mine needs real-time cellar integration, stock tracking at pour level, and payment systems that work with rapid-fire card transactions during peak hours. Add the pubco layer on top, and you’re looking at a completely different set of constraints.

I’ve spoken to operators at other Marston’s CRP pubs, Admiral Taverns tenants, and Stonegate licensees. Every single one reports the same issue: they assumed their pubco would approve any modern EPOS system. Wrong. The real cost of choosing the wrong EPOS system isn’t just the monthly fee—it’s the cost of replacing it mid-contract.

At Teal Farm Pub, we serve Washington, Tyne & Wear with regular quiz nights, sports events, and food service across 180 covers. The system we chose had to handle all of that simultaneously while maintaining compatibility with Marston’s payment infrastructure. That’s a very specific requirement, and it eliminated about 40% of the systems that look good in a generic EPOS review.

Payment Processor Compatibility: The Hidden Gatekeeper

Here’s what most EPOS vendors won’t tell you upfront: their system might work beautifully with Stripe, Square, or PayPal in an independent pub. But if your pubco’s agreement mandates a specific payment processor—or requires all transactions to flow through their own gateway—then that shiny new system becomes a paperweight on your bar.

Payment processor compatibility is not a feature you can add later—it’s a prerequisite to installation. The payment processor is the layer between your EPOS terminal and the pub company’s financial system. If they don’t talk to each other, you can’t process transactions. Full stop.

Marston’s CRP pubs, for example, typically support Elavon or specific integrated gateways. Admiral Taverns tenants often have different requirements. Stonegate agreements sometimes mandate their own processor. I can’t speak for every pubco arrangement, because every tenancy agreement is different, but the pattern is consistent: your pubco controls which payment processors are compatible with their system, and they decide whether a new EPOS vendor is acceptable.

The mistake tied tenants make is asking the EPOS vendor “does your system work with my pubco?” instead of asking the EPOS vendor “what specific payment processors does your system integrate with, and can you confirm in writing that [your exact pubco payment processor] will work without any additional hardware or gateway changes?” These are not the same question.

When I was evaluating systems for Teal Farm Pub, I didn’t ask vendors if they “work with Marston’s.” I asked them which payment processors they integrate with, requested written confirmation that our specific payment gateway was supported, and then contacted Marston’s directly to verify that the system wouldn’t trigger any agreement violations. That’s the process. It takes time, but it’s worth every hour.

Pubco Approval: What You Actually Need in Writing

Your tenancy agreement almost certainly gives you the right to install your own EPOS system. But it also almost certainly includes conditions. Those conditions typically relate to payment processing, data security, and integration with the pubco’s reporting systems. You need to understand what those conditions are before you sign any EPOS contract.

Before you install any new EPOS system as a tied tenant, you must get written approval from your pubco that specifically confirms payment processor compatibility. Not a verbal thumbs-up from a depot manager. Written confirmation that addresses the exact system, the exact payment processor, and the exact integration method.

Most pubcos have a formal approval process. They might ask you to submit a technical specification sheet, confirm the payment processor details, and verify that the system meets their data security standards. This typically takes 2-4 weeks. Some pubcos are quicker. Some take longer. But the timeline doesn’t matter—what matters is that you have written confirmation before the equipment arrives.

The reason for this isn’t bureaucracy. It’s risk management. Your pubco’s financial system, reporting dashboards, and stock reconciliation process all depend on real-time data from your EPOS. If the system you install doesn’t integrate properly, or if the payment processor doesn’t sync correctly, the pubco’s back-office team can’t see what’s happening at your bar. That creates a compliance gap, which creates a breach, which technically gives the pubco grounds to challenge your tenancy or demand system removal.

I had a conversation with an operator at another location who installed a system without written approval. Six weeks in, the pubco’s compliance team noticed the payment processor wasn’t integrating properly with their reconciliation system. They gave him 48 hours to fix it or face a breach notice. The vendor couldn’t troubleshoot it fast enough. He ended up buying a completely different system. All because he skipped the approval step.

Real Costs Beyond the Monthly Fee

When most pub operators evaluate EPOS costs, they look at the monthly or annual fee. That’s the wrong number. The real cost of an EPOS system for tied pubs includes staff training, cellar integration, lost sales during transition, and potential contract lock-in—not just the monthly subscription.

Let’s be specific. At Teal Farm Pub, my labour cost averages 15% against the UK benchmark of 25-30%, because our systems are optimized and our staff know them inside out. But that didn’t happen overnight. The first two weeks of any new system are brutal. Staff are slower, mistakes happen, and you lose sales because people are waiting longer to be served. I estimate that cost at roughly £800-1,200 per week for a 180-cover pub, depending on how busy trading is.

Then there’s cellar management integration. If your new EPOS doesn’t integrate with your pubco’s cellar management system, you’re either manually reconciling stock every day (which adds 30-40 minutes of labour daily), or you’re buying a separate system and paying for two licenses. That integration alone can be worth £150-300 monthly in labour savings. If the EPOS vendor quotes you a system without cellar integration, ask why, and ask what the alternative is.

Finally, there’s the contract lock-in issue. Many EPOS vendors require 24-month contracts with early termination fees. If you commit to a system for 24 months, but you realize at month 4 that it’s not compatible with your pubco’s reporting system, you’re stuck paying for a system you can’t use while also buying something else. That’s a cost most tied tenants don’t account for until it happens.

When evaluating real EPOS costs, use a pub profit margin calculator to understand what your baseline profit looks like now, then model what changes to labour, cellar management, and training time might do to that margin with a new system. That’s the real cost picture.

Your Rights as a Tied Tenant Installing EPOS

Most tied pub tenancy agreements include a clause that gives you the right to choose your own EPOS system, provided you meet certain conditions. Those conditions almost always include: payment processor compatibility, data security standards, and integration with the pubco’s back-office systems. But beyond those requirements, you typically have the right to choose.

Your tenancy agreement is a legal contract that protects your right to run your pub efficiently—and that includes choosing fit-for-purpose systems. If your pubco is unreasonably blocking EPOS vendors that meet all their technical requirements, that’s potentially a breach of the agreement terms on their side. It’s rare, but it happens.

The key word is “reasonably.” A pubco can reasonably require that your EPOS integrates with their payment processor. They can’t reasonably require that you use one specific vendor that costs 50% more than alternatives. If you’re ever in a position where your pubco is blocking a system that meets all their technical requirements but they won’t explain why, that’s a conversation to have with your trade body representative or a solicitor who specializes in pub tenancies.

That said, most pubcos are reasonable. They’re not trying to block you from running an efficient pub. They’re trying to protect their financial system and their ability to reconcile your sales and stock. If you approach the approval process professionally—with technical specifications, written confirmation from the vendor, and a clear integration plan—most pubcos will approve a system within weeks.

The real risk comes when you install a system without approval and hope nobody notices. I’ve seen that go both ways. Sometimes nobody does notice, and the system works fine. Sometimes the pubco’s compliance team catches it at stock take, and you have a real problem. The risk isn’t worth it.

Practical EPOS Selection for Tied Pubs in 2026

If you’re shopping for an EPOS system as a tied tenant in 2026, here’s the process that actually works:

Step 1: Identify your pubco’s approved payment processors and technical requirements. Contact your pubco’s operations team and ask for a written list of approved payment processors and technical specifications that any EPOS system must meet. This usually includes security standards (PCI DSS compliance), real-time reporting capability, and integration with their back-office system. Write it down. You’ll need it.

Step 2: Shortlist EPOS systems that integrate with your approved payment processors. Don’t shortlist based on price, features, or vendor reputation. Shortlist based on payment processor compatibility. That eliminates 50% of the market immediately. Systems like ICRTouch, which has 25 years of reliability in UK pubs, integrate with multiple payment processors and are familiar to most major pubcos. Others like the systems in our best pub EPOS systems guide offer varying levels of compatibility—check each one carefully.

Step 3: Request written confirmation from the vendor. Ask each vendor on your shortlist to provide written confirmation that their system integrates with your specific approved payment processor, and that they’ve successfully integrated with that processor for other tied pub operators on your pubco. Get them to specify any additional hardware, gateway changes, or configuration required. This usually takes 48-72 hours.

Step 4: Submit for pubco approval with all technical documents. Don’t negotiate with the vendor until you’ve got pubco approval in writing. Send your pubco a formal request including: the EPOS vendor name and model, the payment processor they use, the vendor’s written confirmation of compatibility, and any other technical documents they’ve provided. Ask for written approval and a timeline. Allow 2-4 weeks.

Step 5: Plan your implementation timeline. Once you have pubco approval, plan your go-live for a quiet period if possible. Train staff thoroughly before go-live (budget 4-6 hours for core staff). Plan for reduced speed and increased errors for the first 2 weeks. Monitor the system closely during that period. Don’t announce new features to customers until you’re confident staff can deliver them.

I know this sounds like a lot of admin. It is. But it’s ten times less painful than installing a system that your pubco won’t approve, or discovering mid-trading that the payment processor doesn’t work properly. That’s a lesson I’ve learned from watching other operators, not from personal experience—because I did the steps above before I ever signed a contract.

SmartPubTools has 847 active users across the UK, many of them running tied pubs or multi-site operations. The pattern is consistent: operators who get pubco approval in writing before committing never regret it. Operators who skip the approval step and hope for the best almost always do.

For more information, visit pub profit margin calculator.

For more information, visit retail partner earnings calculator.

For more information, visit best pub EPOS systems guide.