Aspenware now offers resorts the opportunity to dynamically price add-ons. The benefits of this include enhanced revenue opportunities and an improved guest experience.
Below, we detail the new features and the impact they can bring to your store.
Add-on products are now priced the same as core products
Add-on products will now reflect the same pricing structure as core products, ensuring consistency across the product selection. If base price is added, it will appear as the max price on the selector.
Add-ons still cannot have required attributes. To handle this, the attribute ‘Start Date’ must be added to the add-on product, and [Date] should be included as a text prompt. However, the date should not be set as a required field for the add-on product. This functionality remains unchanged from the current behavior of dated add-ons.
Since add-ons can now be dynamically priced, the “Is Dynamically Priced” product classification must be applied to any dynamically priced add-on product, just as it would be for a core product.
For an add-on product to be dynamically priced, it must follow the same rules as a core product, requiring at least one attribute combination to be priced. This means:
Add-ons must be configured as “Attributed Add-Ons” to enable dynamic pricing.
They can have just one attribute combination, which can be mapped to a dummy attribute on a core product or potentially left unmapped.
IMPORTANT: In version 3.7, dynamically priced add-ons must have pricing defined for every date that the core product is priced. If any add-on variant is missing pricing for dates when the core product is available, it will be sold at $0. This issue will be resolved in version 3.8, but as this is a pilot release, the fix is not included in version 3.7.
No changes to add-on setup or pricing (Levels cannot cascade across products)
While we’ve made enhancements to pricing and display, there are no changes to the way add-ons are set up. Pricing tiers still do not cascade across products, so you’ll continue to manage each product's pricing independently.
Scenario 1: Pricing Levels (Tiers) Move Independently
In this scenario, pricing levels (tiers) for similar products move independently:
Example:
Product A: Stand-alone Snowshoe Rental
Product B: Add-on Snowshoe Rental
Sales for Product A will not impact the pricing levels (tiers) of Product B, and vice versa. Each product adjusts its pricing levels (tiers) based solely on its own sales activity.
Scenario 2: Pricing Levels Move Together
In this scenario, pricing levels (tiers) are shared and move together.
Example:
Product C: Sunrise Snowshoe Hike (includes Product B as an add-on)
Product D: Moonlit Snowshoe Hike (includes Product B as an add-on)
Both Product C and Product D offer Product B (Add-on Snowshoe Rental) as an add-on. In this case, sales of Product B as an add-on—whether through Product C or Product D—will decrement the pricing tiers of Product B. This would result in price increases for the add-on across both products.
Enhanced data structure for item summary to support dynamically priced add-ons
We’ve improved the underlying data structure used by the item summary to support dynamically priced add-ons. Although the design of the item summary has been updated, there are no functional changes to it. These data structure changes allow dynamically priced add-ons with a base price configured to display price and savings information in a more seamless and consistent manner.
Before
After
Dynamically priced add-ons now display updated pricing once a date is defined
If an add-on is dynamically priced, its price will now appear once a valid date is set. Furthermore, if a base price is defined for that date, savings information will be shown, encouraging customers to select the add-on and helping to drive conversions.
New Note Alert for unavailable add-ons
A new alert is displayed above dynamically priced add-ons (inventoried/cutoff in the future) that are not yet selectable due to dates not being set. This customizable note, available through language strings and Theme Designer (TD) options, informs users when add-ons are disabled because the date is not set yet, preventing confusion and improving the shopping experience.
Language String | Default text | Notes/Location |
|---|---|---|
cloud.notification.note | Note | 
|
publicui.product.note.selectdate.pricing | Select a date to view prices | 
|
Future-Ready Functionality
Built with scalability in mind, with upcoming support for inventoried and cutoff add-ons to further expand flexibility.