EPOS contract terms: what UK pub landlords must know

Last updated: 11 April 2026

Most pub landlords sign an EPOS contract without reading past the monthly fee. That’s the mistake that costs thousands. The real expense isn’t what you pay each month — it’s what you’re locked into when the system underperforms, your supplier goes quiet, or you need to switch providers. I’ve managed 17 staff across front-of-house and kitchen operations at Teal Farm Pub in Washington, Tyne & Wear, and I’ve seen systems that looked perfect in the sales demo grind to a halt on a Saturday night with three staff hitting the same terminal during last orders. That’s when you discover your contract has a three-year minimum term and a £2,000 exit fee.

This guide covers the contract terms that actually matter, the clauses vendors hope you’ll miss, and what to negotiate before you sign. If you’re running a wet-led pub, a food-led venue, or a tied house under a pubco, the rules change — and your contract needs to reflect that.

Minimum Term and Lock-In Periods

The most critical contract term you’ll negotiate is the minimum commitment period. This is the length of time you’re legally bound to the contract, regardless of whether the system works for your pub or not. In 2026, UK EPOS providers typically offer three options: month-to-month (rare and expensive), 12-month minimum, or 24–36 month minimum with a discount applied.

On paper, a 36-month term looks cheaper per month. The maths feel obvious. But here’s what actually happens: you’re locked in for three years. If the software doesn’t integrate with your cellar management, if the staff find it slow during peak service, or if the vendor stops supporting your hardware version, you’re still paying. A month-to-month contract costs more upfront but gives you flexibility. That flexibility is worth something.

What to negotiate: Push for a 12-month minimum with a break clause after month 6. This gives the vendor confidence you’re committed to the trial period (because most EPOS systems need 4–8 weeks to deliver real value as your team learns the workflow), but it protects you if the system genuinely isn’t fit for purpose. If the vendor won’t budge on a 12-month term, ask for a performance-based exit option — if system uptime falls below 99% in any calendar month, you can terminate without penalty.

Tied pub tenants need to add another layer here: check your tenancy agreement for any restrictions on EPOS supplier choices. Some pubcos (like Marston’s) have approved supplier lists, and signing a contract with an unapproved provider could technically breach your lease. Verify this before you commit to a three-year contract.

Break Clauses and Exit Fees

A break clause is your escape route. It’s the contractual right to exit the agreement before the minimum term ends, usually by paying a penalty or providing notice. The strength of your break clause determines whether you’re actually locked in or just committed to a trial period.

Common break clause structures in UK EPOS contracts:

• Annual break clause: You can exit on any anniversary of the contract start date, usually with 30–90 days’ notice. This is industry standard and worth asking for even on longer contracts.
• Performance-based break clause: You can exit if the system fails to meet uptime, feature, or integration standards defined in the contract. This is rarer but negotiable.
• No break clause (locked term): You pay the full contract value regardless of circumstances. This is what vendors prefer and what you should avoid.
• Early termination fees: If there’s no break clause, you’ll pay a penalty to leave early. This is often calculated as the remaining contract value or a percentage of it.

The exit fee matters more than the monthly subscription. I’ve seen contracts where the break clause exists but the penalty is 80% of the remaining contract value — which means it’s useless. A three-year contract at £150 per month with an 80% early termination fee means you’d pay £4,320 to exit after year one. That’s not an escape route; that’s a trap.

What to negotiate: Insist on an annual break clause with 30 days’ notice and zero early termination fees. If the vendor won’t agree, ask for a tiered approach: 50% penalty in year one, 25% in year two, zero in year three. This aligns their incentive with yours — they need to deliver value to keep you, not just lock you in.

Request a written statement of what happens if you invoke the break clause: Do they deactivate your system immediately? Do you get access to your data? How long do you have to migrate to a new provider? These details matter operationally.

Payment Terms and Hidden Costs

The monthly fee you see advertised is rarely the total cost. Hidden costs compound quickly, and most landlords don’t discover them until month two when they get invoiced for training, hardware, PCI compliance, or support add-ons.

Costs to budget for in your EPOS contract:

• Setup and installation: £200–£800 depending on terminal quantity and venue complexity. Venues with kitchen displays or wireless terminals cost more.
• Hardware (if not included): Terminals, card readers, receipt printers, and kitchen screens. Budget £1,500–£4,000 upfront depending on your pub size. When I evaluated systems for Teal Farm Pub, hardware cost was often higher than six months of subscription fees — most comparison sites ignore this entirely.
• Staff training: First-level training is usually included; additional training sessions cost £50–£150 per hour. If you have high staff turnover, this adds up fast.
• PCI DSS compliance: If your system processes card payments, you’ll need PCI compliance certification. Some vendors charge £100–£300 annually for this; others build it into the fee.
• Data backup and cloud storage: Usually included but check the contract. If your data is stored on-premise, you’re responsible for backup costs.
• Support tier upgrades: Standard support is often email-only with 24–48 hour response times. Priority phone support costs £50–£150 monthly extra.
• Payment processing fees: Some contracts bundle card processing (typically 1.5–2.5% per transaction). Others let you choose your processor. Check which model applies.

Use a pub profit margin calculator to model the real cost impact. A £150 monthly EPOS fee seems manageable until you add £1,500 hardware, £500 training, and £100 monthly support — that’s £2,500 in the first month and £250 every month after. For a small wet-led pub with £8,000 monthly turnover, that’s a 3% cost overhead.

What to negotiate: Ask for all costs to be itemised in the contract, including what’s included in the monthly fee and what’s charged separately. Request that hardware is either included in a three-year contract or sold separately at a discounted rate. Negotiate a cap on training costs (e.g., “unlimited training for the first three months, then £50 per session after”).

Payment terms matter too. Ask whether you can pay quarterly or annually to get a discount, or whether you’re locked into monthly payments. Some vendors offer 10–15% discounts for annual prepayment, which improves your cash flow predictability.

Support, SLA and Downtime Liability

Service level agreements (SLAs) define what happens when your EPOS system fails. They specify response times, uptime guarantees, and what compensation you get if the system is down during trading hours. Most pub landlords don’t read them, and that’s why they end up losing £500 in unrung sales on a Friday night with no recourse.

In 2026, standard EPOS SLAs for UK pubs typically offer:

• 99% uptime guarantee: The system should be available 99% of the time (about 7 hours of downtime per month). This sounds good but isn’t specific about when downtime happens. Downtime at 2 a.m. Tuesday is different from downtime at 8 p.m. Friday.
• Phone support response time: 4–24 hours depending on the tier. Budget vendors offer email support only.
• Hardware replacement: If a terminal fails, the vendor sends a replacement. Shipping typically takes 1–3 days.
• No liability clause for data loss or downtime. This is the dangerous bit. Most contracts explicitly state that the vendor is not liable for your lost sales, staff hours, or other indirect costs caused by system failure.

What actually matters in a real pub: On a Saturday night at Teal Farm Pub, three staff are using the same EPOS terminal. If that terminal goes down, you can’t ring sales, run tabs, or print kitchen tickets. You lose revenue immediately. But most standard SLAs don’t compensate you for that loss. They just promise to fix the hardware eventually.

What to negotiate: Push for an uptime guarantee that excludes scheduled maintenance windows. Request a credit against future fees if uptime falls below 99% in any month — typically 5–10% of that month’s fees per percentage point below the target. Ask for a workaround clause: if your terminal fails, can you use a backup system (tablet, mobile terminal, or temporary device) until the hardware is repaired? This keeps you trading.

Insist that the vendor specifies response times for critical issues (terminal failure, payment processing failure) separately from non-critical issues (cosmetic bugs, feature requests). Critical issues should have a 2–4 hour response time and same-day resolution target.

Ask whether the SLA covers internet outages. Many vendors exclude downtime caused by your ISP failing. If that’s the case, ensure your contract specifies offline mode capabilities — your EPOS should work without internet and sync when connection is restored. This is essential for pubs in rural areas or with unreliable broadband.

Tied Pub and Pubco Compatibility

If you’re a tied pub tenant (managed by Marston’s, Wetherspoons, Enterprise, or another pubco), your EPOS choice isn’t completely free. Most pubcos maintain approved supplier lists to ensure systems integrate with their back-office accounting, stock reporting, and rent/loan reconciliation systems.

Signing a contract with an unapproved EPOS provider can breach your tenancy agreement. You might discover this six months in, after you’ve invested in training and data migration. I’ve seen tied pub tenants discover mid-contract that their system can’t integrate with pubco stock reconciliation, forcing a costly switch.

Before signing any EPOS contract, tied pub tenants must:

• Request written confirmation from your pubco that the EPOS provider is approved.
• Ask the pubco for the list of approved providers and the technical requirements your system must meet.
• Request that the EPOS vendor provides written confirmation of compatibility with your pubco’s back-office systems.
• Include a clause in your EPOS contract stating that if the vendor’s integration with your pubco fails, you have the right to exit without penalty.

For independent pubs, this isn’t an issue. But if you’re operating under a pubco tenancy, skipping this step is expensive.

Data Ownership and Migration

Your transaction history, sales data, customer information, and stock records are yours. But many EPOS contracts don’t make this clear, and some vendors treat your data as leverage to keep you locked in.

When you decide to switch EPOS providers (whether you invoke a break clause or your contract ends naturally), you need to migrate your historical data cleanly. This includes:

• Sales transaction history (for tax records and year-end accounts)
• Customer loyalty or tab data (if applicable)
• Stock records and supplier information
• Staff records and performance data

What to ask for in your contract: Confirm that you own all data generated by your pub’s use of the EPOS system. Request a data export option that gives you access to your transaction history in a standard format (CSV, JSON, or XML) that a new provider can import. Ask whether this export is free or charged, and whether it’s available on request or only at contract end.

Specify that the vendor will not delete your data for 12 months after contract termination, giving you time to migrate to a new system. Request that the vendor provides a data dictionary (field definitions) so a new provider understands your data structure.

In 2026, GDPR compliance also matters here. Your contract should specify how the vendor handles personal data (staff details, customer payment information) and confirm that they’ll delete it on request or at contract end.

Critical Questions to Ask Before Signing

When a vendor sends you a contract, don’t sign it immediately. Ask these questions in writing and get written answers added to the contract:

• Is there an annual break clause? If not, what’s the early termination fee and how is it calculated?
• What is the complete total cost of ownership for year one (including setup, hardware, training, support)? And for years two and three?
• If our internet goes down, does the system work offline? How long can it operate offline before syncing is required?
• What’s your uptime guarantee, and what compensation do we receive if it’s not met?
• Can we export our transaction history at any time? What format and what does it cost?
• If we’re a tied pub, can you provide written confirmation that you’re approved by our pubco and compatible with their back-office systems?
• What happens if your company goes out of business? Do we get access to our data or the source code?
• Are there any automatic price increase clauses? If so, what’s the cap?

Get the answers in writing. Email exchanges count. Don’t rely on what the sales rep says in a call — verbal promises mean nothing if the contract doesn’t back them up.

Real-World Impact: What I Learned at Teal Farm Pub

When I was evaluating EPOS systems for Teal Farm Pub, I didn’t just look at the demo. I tested the system during a Saturday night with a full house — card-only payments, kitchen tickets, and bar tabs running simultaneously. That’s when the real contract terms mattered.

The vendor’s demo looked perfect. But when three staff were hitting the same terminal during last orders, the system slowed down. When I asked what happens if this continues, the vendor said they’d investigate. Their SLA response time was 24 hours. In a pub context, that’s useless — I’ve lost a whole night of revenue.

That’s when I realised the contract needed to specify offline mode as non-negotiable. If your system can’t work without the internet, and it slows down during peak hours, you need a fallback. I negotiated a clause that required the vendor to provide temporary mobile terminals if the main system failed for more than two hours during trading.

The contract also needed to reflect real pub operations. Wet-led pubs have completely different EPOS requirements to food-led pubs — most comparison sites miss this entirely. A wet-led pub doesn’t need sophisticated kitchen management, but it needs rock-solid payment processing and stock tracking because your turnover is pure cash and beer cost is your biggest margin. My contract negotiations focused on those specific needs.

The real cost of switching EPOS systems isn’t visible in your monthly bill — it’s hidden in retraining staff, recovering lost sales during the transition, and the time you spend managing a system that doesn’t fit your operation. That’s why the contract terms matter more than the price. A slightly more expensive system with a flexible contract is better than a cheap system that locks you in for three years.

Before you negotiate, you also need to understand whether renting or buying an EPOS system makes sense for your cash flow. That decision will affect which contract structures are available to you.

If you’re comparing different providers, pub IT solutions guide covers the technical requirements you should include in your contract negotiation. And if you’re managing the financial impact, your pub staffing cost calculator will show you how EPOS implementation costs affect your operational budget during the first two months.

For more information, visit pub profit margin calculator.

For more information, visit pub drink pricing calculator.

For more information, visit pub staffing cost calculator.