Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Conflicting tax rates causing failed orders

Previously, resort customers purchasing products with differing different tax rates (for shippable vs. non-shippable products) were seeing failed orders when both types of products were present in the cartwould result in failed orders. Now when two products with differing different rates are in the cart products are properly taxed - at the default tax rate for the resort when non-shippable and the tax rate configured for the shipping address when shippable. In purchased simultaneously both tax rates can apply independently. This issue only applies with those resorts that allow both shippable and non-shippable products. In this rare case resorts need to ensure that Aspenware Commerce and RTP tax zip codes and percentages match exactly. While this should not affect the vast majority of resorts, if If your resort configures taxes by country/state/zip (rather than fixed) and you have any questions please reach out to your service representative.

...

Previously, vouchers were based on hard-coded values in Aspenware Commerce, rather than referencing the RTP voucher template setup. This resulted in inconsistent voucher template values being recorded in the voucher template table (e.g. required, allow unknown recipient, and use recipient redemption customer). Now, voucher values are coming directly from RTP.

Note

Due to this change Aspwenware recommends that all resorts

...

using vouchers test their voucher products when upgrading to the latest Unity.