Hyvä's i18n 1.4.0 wave: What 18 locale releases mean for international Magento merchants

By early June 2026, 18 Hyvä localisation packages had moved to version 1.4.0. If you are running Hyvä on an international Magento store, the update provides a useful new translation baseline across a broad range of European markets and Korean.

What was released

The v1.4.0 update covered 18 locale packages:

• Western Europe: German (DE and CH), French, Spanish, Catalan, Italian, Dutch (NL and BE), Portuguese (BR)

• Eastern Europe: Polish, Bulgarian, Romanian, Ukrainian

• Baltic languages: Latvian, Lithuanian

• Finnic: Estonian

• Scandinavia: Danish

• East Asia: Korean

That gave merchants using those locales a common package version for Hyvä-specific translations.

Hyvä’s localisation documentation explains how these packages work with Magento’s standard CSV translation system.

As of October 2026, Hyvä’s documentation lists 19 pre-built localisation modules, including informal Dutch (nl_DI), so the 18-package June update should not be treated as the complete current catalogue.

Why this matters

On the surface, translation updates might seem routine. For merchants running multiple Magento store views, however, they can still have practical operational value.

Synchronised version parity

One challenge in managing multi-market Magento stores is keeping track of localisation-package versions across different store views.

When German, French and other locale packages are on different versions, development teams need to track which Hyvä-specific strings and fixes are included in each package.

Moving several installed locale packages to the same release can give teams a cleaner maintenance baseline.

That does not mean different package versions automatically cause different checkout behaviour. Hyvä localisation modules primarily provide translated strings; checkout functionality depends on the underlying Theme, Checkout version, Magento configuration and other installed modules.

For agencies and merchants managing multiple markets, the practical benefit is therefore simpler translation-package management and more consistent coverage of Hyvä-specific strings.

Support for international Magento stores

The breadth of available localisation modules is useful for merchants operating Hyvä across several markets.

Hyvä’s localisation packages cover Hyvä-specific interface strings, while the underlying Magento language pack handles Magento core translations.

That distinction matters.

The packages do not automatically translate:

• product names and descriptions

• category content

• CMS pages and blocks

• custom merchant content

• third-party extension strings unless the extension supplies translations

For merchants considering Hyvä for international stores, the localisation modules can reduce theme-specific translation work, but they remain one part of a wider localisation process.

Localisation quality still matters

A translated storefront should be reviewed as a complete customer experience, not simply as a collection of installed language packages.

Incomplete or awkward translations can affect usability, brand consistency and customer confidence.

That includes areas such as:

• navigation

• product and category interfaces

• account pages

• cart and checkout

• validation messages

• accessibility labels

• custom and third-party module strings

The i18n packages provide a useful starting point for Hyvä-specific UI text, but merchants still need QA and market-specific content review.

What else shipped

Other Hyvä-related compatibility and integration releases were also appearing around this period.

For merchants using MageWorx Advanced Product Options or ShipperHQ with Hyvä, the relevant integration packages should be reviewed separately against the versions installed on the project.

These releases are not part of the Hyvä i18n 1.4.0 update itself, so merchants should use the relevant vendor and Hyvä documentation to confirm compatibility before upgrading them.

Practical steps for merchants

If you are running Hyvä in production across multiple markets, here is what we would recommend:

1. Audit your current locale versions. Check which localisation packages are installed, for example with composer show 'hyva-themes/i18n-*', and identify which versions are currently deployed.

2. Update the locale packages you actually use. There is no requirement to install or update every Hyvä locale simply to achieve version parity. Where several active store views use the affected packages, updating them together can make testing and maintenance simpler.

3. Check the corresponding Magento language pack and store-view locale. Hyvä’s localisation modules cover Hyvä-specific strings; they do not replace Magento’s core language pack or automatically change the store-view locale.

4. Clear caches and deploy static content. After installing or updating localisation packages, clear Magento caches. In production mode, deploy static content for the relevant locales before validating the storefront.

5. Test customer journeys in every affected locale. Translation updates can expose layout issues caused by longer strings or missing project-specific translations. Run through the critical path in each active locale before deploying to production.

6. Review project-specific overrides. Check whether local CSV dictionaries override strings supplied by the updated Hyvä localisation package and confirm those overrides are still intentional.

The bigger picture

Hyvä Theme became free and open source in November 2025, lowering the licensing barrier for the Theme itself. Hyvä announced the change on 6 November, with free public availability beginning on 10 November. The Theme uses OSL3 and AFL3 licensing, while supporting Theme modules moved to OSL3.

Hyvä Theme 1.4.0 was also released in November 2025 and introduced changes including Tailwind CSS 4 support, Design Tokens, BFCache support, stable Speculation Rules and View Transitions.

Those changes are separate from the June 2026 i18n package updates, but they provide useful context for merchants assessing the wider Hyvä stack.

For international eCommerce operations, frontend performance is only one part of the picture. Localisation quality, extension compatibility, market-specific content and operational consistency also matter when a store runs across multiple regions.

The June 2026 i18n update is useful because it gives merchants using those 18 locales an updated baseline for Hyvä-specific translations.

It does not remove the wider localisation work required to operate internationally, but it can reduce duplicated theme-level translation effort and make those translations easier to maintain through Composer.

About On Tap

On Tap is a growth-focused eCommerce consultancy specialising in Magento and Hyvä implementations for international brands. From multi-market deployments and localisation strategy to performance optimisation and platform migration, On Tap works with mid-market and enterprise merchants to build eCommerce operations that scale across borders.

If you are planning a multi-market Hyvä deployment, get in touch.