API first approach, does it risk sacrificing in-PMS functionality?
Open APIs make perfect sense to me, build your own platform in a way that makes it easy for other hospitality technology providers to connect to your PMS. This gives hoteliers the opportunity to choose from a far wider choice of automation products and complementary systems.
The API first approach takes this to another level, allowing every bit of data to become accessible to 3rd party systems. Essentially, it allows them to take over an unlimited number of functionalities that you might reasonably expect the PMS to carry out. This is my quandary. I find myself sitting on the fence about making it the be-all and end-all approach to modern PMS development.
“The API first approach might make providers complacent about what their PMS can do.”
Whilst I agree that hoteliers deserve to have options and choices, when it comes to using an unlimited number of well-integrated systems, the API first approach might make providers complacent about what their PMS can do.
APIs should complement PMS features, not replace them, and there are risks associated with ‘outsourcing’ features to 3rd parties. These can come and go or completely change direction over time.
Using multiple providers to tick your operational boxes brings with it multiple subscriptions, logins, potentially devices, and training staff on these different applications.
“What works best really depends on the category of the hotel.”
Having a feature-rich PMS product without the need to use a partner to compensate for lack of functionality appears to be the valid and sensible approach. What works best really depends on the category of the hotel, its location, size, type (independent or chain), market segment, end-user profile, and finally, personal preference.
If you are bit like me, and like to have your cake and eat it too, then a PMS such as OPERA Cloud is the right solution. It combines an industry-leading feature set built-in to the PMS with the Oracle Hospitality Integration Platform (OHIP). This self-service portal is centralised and provides all PMS functionality in API form. Talk to us at HRS Hospitality & Retail Systems about any of the Oracle Hospitality product suites.
What are my favourite OPERA Cloud features?
Far too many to mention, but having worked in hotel front offices and reservation departments, there are features that I wish that I had back then that bring tremendous value to the end-user. For instance, the highly customisable PMS and Sales & Events dashboard, data-rich profiling, reservation queue (if you have ever faced a Monday check-in at a large business hotel, you will know what I mean) and split folio screen.
About the author:
Siggi Schrot started his career in 1997 working in the rooms division of hotels of varying categories and sizes. He transitioned to hospitality technology in 2002 and has since worked as a software consultant and customer success and sales manager.
