Automatically recalculate all per-person product charges on top of the original nightly rate when adjusting guest count
Description:
Currently, when adjusting the number of guests in a reservation, Mews either:
Keeps the total price unchanged (with "Keep old price" ticked), deducting additional product charges (e.g., city tax, breakfast, or other per-person fees) from the accommodation rate—distorting the original pricing structure.
Recalculates the total price (with "Keep old price" unticked), updating the room rate to the current pricing, which can lead to unjustified price increases for guests if rates have changed since booking.
The Problem:
There is no automated way to:
Preserve the original nightly rate (as agreed upon at booking).
Recalculate and add all per-person product charges (e.g., city tax, breakfast, extra bed fees) on top of the existing total—forcing hotels to manually create adjustment products, which is inefficient and error-prone.
This issue applies to every product billed per person (per night), not just city tax.
Desired Solution:
Introduce a third option in Mews that:
Locks the original nightly rate (as booked by the guest).
Automatically recalculates and adds all per-person product charges (city tax, breakfast, etc.) on top of the existing total, ensuring:
Fairness: Guests only pay for additional services (e.g., extra city tax, breakfast), not an unexpected room rate increase.
Transparency: Clear, itemized pricing that’s easy to explain.
Efficiency: No manual adjustments needed, reducing errors and saving time.
Example:
Original booking: 1 person, 100€ nightly rate + 8.25€ city tax = 108.25€ total.
Guest arrives with 2 people.
Ideal outcome: 100€ nightly rate (unchanged) + 2× city tax (16.50€) + any other per-person fees = 100€ + [sum of recalculated per-person products] total.
Why This Matters:
✅ Guest satisfaction: Avoids unexpected rate hikes while ensuring accurate billing for additional services.
✅ Operational efficiency: Eliminates manual workarounds (e.g., creating "adjustment" products).
✅ Scalability: Works for all per-person products, not just city tax.
Use Case:
This would benefit hotels, hostels, and serviced apartments where per-person charges (taxes, meals, amenities) are common but the nightly rate should remain fixed as originally booked.
Call to Action:
If this would streamline your operations, please upvote and share your experiences in the comments! Let’s make this a priority for Mews.
-
Charline . Kreusch
commented
Thank you for sharing this suggestion — I fully agree with the need for improvement here. With the way Mews currently handles guest count adjustments, you always end up having to modify the price manually, which not only creates unnecessary workload but also introduces a significant margin for error.
In my opinion, neither of the existing scenarios is correct:If you keep the old price, Mews deducts per-person products from the room rate, distorting the original agreed-upon pricing.
If you allow the price to recalculate, the system may apply the current (and sometimes higher) daily rate, which can unintentionally increase the guest’s total price.
But there is an additional issue that is often overlooked:
What if the current daily rate is actually lower than the rate at the time of booking?
Front desk staff may not notice this, resulting in guests paying less than they should — which is just as problematic from an operational and commercial perspective.
On top of that, this setup essentially forces us to give reception staff permission to adjust prices.
I strongly prefer not to grant such rights to every staff member. However, with the current functionality, we are pushed in that direction, and that is far from ideal.
That is why the proposed third option in Mews — one that:locks the original nightly rate exactly as it was booked, and
automatically recalculates and adds all per-person products —
would be a major improvement.It ensures transparency, prevents errors, protects both the guest and the property, and eliminates the need for staff to make manual price adjustments they should not be responsible for.
If this enhancement would also streamline your operations, I encourage everyone to upvote and share their experiences. The more voices behind this, the more likely Mews will prioritize this essential functionality. -
Patrick Mattick
commented
Long long overdue!
-
Edith Vonken
commented
Important!
-
Maxine Hofman
commented
let's go for guest satisfaction and efficiency!