When to Outsource Pub IT — and When to DIY


When to Outsource Pub IT — and When to DIY

Written by Shaun Mcmanus
Pub licensee at Teal Farm Pub Washington NE38. Marston’s CRP. 5-star EHO. NSF audit passed March 2026. 180 covers. 15+ years hospitality.

Last updated: 23 April 2026

Running this problem at your pub?

Here's the system I use at The Teal Farm to fix it — real-time labour %, cash position, and VAT liability in one dashboard. 30-minute setup. £97 once, no monthly fees.

Get Pub Command Centre — £97 →

No monthly fees. 30-day money-back guarantee. Built by a working pub landlord.

Most pub operators treat IT as a cost problem instead of a revenue opportunity — and that mistake costs them thousands a year in lost data, downtime, and wasted labour on tasks that should be automated.

The real question isn’t whether you can afford to outsource pub IT services. It’s whether you can afford not to. Your EPOS system, payment processor, staff rotas, and customer data are not sideline operations — they are the operating system of your business.

When I evaluated best pub EPOS systems guide for Teal Farm, I wasn’t just looking at monthly costs. I was looking at the total operational cost: staff training time, the two-week productivity dip, compliance risk if payment processors aren’t configured correctly, and the revenue lost during every hour of downtime. That real-world pressure is what separates a sound IT decision from a cost-cutting mistake.

This guide tells you exactly which IT services are worth outsourcing, which you can handle yourself, and how to spot the false economies that will hurt you later.

Key Takeaways

  • EPOS setup, payment processor integration, and cybersecurity must always be outsourced — the cost of failure is higher than the cost of expertise.
  • Staff training and day-to-day IT support can be handled in-house if you have time, but this is a false economy for most licensees managing 150+ covers.
  • Pubco payment processor compatibility is a tenancy contract issue — verify this before signing any EPOS contract to avoid breaching your terms.
  • The real cost of EPOS is not the monthly fee but the lost revenue during the first two weeks of use and the staff training burden; plan for this upfront.
  • Wet-led pubs and food-led pubs have completely different IT requirements — most generic IT providers miss this distinction entirely.

The Hidden Cost of “Cheap” IT Decisions

Most pub operators calculate IT costs only as the monthly fee. The real cost is measured in lost sales, staff frustration, and compliance risk.

I’ve worked with licensees who chose “free” EPOS systems or knocked together a support team from friends with IT experience. On paper, they saved money. In practice, they paid for it in downtime during peak trading, staff confusion on busy nights, and the nightmare of extracting their data when the system finally failed.

Consider a Saturday night at capacity. Three staff are processing card-only payments, kitchen tickets are printing to multiple stations, and bar tabs are running simultaneously. Your EPOS system needs to handle that load without lag. It needs to process payments through your pubco-approved processor without errors. It needs to log every transaction for VAT and EHO compliance.

Most systems that look good in a quiet demo struggle when real pressure hits. That’s not a software problem — it’s an integration problem. And integration problems are not DIY.

The operators who understand IT cost know this: you’re not paying for the software licence or the hardware. You’re paying for the expertise that keeps your system standing when everything goes wrong on a Friday night at 10pm, with a full house, and three payment terminals hitting the same network.

EPOS and Payment Systems: Always Outsource Setup and Integration

Do not attempt to set up EPOS integration yourself, even if you have technical experience. The cost of a misconfigured payment processor is higher than any outsourcing fee.

Here’s what I learned when we switched systems at Teal Farm: EPOS setup looks straightforward in the vendor’s documentation. You connect the hardware, install the software, pair the card terminal, log in. But the real setup involves seven different moving parts:

  • Configuring payment processor integration (if your pubco requires a specific one, this is non-negotiable)
  • Mapping your menu categories and departments to match your wet/dry/food workflow
  • Setting up staff permissions and password protocols
  • Testing concurrent user load during peak trading (most systems fail here)
  • Backing up your old data and verifying historical transaction logs are retrievable
  • Training staff on the new system without losing a night’s service
  • VAT and settlement reconciliation between your old and new system

One misconfiguration — say, the payment processor isn’t aligned with your pubco’s approved gateway — and you’ve breached your tenancy agreement. You’ve also created a compliance gap where transactions aren’t recorded correctly for settlement. That’s not a mistake you recover from with a phone call.

Outsource this to the EPOS vendor’s implementation team. Yes, it costs extra. A proper implementation with staff training typically runs £800–£1,500. But that cost buys you the certainty that your system will work on day one, that your payment processor is pubco-compatible, and that your staff know how to use it without improvisation.

One detail most comparison sites miss: wet-led pubs have completely different EPOS requirements to food-led pubs. A wet-led operation needs speed, tab management, and rapid payment processing. A food-led operation needs kitchen ticket routing, prep time tracking, and table management. If your implementation team doesn’t understand the difference, your system will be cumbersome and slow.

When evaluating EPOS options, ensure the vendor’s implementation team has experience with pub operations — not just generic hospitality. Ask specifically how they handle tied tenant payment processor restrictions. Most generic hospitality providers will not even know this is a question.

Cybersecurity and PCI Compliance: Non-Negotiable Outsourcing

Cybersecurity and PCI compliance are not cost centres — they are existential risks. Never DIY this. The regulatory and legal liability far exceeds any outsourcing cost.

Your EPOS system, payment processor, and staff data are targets for cybercriminals. If your payment system is compromised, you’re liable for the breach. If customer data is stolen, you’re liable for notification, remediation, and potential fines from the Information Commissioner’s Office.

PCI DSS compliance (Payment Card Industry Data Security Standard) is mandatory if you process card payments. It’s also complex. It requires network segmentation, encryption, regular security audits, and staff training on data handling. A misconfiguration exposes you to massive liability.

Here’s what outsourcing cybersecurity actually means:

  • Your EPOS vendor handles PCI DSS compliance on their platform and hardware
  • Your payment processor handles encrypted transmission of card data
  • You handle policies: staff training on password security, data handling procedures, breach reporting
  • A third-party security audit verifies the entire chain is compliant

The cost? A security audit runs £400–£800. Annual PCI compliance verification might cost another £200–£500. This is not expensive. The cost of a data breach — legal fees, fines, and lost customer trust — is catastrophic.

One detail that matters for tied tenants: your pubco’s payment processor and security requirements are written into your tenancy agreement. Before signing any EPOS contract, verify that the system integrates with your pubco’s approved processor. If it doesn’t, you’re not just buying incompatible software — you’re potentially breaching your lease.

Staff Training and Change Management: Keep This In-House

Staff training should be delivered by someone your team knows and trusts. External training costs more, takes longer, and staff retention of the training is lower.

This is where I diverge from the “outsource everything IT” advice you’ll read elsewhere. Staff training is not a technical problem — it’s a culture and confidence problem. Your team needs to see that the new system makes their job easier, not harder. They need to practice on a quiet night before they use it during service.

Most EPOS vendors offer 2–4 hours of training included in their implementation fee. Take it. But don’t stop there. Assign one staff member as your “EPOS lead” — someone who gets extra training, understands the system deeply, and becomes the go-to person when someone is stuck at the bar during service.

At Teal Farm, I did this myself for the first two weeks. I was on the till during every shift, solving problems in real time, and showing staff confidence that the system was reliable. That hands-on training cut our productivity dip from the typical two weeks to about five days. Most of the remaining time wasn’t learning the EPOS — it was staff developing the muscle memory to use it quickly.

Do not hire an external consultant to train your staff for ongoing support. This is waste money. What you need is someone on your payroll who understands the system well enough to answer questions and troubleshoot basic problems. That person should be trained by the vendor during implementation, then trained by you on your pub’s specific workflow.

Ongoing Support and Maintenance: The Real Costs

This is where the cost-benefit math becomes clear. Ongoing IT support comes in three tiers:

Tier 1: Phone support from the vendor (included in most EPOS contracts, or £50–£150/month)

This handles: software bugs, system crashes, integration issues, payment processor errors. Response time is typically 4–24 hours depending on severity. You cannot DIY this — if your payment system crashes on a Friday night, you need someone on call, not a friend.

Tier 2: Hardware maintenance and network support (£100–£300/month depending on terminal count)

This covers: hardware repairs, router/network diagnostics, backup internet connectivity, firmware updates. If your router fails on a busy night and kills your EPOS connection, a technician needs to troubleshoot or replace it within hours. You cannot DIY this.

Tier 3: Proactive monitoring and security updates (£50–£200/month)

This covers: monitoring your system for issues before they affect you, applying security patches, backing up your data, alerting you to unusual activity. This tier prevents problems instead of solving them. It’s the most cost-effective support tier, but it’s invisible — you only notice it when something would have gone wrong and doesn’t.

Total monthly support cost: £200–£650 depending on your system complexity and uptime requirements. This is not optional. The cost of 4 hours of downtime on a busy night — lost sales plus staff overtime — usually exceeds one month of support fees.

When evaluating outsourcing costs, use a pub profit margin calculator to understand your actual break-even. If your profit margin is 20%, and you lose £500 in sales during a 4-hour downtime, you’ve lost £100 in profit. A month of support costs £400. It takes four downtime incidents to break even. How many incidents will you have in a year if you don’t invest in support? For most pubs, it’s more than four.

Pubco Compliance and Payment Processor Compatibility: The Contract Minefield

Pubco-compatible EPOS systems and payment processor integration is not a technical detail — it’s a contractual obligation written into your tenancy agreement. Verify this before you sign any EPOS contract.

This is the most critical detail that generic IT comparison sites miss entirely. If you’re a tied tenant (Marston’s, Star Pubs, Heineken, Admiral, Punch, Stonegate, etc.), your pubco requires you to use an approved payment processor. They also have approved EPOS systems that integrate with that processor.

If you buy an EPOS system that doesn’t integrate with your pubco’s processor, you’ve created a compliance breach. Your pubco can fine you, refuse to honour your contract, or require you to switch systems immediately — at your cost, not theirs.

Here’s what outsourcing does for you in this context:

  • A reputable EPOS vendor verifies pubco compatibility before you sign
  • The vendor’s implementation team configures your payment processor integration correctly, with written confirmation from your pubco
  • You have a contractual guarantee that the system is compliant with your tenancy agreement
  • If something goes wrong during setup, the vendor is liable — not you

If you try to DIY this or work with a generic IT provider who doesn’t understand pub tenancy agreements, you risk installing an incompatible system. Then you’re forced to pay for a replacement out of pocket.

Before selecting any EPOS system, contact your pubco directly and ask: “Which EPOS systems and payment processors are approved under my tenancy?” Get the answer in writing. Then verify that your chosen system integrates with those approved options. Do not proceed to implementation until you have written confirmation from both your pubco and your EPOS vendor that the setup is compliant.

This single step — outsourcing the verification and integration to someone who knows pub tenancy requirements — saves you thousands and prevents legal risk.

Frequently Asked Questions

Should I outsource EPOS setup if my pubco has already approved a system?

Yes. Approval is not the same as configuration. Your pubco has approved the system in general, but your specific payment processor integration, menu structure, and staff permissions still need to be configured correctly. A misconfiguration during setup can create compliance gaps that don’t show up until your first settlement report fails. Outsource the implementation to the vendor’s team — it costs £800–£1,500 but prevents thousands in rework costs.

Can I train my staff on EPOS myself instead of paying for vendor training?

Partially. Vendor training covers technical setup and system features — this is worth paying for. Your follow-up training, reinforcement, and muscle-memory building should be done in-house by you or an EPOS-trained staff member. This keeps training cost-effective and ensures staff confidence. Plan for a 2–5 day productivity dip when you switch systems, regardless of training quality.

What’s the minimum monthly IT support cost I should expect?

For a single-site pub with one or two EPOS terminals, budget £150–£300/month for reliable vendor support covering phone support, hardware maintenance, and basic monitoring. This typically includes 24-hour emergency response and periodic security updates. Below this price point, you’re likely getting reactive support only — they only help after something breaks, not before.

Is cybersecurity really necessary for a small wet-led pub?

Absolutely. If you process card payments, you are legally required to maintain PCI compliance. The cost of compliance (regular security audits, staff training, encryption) is £400–£800 per year. The cost of a data breach (legal fees, fines, remediation, reputational damage) is £50,000+. Cybersecurity is mandatory, not optional, regardless of your size.

How do I verify that my chosen EPOS system is compatible with my pubco’s payment processor?

Contact your pubco’s operations team directly and ask for a list of approved EPOS systems and payment processors. Get this in writing. Then ask your EPOS vendor: “Does this system integrate with [pubco name] approved processors [list]?” Get written confirmation from the vendor that they have successfully implemented this configuration for other tenants. Do not proceed until you have confirmation from both parties in writing.

You now know which IT services to outsource and which you can handle in-house — but knowing what to outsource is only half the problem. You also need to know if you’re actually making money from all that outsourced support.

Your EPOS tells you what sold. Pub Command Centre tells you whether you made money — real-time labour %, VAT liability and cash position. £97 once, no monthly fees.

For more information, visit retail partner earnings calculator.



Leave a Reply

Your email address will not be published. Required fields are marked *