Hospitality · PMS

PMS integrations that stay in sync on a full night

Your PMS holds every stay, but rates, rooms and guest data also live in the channel manager, the booking engine, housekeeping and finance, and they drift apart on the busiest nights. We build two-way PMS integrations that keep them in step, with every message logged, retried and checked, in your repository and your accounts.

Typical lengthweeks
From€10,000 · £8,700 · $11,500
PlatformsMews, Apaleo, Oracle OPERA Cloud, Cloudbeds

When teams call us

What usually triggers the work

“We're moving off our on-premise PMS and every connection has to be redone.” “Each new property brings its own tools, and none of them talk to the PMS.” “Our hotel customers want us in the Mews or Apaleo marketplace.” In a 2025 Starfleet Research survey of hotel IT leaders, fewer than one in four said their core systems were fully integrated.

Left alone, the gaps show up in front of guests. A room type mapped wrongly or an update that arrives late sells the same room twice, and the guest finds out at the desk. Reception and revenue staff retype what the systems should pass on, and month-end reports disagree with the PMS. For a software company, a connector that drops messages turns into support tickets from every hotel that uses it.

What we deliver

In your repository, demoed every week

  • Two-way integration with Mews, Apaleo, Oracle OPERA Cloud (OHIP) or CloudbedsBuilt on the platform's published API, in its sandbox first and then on one property. You can see every message sent and received.
  • Reservations, rooms, rates and guest data mapped and kept in syncA written field-by-field mapping agreed with your team before any code, and a scheduled comparison of both sides that lists every difference.
  • Retries, replays and alerts when the PMS or your system is downMessages are stored before they are processed, retried, and replayed in order after an outage. Alerts go to the person you name.
  • Certification and marketplace listing for software vendorsWe prepare the test scenarios, documentation and demo the platform asks for, and support the review. The listing stays in your company's name.

How it holds up

The questions a reviewer will ask, answered in the build

01

Each update applied once

Every message carries an idempotency key, so a retried reservation update never creates a second booking or a second charge.

02

Events you can replay

Webhooks from the PMS are verified and stored before they are processed. After an outage they are replayed in order, instead of someone guessing what was missed.

03

Both sides checked

Reservations, rooms and rates are compared between the PMS and your system on a schedule. A difference raises an alert, rather than being found by a guest at check-in.

Proof

What we have built ourselves

We don't list past client PMS work here. Our hospitality proof is the two products we own; the retries, replays and reconciliation described above run in production in our banking orchestration work.

Draft

Kitchen Back Office

Our own back-office service for restaurants: the kitchen sends photos and voice notes, we close the stock counts and report P&L and food cost on our Kitchen app.

Draft

Housekeeping app

Our own app for hotel housekeeping: daily room tasks on staff phones, live room status for supervisors and reception, supplies tracked per room.

Platforms we build for

  • Mews
  • Apaleo
  • Oracle OPERA Cloud
  • Cloudbeds

Often built together: Toast and Lightspeed POS integration and an integration audit to start.

Price

What it costs

A PMS integration starts from €10,000 (£8,700 · $11,500), billed by milestone. Typical length: weeks. Most groups start with the integration audit, a fixed-price first step whose fee is credited in full if you build with us.

All prices

Questions

Before you book

We are a software vendor. Can you build our PMS connector?

Yes. We build it in your repository, under your developer or partner account with the PMS, and hand over documentation and runbooks so your team can run it. If you would rather we keep it working as the PMS changes its API, we agree monthly care separately.

How long does a Mews or Apaleo integration take?

It depends on what you sync and in which direction, and on the platform's own review, which has its own queue. After the audit or a scoping call you get a written timeline and a fixed price for each milestone, before you commit.

Can you work with an on-premise OPERA?

Often, but it is a different job from OPERA Cloud. Older on-premise versions are reached through Oracle's interfaces for that version, which can involve Oracle's own validation and fees; OPERA Cloud goes through OHIP. If you plan to move to the cloud anyway, building against OHIP avoids doing the work twice. The audit tells you which route is realistic.

Who owns the code and the IP?

You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.

Who will actually work on our project?

The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.

How do time zones work for a UK or US team?

We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.

What contracts do you sign?

A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.

How do we pay?

The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.

Free 30-minute call

Tell us what has to work, and by when

You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.

Or write to us
info@jobsdone.pro
Lisbon time: the same clock as London, 4–5 hours ahead of New York

We answer within one working day. We sign an NDA before seeing any code.

Thank you, it's with us

An engineer will reply within one working day with a few times for the call. If it's urgent, email info@jobsdone.pro.