Miva updates include code and database changes that can take a short time to process. While we thoroughly test all updates to ensure they will not affect up-time it is still a good precaution to run updates outside of peak hours.
26R2 is major release including the following feature highlights
Vexture Merchandising now gives merchants greater control over how products are selected, grouped, sorted, and prioritized across the storefront. Merchandising Showcases can be built from collections, categories, Vexture search strings, or AI prompts.
Search results and category product displays now support default, search-specific, and category-specific boosting and sorting rules. Category-level rules can also be inherited by subcategories, allowing merchandising strategies to cascade through the category tree. Each boosting rule supports up to 26 filters.
Want to learn more? See the Vexture documentation.
Page Cache now automatically updates cache keys when related product, category, or page content changes. Product and category edits invalidate only the affected cached content, allowing unrelated pages to continue serving from cache for faster storefront performance.
Flex component JSON requests are kept in sync with page cache state, helping prevent visitors from seeing a mix of old and new data.
Want to learn more? See the Full Page Caching documentation
Category Facets now let shoppers choose multiple matching categories in search results, making it easier to narrow a search.
Product List component settings can also display matching categories as category cards above or below the search results.
Want to learn more? See the Category Facets documentation.
Merchants using AvaTax, TaxCloud, or TaxJar now have clearer tax status information directly in the order overlay. AvaTax displays both the Miva Merchant status and AvaTax transaction status, TaxCloud displays the Miva Merchant status, and TaxJar labels its status field more clearly as Miva Merchant Status.
TaxCloud uses the current completed date for recreated orders to support accurate reporting periods, and AvaTax tracks hash versions internally to help avoid unnecessary API calls.