We will merge the existing Rate Manager with the Revenue Management functionality. From a user perspective, there is little difference between the two modules.
Let us explain why:
We are going to add a landing page as there is currently no useful overview start in the module.
We will rename the module to Revenue Manager. Why should we do this? Because in our current module there are basically 3 functionalities:
Rate Management, where users can configure rates. They can also adjust those rates manually or intelligently using dynamic pricing. This is (and will remain) our paid feature.
Availability management, where users can configure the conditions of stay and when and through which channel accommodation types are bookable.
Discount management, where users can configure offers and vouchers.
All 3 topics are part of the user's revenue management. Therefore, it is better to rename the module accordingly.
We will reorder the current menu items. As discussed above, there are common features that will be grouped together. This will improve our user experience and usability.
We will merge and update the current documentation pages.
In addition, this merger is consistent with what we see with our competitors.
Revenue Management features:
Rate Manager features:
Offer with Add-ons [Package/Compositions with Accommodation]
Rentability Set Import Functionality
New implementation for Allowing rentability for overlapping periods with different weekdays
FAQ
"What will happen to the current Revenue Management and Rate Manager team?"
The teams will operate as they always have. They will focus on the features they created and are responsible for.
"What is the impact for our (current) customers?"
There is no functional impact as the features remain the same. The only impact is the name change and reordering of menu items.
“When can we expect these changes?”
2024Q4 & 2025Q1