Bring Every System Into Alignment

A PMS is not a hotel's ledger but its commercial backbone. Rates leave from there, bookings land there, occupancy is read there, reports are produced there. So while integration looks like an IT subject, its consequences are directly commercial: a broken connection comes back as a sale at the wrong rate, an oversell, or a report nobody trusts.

In hotels the problem usually appears not as a single fault but as a permanent correction effort. A routine has formed in which someone fixes a spreadsheet by hand every morning and someone reconciles two reports every month. That labour is invisible, and it is precisely the cost of missing integration.

A hotel whose data flow is unhealthy shows these symptoms:

• The PMS and the channel manager show different occupancy for the same day.
• Some bookings from channels are entered or corrected by hand.
• A cancellation is processed in the channel but the room still shows as sold in the PMS.
• A rate update reaches the channel in hours rather than minutes.
• Room revenue does not tie to accounting at month end, and the gap comes from the same line every month.
• Producing a report means exporting from several systems and merging them.
• The same guest exists under several records.

The aim of integration is not to reduce the number of systems but to make the same number the same everywhere. When two systems show different figures, the problem is not which is right but that nobody defined which one is the source.

An integration plan starts by writing down which data flows in which direction. Where the direction is undefined, two systems overwrite each other and nobody knows which one won.

Filling in this table usually reveals two things: some connections were never built, and some data is fed from two places at once. The second is more dangerous, because it throws no error — it simply produces a different answer, quietly.

Room type and rate code mapping

The room type in the PMS must match the product in the channel exactly, and the rate code must match the rate plan. When the mapping is wrong the error repeats on every booking rather than once, and is usually noticed months later.

Lag

How long a rate or stop-sale update takes to reach the channel is measured during setup. On a high-demand date, a lag of a few hours means inventory that could not be closed.

Cancellation and amendment sync

Delivering a new booking usually works; the real break happens on cancellations and date changes. If testing only covers creating a booking, that scenario is never tried.

Duplicate guest records

The same guest held under several records makes the repeat stay rate and any loyalty work meaningless. The merge rule is defined during setup; cleaning it up afterwards costs far more.

Tax and rate display

Whether the rate travels inclusive or exclusive of tax is the most frequently confused point between channel and PMS. When it is confused, the guest sees the wrong amount and the revenue does not tie at month end.

Integration errors share one quality: they are silent. The system raises no warning; it simply produces the wrong number. The value of a setup therefore lies not in the connection itself but in the coverage of its test scenarios.

A new connection, or a new PMS, is tried end to end before going live. The sequence is this:

1. 01System inventory — which systems exist, which are connected, which data comes from where.
2. 02Source definition — one source of truth is chosen per number. Two sources for the same metric make the report disputable.
3. 03Mapping table — room types, rate codes, segment and channel codes written against each other. This document is the setup's most valuable output.
4. 04Test scenarios — new booking, date change, cancellation, no-show, room move, group block, ancillary charge. Each is verified in both systems.
5. 05Lag measurement — how long rate and stop-sale updates take to reach the channel is recorded.
6. 06Parallel running — where possible, old and new flows run together for a period and the numbers are compared.
7. 07Go-live and supervision — daily reconciliation in the first days; this is the window in which errors are caught.
8. 08Handover — the checklist, the mapping table and the troubleshooting steps stay in the hotel in writing.

Test scenarios are the step skipped most often, and skipping it is always paid for in the same place: on opening or migration day, in front of the guest.

An integration can work technically and the reporting can still be unreliable. The cause is usually inconsistent data entry: the same segment entered under different codes, the channel code left blank, group bookings recorded as transient.

• Segment and channel codes are kept limited and written down; a free-text field breaks the report.
• Mandatory fields are few enough not to slow the operation and many enough to hold the report up.
• Entry rules are explained to reception and reservations; consistency cannot be expected from rules nobody knows.
• A regular data audit runs: records with no code, duplicate guests, unusual rates.
• Definitions live in one document, and reporting speaks the same language as that document.

The quality of a report is the quality of its weakest data entry. Integration work therefore starts with systems and ends with the team's daily habits.

• A system map — which data flows from where to where, and in which direction.
• Source definitions — one source of truth per metric.
• A mapping table — room type, rate code, segment and channel equivalents.
• A test scenario list — the control set to use before and after migration.
• Lag measurement — how long critical updates take to reach the channel.
• Data entry rules — a short, usable guide for reception and reservations.
• A reconciliation routine — daily and monthly comparison between PMS, accounting and channels.
• A handover file — troubleshooting steps and responsibilities.

The goal is not to change the system but to make the systems you have understand one another correctly. Built properly, the visible result of integration is this: nobody fixes the spreadsheet by hand in the morning.