Skip to main content
Talk to an expert
ServiceHyvä theme development

Hyvä theme development that lasts.

A Hyvä theme is a long-lived asset, not a one-off cosmetic pass. We translate design into a maintainable theme: shared components, design tokens, category, product, basket and account UI, with extension compatibility planned rather than discovered. UK English copy, plain commercial intent, no hype.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01Hyvä theme work, end to end
  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 · Hyvä theme work, end to end

Hyvä theme work, end to end

Design into a real theme
Figma or design system translated into a Hyvä theme with shared components, tokens and predictable layout patterns the team can extend without rewrites.
Tailwind and Alpine in practice
Tailwind utility classes and Alpine interactions used consistently so the storefront stays lean, the bundle stays small and new pages follow a known pattern.
Category and product page UI
PLP, PDP, faceted navigation, variants, swatches and stock state built against the merchant's buyer flow, not against a generic theme demo.
Basket and mini-basket
Basket, mini-basket and add-to-basket states wired into the storefront with care for partial dispatch, depot stock and B2B account behaviour.
Account, orders and self-service
Account, order history, reorder, address book and credit views built in Hyvä for both retail and trade audiences.
Extension compatibility planned
Hyvä-compatible variants identified for the extensions that matter; replacements scoped honestly where none exists, before the theme work locks in.
Content blocks and editorial surface
Reusable content blocks, banners and landing patterns the editorial team can compose without engineering, while keeping the theme consistent.
Accessibility as a default
Keyboard navigation, focus states, semantic markup and colour contrast set in components so the storefront meets WCAG AA without per-page rework.
Long-term maintainability
Components documented, naming conventions enforced and patterns reused so the theme stays workable through future Magento and Hyvä releases.
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.

Can we keep our existing brand on Hyvä?

Yes. The Hyvä theme is built against your design system; the framework does not dictate look and feel. Design tokens and components reflect the brand.

How long does a Hyvä theme build take?

It varies with catalogue depth, B2B behaviour and extension count. A short discovery names a realistic shape before any build is committed.

Do we have to rebuild every page in Hyvä?

Usually yes, because the frontend stack changes. We sequence the rebuild around critical buyer journeys rather than treating every template as equal.

Will our existing extensions still render in the theme?

Only where a Hyvä-compatible variant exists or a replacement is built. That gap is mapped before the theme work starts, not during it.

Can iWeb support the theme after launch?

Yes. Ongoing Hyvä support covers bug fixes, extension compatibility, performance regressions and Magento upgrades under a written runbook.

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ä development →