Skip to main content
Talk to an expert
ServiceHyvä development

Hyvä development for Adobe Commerce and Magento.

Hyvä is a lighter frontend stack for Adobe Commerce and Magento Open Source. We work as experienced Hyvä developers, building storefronts, supporting checkout work, planning migrations from Luma and keeping the wider catalogue, ERP and operational estate honest. This page covers what Hyvä development looks like in practice, when it earns its place, and where it does not solve the underlying problem.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01What Hyvä development covers
  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 · What Hyvä development covers

What Hyvä development covers

What Hyvä actually changes
Hyvä replaces the Luma frontend with a lighter Tailwind and Alpine stack. Catalogue, checkout core and admin still run inside Adobe Commerce or Magento; the rebuild is the storefront layer.
Storefront build and component work
Templates, components, blocks and category, product and basket pages built against the merchant's design system rather than a generic theme. Maintainable code, not a one-off cosmetic pass.
Extension and module compatibility
Many Magento extensions need a Hyvä-compatible variant or a replacement. We map that work honestly before recommending a rebuild; surprise extension work is the biggest Hyvä project risk.
Where Hyvä does not help
Hyvä is not a fix for a struggling catalogue, a leaky integration boundary or a slow ERP. When the bottleneck lives elsewhere, we say so.
B2B and trade behaviour on Hyvä
Account-only catalogues, customer-specific pricing, depot stock and quote-to-cart all need to keep working on the Hyvä storefront. We scope that per merchant rather than assume defaults.
PIM, ERP and operational systems unchanged
Catalogue truth still lives in PIM, commercial data still lives in ERP. Hyvä does not move those boundaries; the storefront just reads them.
Honest fit read before commit
A senior, written read on whether Hyvä is the right step, what needs rework, and what realistic delivery shape looks like, before any rebuild is scoped.
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 iWeb an official Hyvä partner?

We work as experienced Hyvä developers. We do not claim official Hyvä partnership, certification or accreditation unless it is set out in our public credentials.

Does Hyvä replace Adobe Commerce or Magento?

No. Hyvä replaces the storefront frontend. The catalogue, checkout core and admin still run on Adobe Commerce or Magento Open Source.

Will Hyvä make our site faster on its own?

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

What happens to our existing Magento extensions?

Many extensions need a Hyvä-compatible variant or a replacement. We audit them up front so the work is scoped, not discovered mid-build.

Can iWeb take over an existing Hyvä build?

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

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 hyvä commerce →