...
| Table of Contents |
|---|
Resolved Issues
Conflicting tax rates causing failed orders
Previously, when customers added two products to their carts resort customers with differing tax configurations - based on country/state/zip and therefore differing tax percentages - the order failed with a message that the tax collected differed from expected tax. While the manner in which taxes can be configured for shipping addresses did not change with this fix, now rates (for shippable vs. non-shippable products) were seeing failed orders when both types of products were present in the cart. Now when two products with differing rates are in the cart (a shipped and non-shipped product) the products that are not shipped will be taxed according to properly taxed - at the default tax rate for the resort , and the shippable items will all be taxed at when non-shippable and the tax rate configured for the shipping address when shippable. 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 your resort configures taxes by country/state/zip (not fixed) in Aspenware Commerce (this usually only applies to resorts using retail and shippingrather than fixed) and you have any questions please reach out to your service representative.
Vouchers not referencing the RTP voucher template setup
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. Aspwenware recommends that all resorts successfully leveraging vouchers ensure that the formerly hard-coded values are an exact match to the RTP templates.