Hotel manager with a tablet next to connected hotel systems: card terminal, PMS screen and globe

Connecting hotel systems: a PMS, POS and channel manager that work together

You connect hotel systems by choosing one leading system per data type and linking the other systems to it. The PMS is usually the heart: the channel manager puts bookings into it, the POS charges spending to the room and accounting receives the revenue. What the standard integrations don’t do, we build through the API of your PMS.

Why does your team still retype data between hotel systems?

Your team retypes data because standard integrations often only pass on the basics. A channel manager puts name, dates and rate into the PMS, but special requests stay in the Booking.com email. A POS integration charges the amount to the room, but packages and group lunches still run by hand. Most hotels work with ten or more systems side by side. Every extra system is a place where data can differ. How special requests from Booking.com emails still reach the PMS, you can read at OTA emails processed in your PMS.

Which hotel systems do you connect to the PMS?

  • Channel manager. Bookings, changes and cancellations from Booking.com and Expedia go to the PMS. Availability and rates go back to the channels.

  • POS. Spending in the restaurant and bar goes to the room or the group account. Revenue per department goes to accounting.

  • Table reservation system. Breakfast, dinner and group lunches sit in the restaurant’s reservation system, such as Zenchef or Formitable.

  • Accounting. Revenue, payments and invoices go from PMS and POS to Exact Online, AFAS or Twinfield.

  • Rota tool. Expected occupancy from the PMS determines how many people you schedule per department.

  • Guest communication and door locks. Guest details and stay dates go to your email tool, online check-in and keys.

When is a standard integration enough?

A standard integration is enough if it passes exactly the data your team needs. Mews, Cloudbeds and Apaleo each have a marketplace with ready-made integrations. Test such an integration with real scenarios: a change, a cancellation, a group and a package. If everything comes through correctly, nothing needs to be built. If manual work remains, that is where a custom integration comes in. Working with Mews? Read how we connect Mews through the Mews Marketplace and the Mews API.

How do we connect hotel systems without a standard integration?

We connect hotel systems without a standard integration through their API, in four steps.

  1. Mapping. We walk through the processes with your team, from booking to invoice, and note where data is retyped.

  2. One leading system per data type. For each data type we record which system holds the truth: reservations in the PMS, tables in the reservation system and revenue in accounting.

  3. Build and test. We build the integration and test it with your own bookings and receipts, alongside your team’s manual work.

  4. Monitor. If an integration stops, for example after a vendor update, you get an alert right away. An integration that fails unnoticed costs more than no integration.

What such an integration costs and what you pay for, you can read at having an API integration built.

From practice

A hotel group ran six hotels in two countries on a PMS more than eight years old. At the front desk four to six systems were open at once, and group bookings sat in spreadsheets. We brought the landscape back from sixteen to seven tools and connected what remained. That removed about 92 hours of manual work a week, and the project paid for itself within two months. Read how that hotel group reduced its systems to a clear stack.

When don’t you need us?

If you work with a PMS and a handful of tools that work well together through the marketplace, you don’t need a custom integration. If you are considering a PMS switch, wait with building integrations and choose the PMS first. Read how to choose a hotel PMS.

Frequently asked questions

Do I need to replace systems to connect them?

No. We connect the systems you already have. Sometimes the overview shows a tool is redundant, because the PMS already does the same.

Which systems do you work with?

PMSs such as Mews, Cloudbeds, Apaleo, Opera Cloud, protel and Clock PMS, POS systems such as Lightspeed and unTill, reservation systems such as Zenchef and accounting software such as Exact Online. If a system has an API, we can usually connect to it.

Who manages the integrations after go-live?

We do. The integrations run on our side, we monitor them and adjust them when a vendor changes something.

What happens when an integration hits an error?

Your team gets an alert with the booking or receipt concerned. The integration fills in nothing it is not sure about.

Have your hotel systems connected?

Want to know where most of the retyping happens in your hotel? Plan a call of half an hour. Together we look at your PMS, your POS and your other systems.

Ready to put AI
to work?

Do the AI Scan or plan a call, we'll take it from there.

Ready to put AI
to work?

Do the AI Scan or plan a call, we'll take it from there.

Ready to put AI
to work?

Do the AI Scan or plan a call, we'll take it from there.