Pricing rules

The rule stack

A nightly rate is not one number. It is a base rate with rules applied in order, each one adjusting what the last one produced. The stack is visible, and every rate on the calendar can be opened to show which rules moved it and by how much.

Writing a rule

A rule is a condition and an adjustment. The condition matches on a date range, the days of the week, lead time, length of stay, the nights in a gap, or occupancy in the surrounding week, and a season or a local event is a date range with a name on it. Nothing else can be matched on, which is what keeps the stack readable. The automations have a grammar of their own: see what runs on its own.

Floors and ceilings

Set a floor and a ceiling per unit. They are absolute: no combination of rules can take a rate under the floor or over the ceiling, however the arithmetic works out. A stack of small discounts compounding into a rate that does not cover the cleaning is the failure a floor exists to prevent.

What Dardaris will not do

It will not change a rate on a booked night, and it will not undercut your floor to fill an orphan gap. If the only way to sell a night is below the floor, it says so and leaves the decision with you.

Dardaris does not write a price by itself. It proposes one, with the rules that produced it, and you apply it. Where that line sits for everything else it does: autonomy tiers and spend caps.

The other half of a turnover: cleaning.