Capability
Rates by date range, day of week and length of stay, edited by the operator directly with no support ticket and no vendor lead time.
Rates sit against date ranges, so peak, shoulder and off-season are separate rather than one price with manual overrides on top. Day-of-week rules layer over that, because a Saturday in July prices differently from a Tuesday in July.
Length-of-stay pricing is native. A seven-day hire costs seven times the daily rate only if you say so, and multi-day breaks are expressed as rules rather than as discount codes.
The operator edits all of it. Nothing here needs a ticket to a vendor, which is the reason most operators leave rates wrong.
Season revenue at 30 rentals a week: $0
Click a week to move it between bands. Rates are yours to set on the day demand moves, without waiting on anybody.
Peak weeks priced like shoulder weeks because changing a rate took a phone call.
The number to watch is revenue per available unit through the peak weeks.
There is no automated demand-based pricing engine. Rates change when you change them. For most seasonal operators that is the wanted behaviour, and it is not yield management.
Every capability page on this site carries a section like this one. Why that is.
Rates by date range, day of week and length of stay, edited by the operator directly with no support ticket and no vendor lead time.
Bodhisys handles it as part of the platform rather than as a paid module or a partner integration. There is no monthly fee. A 4.5% charge is added to each reservation and paid by your customer at checkout.
Yes, directly. No support ticket and no vendor lead time.
Yes. Length-of-stay pricing is a native rule rather than a discount code.
No. Rates change when you change them.
The same capability behaves differently by category. These are the per-industry versions.
Verified against public documentation, 2026-08.
