Hyvä Theme Development

Individually, after the extension audit, because the number of modules whose frontend has to be ported, rewritten or replaced decides most of the work. The audit produces a fixed scope and a fixed price before the build starts. There is no price list on this site because no two Luma stores carry the same extension stack.

Most stores go from audit to cutover in eight to twelve weeks. A store with few extensions and a simple design sits at the short end; a store with a large module stack, a custom checkout and B2B features at the long end. The audit gives you the dates for your store rather than the average.

Each one is handled on its own terms. Many popular modules have an official or community Hyvä compatibility module and port cleanly. Some need their frontend rewritten for Alpine.js, and a few are better replaced by a module built for Hyvä. The audit lists every extension with its route, so there are no surprises in the build.

Not necessarily. Hyvä Checkout is a paid product and a good one, but a Hyvä storefront can run with the standard Luma checkout behind it for a first release, and some stores keep a custom checkout. The audit weighs your payment and shipping extensions, your B2B needs and your budget, and recommends one of the three.

A theme switch does not change URLs, and we make sure it does not change anything else Google reads: canonical tags, structured data, meta data, internal links and the tracking stack are carried over and checked against the baseline before cutover. Faster pages tend to help rankings, not hurt them, and the ranking watch after launch confirms it.

Yes, and often both should happen in one run. Hyvä supports the current 2.4 lines, so a store on an old version usually takes the release upgrade and the new frontend together, rehearsed on one staging copy and launched in one window.

Yes. Since 10 November 2025 the Hyvä theme has been licensed under OSL 3.0 and AFL 3.0, the same licences Magento Open Source uses, and is available through Composer without a licence fee. Hyvä Checkout and the commercial add-ons remain paid products.

Yes. The Sales Agent integrates natively with Magento 2 and ships a widget for Hyvä as well as Luma, so a store that moves to Hyvä keeps its AI assistant, its catalog sync and its order tracking without any extra work.

Hyvä is the right answer for most Magento stores: it keeps Magento's own rendering, so every backend feature and most extensions keep working, and it reaches the Core Web Vitals targets without a separate frontend application to host and maintain. PWA Studio and custom headless builds make sense when a store needs an app-like experience across several channels and has the team to run it. We build both and will tell you which fits.

Yes. The theme is built from your design tokens, colours, type and spacing, and the pages are rebuilt to your existing layouts unless you want to change them. Many stores use the migration to fix what the Luma theme made hard, but that is a choice, not a requirement.

Yes. Company accounts, shared catalogs, requisition lists, quotes and customer-specific pricing from Adobe Commerce B2B or from third-party modules all run on a Hyvä storefront, with their frontends ported like any other extension. The audit lists them with the rest.

Your team can, because the handover includes the theme's documentation and the build tooling, and Tailwind and Alpine are far easier to change than Knockout and RequireJS. Many stores keep us on ongoing support for upgrades, patches and new features, but nothing in the theme depends on that.