Skip to main content
Talk to an expert
PlatformMagento Open Source with Hyvä

Magento Open Source with Hyvä, modernised honestly.

Magento Open Source with a Hyvä frontend is a sensible modernisation path for Luma-based stores that do not need Adobe Commerce features. We help merchants decide whether Hyvä is the right next step, plan the move from Luma, manage extension compatibility, and keep the store trading throughout.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Where Hyvä fits with Magento Open Source
  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 with Magento Open Source

Where Hyvä fits with Magento Open Source

Why Magento Open Source plus Hyvä
For merchants on Magento Open Source whose Luma frontend has become the trading constraint, Hyvä gives a lighter storefront without changing the underlying platform.
When Adobe Commerce might be the answer instead
Where the brief needs B2B account features, requisition lists or shared catalogues across many sites, Adobe Commerce may be the right move; Hyvä alone may not be enough.
Extension compatibility
Magento Open Source extensions on the Luma frontend need a Hyvä-compatible variant, a replacement or retirement. Mapped before the rebuild is scoped.
PIM, ERP and operational systems
Catalogue truth stays in PIM; commercial data stays in ERP. Hyvä changes the frontend, not the integration boundary; the design work is unaffected.
B2B and trade behaviour
Trade pricing, account behaviour and depot stock kept working on Hyvä; B2B is treated as first-class rather than a retrofit on top of B2C templates.
Tracking, analytics and SEO continuity
GTM, GA4, structured data and URL continuity planned through the move so the modernisation does not silently cost organic traffic.
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 Magento Open Source still viable in 2026?

Yes, for many merchants. Where the operating model does not need Adobe Commerce features, Magento Open Source with a Hyvä frontend is a sensible, supported path.

Should we move to Adobe Commerce or to Hyvä?

Different decisions. Adobe Commerce changes the platform; Hyvä changes the frontend. A short, written read on the brief covers which fits, or whether to do both.

How do we keep extensions working through the move?

Extension audit happens before the rebuild is scoped. Compatibility, replacement and retirement are mapped per extension, not assumed.

Will SEO traffic survive the move?

Yes if URLs, redirects, structured data and tracking are preserved. SEO continuity is planned up front, not patched after launch.

Is iWeb an official Hyvä partner on Magento Open Source?

We work as experienced Hyvä developers. Official partnership, certification 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 magento services →