Hello Mews Community, 

If you want a car, plane or bike to go fast and perform well, it needs to be streamlined. The same goes for hotel operations. That’s why we’re excited to announce a new feature in Mews Multi-Property to help hotel groups and chains streamline your operations even more: central rate and policy management.  

If you're the one who has the arduous task of configuring rate groups and policies across hotels, you probably share our excitement. For those of you who aren't as familiar with the standard process, you'll have to trust us – it kicks operational efficiency up a gear. Let’s dive into what this new feature means for your multi-property management. 

What's new? 

Until now, the policies attached to rate groups were fixed and to apply a different policy required duplicating settings. While it worked, it was cumbersome and resulted in multiple rate groups that were difficult to manage – not exactly streamlined. 

Through this update, we’ve made rate groups and policies exist independently. So, you can now create a payment policy or cancellation policy once and reuse it across rate groups, rates and even across multiple properties.  
 

Why you’ll love this feature 

• Ensure consistency: Easily standardize your rate management strategy across groups, brands and portfolios. 

• Maintain standards: Make it easier for individual properties to adhere to group requirements. 

• Minimize human error: With less manual work to manage rates and policies, you’ll reduce the risk of mistakes and inconsistencies. 

• Enjoy more flexibility: Effortlessly adjust payment policies to accommodate regional differences if required. 

Now that you can manage rate groups and policies centrally in Mews, expect a satisfying boost in efficiency as well as more opportunities to maximize cancellation revenue across your operations. 

So, don’t let us keep you; go try out your new streamlined Mews Multi-Property and do something remarkable with the time you save  
 

We’d like to say thank you to all the Mews Community members and beta testers who helped us research, develop and test the first iteration of this feature. You have been so generous with your time, and we truly appreciate your input