Pricing controls and price hierarchy

In Atomize, various pricing control options allow you to influence the pricing algorithm to align and operate with your hotel’s specific needs and market conditions.

The price hierarchy in Atomize defines the price boundaries that the price recommendations should be within. It ensures that price recommendations never go below or over the price points you decide. You can set the minimum and maximum price boundaries for each individual room type, as well as the offset between them. 

For each hotel there is always a default price hierarchy but you also have to option to set up seasonal hierarchies or override the hierarchy for certain stay dates.
In addition, you can also apply rules for the prices on the near-time days before the arrival date.

We have explained the different pricing control options below, how they are meant to be used, and how they function together. The article consists of the following sections:

• Default price hierarchy
• Seasonal price hierarchy
• Hierarchy override
• Price override
• Near-time pricing rules
• Hierarchical order of pricing controls

Default price hierarchy

For each hotel, there is always one default price hierarchy. You find your price hierarchy under the settings menu.

The default price hierarchy establishes the price boundaries for all future dates unless a seasonal price hierarchy or hierarchy override has been configured.

To set up or make changes to your default price hierarchy in Atomize you can learn more here.

Seasonal price hierarchy 

A seasonal price hierarchy is set for a certain time period and overrules the default price hierarchy.

This function can be used to apply different rules to multiple distinct periods. It can be applied for longer time periods (e.g. for seasons), or repeatedly on certain days of the week (e.g. Fridays and Saturdays). It is possible to add up to ten different seasonal price hierarchies. 

For temporary daily changes in the price hierarchy (e.g., for an event), please use the price hierarchy ruleset function.

To set up your seasonal price hierarchies in Atomize, learn more here.

Hierarchy override (Min/max)

The hierarchy override allows you to increase or decrease the minimum (and/or maximum) price allowed to be set by Atomize on a certain stay date or a smaller set of stay dates.

On certain occasions, such as when there is a special event influencing your business, you might feel the need to adjust the floor or ceiling prices configured in the price hierarchy. By using the hierarchy override feature you can do so.

The difference between the hierarchy override and the seasonal price hierarchy is that overrides should be used when there is a temporary change on a unique, certain occasion and the seasonal hierarchy should be used for recurring longer time periods such as different seasons and/or certain days of the week.

To set up your hierarchy overrides in Atomize, learn more here.

Price override (fixed)

A price override allows you to override the current price. It is sticky, meaning that it will stay until you actively remove it by choosing to accept a new price recommendation.

A price override is allowed to break the price hierarchy, however your default price hierarchy configurations are set up. In other words, no matter what default price hierarchy you have configured you can always override a price without that it is having an impact on other room types' prices. 

To set up your price override in Atomize, learn more here.

Near-time pricing rules

You can apply price rules for dates approaching arrival to ensure that you don't get any sudden or unwanted price changes in the last hours or days. 

If a hierarchy is changed or overridden, the price rule applied will adjust to the newly configured price limits. However, a fixed price override always takes precedence regardless of which rule is applied.

To set up near-time pricing rules, learn more, here. 

Hierarchical order of pricing controls

One stay date can have multiple price controls applied, to understand the order in which they apply, read more here.