Adding Customer Metric to Mews Analytics / Reports Average Rate, Occupancy etc..
In Mews the statistics are calculated using room / beds occupied and not by customer count.
We'd like to be able to calculate all statistics in Mews reports & Analytics by customer. This could be achieved by adding a setting to use customer count.
Average rate instead of calculated occupied rooms/revenue use customers/revenue
Occupancy instead of calculating by occupied rooms/available rooms use customers occupying rooms/available rooms

Hi Nick,
Thanks for posting this! We are looking into revamping how we calculate statistics in the future and will consider this enhancement at that point. Many thanks for your contribution and look forward to hearing more ideas from you!
-
Mark Nykjær commented
I would like to propose an enhancement regarding the way occupancy is calculated in Mews. Currently, Mews accounts for all spaces created in the system, including virtual connecting rooms, which results in occupancy reports reflecting a higher number of available spaces than the actual number of physical rooms in the hotel.
For example, in our case, we have 86 actual rooms, but Mews calculates availability based on 96 spaces, including virtual connecting rooms. This affects key performance metrics such as occupancy rates, revenue per available room (RevPAR), and benchmarking comparisons, as the reported figures do not align with our true capacity.
Benchmarking Alliance has the capability to differentiate between actual and virtual rooms, ensuring accurate reporting. It would be highly beneficial if Mews could introduce a similar feature, allowing users to choose whether to base occupancy calculations on the actual number of rooms rather than spaces.
Would it be possible to implement an option in reports that enables filtering out virtual/connecting rooms to ensure a more precise reflection of hotel performance?
I encourage others who find this relevant to support this suggestion to improve reporting accuracy in Mews.