Understanding Customization and Date-Specific Override Hierarchy

Understanding Customization and Date-Specific Override Hierarchy

It is important to understand the hierarchy of which rules will apply when. Like someone wise once said:

With great power comes great responsibility.

The ability to set rules at an account/PMS level is useful if you manage tens or hundreds of listings so that you don't have to set customizations for each one of them individually. This post is to clarify which customizations get applied when you have both an account and listing level customizations present. There are two kind of customizations available with PriceLabs today:
  1. Customization Rules: These are broad rules such as last minute discounting/premium, orphan day discount/premium, and minimum night settings.
  2. Date Specific Overrides: These are applied to specific dates, and can be specific prices override (where you specify the amount), % override (where you add a specific discount/premium for specific dates), or min-nights
Both types of rules can be setup at the account (PMS) level, group level, and at a listing level. Here is what happens if you have various rules setup at all levels.

Identifying the Applicable Customization Rule







We first identify which customization rules will be applied for a listing by using the following logic for each of the customizations
  1. if the corresponding listing level customization is on, then that gets used.
  2. if the corresponding listing level customization is off, but the group level customization is on, then the group level customization gets used.
  3. if the corresponding listing level and group level customizations are off, but account level customization is on, then the account level customization gets used.
 Note: as the image above shows the min-night settings are all or nothing, so you can't have rules from different levels mixing (i.e., you can't have some min-night customizations from one level and some from another level).

Identifying the Applicable Date-Specific Override 
The following example shows what happens if a date has both a listing, group and account level overrides. 









For each of the two date specific overrides (price and min-stay):
  1. if a date has a listing level override, then that gets used.
  2. if a date doesn't have the corresponding listing level override, and has one at the group level, then the corresponding group level override gets used.
  3. if a date doesn't have the corresponding listing or group level overrides, and has one at the account level, then the corresponding account level override gets used.
Another example:




Applying the Identified Customizations and Overrides
Things are straightforward if on any date only one customization or date-specific override is applicable. If not the different overrides and customizations are applied in the following order to determine that day's price:
  1. If there are 'fixed' overrides or customization, they are applied in the following order: date-specific override OVER last-min customization OVER orphan-day customization.
    Note: account/group level '% of base price' overrides are considered 'fixed'.
  2. For dates that don't have any 'fixed' customization applying to it, the last-minute and orphan day customizations are applied if necessary. If a date has both of them being applied (a last-min orphan day!):
    1. if both are discounts, the larger of the two discounts is applied (since applying both discounts can result in a very large discount)
    2. If one is a discount and one is a premium, or if they are both premiums, both are applied
  3. Finally, the date specific "% adjustment on recommended price" overrides and "occupancy based adjustments" are applied on top of the price to all dates that don't have a "fixed" customization.
To determine the minimum stay requirement the applicable min-night customizations and overrides are applied in the following hierarchy (in case a date has more than one rule): date-specific overrides OVER far-out customization OVER last-min customization OVER default setting. The orphan day customization is applied over everything else if it won't increase the min-night setting on a day.
For example, suppose you have a last-min min-night of 1 within 10 days, and orphan gap rule of "length of gap" for gaps 1-3 days. For an orphan gap of 2 days in the coming week, the "length of gap" orphan rule wouldn't apply because the last-min rule of 1 is lower.

We understand that this might be a lot to take in, but it is important to understand these if you are using customizations at multiple levels. Once you have gone through these, you will realize that these are fairly logical and easy to understand, and will be able to use these powerful features to their fullest!


    • Related Articles

    • Date-Specific Overrides

      You can add a date-specific override to your listing using one of two ways: by clicking and dragging to select your dates, or by clicking the green Date Specific Override button to the right of the calendar which will open a smaller calendar where ...
    • Bulk Date-Level Override Options

      When you're making overrides at a group or account level, it's generally better to do those in percentages instead of fixed values since different listings might have different base/min/max rates and you don't want the same fixed amount on each of ...
    • Video: Customization Hierarchies Explained

    • Adjacent Factor Customization

      The Adjacent Factor customization will adjust the rate for the selected number of days before and after a booking. Please note that rates will only be adjusted the next time a sync happens after a booking is made. So if a reservation is made in the ...
    • Using Group Customizations to Help Manage Multiple Listings

      PriceLabs provides a framework where you can manage customizations and date-specific overrides for each listing, or you can group multiple listings together and manage them at once! These groups can be anything: City Names: If you have listings in ...