In the offseason, or for unrented weeks, or last minute bookings - would like the ability to use a price scale based on occupancy, similar to what I saw on booking.com. This would allow us to continue to charge full price when at max occupancy, and have a reduction table when a group has fewer occupants. Would like to be able to turn this on by week, day, or a season
I'm not clear in what way this is functionally different from how it works now? It sounds like you're saying you want to price for full occupancy, and then offer discounts if you only bring fewer people. The way OwnerRez, and all the major listing channels, work is to have a base rate at minimum occupancy, and then charge additionally for extra people up to the max. Mathematically this works out the same.
This is not price increase per person, it’s the opposite. Booking.com has an optional price chart that lists reduction based on occupancy. We have six bedroom and have had 5 people up to 12, the table in booking.com lists total occupancy and allows for a reduction ifor a smaller party For example an automated reduction for fewer guests. An example below After API I could not find booking.com chart to take a photo if it..
occuoancy. Reduction %
12. 100
11 97
10 93
9 90
8
7…..
Booking .com summary…
Pricing per guest is a pricing use case where properties can specify prices depending on the number of guests planning to stay in a room. For example, an accommodation that can host 5 guests (maximum occupancy) can have a pricing strategy such that guests fewer than 5 can book the unit for a reduced price. This can help in maximising the inventory bookings.
Booking offers three pricing types that support pricing per guests pricing use case, namely:
Yes, I understand the distinction - I'm just saying that mathematically, the same end result can already be achieved.
I wasn't personally aware that Booking.com supports doing it this way, but I do know that none of the other major listing channels do. So I doubt adding this unique corner-case would be a high priority. Still, let's see how the voting goes.
Please share a current work around.
It's what I described earlier - set a base price with fewer people, and then surcharges for additional guests, such that the end resulting totals are what you're looking for.