Hyvä Checkout is not bundled with the free Hyvä Theme. It’s a separate commercial product licensed per Magento installation, or included as part of a Hyvä Commerce license. You must explicitly license and install Hyvä Checkout; otherwise your store continues using Luma or another checkout solution.
How Hyvä Checkout is packaged
Official Hyvä documentation is very explicit: “The Hyvä Checkout is a stand-alone commercial product” and “the prime checkout for Hyvä Themes.”
- Hyvä Theme – the storefront theme. As of November 2025 it is open source and free.
- Hyvä Checkout – a separate commercial checkout module for Magento 2, tightly integrated with Hyvä Themes.
- Hyvä Commerce – a broader suite that includes Hyvä Themes, Hyvä Checkout, Hyvä UI, and other components under one license.
Earlier, you needed both a theme license and a checkout license. After the theme became free, Hyvä clarified that Hyvä Checkout (and Enterprise) no longer require a paid theme license, but they are still proprietary products with their own licensing.
Licensing: separate vs bundled with Hyvä Commerce
1. Standalone Hyvä Checkout license
The Hyvä software license and partner docs describe Hyvä Checkout as a standalone module with its own license, separate from the theme. A typical license:
- Covers one Magento (Adobe Commerce) installation with unlimited store views and domains.
- Has a one-time license fee plus optional annual support/updates (values vary by source and may change over time).
- Gives access to code via Private Packagist or GitLab, plus documentation and support.
2. Included with Hyvä Commerce
Hyvä Commerce bundles multiple products under a single license: Hyvä Themes, Hyvä Checkout, Hyvä UI, CMS extras and more.
- Buying Hyvä Commerce means you don’t buy Hyvä Checkout separately; it’s part of the suite.
- Commerce can be a better option if you also want UI component libraries, CMS tools, and Enterprise/B2B features.
3. Free Hyvä Theme + optional paid checkout
With the theme now open source and free, your minimal combination looks like:
- Free Hyvä Theme only: you “bring your own checkout” (Luma, third-party, or React).
- Free Hyvä Theme + Hyvä Checkout license: best integrated checkout, still licensed separately.
- Hyvä Commerce license: theme + checkout + extras in one package.
Steps to get and install Hyvä Checkout
Once you’ve decided that Hyvä Checkout (not just Luma fallback) is the right fit, follow this process.
-
Choose how you’ll license Checkout
Decide whether you’ll purchase:- A standalone Hyvä Checkout license; or
- A Hyvä Commerce license, which includes Checkout plus other products.
-
Obtain your Hyvä credentials
From the Hyvä customer portal you’ll get:- A Private Packagist key associated with your Hyvä Checkout or Commerce license; or
- GitLab access if you are an agency/technology partner.
-
Install the Hyvä Checkout module via Composer
Using your credentials, require the package:composer require hyva-themes/magento2-hyva-checkout
-
Run Magento setup and adjust HTML minification
Official docs instruct you to:- Disable HTML minification for templates (or set
dev/template/minify_htmlto 0). - Run
bin/magento setup:upgrade, optionallysetup:di:compile, andsetup:static-content:deploy. - Flush caches with
bin/magento cache:flush.
- Disable HTML minification for templates (or set
-
Activate Hyvä Checkout in the admin
In Stores > Configuration > Hyvä Themes > Checkout, change the “Checkout” setting from “Magento Luma” to “Hyvä Default” to opt into Hyvä Checkout. -
Test full checkout and payment flows on staging
Before going live, test guest and logged-in checkout, main payment methods, shipping options, discounts, and edge cases.
Example CLI snippet: add Hyvä Checkout
Adjust repository and keys based on your Hyvä Checkout or Hyvä Commerce license. Follow the official docs for the latest commands.
# From your Magento 2 root
# 1) Configure Private Packagist access (example)
composer config --auth http-basic.hyva-themes.repo.packagist.com token
composer config repositories.hyva composer https://hyva-themes.repo.packagist.com/
# 2) Require Hyvä Checkout
composer require hyva-themes/magento2-hyva-checkout
# 3) Disable HTML minification if needed
bin/magento config:set dev/template/minify_html 0
# 4) Upgrade and deploy
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
# 5) Flush caches
bin/magento cache:flush
These steps follow the official Hyvä Checkout installation guide.
- Never switch checkout on production without staging tests and backups.
- Align changes with your payment providers and monitor logs, error tracking, and conversion rates during rollout.
- Keep a rollback plan (switch back to Luma checkout or previous version) ready.
Important notes: theme, versions, and checkout alternatives
1. Hyvä Theme is free; Hyvä Checkout is not
- Hyvä Theme is now open source and free to use under OSL3 + AFL3, for Magento Open Source and Adobe Commerce.
- Hyvä Checkout remains a proprietary product; you pay for either Hyvä Checkout or Hyvä Commerce to use it legally.
2. Version requirements
- Hyvä Checkout requires modern Magento 2.4.x (2.4.5/2.4.6/2.4.7/2.4.8+) and PHP 8.1+. It also depends on recent Hyvä Theme versions.
- Newer Hyvä Checkout releases introduce CSP-related requirements (nonce provider), so staying current on Magento patches matters.
3. Alternatives if you don’t buy Hyvä Checkout
Hyvä is a “bring your own checkout” theme. Official docs list three options: Hyvä Checkout, Luma checkout (via fallback), and third-party/React-based checkouts.
- Luma checkout with fallback: keep your existing Luma checkout and payment integrations.
- Third-party one-step checkouts: many vendors are compatible via Luma fallback or Hyvä-ready versions.
- Hyvä React Checkout: open-source React toolbox that can run with or without Hyvä Theme.
Verification checklist: is your Hyvä Checkout setup correct?
After licensing and installing Hyvä Checkout, use this checklist to confirm the product and license situation is as expected:
- Composer:
hyva-themes/magento2-hyva-checkoutappears incomposer.jsonandvendor/. - License access: Private Packagist or GitLab access works; no auth errors on
composer install. - Admin config: under Hyvä Themes > Checkout, “Hyvä Default” is selected and saved.
- Checkout routing:
/checkoutloads Hyvä Checkout UI, not an empty page or Luma layout. - Payments: at least one working payment method (test mode) is configured and can place orders end to end.
- Logs: no recurring PHP errors or JS errors related to the Hyvä Checkout module.
- Support plan: you know whether you have an active support/updates plan and who handles upgrades.
FAQs: Hyvä Checkout – included or separate?
Is Hyvä Checkout included when I install the free Hyvä Theme?
No. Installing the free Hyvä Theme does not automatically give you Hyvä Checkout. You must buy a Hyvä Checkout license or a Hyvä Commerce license, then install the module via Composer and enable it in the admin.
Is Hyvä Checkout part of Hyvä Commerce by default?
Yes. Hyvä Commerce bundles multiple products including Hyvä Themes, Hyvä Checkout, Hyvä UI and others. If you license Hyvä Commerce, you don’t need a separate Hyvä Checkout license.
Do I still need a Hyvä Theme license to buy Hyvä Checkout?
No. Since Hyvä Theme became free and open source, Hyvä explicitly states that Hyvä Checkout and Enterprise no longer require a paid theme license. You just need a Checkout or Commerce license.
Why did Hyvä make Checkout a separate product at all?
Community explanations and FAQs highlight two reasons: checkout is complex enough to justify its own roadmap and support model, and merchants should be able to choose between Hyvä Checkout, Luma checkout, or third-party solutions without being forced into one option.
Can I adopt Hyvä Theme now and add Hyvä Checkout later?
Yes. A common migration path is: launch Hyvä Theme with Luma checkout (via fallback), stabilize, then license and roll out Hyvä Checkout once payment integrations are ready. This spreads cost and risk over time.
Not sure if you need Hyvä Checkout, Hyvä Commerce, or just Luma fallback?
Your checkout choice affects conversion, integration cost, and long-term maintenance. The right answer depends on your payment stack, B2B needs, and roadmap—not just licensing.
- Compare Hyvä Checkout vs Luma vs third-party checkouts for your store.
- Estimate effort to migrate existing payment/shipping modules.
- Decide whether standalone Checkout or full Hyvä Commerce makes more sense.
- Plan a safe rollout with monitoring and rollback options.
