Best full-service eCommerce agency 2026
Hyvä released version 1.2.8 of its ElasticSuite compatibility module on 3 June 2026, adding support for Smile ElasticSuite 2.12.x.
The update is relevant to merchants planning Magento 2.4.9 upgrades because Smile introduced ElasticSuite 2.12.0 as the first release in its 2.12.x branch for Magento 2.4.9 compatibility.
For merchants using Hyvä and ElasticSuite together, version 1.2.8 brings the Hyvä compatibility layer in line with that newer ElasticSuite branch. It is primarily a compatibility update rather than a release of new search functionality.
What changed
Version 1.2.8 of hyva-themes/magento2-smile-elasticsuite adds support for Smile ElasticSuite 2.12.x.
Smile released ElasticSuite 2.12.0 on 1 June 2026. Smile describes 2.12.x as the branch for Magento 2.4.9 and later, and its compatibility matrix maps Magento 2.4.9+ to ElasticSuite 2.12.x.
Hyvä maintains a separate ElasticSuite compatibility module for the storefront integration between ElasticSuite and Hyvä Themes. Version 1.2.8 extends that compatibility layer to the new ElasticSuite 2.12.x branch.
The practical implication is that merchants using Magento 2.4.9, ElasticSuite and Hyvä can assess these versions together as part of their upgrade path.
That does not mean every implementation will require the same work. Custom theme development, additional ElasticSuite modules, third-party extensions and site-specific search configuration can still affect an upgrade.
Why ElasticSuite compatibility matters
ElasticSuite, developed by Smile, provides search and merchandising functionality for Magento, including autocomplete, layered navigation, virtual categories, range sliders and search relevance controls.
Hyvä and Smile have supported an ElasticSuite integration for Hyvä since 2022. Hyvä’s compatibility layer adapts ElasticSuite storefront functionality for a Hyvä-based frontend.
The documented integration includes functionality such as:
-
search autocomplete
-
product, category and popular-search suggestions
-
layered navigation
-
range sliders
-
multiselect filters
-
virtual categories
-
search-result pages
-
search relevance functionality
For merchants using both products, this means Magento upgrades need to account for three related components: the Magento or Adobe Commerce version, the compatible ElasticSuite branch and the Hyvä compatibility module.
For Magento 2.4.9, Smile’s documented compatibility path is ElasticSuite 2.12.x. Hyvä ElasticSuite 1.2.8 adds support for that ElasticSuite branch.
The broader context: Magento 2.4.9 compatibility
Magento Open Source 2.4.9 and Adobe Commerce 2.4.9 were released in May 2026 with platform and dependency changes that extension developers needed to account for.
Smile subsequently introduced ElasticSuite 2.12.x specifically for Magento 2.4.9 and later. Its 2.12.0 release notes explain that some of the changes required for Magento 2.4.9 could not be incorporated into the existing 2.11.x branch, leading Smile to establish 2.12.x as the compatibility line for Magento 2.4.9+.
Hyvä ElasticSuite 1.2.8 then extended Hyvä’s compatibility module to support that new ElasticSuite branch.
For merchants using all three components, the relevant versions to assess as part of a Magento 2.4.9 upgrade are therefore:
-
Magento Open Source or Adobe Commerce 2.4.9
-
Smile ElasticSuite 2.12.x
-
Hyvä ElasticSuite compatibility module 1.2.8
This gives merchants a clearer starting point for compatibility testing. It should not, however, be treated as confirmation that every site can upgrade without additional work.
Practical steps for merchants
If you are using Hyvä and ElasticSuite and planning a Magento 2.4.9 upgrade, On Tap recommends the following checks.
Review the full upgrade path
Confirm the versions of Magento or Adobe Commerce, ElasticSuite and the Hyvä compatibility module that will be used in the upgrade.
For Magento 2.4.9, Smile’s compatibility guidance points to ElasticSuite 2.12.x, while Hyvä ElasticSuite 1.2.8 adds support for that branch.
Your development team or Hyvä partner should also review the rest of the extension stack before deployment. Compatibility of these three components does not automatically establish compatibility for other modules or customisations.
Test search and navigation in staging
Search and layered navigation are important parts of product discovery, so they should be included in regression testing before release.
On Tap recommends testing the functionality your store actually uses, including:
-
autocomplete and search suggestions
-
search-result pages
-
layered navigation and filters
-
price and range filters
-
virtual categories
-
merchandising and relevance configuration
-
zero-result and unusual search queries
-
custom ElasticSuite modules
-
frontend overrides or other search-related customisations
Testing should reflect the merchant’s own implementation rather than assuming that package-level compatibility guarantees identical behaviour across every store.
Review additional ElasticSuite modules separately
If your store uses premium ElasticSuite functionality, community modules or bespoke integrations built around ElasticSuite, check those components independently.
Support in the core Hyvä ElasticSuite compatibility module does not automatically confirm compatibility for every extension or custom module that depends on ElasticSuite.
The same principle applies to other third-party components in the Magento stack.
Benchmark before and after the upgrade
Before deployment, record the search and navigation measures that matter to your business.
Depending on your analytics setup, these could include:
-
search usage
-
zero-result searches
-
search-assisted conversion
-
popular search queries
-
frontend performance
After deployment, compare these measures with the pre-upgrade baseline.
The purpose is to identify regressions or unexpected changes following the upgrade, rather than assuming that a compatibility release will itself improve search performance or commercial results.
The bigger picture
Hyvä ElasticSuite 1.2.8 is a focused compatibility update rather than a major search-feature release.
Its significance for merchants planning Magento 2.4.9 is that the Hyvä compatibility layer now supports the ElasticSuite 2.12.x branch that Smile introduced for Magento 2.4.9 and later.
That gives merchants using Magento, ElasticSuite and Hyvä a clearer compatibility path to assess and test.
It does not remove the need to review the wider extension stack or validate site-specific search functionality. Customisations, additional ElasticSuite modules and other third-party extensions still need to be considered as part of the upgrade.
For merchants relying on ElasticSuite, the practical next step is therefore to confirm the complete version combination, test the storefront functionality they use and treat the compatibility update as one part of the wider Magento 2.4.9 upgrade process.
About On Tap
On Tap is a growth-focused eCommerce consultancy specialising in Magento, Adobe Commerce and Hyvä implementations for mid-market and enterprise merchants.
From platform upgrades and extension compatibility audits to performance optimisation and search experience strategy, On Tap helps merchants plan and test changes across complex Magento environments.
If you are running Hyvä and ElasticSuite and want help assessing your Magento 2.4.9 upgrade path, get in touch with the On Tap team.
