Skip to main content
Talk to an expert
PlatformAdobe Commerce with Hyvä

Adobe Commerce with Hyvä, as a frontend layer.

Hyvä is the storefront frontend; Adobe Commerce still runs catalogue, B2B, checkout core and admin. This page covers how the two fit together, where Hyvä earns its place on an Adobe Commerce build, and where it needs care. We work as experienced Hyvä developers on Adobe Commerce, not as a vendor reseller.
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 changes, what does not
Hyvä replaces the Luma frontend. Adobe Commerce still owns catalogue, B2B, pricing, promotions, checkout core and admin. The change is the storefront layer.
When Hyvä suits Adobe Commerce
When the storefront is the trading constraint, the operating model can adopt a new frontend, and the integration boundary with ERP, PIM and OMS is stable.
When Adobe Commerce features need care
B2B account features, shared catalogues, requisition lists and approvals all need to keep working on the Hyvä storefront; that is scoping work, not luck.
Extension compatibility
Adobe Commerce extensions still need a Hyvä-compatible variant or replacement on the frontend. We audit that early, before the rebuild is scoped.
PIM and catalogue truth
Catalogue truth still lives in PIM (Akeneo or similar). Adobe Commerce reads it; Hyvä renders it. Hyvä does not change the integration boundary.
ERP, pricing and stock
ERP still owns commercial data. Pricing and stock flow into Adobe Commerce, Adobe Commerce serves them, Hyvä renders them.
OMS, fulfilment and post-order
Order capture stays in Adobe Commerce; OMS, fulfilment and customer-visible order state continue to behave the same way.
B2B trade behaviour on Hyvä
Account-only catalogues, customer-specific pricing, depot stock and quote-to-cart all kept working on the Hyvä storefront, treated as first-class rather than retrofit.
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.

Do we need Adobe Commerce to use Hyvä?

No. Hyvä works with both Adobe Commerce and Magento Open Source. This page is about the Adobe Commerce pairing; the Magento Open Source pairing has its own page.

Will Adobe Commerce B2B features still work on Hyvä?

Yes, with scoping. Shared catalogues, requisition lists, quotes and approvals stay in Adobe Commerce; the Hyvä storefront renders them correctly.

Should we move to Hyvä Checkout as well?

It is a separate decision. Many Adobe Commerce merchants keep the Adobe Commerce checkout core at first and revisit Hyvä Checkout once the storefront is live.

Does Hyvä reduce our Adobe Commerce licence cost?

No. Hyvä changes the frontend; the Adobe Commerce licence and the underlying platform contract are unchanged.

Is iWeb an official Hyvä or Adobe partner here?

We work as experienced Hyvä developers and as a UK Adobe Commerce agency. Partnership or accreditation language is not used unless set out in our public credentials.

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

Talk to a Hyvä developer

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 →