Aspenware is happy to present Aspenware Commerce 2.13.0 - 2.13.23. In these releases, we’re introducing enhancements to voucher redemption, new functionality for AxessPUB reload for Siriusware resorts, waiver enhancements, inventory enhancements, and several priority bug fixes. Please also see the 3.8 Unity Release Notes Aspenware Unity release notes for additional enhancements and fixes.
...
1Risk Waiver Enhancements for Siriusware resorts
Enhancements to the Product Detail Page
...
Features and Updates
Configurable waiver text
...
For more information see Aspenware Commerce 2.13 Release Guide - Product-discount and Discount Vouchers.
Dedicated voucher validation page
In addition to offering voucher validation through the new voucher banner as well as My Account, Aspenware Commerce now offers an optional dedicated voucher validation page. This page, which is unique from a PDP, can be linked to from anywhere. When a voucher ID is entered, the guest is navigated through the existing validation modal and, if successful, will be prompted to redeem their voucher. As with all voucher validation, in the case of a product or product/discount voucher the guest will be navigated to the appropriate PDP; in the case of a discount voucher, the guest will be prompted to carry on shopping in the case of a discount voucher.
Inventory Pool Improvements
...
for subscriptions where the status is active, the admin can change the next payment date only if it’s a date in the future.
for subscriptions where the status is frozen or canceled, the admin can set the next payment date to a future date, even if the next payment date is in the past. After the admin changes the next payment date to a future date, the admin must then also change the enrollment status to Active.
Dedicated voucher validation page
...
Address Syncing to POS now supported for Square payment provider
Previously, if Square was configured as a payment provider, a full address beyond zip code could not be collected or synced to the POS. Our integration of the Square payment API does not have address verification beyond zipcode, and our integration still does not have address verification beyond zipcode, however, if desired, Billing Address can be collected on the payment step and synced to the POS. The downside of enabling this is that zip code will be asked for twice.
...
Resolved Issues
Private Lesson Comments Longer than 255 characters caused order failures
...
Previously, if guests continued selecting Add to Cart repeatedly, they could continue adding to cart to add more inventory than was available. They couldn’t check out (and received a message explaining that inventory was not available), but they could add to the cart. This issue is resolved and guests will now receive a ‘toast’ message on the PDP when they attempt to add more to the cart than is available.
Address Syncing to POS now supported for Square payment provider
Previously, if Square was configured as a payment provider, a full address beyond zip code could not be collected or synced to the POS. Our integration of the Square payment API does not have address verification beyond zipcode, and our integration still does not have address verification beyond zipcode, however, if desired, Billing Address can be collected on the payment step and synced to the POS. The downside of enabling this is that zip code will be asked for twice.
Detailed error messages no longer displayed to admins in Order Queue
...
Resorts who use Identity for authentication in Aspenware Commerce have reported an intermittent problem for some accounts. For some (not all), they’re being created without a birthdate in RTPONE. A birthdate can be added during checkout on the Assign Products step for accounts that are created in this state.
Guests can add more slots than available to the cart when initial locks expire but cannot successfully checkout with them
...