Hotel PMS integration in the UK

Last updated: 11 April 2026

Most hotel operators still manually transfer guest bills from their restaurant EPOS to their property management system — a process that wastes time, introduces billing errors, and creates reconciliation headaches at the end of every shift. Hotel PMS integration in the UK is no longer a nice-to-have feature; it’s become essential for any hospitality venue operating multiple outlets and managing complex guest billing. Whether you run a country hotel with a pub, restaurant, and spa, or a town-centre establishment with bars and dining rooms, integrating your pub management software directly into your property management system eliminates the manual data entry that eats up staff time and creates audit trails that actually make sense.

This guide walks you through exactly how PMS integration works, what systems talk to each other in the UK hospitality market, the real costs involved, and the practical setup questions you need to answer before you commit to any integration project.

What is hotel PMS integration and how does it work?

Hotel PMS integration connects your point of sale system directly to your property management system via an API (application programming interface), so guest bills, room charges, and payment data flow automatically between the two systems without anyone manually re-entering information. The guest has a meal at your hotel restaurant, the waiter rings it through the EPOS, and moments later that charge appears on the guest’s folio in the PMS — ready to be added to their final bill.

Without integration, someone has to manually note the EPOS transactions, log into the PMS, find the right guest folio, and manually enter each charge. It sounds simple when you describe it once. In practice, across a busy weekend with a 120-cover restaurant, a spa, and a bar all running simultaneously, manual entry becomes a source of errors, missed charges, and angry guests at checkout who are billed for things twice (or not at all).

Integration works in one of two ways. Real-time integration sends data instantly as soon as a transaction is completed on the EPOS — this is the gold standard but requires both systems to support live API connections. Batch integration collects transactions throughout the shift and syncs them at set times (usually every 30 minutes or hourly) — it’s slightly less instant but more reliable in hotels with patchy WiFi or older PMS systems.

The three types of data that need to sync

• Guest billing: Food and beverage charges from your restaurant, bar, or room service need to post to the correct guest folio automatically.
• Payment reconciliation: If a guest pays cash at the EPOS for a meal, the PMS needs to know whether that payment should go to their folio or be recorded as a separate cash transaction.
• Outlet mapping: Your PMS needs to know which EPOS terminals belong to which outlets (restaurant, bar, spa, etc.) so charges are recorded against the right revenue centre.

Why PMS integration matters for multi-outlet hotels

I’ve personally managed pub staffing cost calculator scenarios across 17 staff in FOH and kitchen environments where a single EPOS system was running a fast-moving venue with quiz nights and event evenings. In a hotel environment, the complexity multiplies because you’re not just managing one bar — you’re managing a restaurant, possibly a spa, room service, and a hotel bar, all charging to different guest folios, and all needing to reconcile at the end of the night.

The cost of not having integration isn’t the monthly software fee — it’s the three hours a night your night manager spends manually matching EPOS tills to guest folios. It’s the missed revenue when a room service charge doesn’t make it onto the final bill. It’s the guest complaints at checkout because they were billed twice for a meal. It’s the audit trail that doesn’t exist because nobody documented which staff member entered which transaction.

The most effective way to reduce hotel revenue leakage and staff time spent on manual billing is to implement direct PMS integration, which eliminates manual data entry and creates an automatic audit trail of every transaction linked to a specific guest. Hotels using integrated systems report that they spend less time investigating guest disputes because every transaction is timestamped, mapped to a specific server or outlet, and permanently linked to the guest’s folio.

Multi-outlet hotels face specific challenges

A traditional pub or restaurant runs a single EPOS system capturing all sales in one place. A hotel with a restaurant, bar, spa treatment room, and room service needs multiple EPOS terminals or multiple systems, all feeding into one PMS. This creates a coordination problem:

• Your restaurant EPOS is on one terminal, your bar EPOS on another — they might even be different systems entirely.
• Each outlet has different payment workflows (the spa might take advance bookings, the restaurant expects payment at table).
• End-of-service reconciliation becomes a nightmare if you have to manually audit three or four different EPOS systems against guest folios.
• Your accounting system needs to pull revenue data from multiple outlets but also needs guest-level detail — manual processes create data silos.

PMS integration solves these problems by creating a single data source of truth. Every transaction from every outlet flows into the PMS, mapped to the correct guest, with a permanent audit trail.

Which EPOS and PMS systems integrate in the UK

Not every EPOS system integrates with every PMS. This is one of the most common mistakes UK hoteliers make — they buy an EPOS system because it’s cheap or they like the interface, only to discover later that it doesn’t integrate with their Fidelio, Micros, or Opera PMS, and they’re stuck doing manual entry anyway.

Before you commit to any EPOS or PMS system, verify that integration is actually possible. Check directly with both vendors. A “we can probably integrate” from a salesman is not the same as a documented, tested API integration with real implementation costs and timelines.

Major UK hotel PMS systems and EPOS integration support

• Oracle Micros / Opera: Market-leading PMS with broad EPOS integration. Most modern EPOS systems integrate with Micros via their open API. If you’re on Micros, integration options are relatively straightforward.
• Fidelio (Sabre): Common in mid-market UK hotels. Integration is possible but often requires custom development — budget accordingly.
• Nightfall: Popular in independent UK hotels. Has documented EPOS integrations but fewer off-the-shelf options than Micros.
• Amadeus / Hospitality: Used in larger hotel chains. Integration capability depends on your specific version and whether you’re using cloud or on-premises deployment.
• MarginEdge and other cloud-based PMS platforms: Newer platforms often have better API documentation and faster integration timelines, but smaller feature set for complex multi-outlet scenarios.

On the EPOS side, systems like Lightspeed, Kobas, and Tillpoint all support integration with major hotel PMS platforms. The real question is whether your specific EPOS version talks to your specific PMS version — this is where it gets technical.

How to set up PMS integration step by step

Implementation isn’t complex once you understand the workflow, but it does require technical knowledge and careful planning. Here’s what the process actually looks like:

Step 1: Audit your current setup

Before you contact your vendors, document exactly what you’re running:

• Which PMS are you using, and what version? (This matters — an 8-year-old Micros system integrates differently than Micros Cloud)
• How many EPOS terminals do you have, and where are they located?
• Which EPOS system are you running now, or planning to install?
• Are your EPOS terminals networked (connected to WiFi or ethernet), or are they standalone?
• Who is your internet service provider, and what’s your uptime guarantee?

Step 2: Verify integration is technically possible

Ask your PMS vendor and EPOS vendor directly: “Do you have a documented API integration between your systems? Can you provide integration documentation, expected costs, and estimated setup time?” If they hedge or redirect you to a third-party integrator, budget extra for custom development.

Step 3: Map your outlet structure

Your PMS needs to know the difference between a charge from the restaurant EPOS and a charge from the bar EPOS. This requires careful outlet mapping:

• Decide how many revenue centres you need (most hotels have Restaurant, Bar, Room Service, Spa, Minibar — some have more).
• Assign each EPOS terminal to a revenue centre in your EPOS system.
• Create matching revenue centres in your PMS that will receive charges from each EPOS outlet.
• Document the mapping in a spreadsheet so your integration technician can configure the API correctly.

Step 4: Configure the API connection

The most effective way to configure PMS integration is to start with a test environment first — never go live directly in your production PMS with real guest data. Your integration technician (either from your PMS vendor, EPOS vendor, or a third-party integrator) will:

• Generate API credentials (a token or key that allows your EPOS to communicate with your PMS).
• Configure which data fields sync in which direction (EPOS to PMS, or bi-directional).
• Set up the frequency of sync (real-time, or batch every 30 minutes).
• Test with dummy transactions to make sure charges appear on test guest folios correctly.

Step 5: Staff training and go-live

Once testing is complete, you’re ready to go live. But don’t just switch it on during a busy Saturday night. Here’s what actually works:

• Go live during a quiet period — a Tuesday night, for example.
• Have your integration technician on standby for the first 48 hours.
• Brief all staff on the new workflow (charges should appear on guest folios automatically — they don’t need to do anything different).
• Have your night manager check reconciliation carefully for the first week to catch any mapping errors.

The real cost of PMS integration in 2026

Integration costs vary wildly depending on your systems and how much custom configuration is needed. Here’s what you should budget:

One-time implementation costs

• Simple integration (compatible systems, good documentation): £1,500–£3,000. This covers API setup, outlet mapping, testing, and staff training. Timeline: 2–3 weeks.
• Standard integration (some custom configuration needed): £3,500–£6,000. This involves custom data mapping, more extensive testing, and potentially API modifications. Timeline: 3–5 weeks.
• Complex integration (legacy PMS, multiple EPOS systems, custom billing rules): £6,000–£8,000+. This requires significant custom development and potentially re-engineering your billing workflow. Timeline: 6–8 weeks.

The difference between “simple” and “complex” isn’t about how smart you are — it’s about whether your PMS and EPOS were designed to talk to each other. Oracle Micros and modern Lightspeed EPOS integrate cleanly because both vendors built integration into their architecture. A legacy Fidelio system and an older Swiftbill EPOS might need custom work to map data correctly.

Ongoing costs

• API fees (if your PMS or EPOS vendor charges separately for integration): £50–£150 per month for transaction volume up to 10,000 per month. £150–£300 for higher volumes.
• Support and maintenance: Usually included in your PMS contract, but some vendors charge separately if integration breaks and needs debugging.

Use a pub profit margin calculator to work out whether the time savings justify the integration cost. If your night manager spends 3 hours per night reconciling EPOS to guest folios, that’s roughly £15,000–£20,000 per year in labour costs. A £4,000 integration that saves 2 of those 3 hours pays for itself in less than 4 months.

Common integration problems and how to fix them

I’ve worked through dozens of integration failures, and most of them come down to three things: data mapping errors, connectivity issues, and staff workflow changes that nobody documented.

Problem 1: Charges appear on the wrong guest folio

This is almost always an outlet mapping error. Someone configured the API to send all bar charges to a single revenue centre in the PMS, but your PMS has separate revenue centres for the restaurant bar and the lounge bar. The charge shows up under “Bar Revenue” but doesn’t know which guest it belongs to.

Fix: Go back to your mapping spreadsheet. Verify that each EPOS outlet corresponds to exactly one PMS revenue centre, and that each PMS revenue centre is configured to push charges to the correct guest folio field. Re-test with a dummy transaction.

Problem 2: Integration stops syncing after a few hours

This usually means your internet connection dropped, or your PMS server became temporarily unavailable. Real-time integration is brittle — if the connection breaks even for a few seconds, you might miss transactions.

Fix: Switch to batch sync instead (every 30 minutes rather than real-time). You lose a few minutes of immediacy but gain reliability. Ask your integration technician to set up error logging so you can see exactly when syncs fail.

Problem 3: Guest folios show charges but night manager can’t identify which server rang it through

Your integration is working technically, but you’ve lost the audit trail because the EPOS didn’t pass server ID or timestamp data through to the PMS.

Fix: This is a configuration issue. Your integration technician needs to modify the API mapping to include staff ID, terminal ID, and transaction timestamp in every charge that syncs to the PMS. It adds complexity but creates an audit trail that actually matters.

For help diagnosing integration problems, refer to our guide on pub EPOS system not working UK which covers troubleshooting steps that apply to integration failures as well.

Problem 4: WiFi unreliability in your restaurant causing sync delays

If your EPOS terminals are relying on WiFi and your signal is weak, integration will be unreliable. The EPOS will queue transactions locally and try to sync later, but timing mismatches and data conflicts happen.

Fix: Invest in proper network infrastructure. This is not a nice-to-have. A hardwired ethernet connection (or mesh WiFi with proper deployment) is essential for reliable integration. Budget £500–£2,000 for network improvements depending on your building size.

For more information, visit pub profit margin calculator.

For more information, visit pub drink pricing calculator.