This is critical for us. We noticed that the issue becomes worse if you have the City tax set as product. When you add a second guest the nightly price reduces to accomodate the City tax and the product generating a lot of manual work for the local teams.

The current behaviour is very strange. Mews mixes up room price and add-ons.

Please change immediately! It is not conceivable to calculate the room rate from the average room rate + added values. It makes absolutely no sense

Obviously, this should be changed ASAP. Reading all the comments below, an explenation would not be needed anymore.

Please action on this - sometimes we actually cancel and recreate an entire reservation because of this issue. It makes no sense that the price is altered with product value, simply because it needs to put it somewhere?

This is a big problem for us. We have holiday homes where the amount op guests is changing often. Now we have a lot of hassle to make these bookings correct again.

It is important that the roomrate does not change when changing the number of persons. Only the items such as citytax or breakfast need to be changed. So we would like the button keep old price to be used for the room price and not the total price.

This product is not useful for us as we can not see the correct prices after they change!! So it is a lot of work for us to fix it. therefore 'keep old price' should keep the old price and not change it.

For me the option: keep old price refers to keep old price for the room rate, no matter how many packages there might be in the booking, so this option is not useful for us if the room rate is changed. :(

The current system is driving me and my team crazy. In our city the city tax depends on number of people and also age of the kids, everytime we change this parameter the daily rates are affected even with "keep the old prices" selected and we have to fix it manually for each reservation. Please update it!

There is no logic in the currect way of working. Keep old price should mean keep old room rate. Additional products such as city tax, etc are mostly dependend on how many people stay in a room.

If I have booked a room with a price of 100€, Mews calculates 2 prices :
1) the price of the room excluding additional products
2) the price with additional products. Additional products can depend on the number of persons, like the stay tax.

If the stay tax is 3 € per person, and if I book the room for 2 persons, the total price including products would be 106 €.

If I change the number of persons to 1 while ticking "keep old price", Mews changes the price excluding products to 103 and keeps the price including products at 106 €.

In my opinion, there is a design error in the code.

If the checkbox "Keep old price" is checked, Mews should keep the price excluding products, instead of keeping the price with products.

The issue has been reported to the development team, and they answered that the behaviour is correct (as designed) without providing a logical explanation.

When changing the number of people in a booking if you select KEEP OLD PRICE, the system will change the city tax and add the difference to the room price. Please change this so that the price of the room is not changed, the city tax has nothing to do with room night prices.

When changing the number of people in a booking if you select KEEP OLD PRICE, the system will change the city tax and add the difference to the room price. Please change this so that the price of the room is not changed, the city tax has nothing to do with room night prices.