Overview: Dynamic Pricing

This feature is supported for: All versions of Aspenware Commerce. The product must have a date to leverage this functionality.

This feature is not supported for: Non-date based products.

HINT: A video training of the Dynamic Pricing module in Version 2.20 or later is available. The Dynamic Pricing training portion begins at 7:59.

Key Terms

Time Period Group (TPG) - (formerly called Season Type in Legacy Dynamic Pricing)

A Time Period Group (season type) is a collection of Time Periods that share the same pricing rules. Only one Time Period Group can be assigned to a product, but a Time Period Group can have many Time Periods assigned to it. All Time Periods within a specific Time Period Group are assigned to the product when the product is assigned to the corresponding TPG. Examples of Time Periods that could be applied to the TPG EARLY FALL: September/October Weekend, September/October Weekday.

Time Period (formerly called Season in Legacy Dynamic Pricing)

A Time Period (season) is assigned to a Time Period Groups (TPG). A Time Period (season) is a collection of dates that share the same pricing rules. A season creates a “template” of dates from which an administrator can apply pricing rules across a set of dates. Examples of a Time Period might be Early Fall, or Pre Season. Only one Time Period Group can be assigned to a product, but a Time Period Group can have many Time Periods assigned to it. 

Days to Arrival (formerly called Override Windows in Legacy Dynamic Pricing)

Rewarding a customer a discount for purchasing in advance starts with defining DAYS TO ARRIVAL window. Specifically, the value reflects how many days in advance the customer is booking from the start date of that trip. Common Days to Arrival Windows (formerly called override windows) examples include:

  • 48 hours+ pricing - resorts often charge a lower rate to guests who are not last-minute bookers.

  • Within 48 hours - resorts often charge the window rate or a slightly lower rate than what they would pay at the window.

  • 30+ days - resorts may offer a larger discount if a guest books farther in advance

Max Price (Formerly known as Base Price or Old Price)

The Max Price represents the “Window” or “Rack Rate” of a product. It's used to calculate the percentage discount for any online price and is required to display the savings compared to the window rate. Max Prices can be displayed alongside the online prices crossed out in the cart notice and product detail page (PDP). Showing a crossed-out price helps guests see the savings they’re getting by purchasing online.

For dynamically priced products, the term Base Price is used interchangeably with Max Price in the Admin. The base price should be the first price set in the Pricing Calendar and is reflected in the variants list. When defining the base price, avoid applying tiers.

For non-dynamically priced products, the term Old Price is used synonymously with Max Price in the Admin. This price also represents a maximum amount for the product that would be charged at the window.

Levels (formerly called Tiers in Legacy Dynamic Pricing)

A Level (tier) is defined as a pricing tier in which there are defined quantities for a set price. Once that set price has sold out, the next tier (often with a higher price) will take into effect. Levels should be generated in the order in which they are to be consumed, as the priority is set at creation. Use the description field to distinguish between tiers. Priority 1 ties are consumed first. For example:

  • Tier 1 - $50 - 5 tickets available for purchase

  • Tier 2 - $60 - 10 tickets available for purchase

  • Tier 3 - $70 - 10 tickets available for purchase

  • Tier 4 - $80 - Unlimited tickets available for purchase

Feature Description

The Dynamic Pricing feature within Aspenware Commerce enables resorts to utilize date-based pricing so that flexible prices can be set based on current market demands. Resorts can change prices based on date windows that take advantage of high-volume days of the week, holidays, or weekends. Dynamic pricing enables pricing that accounts for historical sales data, current demand behavior, and how far in advance a guest is purchasing.

The following types of products can be set up for dynamic pricing:

  • Products where price changes depending on the reservation date (e.g. during a certain season or on weekends, a product is sold at a higher price).

  • Products that are not available every day of the season but do not use inventory pools to narrow available dates.

  • Products that you wish to display the pricing calendar in order to display how much inventory is left throughout the season.

  • Products that you wish to charge more on more popular dates based on current demand behavior, using levels (formerly called tiers).

  • Products that you wish to use historical data to charge more on more popular dates, using seasons.

  • Products that offer discounted pricing to guests who book further in advance and then charge higher rates to “last-minute bookers,” using Days To Arrival windows.

  • Products that you desire to show the larger pricing calendar alongside.

Display options

Resorts have the option to display a large interactive calendar. By default, the standard calendar will display but resorts can utilize a store-wide feature to enable a more custom calendar appearance, detailed configuration and options can be viewed in Advanced Dynamic Pricing Calendar.

Large Calendar

The standard large pricing calendar displays a view where guests can select different attributes such as Age, Number of Days, etc that will change the values displayed on the calendar. Based on the configuration in Aspenware, guests can see:

  • The number of tickets left at a specific tier

  • The % savings off the window rate (calculated against the base price defined within dynamic pricing)

  • The price for available dates

  • The remaining quantity left at the pricing tier, if configured with ‘levels, and the remaining quantity left is below the defined threshold.

  • Available inventory if configured with inventory in the POS and the remaining inventory left is below the defined inventory threshold.

  • When a date is sold out

  • When a date is not available

Use the chart below to compare how the new Cloud UI Redesigned Pricing Calendar stacks up against the standard Commerce calendar and the Advanced Pricing Calendar.

Scenario

Commerce Pricing Calendar

Commerce Advanced Pricing Calendar

Cloud UI Pricing Calendar

Scenario

Commerce Pricing Calendar

Commerce Advanced Pricing Calendar

Cloud UI Pricing Calendar

Product uses tiered pricing, and the threshold has been hit to trigger the “Only 10 left at this price!” message.

A banner shows how many are left on all dates with price scarcity.

Background of dates with price scarcity can be shaded and the legend may be customized.

Banner indicating how many left display.

Dates with only price scarcity have green text and no background shading.

Banners showing how many are left have been removed to simplify pricing information presented to the guest.

Product has inventory and has reached the threshold to trigger messaging that inventory is low for that date.

A banner shows how many are left on all dates with inventory scarcity.

 

Background of dates with inventory scarcity can be shaded and the legend may be customized to indicate plenty, low inventory, and sold out uniquely, and customize the legend for each status.

A banner indicates how many are left on that date.

If date has both inventory and price scarcity, dates with price scarcity have red text. Red text is not customizable and has no legend.

Triggered dates are shaded yellow. The yellow color is configurable in the Aspenware Styling pluginr, but we recommend #F6D241 for ADA compliance.

A legend for background shading is available to help with user comprehension.

 

 

Product has inventory and sold out threshold has been triggered.

Sold out dates show the day in grey, have a grey diagonal slash through them, and have the words “SOLD OUT” displayed.

(Note that this treatment is different from the “Unavailable” treatment for days in the past, past the cutoff time, etc. Unavailable dates will simply have a light grey date and not be clickable.)

Sold out dates have a grey background, and the legend value for sold is customizable.

 

Sold out dates have a grey background, and the legend value for sold out is customizable.