There are Nightly Rate (min) and Nightly Rate (max) fields for properties but they don't actually control the minimum and maximum per night price.
There are many reasons why rates might be set at wrong values by mistakes (such as overlapping discounts, seasons without prices etc).
So, it'd be great if the Nightly Rate (min) and Nightly Rate (max) fields didn't allow the rates to go less or more than the set range. If the rates go less than Nightly Rate (min) then they could be set to Nightly Rate (min) value.
It'd be terrible to deal with bookings that might mistakenly get a very low per night values.
Those min and max rates are for display purposes only - we auto fill them based on when your rates change or you can override them to say what you want. We thought about doing what you asked in the past. The problem with that is that it tends to lead to bad behavior and confusion. When rates are advertised in quotes, it would be unknown where the rate comes from because what's in the rate engine would be cut off by the min/max. The guest and user (you) would both be confused and ask questions. But it's an interesting idea that we'll continue thinking about!
I think this is a very important area and open to costly mistakes. I hope you find a way to sort out the issues you're mentioning in your message and implement this soon. Working with rates/ seasons etc without having a security layer like this quite scary, to be honest. Thank you for your consideration.