Release Date: January 2024

Enhancements

GL Export

The GL export functionality in previous 2.44.x versions of Aspenware Commerce, is now available in Commerce 3.3.

Increased Flexibility for Frontend Navigation

We have replaced some hardcoded URL paths in My Account navigation tabs to increase the flexibility in how frontend navigation can be built. This also reduces the number of locations to maintain code.

New Language String for Voucher and Gift Card Entry Box

Aspenware has implemented the ability to make the “Apply” button beneath the voucher/gift card entry box a configurable language string. This addition allows you to determine resort-specific language based on how your resort uses payment value vouchers and/or gift cards, reducing guest confusion in the checkout process. Update this string by adding your preferred title for the button in account.login.checkout.payment.voucherbuttonlabel language string Value field (the default remains “Apply”). Note, that the button text will appear on one line only, so it is recommended to test your text on laptop and mobile as the box will extend horizontally to fit the text. See the Language Strings Library for information on updating language strings.

Resolved Issues

QR Code Generator and Print-at-Home Ticketing

For the Print at Home email with QR codes for each ticket, there was an issue where the information listed next to each QR code wasn’t displaying the assigned customer’s name or the name of the product, making differentiating barcodes for multiple people in an order difficult. This has been fixed.

$0 Order Failure for RTP-Connect

In Commerce Version 3.2.1, $0 orders were failing for resorts using RTP-Connect due to a missing billing address. This issue has been resolved.

1Risk Waivers Email Function

In Commerce 3.0 and later, resorts using the 1Risk waivers email function were not receiving waiver emails. This issue has been resolved.

Voucher Redemption Limits

Previously, in some cases, multiple-use voucher limits were not being honored. Now, vouchers that allow for multiple uses are properly decrementing quantity to the limit set in RTP. After that number of redemptions is met, the voucher becomes unavailable to redeem via Aspenware Commerce.

Dynamic Pricing Tool for non-US Resorts

Previously, resorts with a CA, NZ, or AU culture were uable to add dynamic pricing in the Dynamic Pricing tool. This has been resolved and the tool is supported for all store cultures.

Dynamic Pricing Upload

Previously, the dynamic pricing upload capability would time out if the number of rows exceeded 1000, This has been resolved and is now much more performant with more pricing rows.

Multiple Override Windows in Dynamic Pricing

Previously, if a resort used multiple override windows in their dynamic pricing strategy and only had tiers defined for “closer in” override windows, tiers would be decremented even if the price wasn’t charged to the customer. The previous work-around required that a resort add a “dummy” tier for the further-out override windows as well at the same price as the list price. This workaround is no longer required and tiered pricing now increments as expected with this pricing configuration. If the workaround has been implemeted, it may stay in place without issue.

My Account

Previously, zip codes added to My Account weren’t saving properly. This has been resolved and zip codes now save as expected in the customer information section in my account.

Payment Plan Processing During an Extended Outage

Previously, if a resort experienced an extended outage during a payment plan processing, when the failed payment was manually retried, more than one transaction entry would appear in RTP resulting in over-reporting of the Aspenware Ecomm Clearing Payment for Accounting. This issue has been resolved.

Today’s Date with Scarcity Indication

Previously, if scarcity indication was used on the PDP, today’s date would always show as white even if the inventory levels triggered the scarcity color coding. This has been resolved and color-coding displays as expected.

Date Cutoff in Mini-Cart

Previously, some themes would cut off date display, making it difficult for guests to see the full date in the mini cart at times. This issue has been resolved and all dates should display fully and according to selected date format style.

Loyalty

A security fix was made to the Loyalty feature calling of nopCommerce endpoints to display loyalty information about the logged-in user (like point balances). Previously, these endpoints were also returning API keys that should not have been returned. This has been resolved and the keys are no longer returned and old keys will be recycled.

Postal Code Collection at Checkout

As a result of the 3.0 Commerce platform upgrade, enabling postal code to be collected at the checkout complete step (triggered by the OrderSettings.CollectMissingCustomerInfo setting), was not properly saving postal code data. This issue has been resolved.

API Update

Aspenware has addressed an API-related vulnerability that was identified during routine penetration testing.

Moneris Dynamic Pricing Total

Previously, for resorts using the Moneris payment gateway, a limited number of dynamically-priced products with a total amount ending in .00 cents were causing a failure. This issue has been resolved.

FreedomPay Card Number Entry Error

In previous versions of FreedomPay, customers could inadvertently enter their credit card number in the “Name on Card” field in the payment details portion of the checkout. Customers can now enter no more than 4 digits in the name field (leaving room for names with numbers in them) and messaging will indicate an invalid name to alert users to the error.

Open

Release Date: 1/12/24

We have added functionality to the build out of the new Aspenware Identity (Auth0) platform. This feature is still in development, but this release marks a milestone in much of the required functionality. Look for updates coming soon regarding when this platform will be available for adoption.

Release Date: 1/12/24

Enhancements

Split Tax Functionality

When an RTP component is set up with split taxes, as long as the overall tax collected for a component when all tax rates are summed up is equal to the tax collected for the product in Aspenware Commerce (and other rules that are detailed below are also followed), resorts using Unity should be able to successfully sell components that have multiple tax rates on a single component. For example, a product configured in Aspenware Commerce would be configured with an 8% tax in nopCommerce, but when it goes into RTP, Unity checks the RTP component setup to see that it should actually send in a 6% AND a 2% tax for the product’s component rather than an 8% tax (which was shown to the guest), but the total tax amount collected is equal, so it’s a supported configuration.

The MatchTaxCalculation setting should be TRUE if a resort wants to take advantage of split tax functionality. See the MatchTaxCalculation Documentation for details about this setting as well as information about what tax scenarios are not supported by Aspenware.

Resolved Issues

Credit Card Storage Across Resort Group

Some resorts that are part of larger resort groups experienced an issue with saving a credit card to Resort Charge in My Account. The issue has been fixed, and users at all resorts can now successfully save credit cards for Resort Charge.

BLE Scanning

Previously, BLE scanning on guest phones was not working properly at select resort gates. For resorts who have this enabled, this has been resolved and BLE scanning now works as expected.