...
For more information see Aspenware Commerce 2.13 Release Guide - Product-discount and Discount Vouchers.
Dedicated voucher validation page (2.13.2)
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.
...
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.
Address Syncing to POS now supported for Square payment provider (2.13.3)
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.
...
In these release notes, and for future major releases, Aspenware will now include a summary of issues that are present in the release, and which have not yet been addressed. This summary is not an exhaustive list of every issue, but it includes both bugs Aspenware found in internal testing and bugs which have been reported but not yet addressed. The known issues listed here are planned to be addressed in a near-term release, either in the next hotfix, or in the next major release.
The inventory order lock is not removed on initial inventory sync from POS but on the subsequent inventory sync, resulting in double counting inventory for several minutes until the sync runs again
...
Activity products for resorts using RTP|Connec
For resorts who use RTP|Connect and sell activity products, orders containing activity products are failing to process successfully to RTP|ONE because of a problem with LockIDs. Connect does not support automatically extending activity locks, so if the activity lock expires between the time the shopper begins his order and when he gets to checkout, his order will fail with the message ‘method or operation is not implemented'. This issue can be mitigated by setting the Activity Order Lock in RTP to a longer interval until this issue is addressed.
Voucher banner overlaps cart for some sites
...
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.
...
If a guest adds the last remaining spot to the cart, waits for the lock to expire, and adds that product to their cart again, they could add 2 to the cart when only 1 inventory spot is available. The guest cannot checkout with those two slots, the guest will receive an insufficient inventory message.
Inventory order lock is not removed on initial inventory sync (but it is on the next sync)
This release guide details what was changed about Aspenware Inventory for this version. In this guide, you’ll find an architecture diagram that explains how inventory locks work. This issue is that locks are not removed the first time inventory is synced from the POS. On the next sync, they are removed. This results in double-counting inventory for n minutes until the sync runs again. To restate another way, locks are being held for too long, since they are not removed the first time after the inventory sync from POS to Aspenware Commerce runs, but on the second sync after the order completes. So, a single slot can be counted twice for several minutes (1 from the order lock that was not immediately removed, and 1 from the updated inventory sync from the POS, which then has that slot decremented). This known issue can be mitigated by setting the inventory sync to run in pairs. First, figure out how long the inventory function takes to run in your environment (e.g., the function takes 2 minutes to run). Then, set the inventory function to run back to back on the interval it was configured to run before (i.e., if it was set to run every 15 min, and the function takes 2 minutes to run, set the inventory function to run every 13 minutes and every 15 minutes).