Hyvä Compatibility Checker FAQ
All 12 answers
How is “compatibility” defined here?
A verdict of Compatible means the extension renders its frontend HTML correctly under Hyvä 1.3+, doesn’t inject Knockout or RequireJS dependencies, doesn’t break the cart or checkout flow, and survives a clean reindex + setup:upgrade. Backend admin behaviour is identical regardless of frontend theme, every status here judges only the storefront. So if a verdict says “Compatible”, you can install it next to Hyvä without porting work; if it says anything else, the row description explains exactly what gap remains.
What does “Hyvä module” mean, do I install something separate?
Yes. A Hyvä module verdict means the vendor (or community) ships a small bridge package, usually free, distributed via composer or marketplace, that re-renders the extension’s frontend in Tailwind+Alpine instead of Luma’s Knockout. The pattern is: composer require vendor/extension-hyva alongside the original vendor/extension, run setup:upgrade, and the storefront just works. Both packages are required, the original handles the backend and business logic, the Hyvä one re-skins the frontend.
My extension says “Partial”, what work is needed?
A Partial verdict means the backend works perfectly under Hyvä but parts of the frontend, usually small AJAX widgets or PDP-block JS, are still in Knockout/RequireJS and render either broken or not at all. The fix is rewriting the frontend templates in Alpine.js + Tailwind. Port budget is quoted per extension, depending on how big the frontend surface is. A simple PDP info-block is a small port; a quote-cart UI or marketplace vendor-storefront is a much larger one. The Partial-row description on the checker tells you which surface needs work.
I have Blockers, what do I do about them?
Blockers can’t cohabit with Hyvä, they own a flow Hyvä also wants to own (most often the entire checkout). The fix is replacement, not bridging: remove the blocker, install the Hyvä native equivalent, migrate any custom config across. The most common case is a One-Step-Checkout extension, replaced by Hyvä Checkout (free, included in Hyvä 1.3+). For each Blocker the checker shows you what to swap to. Replacement effort depends on how many custom payment/shipping integrations you had hooked into the old flow, and is quoted per scope.
Why is One-Step-Checkout marked Blocker if Hyvä has its own checkout?
Exactly because Hyvä has its own checkout. Mageplaza, Amasty and IWD One-Step-Checkout extensions all rewrite Magento’s entire checkout in Knockout, which is the layer Hyvä replaces. Two checkouts can’t cohabit. Hyvä Checkout already does what those extensions do (one-page render, < 1 second, every major payment gateway, Klarna/Adyen/Stripe-element bridges) and ships free with Hyvä 1.3+. Removing the OSC extension also drops the licence fee, net win on cost, performance, and stability.
How accurate / current is the database?
Every row was hand-verified by installing the extension on a Hyvä 1.3+ staging store and running real customer flows, not auto-scraped, not vendor-claimed. The database is updated every quarter, plus ad-hoc whenever a vendor ships a new Hyvä bridge. Last full sweep: Q2 2026. If you spot a row that looks out of date based on your own testing, message me on WhatsApp, I’ll re-verify and update for everyone.
My extension isn’t in the list, what should I assume?
Treat it as ? Unknown: assume it might need work until proved otherwise. The fastest way to lock the verdict is a focused spike, install the extension on a Hyvä staging copy, click through the customer flows, screenshot any visual or functional gaps. That gives you the verdict, the porting effort, and the risk profile. If you have several unknowns, send the list via the audit form below and I’ll spike the lot together.
I’m about to start a Hyvä migration, what do I do with this report?
Three steps:
- Lock all Unknowns via focused spikes, never start a migration with unknowns in scope.
- Quote every Partial with a fixed-price port budget (use the per-extension hours estimate × your dev rate).
- Plan replacements for every Blocker, spec the swap-out (e.g. Hyvä Checkout for OSC) before the migration kicks off.
Add the totals and you’ve got a realistic Hyvä migration scope before you sign anything. Most surprise-rework on Hyvä projects comes from skipping this audit and discovering Partials / Blockers mid-build.
How much does it cost to port a “Partial” extension?
Per-extension port effort depends on the frontend surface:
- Small frontend surface (one PDP block, one info-widget)
- Medium surface (multi-block, AJAX category filter, customer-account page)
- Large surface (quote-cart UI, vendor storefront, multi-step wizard)
Every port is part of a fixed written quote for your scope.
Does this work for custom in-house extensions?
The checker covers third-party extensions only, in-house custom modules need a per-module audit. Same verdict scheme applies: read the module’s frontend code, check whether it uses Knockout / RequireJS, count the number of phtml templates that reference Magento’s frontend JS APIs, estimate the Alpine port effort. As a quick rule of thumb, a custom module with no frontend code is automatically Compatible; one with 2 or more phtml templates and AJAX is almost always Partial. Send the module list via the audit form for a written verdict per module.
You said Hyvä 1.3+, what about earlier versions?
Hyvä 1.3+ is the recommended baseline because it ships Hyvä Checkout natively (no separate licence) and enables the official Adobe Commerce 2.4.9 native-Hyvä integration. Hyvä 1.2.x is still supported by every vendor compat module here, but if you’re upgrading the theme anyway, jump to 1.3+. Hyvä 1.1.x and earlier, some compat modules may have minor regressions; treat anything older than 1.2 as legacy and budget a small upgrade tax.
After all this audit work, is Hyvä migration still worth it?
Yes, almost always. Even with 5-10 Partials and 1-2 Blockers, the Hyvä migration is usually worth it: a faster storefront that tends to help conversion (measure it on your own store), and faster future feature builds (Tailwind+Alpine is faster to build with than Knockout). The audit just makes sure you go in with eyes open and a fixed budget, not with surprise rework eating the savings.
Related FAQ topics
All FAQ topics-
Magento Upgrade
Common questions about upgrading Adobe Commerce / Magento Open Source. -
Hyvä Development
Common questions about Hyvä theme development, migration from Luma, and Hyvä Checkout.
-
Magento Performance
Common questions about Magento performance optimization, Lighthouse... -
Emergency Bug Fixing
Common questions about emergency e-commerce bug fixing across... -
Hiring a Freelance Magento Developer
Questions about Magento project scope, quotes, start dates... -
Magento B2B Development
Common questions about Adobe Commerce B2B, Magento B2B development...