How to set pricing recommendations in Atomize RMS by Mews FAQ

Revenue managers or system administrators set up and manage the price hierarchy in Atomize during onboarding or when updating the property’s pricing strategy. The hierarchy defines the minimum and maximum prices for each room type, giving Atomize a pricing range to optimize within. This setup supports dynamic, demand-based pricing while keeping rates under your control. You manage the price hierarchy in Atomize, under the Settings menu.

This article answers the most frequently asked questions about price hierarchies in Atomize.

 

In this article, you can find answers to the most frequently asked questions:

 

How to use the Price hierarchy in Atomize?

A price hierarchy sets the minimum and maximum price for each room type. It ensures your prices stay within the limits you define. You can:

  • Use a default price hierarchy for all dates

  • Add up to 10 seasonal price hierarchies for specific periods or days of the week

  • Enable a tiered price hierarchy to group room types and apply flexible pricing

Note: Atomize applies your price hierarchies to all future years unless you update them.

 

How do I edit the default price hierarchy?

You can learn how to edit the default price hierarchy in our help article: How to set up or change the minimum and maximum price boundaries in Atomize RMS by Mews 

 

What is a tiered price hierarchy?

A tiered price hierarchy gives you more flexibility by grouping room types into tiers. You can independently price rooms within the same tier, while the price structure still maintains a logical order between tiers.

 

This setup helps you:

  • Allow each room type to follow its own demand pattern

  • Maintain consistent pricing logic across tiers

  • Maximize revenue with more dynamic control

Note: The tiered hierarchy is ideal if you want flexible pricing without sacrificing structure.

Read more about tiered price hierarchies in the help article: Tiered price hierarchy in Atomize FAQ

 

What is a seasonal price hierarchy?

A seasonal price hierarchy lets you set different pricing rules for a specific time period. You often use it for high-demand seasons or recurring weekly patterns.

To create a seasonal price hierarchy:

  1. In Atomize, click Settings > Seasonal price hierarchy

  2. Click + Add alternative price hierarchy.

  3. Complete the following fields:

    1. Name: Enter a name.

    2. Dates: Click to select the active date range.

    3. Price boundaries: Enter price boundaries for all or selected days of the week.

  4. Click Save.

Note: You cannot set overlapping time periods. Days not included in the seasonal hierarchy follow the default hierarchy.

 

Can I set different price rules for different days of the week?

Yes. When setting up or editing a seasonal hierarchy:

  1. Under Price hierarchy ruleset, click Custom.

  2. Choose one or more days and enter the price boundaries for each room type.

  3. To add rules for other days, click + Add additional ruleset for other days of the week.

  4. To remove a rule, click Remove additional ruleset.

  5. Click Save.

Note: If you do not configure certain days, those days follow the default price hierarchy.

 

How do I see when seasonal hierarchies are active?

Use the calendar overview on the Price hierarchy page. Each seasonal hierarchy appears in a unique color. In the calendar, you see:

  • When each seasonal hierarchy is active

  • Which days of the week it applies to

  • Both the current and next calendar year

 

What is the price range boundaries graph?

The price range boundaries graph shows a visual summary of your minimum and maximum room prices. It reflects:

  • The lowest price for your cheapest room

  • The highest price for your most expensive room

Note: This graph does not show price overrides or weekday-specific differences.

 

What happens if my changes create pricing conflicts?

If your new configuration causes conflicts with current prices, Atomize prompts you to accept suggested changes. These changes update affected prices to match the new hierarchy.

You must accept the changes to apply the new setup.

 

Was this article helpful?
00



Feedback