2.20 Commerce Release Notes

Owned by Leigh Bush, created
Last updated: Mar 24, 2023 by Sarah Holst
7 min read

Published Sept. 18, 2021.

With great pleasure, Aspenware presents Aspenware Commerce 2.20. We’re excited to offer more functionality alongside our newly released Fast Flow functionality, including a new way to redeem Mountain Collective days at participating resorts. Experience an improved flow when configuring dynamic pricing within the Aspenware Commerce administration. We’ve also addressed several high-priority bugs.

 

Updates, Features, and Upgrades

Dynamic Pricing Reimagined

Dynamic pricing is a powerful tool that if used well can drive yield significantly. Some resorts use dynamic pricing daily to adjust to changing demand with great success; however, due to the complexity of configuring this feature and issues that could arise when adjusting dynamic pricing, this tool was often used in a set-it-and-forget-it manner. Aspenware is thrilled to announce Dynamic Pricing Reimagined. Now, dynamic pricing can be configured from the product editor screen with our easy-to-use wizard. Once configured, the reimagined pricing tool makes on-the-fly updates easy to manage and significantly reduces the overall time spent setting up and managing product pricing. See the Reimagined Dynamic Pricing documentation for more information.

Fast Flow Enhanced, Advanced Product Configurations to be used in Combination with Fast Flow

Fast Flow, released in 2.19, allows guests to scan media QR codes or enter media IDs on the product detail page to allow for quick product assignment even for guests who have not logged in or are not a part of the shopper’s household. When combined with Selective Guest Checkout, Aspenware Fast Flow becomes a streamlined flow with the fewest steps to purchase yet. Now, in addition to Fast Flow working in combination with simple product configurations, Fast Flow also works with many advanced product configurations. See the Reservation Products documentation for more information.

  • Reservations with Fast Flow - Aspenware has added new functionality to our Fast Flow and Reservation plugins, allowing them to be used in combination. Prior to this release, a guest had to log in before they could add a $0 fenced reservation product to the cart. Now with Fast Flow + Reservations, reservation products can be configured so that a guest can validate that they are eligible for a reservation product by entering or scanning their media code or entering their Mountain Collective voucher code (read more below).

  • Assignment Stored Procedures with Fast Flow (Specifically a Mountain Collective Redemption Procedure) - Fast Flow and Validated Prompts that are set up to validate customer assignment can now be used in combination. There are many unique applications for using these features together to support your fenced product requirements, including offering a one-stop flow for Mountian Collective or IKON reservations. Aspenware already supports the redemption of Mountain Collective days with its voucher functionality so that these guests can bypass your ticket line; however, now using its new custom Mountain Collective product configuration, which combines Fast Flow, Reservations, and a custom Stored Procedure, you can enable the entire redemption and reservation process in a single product. First, guests validate that they are eligible to redeem their Mountain Collective days at your resort by entering their voucher code online. When they enter their voucher code for the first time they are auto-created as a customer in your RTP|One. Second, they can load access for days they wish to ski onto new or existing resort media and the shop restricts guests to their allowed number of days. Finally, these guests can re-enter their voucher ID to see their reserved days and can cancel/change the dates of their reservation themselves. Submit a helpdesk ticket asking for a professional services project to discuss how to enable this or other custom stored procedure functionality in your store for the coming season. We expect these product configuration options can reduce staff overhead and guest frustration around selling certain fenced products.

  • Customer Assignment with Fast Flow - Aspenware’s Fast Flow feature now works alongside functionality that enables logged-in guests to assign products to their household members on the product detail page. Fast Flow and household assignment work as an “either-or” method of assignment, either I assign the product through Fast Flow or I assign the product through customer assignment on the product detail page. This means if a logged-in customer wants to load some Fast Flow products to existing members of their household by selecting their name instead of entering their media ID and other products to members outside of their household by entering or scanning their media IDs, they can.

  • Age Rules with Fast Flow - Aspenware’s Fast Flow feature now works alongside RTP|One configured Age Rules. If a product is configured with Fast Flow and has age restrictions on the product header being sold in RTP|One, then upon entry of the media ID, the customer whose media ID is entered will be checked for both media and age eligibility. If the customer is not eligible, they will be returned invalid with an error message indicating why. Note that Aspenware Age Rules will not be used for Fast Flow age restrictions, only age rules configured in RTP|One will be applied to Fast Flow products.

  • Attributes with Fast Flow - Attributes are also supported with Fast Flow, so if a product has an “Adult” and “Child” variant option, the entered media will be re-checked for eligibility upon attribute change and if the previously validated customer is not eligible for the new variant, perhaps because they are too old, an error message will indicate why.

Resolved Issues

  • Redirecting guests to checkout when logged in through Identity

    • Previously when a guest selected to checkout and was not logged in, once they authenticated through Aspenware Identity they were not being redirected to the checkout page, but to the store. This issue is fixed.

  • Fast Flow QR code scanner retry

    • Previously when using the Fast Flow QR code reader functionality, released in 2.19, if the initial scan came back invalid there was no way to try again outside of refreshing the page. This has been fixed.

  • Fast Flow subsequent invalid media entry showing as valid if preceded by a valid entry

    • After a customer has been validated by entering in or scanning their media ID, a subsequent invalid media entry will remain assigned to the initial validated customer. This issue has been fixed.

  • Enforcing Cross-Sell Display Limits

    • The setting to limit how many times a cross-sold product is presenting is not always being respected. This issue has been fixed.

  • Tax Rounding on Payment Plan Payments resulting in an out of balance between RTP|One and Aspenware Commerce

    • When payment plan payments had tax configured in RTP|One, for some specific dollar amounts, the tax amount would be reported to RTP|One off by a cent or two, resulting in an out of balance. This has been fixed.

  • Payment Plan Payment Modal on the PDP

    • In 2.19, if a product is configured as an Aspenware Payment Plan product the “View Payment Schedule” modal is failing to trigger on the product detail page and in your cart. This has been fixed.

  • Add On selection not updating the price on the product detail page

    • In 2.19, if an add-on option is selected on the product detail page, the price shown next to the add to cart button was not reflective of the core product price + the add-on product price, though the price in the cart was correct. This has been fixed.

  • Occasionally EZLinks Tee Time products quantities are adjusting during checkout to invalid quantities. This issue has been fixed.

  • For EZLinks Tee Time products, the cart ID from Aspenware Commerce is now being sent to the Trans # in EZLinks. This will result in better data to troubleshoot future issues.

Upcoming work

IKON Friends and Family Ticket Redemption using integration into IKON Identity and API

Heartland Payment Provider Support

Enable parking product sales using Arrive (3rd Party) as the Parking fulfillment system

Known Issues

  • Capture of Additional Customer Data feature does not work for checkout data capture in this version (Fixed in 2.20.2)

  • Opt-out of Marketing Checkbox is not present on Create Account or My Account (Fixed in 2.20.2)

  • When a product uses multiple inventory locations and is set to autofulfill, if a customer orders multiple inventoried products across locations, the locations are getting incorrectly assigned to the first location upon autofulfil. Work around is to turn off autofulfill on these products.

  • For orders that have multiple vouchers assigned to the same recipient, only the first voucher is getting assigned to this recipient.

  • If using RTP Connect and products that are set up as non-consecutive date selection with add ons, the wrong price for these add ons is passed into RTP|One on order complete. Work around is to turn off non-consecutive date selection or switch to Unity for order placement.

  • When using the new Fast Flow with Reservations functionality, reserving two different people for the same day is incorrectly assigning both reservations to the first person.

  • When using Payeezy as the gateway and resort charge is enabled, guests are allowed to define a credit card that is not the card being used for the order for resort charge. This should be disabled as a different card number will not be stored as a tokenized value.

  • For Fast Flow products, scanning of a QR code to populate media ID does not work on Chrome, which impacts Android users.

  • On the large pricing calendar, dates that are not defined with inventory in the POS are showing as sold out rather than crossed out.

  • For Aspenware Payment Plans, payment plan payments with tax configured are experiencing a tax rounding discrepancy between what is sent to RTP|One and what the customer paid for certain payment amounts.

  • Do not enable the Dynamic Pricing v2 plugin/functionality in this version. A bug was found that where if you edit a product that does not have dynamic pricing added to it, the base window is getting automatically created, which could result in dates that are available showing as unavailable. Aspenware has gone ahead and disabled this plugin from all test and production stores on this version. We have also fixed any products that might have already been impacted by this issue to prevent future issues. (Expected to be fixed in 2.21)