Hey Alice, yes, a warning pop up would be better than the status quo.

I'm still a little confused as to why the price would change for the accommodation once somebody has booked and agreed to a rate? For us, the main changes would be when adding a guest or removing a guest as this would change our tourist tax but the rate itself is not tied to guest numbers.

If we were to move the reservation to a different property or different dates then this should change the rate as this makes sense.

A warning before would be an option but I still don't really understand why this happens in the first instance so would be good to get the real fix in place.

I think you'd need to differentiate between different type of changes to the lead.

If things like number of guests, number of pets, or booking dates changed - this confirmation message is appropriate. BUT if I changed things like email, name, notes etc. it shouldn't prompt a change in pricing.

Hi team, thank you for your interest in this idea. We've looked into the underlying issue, and we agree that being able to update booking information without unintentionally changing the price would be the ideal experience.

We've explored a solution that would allow you to "freeze" the pricing details while updating the booking information (like guest count, property dates), but this would require a significant amount of Engineering work and is unlikely to be something we can prioritize before the end of the year.

In the meantime, we're considering a lighter-weight solution: if changing the guest information causes the price to change, we could display a warning before saving, for example:
"Your price details have been updated based on the changes you've made. Do you want to continue?"

This would help prevent an accidental price change, but it's important to note that it would not preserve the original price. If you want to keep the original price, you would still need to manually adjust the price back after changing the guest count. It would also add an extra confirmation step to the workflow.

Would this kind of warning be helpful despite the additional step and the need to manually restore the price, or would it be more frustrating than useful?

Thanks for your feedback.

I am pretty sure this is intentional. But may be there could be an option to maintain current rates or update based on property/dates when modifying a lead. Especially for multi-unit.

PM inquired whether moving a channel booking (Airbnb/Booking.com) from one property to another, or between sub-units within a multi-unit property, which causes a price change, is there a way to retain the booking original price?