It is important to understand the hierarchy of which rules will apply when multiple customizations are set at different levels. Like someone wise once said: With great power comes great responsibility.

The ability to set rules at the Account, Group, Subgroup, and Listing levels is useful if you manage multiple listings, as it helps avoid setting customizations individually for each one. This guide clarifies how PriceLabs applies customizations when they exist at two or more of these levels.

Types of Customizations

PriceLabs offers two main types of customizations:

• Customization Rules: These are broad rules such as Last-Minute Pricing, Orphan Day Pricing, and Minimum Night Restrictions.
  
• Date-Specific Overrides: These apply to specific dates and can include:
  
• Fixed Price Override: A set price for a specific date.
  
• Percentage Override: A percentage-based price adjustment.
  
• Minimum Night Override: A change in minimum stay requirements for specific dates.

By default, the hierarchy for customizations and date-specific overrides is as follows:

Both types of customizations can be applied at the Account (PMS), Group, and Listing levels. Below is how PriceLabs determines which rule applies when multiple rules exist at different levels.

Identifying the Applicable Customization Rule

1. If a Listing-Level customization exists, it takes priority and is applied.
   
2. If no Listing-Level customization exists, but a Subgroup-Level customization does, the Subgroup-Level customization is applied.
   
3. If no Listing-Level or Subgroup-Level customization exists, but a Group-Level customization does, the Group-Level customization is applied.
   
4. If no Listing-Level, Subgroup-Level, or Group-Level customization exists, but an Account-Level customization does, then the Account-Level customization is applied.

Important: Minimum Stay settings are all-or-nothing, meaning you cannot mix rules from different levels (e.g., you cannot combine some Minimum Night customizations from one level and others from another).

1. You have the Default, Orphan gap, and Last Minute set in the Account Level.
   
2. If you set the Minimum Stay Default on the Listing Level, the Default, Orphan gap, and Last Minute set in the Account Level will be ignored.
   
3. Only the Minimum Stay Default on the Listing Level will be applied.

Identifying the Applicable Date-Specific Override

If a date has multiple Date-Specific Overrides set at different levels, PriceLabs determines which one to apply using this hierarchy:

1. If a Listing-Level override exists, it is applied.
   
2. If no Listing-Level override exists, but a Subgroup-Level override does, then the Subgroup-Level override is applied.
   
3. If no Listing-Level or Subgroup-Level override exists, but a Group-Level override does, the Group-Level override is applied.
   
4. If no Listing-Level, Subgroup-Level, or Group-Level override exists, but an Account-Level override does, then the Account-Level override is applied.

For example, if a specific date has overrides set at the Listing, Group, and Account levels, the Listing-Level override will take precedence. More examples shown on the table below:

Applying Customizations and Overrides

If only one customization or Date-Specific Override applies to a given date, it is straightforward. If multiple customizations and overrides apply, they are applied in the following order:

1. Date-Specific Override (Fixed Price) → Last Minute Price → Orphan Day Price
   
1. Note: Account and Group-Level % change on Base Price overrides are considered "Fixed."
   
2. If an Account or Group-Level % change on Base Price override exists, and no Fixed Price Listing-Level override is set, the Account or Group-Level % change on Base Price override takes precedence.
   
3. If a Fixed Minimum or Maximum Listing-Level override exists, the Account or Group-Level % change on Base Price override still takes precedence.
   
4. Example:
   
• A listing has a Fixed Maximum Price of 1,450 at the Listing Level.
  
• A +270% change on Base Price override is set at the Group Level.
  
• The final price is calculated as 475 (Base Price) × 3.70 + 10% final adjustment = 1,933, not 1,450.
  
  
5. Applying Last-Minute and Orphan Day Pricing (if applicable)
   
1. If no Date-Specific Overrides apply, Last-Minute and Orphan Day prices are used.
   
2. If both Last-Minute and Orphan Day pricing exist:
   
1. If both are discounts, the larger discount is applied.
   
2. If one is a discount and the other is a premium, or if both are premiums, both are applied.
   
6. Percentage-Based Adjustments and Occupancy-Based Adjustments      
   
1. These are applied on top of the price to all dates that don't have 'Fixed' pricing customization.
   
7. Determining the Minimum Stay Requirement
   
1. The following hierarchy determines which Minimum Night Rule applies (if multiple exist):
   Date-Specific Override → Far-Out Minimum Stay → Last-Minute Minimum Stay → Default Minimum Stay
2. Orphan Day Customization Exception:
   
1. If an Orphan Day customization is set, it overrides all other Minimum Stay settings only if it results in a lower minimum night setting.
   
3. Example:
   
1. You set a Last-Minute Minimum Night rule of 1 night within 10 days.
   
2. You also set an Orphan Gap rule of "length of gap" for 1-3 day gaps.
   
3. If there’s an orphan gap of 2 days in the coming week, the "length of gap" rule does not apply because the Last-Minute rule of 1 night takes precedence.