Skip to main content
Talk to an expert
PlatformHyvä Commerce

Hyvä Commerce for faster Magento storefronts.

Hyvä is a high-performance storefront framework for Adobe Commerce and Magento, with a growing checkout and commerce surface of its own. It earns its place when storefront performance is the trading constraint and the operational shape can adopt a new front-end without breaking the rest of the estate. This page covers where Hyvä fits, what needs planning properly, and how iWeb helps shape the right storefront architecture around the brief.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Where Hyvä fits inside an Adobe Commerce estate
  2. 02Selected case studies.
  3. 03How this platform fits the wider commerce estate.
  4. 04Questions we get asked.
  5. 05Clients we build for.
  6. 06Where this fits in the wider estate.
01 · Where Hyvä fits inside an Adobe Commerce estate

Where Hyvä fits inside an Adobe Commerce estate

What Hyvä actually changes
Hyvä replaces the Magento Luma frontend with a lighter, faster storefront stack. Catalogue, checkout core and admin still live in Adobe Commerce; the rebuild is the storefront layer.
Performance honestly measured
Hyvä delivers real Core Web Vitals improvements when the rest of the stack co-operates. iWeb measures the gain against real buying journeys, not synthetic homepages.
Hyvä Checkout and Commerce
Hyvä Checkout and the wider Hyvä Commerce surface are an additional decision. The trade-off is faster delivery against giving up some Magento extension behaviour.
Existing extensions and customisations
Many Magento extensions need a Hyvä-compatible variant or replacement. iWeb maps that work honestly before recommending a Hyvä rebuild.
PIM, ERP and operational systems
Hyvä changes nothing in the PIM, ERP or OMS boundary. The catalogue, pricing and stock truth still come from the same systems they did before.
When Hyvä is the wrong fix
Hyvä is not a fix for a struggling catalogue, a leaky integration boundary or a slow ERP. iWeb will say so when a performance problem lives elsewhere.
B2B and trade behaviour on Hyvä
B2B account trading, price lists, depot stock and quote-to-cart all need to work on the Hyvä storefront. The design is scoped per merchant.
Migration sequencing
Hyvä migration by domain or by traffic share keeps trading live throughout; a big-bang relaunch is rarely the right shape.
Tooling and team enablement
Hyvä uses Tailwind and Alpine. iWeb keeps the merchant's internal team enabled so the storefront does not become a black box.
Hosting and infrastructure
Hyvä reshapes the storefront; hosting and CDN strategy still matter. iWeb keeps performance gains real at the edge, not just at the server.
Long-term Hyvä support
Hyvä storefronts need support like any other: incidents, releases and upgrades governed under the same operating model as the wider Adobe Commerce estate.
Honest "is Hyvä the fix" read
Hyvä is not a fix for a struggling catalogue, a leaky integration boundary or a slow ERP. Where the performance problem lives elsewhere, iWeb will say so rather than recommend a rebuild.
02 · Relevant iWeb work
03 · Platform fit and estate context

How this platform fits the wider commerce estate.

Fit against operational shape
Catalogue depth, trade complexity, branch logic and ERP integration named honestly before the platform decision is fixed, not assumed from a vendor demo.
Integration boundary with ERP
ERP owns commercial data, pricing and stock. The commerce platform reads the boundary through governed APIs; the boundary itself is the most important design decision in the estate.
PIM as the catalogue system of record
Deep catalogue governance lives in PIM (Akeneo, Salsify or similar). The commerce platform reads from PIM rather than re-modelling product data in the storefront.
OMS and fulfilment surface
Order management, partial dispatch, returns and customer-visible order state live in operational systems. The platform reads what operations actually did.
Search and merchandising
Native search plus specialist engines (Algolia, Constructor.io) assessed against the actual query mix, not a vendor benchmark. Relevance is a continuous activity.
B2B and trade behaviour
Account-only catalogues, customer-specific pricing, depot stock, quote-to-cart and partial dispatch modelled inside the platform rather than patched at the storefront.
Multi-store and multi-territory
Brand, market and territory storefronts modelled with shared catalogue, pricing and operations rather than parallel sites that drift apart.
Total cost over five years
Licence, hosting, engineering and support modelled honestly across the lifecycle, not just year one. The cheap year-one platform is often the expensive five-year one.
Headless and composable trade-offs
Headless or composable storefronts where they earn their place, not as a default. The trade-off between optionality and integration surface is named upfront.
Operational ownership and runbook
Long-term support, releases and integration ownership inside a UK agency that runs platforms day to day, with a written runbook the on-call team can act on.
Replatform sequencing
Where a platform move is on the table, sequencing by domain, traffic share or territory keeps trading live throughout. Big-bang relaunches are rarely the right shape.
Honest "do not move" advice
Where the existing platform is the right answer, iWeb says so on the record. A senior, written read on the brief is the deliverable, not a sales pitch.
04 · Questions we get asked

Questions we get asked.

Is Hyvä a replacement for Adobe Commerce?

No. Hyvä replaces the storefront frontend. Adobe Commerce still runs catalogue, checkout core and admin. The decision is about the storefront layer, not the platform.

What performance gain is realistic from Hyvä?

Real Core Web Vitals improvement is typical when the rest of the stack co-operates. iWeb measures the gain against real buying journeys, not synthetic homepages, so the number is honest.

Do existing Magento extensions still work?

Many need a Hyvä-compatible variant or replacement. iWeb maps that work before recommending a rebuild; surprise extension work is the most common Hyvä project risk.

Should I add Hyvä Checkout at the same time?

Sometimes. Hyvä Checkout and the wider Hyvä Commerce surface trade faster delivery against giving up some Magento extension behaviour. The decision is scoped per merchant.

Will Hyvä fix a slow site by itself?

Only if the slowness lives in the storefront. If the catalogue, integrations or ERP are the bottleneck, Hyvä will not help; iWeb will say so.

How does iWeb choose between platforms?

Against operational shape: catalogue depth, trade complexity, ERP integration, multi-territory rules and five-year cost. The decision is written down with trade-offs, not assumed from a vendor demo.

Where does ERP integration sit in the platform decision?

It is a primary input. Some platforms make ERP integration straightforward, some make it expensive. iWeb names the trade-off rather than hiding it.

Does iWeb deliver headless or composable storefronts?

Where they earn their place. The trade-off between optionality and integration surface is named upfront; composable is not a default.

How is search handled on this platform?

Native search where the query mix supports it; specialist engines (Algolia, Constructor.io) where the catalogue, volume or merchandising appetite justify them. Relevance is a continuous activity.

Where does PIM sit relative to the commerce platform?

PIM owns catalogue truth (attributes, variants, assets, channel readiness). The commerce platform reads from PIM rather than re-modelling deep product data in the storefront.

Can iWeb take over an existing build on this platform?

Yes, where the brief fits. iWeb will give a senior, written read on what is working, what needs remediation and what is honestly fixable, and the first month on support stays deliberately conservative on change.

How does iWeb size a five-year total cost picture?

Licence, hosting, engineering and support across the lifecycle, including the integration surface and operational ownership. The headline year-one number is rarely the honest comparison.

Accreditations & assurance
Gold Commerce Partner
Specialised in Commerce & AI
ISO certified
27001 · 9001 · 42001
Cyber Essentials Plus
Independently verified security
WCAG 2.2 AA
Accessibility embedded by design
Employee-owned
The same team, long term
Next step

Hyvä migration brief still open?

Send the brief. You'll get a written response from a senior expert on the platform, ERP and operational realities we'd look at first, not a pitch deck.
Talk to an expertor see adobe commerce →