Property management systems
Harlow reaches a property management system in one of two ways: through the hotel's own PMS screens, from the connector workstation, or through the vendor's interface where one exists. Either way, nothing about the PMS changes.
Two ways in
- Through the screens
- The connector works in the PMS client as a named user would, on request, with each action recorded. This is how Opera 5 is supported today, and how PMS platforms without a usable interface are reached.
- Through the interface
- Where the vendor offers one (Oracle's OHIP for Opera Cloud, for example), Harlow uses it. Fewer moving parts, no workstation needed for that system.
Platforms
| PMS | How | Notes |
|---|---|---|
| Opera 5 | Screens, from the connector workstation | A named Opera user; the night-audit window is respected. |
| Opera Cloud | OHIP where the property has it, else screens | Ask us which applies to your contract. |
| Mews | Screens or interface | Confirmed per property. |
| Cloudbeds, Apaleo, Protel, OpenHotel | Screens | Confirmed per property. |
What Harlow does in a PMS
- Reads what a request needs: the reservation for a room, arrivals and departures for the day, the room roster.
- Writes what was approved: a trace or ticket, a profile note, a checkout change, within the permissions the Opera user has.
- Nothing else. The connector does not browse, export or read screens a request did not ask for.
Trace first, then live
Every integration starts in a mode where writes are recorded as traces for the hotel to check. Live writes are switched on together with the hotel once the first ones have been checked, and the IT view shows which mode the property is in.