Hyvä is a “bring your own checkout” frontend. You can integrate Hyvä Checkout, keep Magento’s default Luma checkout via the Hyvä fallback, use Hyvä React Checkout, or connect a third-party one-step checkout through Luma-based layouts. The best choice depends on budget, stack, and required features.
Checkout options with Hyvä Themes
Hyvä doesn’t force one checkout. The official docs describe it as “bring your own checkout,” with multiple supported patterns: Hyvä Checkout, Luma checkout, React Checkout, and third-party checkouts.
1. Hyvä Checkout (recommended)
Hyvä Checkout is a separate product, tightly integrated with Hyvä Themes and designed for maximum performance and UX. It is installed via Composer
(hyva-themes/magento2-hyva-checkout) and configured under Hyvä’s checkout settings.
- Best overall integration with Hyvä Theme.
- Modern stack, focused on conversion and speed.
- Growing ecosystem of “Hyvä Checkout ready” extensions (Amasty, Magespark, Buckaroo, Mollie, etc.).
2. Luma checkout via Hyvä fallback
You can keep the classic Magento Luma checkout (or Luma-based one-step checkouts) by using Hyvä’s fallback module and the Luma checkout package
(hyva-themes/magento2-luma-checkout).
- Minimal change if you already use Luma or a Luma-based checkout.
- Hyvä serves the rest of the site; checkout routes fall back to Luma layout.
- Typical pattern for Mageplaza / MageSpark / Amasty / Aheadworks checkout extensions.
3. Hyvä React Checkout (toolbox)
Hyvä React Checkout (hyva-themes/magento2-react-checkout) is an open-source React-based checkout for Magento 2.3.4+. It’s explicitly positioned as a toolbox, not plug-and-play, and requires React expertise.
- Great for highly customized checkout experiences.
- Works with Hyvä or even Luma, depending on configuration.
- More development effort and maintenance than Hyvä Checkout.
4. Third-party one-step checkout extensions
Many popular third-party checkouts (Mageplaza, Magespark, Amasty, etc.) now advertise Hyvä compatibility either via the Luma fallback or dedicated Hyvä-ready packages.
- Use Hyvä’s theme fallback to send checkout URLs to the extension.
- Check the vendor’s docs for “Hyvä checkout ready” or “Hyvä theme support”.
- Confirm which variants they support (Hyvä Checkout vs Luma fallback).
Step-by-step: integrate Hyvä Themes with your checkout
The exact commands differ by product, but the integration process always follows the same pattern: choose a strategy, install the checkout, wire it into Hyvä, then test thoroughly.
-
Choose your checkout strategy
Decide if you want:- Hyvä Checkout (best integrated, separate license).
- Luma checkout or Luma-based one-step checkout via fallback.
- Hyvä React Checkout for custom React flows.
-
Install the checkout package via Composer
From your Magento root, install the relevant module:hyva-themes/magento2-hyva-checkoutfor Hyvä Checkout.hyva-themes/magento2-luma-checkoutfor Luma fallback checkout.hyva-themes/magento2-react-checkoutfor React Checkout.- Third-party checkout module (e.g., Mageplaza, Magespark, Amasty) following vendor docs.
-
Run Magento setup commands
After requiring the package, run:bin/magento setup:upgrade- Optionally
bin/magento setup:di:compile(for production) bin/magento setup:static-content:deploy(for production)bin/magento cache:flush
-
Configure checkout mode in the admin
Depending on your choice:- For Hyvä Checkout, go to Stores > Configuration > Hyvä Themes > Checkout and select Hyvä as the default checkout.
-
For Luma checkout or one-step extensions, use Hyvä Themes > Theme Fallback to route
/checkout(and related URLs) to the fallback theme. -
For React Checkout, enable it via system config or CLI flag (e.g.,
hyva_react_checkout/general/enable).
-
Connect payment & shipping methods
Make sure your payment/shipping providers are compatible with your chosen checkout:- Use “Hyvä Checkout ready” or “Hyvä React Checkout” payment modules where available (Mollie, Buckaroo, others).
- For legacy modules, you may need Hyvä compatibility modules or fall back to Luma checkout.
-
Test the entire checkout journey on staging
Run through guest and logged-in checkout, multiple payment methods, shipping methods, discounts, and edge cases. Fix any conflicts before touching production.
Example: install Hyvä Checkout and enable it
Always confirm the exact package names and commands in the latest Hyvä Checkout docs and your license portal.
# From your Magento 2 root
# 1) Install Hyvä Checkout (requires a valid license)
composer require hyva-themes/magento2-hyva-checkout
# 2) (Recommended) disable HTML minification for Hyvä Checkout
bin/magento config:set dev/template/minify_html 0
# 3) Upgrade and deploy
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
# 4) Flush caches
bin/magento cache:flush
These commands mirror those in Hyvä’s official installation instructions for Hyvä Checkout.
- Never switch checkout on a live store without full staging tests and backups.
- Coordinate with payment providers—failed checkout means lost revenue.
- Monitor logs and analytics closely after rollout (errors, drop-offs, conversion rate).
Important notes: versions, B2B, and third-party modules
1. Magento & Hyvä versions
- Hyvä theme targets Magento 2.4.x; Hyvä Checkout and React Checkout have their own minimum Magento and PHP versions (React Checkout supports 2.3.4+).
- Always check each product’s compatibility matrix (especially for Adobe Commerce and B2B features).
2. Adobe Commerce & B2B features
Hyvä Checkout and Hyvä React Checkout focus primarily on standard Magento flows. Some Adobe Commerce-specific B2B features are still evolving or require extra work.
- Check the Hyvä Checkout feature matrix if you rely on quotes, company accounts, requisition lists, etc.
- Where coverage is missing, you may need fallback checkout or custom React components.
3. Payment and shipping modules
For Hyvä Checkout and React Checkout, payment and shipping methods must expose compatible UI components. The ecosystem now includes many “Hyvä Checkout ready” modules (Mollie, Buckaroo, and others).
- Prefer vendors that explicitly mention Hyvä Checkout or Hyvä React Checkout compatibility.
- For unsupported methods, plan for a custom compatibility module using Hyvä guidelines.
4. Performance expectations
One reason to move from Luma checkout to Hyvä Checkout or React Checkout is performance—fewer requests and a more modern frontend. Independent reviews highlight performance gains but also note that checkout still needs careful extension compatibility.
Verification checklist: is your checkout properly integrated with Hyvä?
After integrating any checkout with Hyvä on staging, validate it with this checklist before going live:
- Correct routing:
/checkoutand related URLs load the intended checkout (Hyvä, Luma, React, or third-party). - Guest checkout: add to cart → checkout → place order works for a guest user.
- Registered checkout: log in, place order, see it in “My Orders”.
- Payment methods: all enabled payment methods appear and complete orders successfully.
- Shipping methods: shipping options, costs, and delivery info display correctly.
- Coupons & totals: discounts, taxes, and totals calculations are correct.
- JS & logs: browser console is free of recurring errors; Magento logs show no checkout-related fatal errors.
- Performance: Lighthouse / PageSpeed scores on the checkout route are acceptable and stable over time.
FAQs: Hyvä Themes and checkout integration
Do I have to buy Hyvä Checkout to use Hyvä Themes?
No. Hyvä Checkout is a separate, optional product. You can continue using the standard Luma checkout or compatible third-party checkouts using Hyvä’s fallback. Hyvä’s own docs explicitly present multiple checkout options.
Is Hyvä Checkout plug-and-play?
It’s close, but you still need to install it via Composer, configure it in the admin, and ensure your payment/shipping methods are compatible. Hyvä provides detailed installation docs, and many vendors now ship Hyvä Checkout ready integrations.
When should I use Luma checkout instead of Hyvä Checkout?
Luma checkout via fallback is useful if your stack depends heavily on Luma-only or legacy checkout extensions and you’re not ready to rebuild them yet. It lets you get Hyvä’s performance on catalog while deferring a full checkout migration.
Is Hyvä React Checkout the same as Hyvä Checkout?
No. Hyvä React Checkout is an open-source React toolbox, not a plug-and-play product, and it can even run with non-Hyvä themes. Hyvä Checkout is the commercial, tightly integrated checkout aimed at most stores.
How do I know if my payment extension supports Hyvä Checkout?
Check the vendor’s docs or product page for “Hyvä Checkout” or “Hyvä React Checkout” support. Many providers now offer dedicated modules or compatibility guides (for example, Mollie, Buckaroo, Magespark, Amasty and others list Hyvä checkout-ready extensions).
Not sure which checkout is right for your Hyvä store?
Choosing between Hyvä Checkout, Luma fallback, React Checkout, or a third-party one-step checkout can significantly impact conversion, performance, and maintenance costs. A short technical review can give you a clear recommendation tied to your stack and roadmap.
- Assessment of your current checkout, payment, and shipping stack.
- Comparison of Hyvä Checkout vs Luma fallback vs third-party options for your use case.
- Risk and effort estimate for each integration route.
- Rollout plan and monitoring checklist for a safe switch.
