Ceiling/Floor

1. Click , then Decisions, and then Pricing Configuration.
2. Click to edit the Primary Priced or Independent product.
   The Definition page displays.
3. Click the Ceiling/Floor tab.

Before you use Suggest, ensure the Offsets, Supplements, Rounding Rules, Base Room Types, and Special Event setup is correct. Those configurations impact the suggested values.

How to use Suggest

In this example, it shows how to save the suggested values as a draft. To accept the draft values and replace the values in the Current Configuration tab, click Save.

1. Click Suggest. If the Suggest option is not available, enter values manually.
   A new Draft tab opens with the suggested Floor and Ceiling values for the Base Room Type of each Room Class and, if applicable, Seasons.
2. On the Draft tab, review the Ceiling, Floor, and if applicable, Season values by day of week to ensure they meet your business needs. Make changes, if needed.
   Note: for Price Excluded Room Classes, no values are suggested, and you enter the fixed price.
3. If needed, click Export to Excel to review suggestions on a spreadsheet.
4. Continue with any of the following actions: 
   • Click Clear to remove all suggestions and enter your own.
   • Click to delete the Draft completely.
   • Click Save as Draft to continue your review later.
   • Click Save to accept the draft values and replace the values in the Current Configuration tab.

1. Enter the Ceiling and Floor values for each Base Room Type and day of the week:
   1. Enter the Ceiling and Floor values in the Value field. The value populates each day of the week.
   2. Press the Tab key to navigate to each day of the week to edit each value, if needed.
2. If needed, click Export to Excel to review suggestions on a spreadsheet.
3. Click Save.
4. Continue your pricing setup with Offsets to price other room types within a Room Class differently, if needed.

If you have a complex setup with many seasons, or you manage pricing data for multiple properties in one place, or both, use the upload option.

1. Click Export to Excel to download the template with the current values.
   Note: Importing replaces the old values and you can't recover them.
2. Save the workbook to a location on your computer.
3. Add the new values or change existing values as needed.
   For details on entering the data, use the Upload Instructions tab in the Excel file.
4. If you made changes, save the modified workbook in an XLSX format.
5. Click upload . A warning message displays, click Yes to continue.
6. Navigate to and select the saved workbook, then click Open.
   G3 RMS checks the workbook for data and formatting errors. If the system finds no errors, it displays the imported data. If it finds errors, it cancels the import and tells you which rows have errors. Click the export icon to export the error list. Correct the errors, then re-import the workbook.

If you entered your default pricing setup without suggestions, use the following steps to create optional seasons. For example, during your high demand season, the lowest rate that you want to sell might be higher than during the rest of the year.

1. In the Seasons panel, click Add .
2. Add a Season Name. You can refer to this name later if you want to copy a season to create another.
3. Type or select the Start Date for the season. The Start Date must be greater than or equal to the System Date.
4. Type or select the End Date for the season. The End Date can be any future date and is not limited by the forecast window.
5. Change the default Ceiling and Floor values for each required Base Room Type and day of the week. If you have already created a season, you can also use the Copy From menu to copy an existing season's values.
   1. Enter the Ceiling and Floor values in the Value field. The value populates each day of the week.
   2. Press the Tab key to navigate to each day of the week to edit each value, if needed.
6. Click Save.

How G3 RMS handles changes that lead to overlapping seasons:

If you add seasons that lead to overlapping dates, G3 RMS follows these rules:

• If you add a new season in the middle of an existing season, G3 RMS splits the existing season into two seasons, one before the new season and one after the new season. These two have the values of the original season. The new season has the new values.
• If you add a new season that partially overlaps (later start date, same end date as existing season), two seasons result. The new season and its values apply to the overlapping dates.
• If you add a new season that includes all the dates of an existing season, the new season takes over and its values replace those of the existing season.

When G3 RMS suggests Floor and Ceiling values, it checks and, if needed, creates up to four seasons per year for the next two years where pricing differs from the default values. It also creates a season for each recurring Special Event that had either a higher or a lower pricing structure than normal days. Review and change the season, if needed.

1. If necessary, change the selected checkboxes to view only Present or Future seasons. Or use the search box to filter by name of the season.
2. Click Edit for the season that you want to edit.
3. Change the Season Name, if needed.
4. Type or select a new Start Date for the season, if needed. To be changed, the Start Date must be greater than or equal to the System Date.
5. Type or select a new End Date for the season, if needed. The End Date can be any future date and is not limited by the forecast window.
6. Type new Ceiling or Floor values for each day of the week, as needed.
7. Click Save.

You can completely delete a future season (with a Start Date after the System Date). When you delete a current season, G3 RMS splits the season and deletes only future dates. You can't delete past seasons. G3 RMS deletes past seasons based on the data retention policy.

1. Click Delete for the season that you want to delete.
2. Click OK.

G3 RMS learns price sensitivity for each price point from past reservations. In the example of a historical range from 100 to 200, the system has learned the price sensitivity for these prices from past guest behavior. Because you have never sold rooms at 250, the system has not learned the price sensitivity for that price point yet. Until G3 RMS can learn from actual behavior, it assumes the price sensitivity is the same as for the closest known price point (200, in this case).

If your property uses a Limited Data Build, projections replace the missing historical data. Make sure that the ADR in the projections aligns with the price range that you set up.

The system learns quickly, so use small increments if you want to explore a lower or higher pricing strategy than in the past. In the above example with a historical range of 100 to 200, don't change the range to 100 to 250 or 70 to 200. Instead, start with 90 or 220, and let the system learn while you monitor the forecast and decisions. Then, if successful, expand the range.

If you used a price point in the past for only a handful of dates (for example, only during high-demand special events), do not make it the default Ceiling value for the year. Instead, set up a season when that price point is the Ceiling value. The reason is the same as why you should start with your historical prices, namely how the system learns price sensitivity. If you use the highest price as the Ceiling for the full year, G3 RMS likely will use it over other dates with less demand until it learns the true price sensitivity over non-peak demand dates.