With great pleasure, Aspenware presents Aspenware Commerce 2.21. This release is compatible and must be deployed jointly with Aspenware Identity version 2.11 and Aspenware Unity version 3.16.
Updates, Features, and Upgrades
Ikon Pass Friends & Family Integration
Aspenware is excited to provide integration for Ikon Pass Friends & Family entitlement holders. With this new plugin, resorts that offer Friends & Family discounts for Ikon Pass holders can redeem them through the local resort’s Aspenware Commerce platform, eliminating the need to visit a service desk to redeem these discounts. This plugin will install a component on the discount ticket product detail page that enables Ikon Pass login and returns and displays available entitlements. Adding to cart decrements available entitlements visually and prevents guests from adding more entitlements than are available to the user (see Release Guide for limitations). Once a purchase is complete, entitlements are updated/deducted in the Alterra database. For configuration information see the 2.21 Release Guide for Ikon Pass Friends & Family Plugin. For more details on the guest flow and value of turning this feature on at your resort, please read https://hub.aspenware.net/main/Announcing-IKON-Pass-Friends-&-Family-Discount-Redemption.1980170312.html .
IMPORTANT: Enabling this feature does require an annual feature subscription fee. Talk to your Aspenware representative about adding this feature to your Aspenware Commerce subscription.
Heartland Payment Gateway
Aspenware is excited to expand options for credit card processing to include Heartland Systems, one of the largest providers in the USA. Our robust integration also supports tokenization in conjunction with RTP|One V. 2021. For more information and configuration details, see the 2.21 Release Guide - Heartland Payment Gateway .
Print at Home for Siriusware
Print at Home functionality is now available for resorts that use Siriusware as POS. This feature - previously only supported for RTP|One - activates upon the purchase of specific products, sending a follow-up email containing barcodes to be used for access control when scanned onsite by native POS scanners. For more information and configuration details, see the 2.21 Release Guide - Print at Home Ticketing.
Arrive Parking
Working with two third-party vendors, Arrive Parking and Hoorooh Digital Services, Aspenware now enables resorts to sell parking through the Aspenware store where the availability and pricing are managed within Arrive Parking. This parking integration supports displaying a new custom product detail page (PDP) that is purpose-built for easily showing parking availability and pricing across multiple lots. Parking inventory limits and pricing that are managed in Arrive are displayed and enforced within Aspenware Commerce in order to sell parking products. When these parking products are sold, they are routed to Arrive Parking as the fulfillment system. In addition to enabling the sales of parking products within Aspenware Commerce, refunds that are initiated within Arrive’s ParkWhiz app are routed to Aspenware Commerce, where Unity triggers the refund to Payeezy and returns the result to Arrive for display on the ParkWhiz app. For more information and configuration details, see the 2.21 Release Guide - Arrive Parking.
NOTE: This enhancement is currently only available to customers who have partnership agreements with Arrive Parking and Hoorooh Digital Services. Also, refunds are only available to resorts using Payeezy as a payment gateway.
Resolved Issues
Memory fixes - Aspenware Commerce will now run in 64-bit mode, which resolves a memory-related issue some sites were experiencing. This fix requires a web configuration setting change and will be automatic for every site upon updating to version 2.21.
Resort initiated configuration steps: If you receive an “out of memory” error when navigating Aspenware Commerce admin or if Azure indicates a memory issue and you are on version 2.21 or later, check with your Aspenware Representative to ensure your store is running in 64-bit mode.
For Fast Flow products, scanning a QR code to populate media ID does not work on Chrome, which impacts Android users. Note that this fix requires a web configuration setting change.
Resort initiated configuration steps: If experiencing this issue on any version 2.21 or later, contact your Aspenware representative about updating the web configuration for the “Feature Policy” section to set the i“camera mode” to ‘self.'
On the large pricing calendar, dates that are not defined with inventory in the POS are showing as sold out rather than crossed out. Note that the small calendar that appears on the product detail page does not follow this exact same logic and dates that are not priced and do not have defined inventory will continue to display as sold out when hovered over (see known issues below). To determine which message/treatment is given to dates on the large pricing calendar, the following logic is used:
If dynamic pricing is not configured for a date, the date shown crossed out, no sold-out messaging will appear on the large even if inventory comes back 0 for that date.
If dynamic pricing is configured and inventory is configured on a date and if inventory is sold out or not present for a date, the date will show as sold out.
If dynamic pricing is configured and inventory is configured on a date and inventory is available on that date, show price.
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 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. A workaround is to turn off autofulfill on these products. (Also see Unity 3.16 Release Notes.)
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. A workaround is to turn off non-consecutive date selection or switch to Unity for order placement. (Also see Unity 3.16 Release Notes)
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. (Also see Unity 3.16 Release Notes)
Better error messaging for guests who do not have a birth date defined on their profile but try to login through Aspenware Identity.
Resort-initiated configuration steps: Work with your Aspenware Representative to update the content displayed to a guest when they try to log in but required information is missing from their account, requiring them to call. The associated string is account.create.informationmissing. (Also see Identity 2.11 Release Notes).
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 capability is now disabled, so only the card used to pay for the transaction can be stored as the primary (resort charge) credit card profile and this primary card will be stored as a tokenized value.
For orders that have multiple vouchers assigned to the same recipient, only the first voucher is getting assigned to this recipient. (Also see Unity 3.16 Release Notes)
Cannot create new subscription types in Aspenware Admin.
If a resort uses Aspenware Identity for authentication and if click tracking was turned on in SendGrid, for some email clients (namely Outlook 365), the URL for password reset links exceeded the URL length parameters for that email client and would get truncated, returning invalid. (Also see Identity 2.11 Release Notes).
Resort-initated configuration steps: If you previously disabled click tracking from SendGrid, and wish to enable this, enable this setting in SendGrid and test a password reset flow using Identity.
For resorts that use a combination of Aspenware Identity and the Loyalty feature in Commerce, when guests are asked to enroll in the Loyalty Program from Identity, the content next to the enrollment checkbox now supports some HTML. See documentation for additional details on supported HTML. (Also see Identity 2.11 Release Notes).
Resort-initiated configuration steps: Reach out to your Aspenware Representative with the desired content to be displayed next to the Loyalty opt-in checkbox within Identity after reviewing documentation.
For the Capture of Additional Customer Data feature, when capturing zip code only, data always sends back USA as the country in the RTP|One address profile regardless of the resort’s location.
Resort-initiated configuration steps: If you are leveraging this feature and are located outside of the USA, additional configuration within Aspenware Commerce Admin is required. From within Configuration>Countries, ensure to ensure the proper default country is set by changing the Display Order of the default country to 1 and if the default country is something other than the U.S., change the display order of the U.S. to 100.
The issue identified with Dynamic Pricing Reimagined can be resolved by running a specific script in customer environments. Aspenware will reach out about re-enabling this plugin and running this script to unlock the improved dynamic pricing functionality in your environment.
Known Issues
For Arrive products, the add to cart button has a formatting issue that presents itself differently on the different resort’s themes that we didn’t see internally. This will be fixed in a 2.21.1 hotfix.
Guests who do not have a birth date defined on their profile are not able to log in through Identity.(Expected to be resolved in 2.23 - the next major release)
On very few payment plan payments when a certain error is returned, the customer is successfully charged more than once but shows as failed payment in Aspenware Commerce. (expected to be resolved in 2.23 - the next major release)
On order confirmation emails, the assigned guest’s name is not displayed. (expected to be resolved in 2.23 - the next major release)
Some resorts have reported that the order history page “bleeds off the page” and this appears to be theme specific and will be handled case by case. If you notice your site experiencing this, contact support@aspenware.com.
On the calendar on the product detail page (PDP), dates that are not defined with inventory in the POS are showing as sold out rather than crossed out. This is resolved on the large calendar, but not for the small PDP calendar.
Phone prefix is not being sent to RTP|One when the phone number is collected in checkout.
When a phone number is updated in My Account, it is resulting in an invalid number being added to the beginning of the phone number in RTP|One.
For resorts using Identity, if you create an account with an email that already has an authentication profile associated with it and gets an error that the email already exists, then change the email to an email that does not have an associated authentication profile, the error persists until you exit the create account page and re-enter. (expected to be resolved in 2.23 - the next major release)
Aspenware Identity doesn’t automatically redirect the guest back to the PDP they were on prior to selecting to sign in unless they explicitly use a redirect URL where sign-in is required. This is a feature enhancement to Identity. (expected to be added in 2.23 - the next major release)
A few cosmetic enhancements for the “pay-with-points” Loyalty module will be added to the 2.22 release.