Release Notes

1.1.0

Released: Sep 2026

Release Highlights

Allow Avalara settings AVALARA_COMPANY_CODE and TAX_CODE_MAP to be specified for each store selector

Previously, every store filed its taxes under the single Avalara company code set for the plugin. Each store can now file under its own Avalara company code. The tax code map can also be set per store, so stores can map the same product to different Avalara tax codes. A store quotes, commits and cancels under one company code throughout, so tax is remitted by the company that calculated it.

Both settings are optional, and each falls back on its own. A store that sets neither behaves exactly as it does today, so a deployment that does not need this feature is unaffected.

The Avalara account and license remain shared by all stores. This feature separates the companies you file under, not the Avalara credentials you connect with.

See Configuring for the format and a worked example. Note that once any store is given its own configuration, the stores without one need a catch-all entry, or they stop calculating tax through Avalara.

1.0.2

Released: Aug 2026

Release Highlights

Fixed cache key so a single checkout does not invoke Avalara twice

Previously, a single purchase caused this plugin to invoke more tax calculation calls than it needed to. The tax calculated for the shopping cart was not reused when the shopper submitted the order, so the same question was asked twice.

The cause was internal. The plugin compared the cart request and the order request in full, including identifiers that Self-Managed Commerce changes between the two stages. Those identifiers cannot change the tax owed, but they made the two requests look different to the plugin.

A typical purchase therefore raised three Avalara transactions instead of two. Avalara bills per transaction, so the extra call added cost with no benefit. Stores with high order volume could also reach their Avalara rate limit sooner than expected.

The plugin now compares only the details that can change the tax owed. These include the addresses, the currency, the line items and their prices, and the shopper's tax exemption details. The cart result is reused at checkout, so a purchase raises two Avalara transactions.

Added settings to size the tax result cache

Three optional settings now control how many tax results the plugin holds, and for how long. Use them if you want to trade memory for fewer Avalara calls, or the reverse. See Configuring for the defaults and for guidance on changing them.

1.0.1

Released: May 2024

Release Highlights

Modified logic to avoid reusing cached tax calculation from shopping cart when determining taxes at checkout

The logic to allow cached tax calculation for a shopping cart to be reused when checking out was unnecessarily complex, and was giving us indications of possible edge cases where tax calculation failures could occur. Therefore we have reverted this performance optimization to improve code maintainability and plugin reliability.

1.0.0

Released: Jul 2022

Release Highlights

Initial Release

Avalara plugin compatible with Extension Point Framework version 1.1.0. This plugin supports the following:

• Tax calculations for shopping carts.
• Tax commits at checkout to notify Avalara that taxes should be remitted.
• Tax deletes to remove tax remittance if checkout fails or if the order is cancelled.