Hyvä Theme customization: What's possible and what's not
Hyvä Theme is highly customizable. The customization patterns are different from Magento Luma's, Tailwind config and Alpine components instead of LESS overrides and Knockout view models, but the flexibility is comparable.
This post is the honest guide to what's easy, what's hard, and what crosses into "you should hire a Hyvä specialist for this rather than your in-house generalist dev."
What's easy, your in-house frontend dev can ship in a day
These customizations stay in Tailwind config territory:
1. Brand colors, typography, spacing
Hyvä uses Tailwind's config-driven design system. Change colors, fonts, spacing scale, border radii, all in the tailwind.config.js file. No template changes required for any of these.
Effort: half a day.
2. Header / footer layout adjustments
Adding a banner above the header, rearranging footer columns, changing the navigation structure, straightforward Tailwind + Hyvä template edits.
Effort: 1–3 days depending on complexity.
3. PDP minor layout changes
Adding a trust badge under the add-to-cart button, repositioning the price block, adding a sticky add-to-cart on scroll, all in standard Hyvä template territory.
Effort: 1–2 days per change.
4. Adding a CMS block to a category page
Standard Magento CMS block + Hyvä template inclusion. Magento admin work + minor template edit.
Effort: 2–4 hours.
5. Custom badge / label on products
"NEW" badge, "ON SALE" badge, custom tag rendering on PDP and PLP, Tailwind + conditional rendering in template.
Effort: half a day.
6. Newsletter signup form styling
Restyling the existing Hyvä newsletter form to match brand, changing the layout, adding fields, Tailwind work.
Effort: half a day.
What's medium, needs Hyvä-aware dev, 3–7 days
These customizations need someone who knows the Hyvä module pattern + some Alpine.js:
1. Custom mini-cart behavior
Changing how the mini-cart triggers, what it shows, how items render. Requires Alpine.js component work + integration with Hyvä's cart store.
Effort: 3–5 days.
2. Custom PDP image gallery
Replacing the default image gallery with a custom layout (zoom on hover, 360° viewer integration, video integration), Alpine.js component work + image-loading optimization.
Effort: 5–7 days.
3. Custom search autocomplete
Custom search dropdown behavior, custom result rendering, integrating a third-party search service (Algolia, Klevu, ElasticSuite), needs Alpine + JS integration with the search backend.
Effort: 5–10 days depending on backend.
4. PDP variant selector customization
Custom configurable product selector (e.g. swatch-based instead of dropdown, with custom rendering of price changes per variant), Alpine reactive component.
Effort: 3–5 days.
5. Custom checkout fields
Adding fields to Hyvä Checkout (gift message, delivery instructions, B2B PO number), requires Hyvä Checkout module work plus backend persistence.
Effort: 3–5 days per field.
6. Custom product list filtering
Adding custom facets to PLP (e.g. by brand + by vehicle make + by price range), custom filter UI, multi-select faceted filtering, Alpine component + Magento layered navigation integration.
Effort: 5–10 days.
What's hard, Hyvä specialist territory, 1–4 weeks
These need someone who's shipped multiple Hyvä projects:
1. Hyvä compatibility modules for paid extensions
Re-implementing a third-party Magento extension's frontend under Hyvä. The pattern is well-documented but the implementation is tedious, extension count matters more than complexity per extension.
Effort: 3–10 days per extension depending on complexity. £1.5k–£8k each.
2. Custom Hyvä Checkout payment-method integration
Building a Hyvä Checkout payment method for a gateway without vendor-supplied integration. Requires payment-renderer pattern knowledge + gateway-specific integration work.
Effort: 5–10 days. £2k–£6k.
3. Multi-store / multi-website theme variations
Different visual styles per store-view on a multi-website Magento setup. Requires theme inheritance setup + per-store Tailwind config.
Effort: 5–15 days depending on variation count.
4. Custom product configurator
Bespoke configurable product UI with live preview (e.g. custom-printed signage, configurable jewelry, modular furniture). Requires custom Alpine component + backend price calculation integration.
Effort: 10–20 days. £5k–£15k.
5. B2B-specific surfaces
Company-account self-service, shared-catalog rendering, customer-specific pricing display, quote workflows, approval routing, each is a separate Hyvä surface.
Effort: 5–10 days per surface. See Hyvä for B2B Ecommerce for the full guide.
6. Custom search integration
Replacing Magento's default search with Algolia, Klevu, Bloomreach, or similar, full integration including PLP rendering, search-page rendering, autocomplete, faceted navigation.
Effort: 15–25 days. £8k–£18k.
7. Custom customer-account features
Adding subscriptions, gift cards, store credit, returns portal, multi-address shipping, wishlists with custom features, each is a separate Hyvä template surface.
Effort: 5–10 days per feature. £2k–£6k each.
What's very hard, specialist + significant investment
These cross into "this is a project, not a customization":
1. Vehicle compatibility lookup (auto parts)
Year-make-model-engine cascading dropdown with backend lookup + URL state preservation + saved-vehicle persistence. Significant Alpine component + backend integration work.
Effort: 10–15 days. £6k–£10k. (We've open-sourced our implementation pattern, see Hyvä for auto parts retailers.)
2. Custom checkout flow
Multi-step checkout customization, B2B approval routing, conditional fields per shipping country, custom shipping rate calculators with UI.
Effort: 15–30 days. £10k–£25k.
3. Live AR / 3D product viewers
Integrating WebGL-based product viewers, AR try-on, 3D product configurators. Significant frontend work + asset pipeline + performance tuning.
Effort: 20–40 days. £15k–£35k.
4. Custom B2B portal
Full bespoke B2B customer portal with custom dashboards, reporting, multi-account ordering, invoice management, ledger access.
Effort: 30–60 days. £25k–£60k.
5. Multi-region / multi-currency complex routing
Custom region-selection UI, per-region pricing/availability/promotions, automatic currency conversion display, region-specific tax handling.
Effort: 20–35 days. £15k–£30k.
What's not possible (or shouldn't be attempted)
Some customization requests are genuinely hard or wrong-headed:
1. Replacing Hyvä's render engine
You can't (and shouldn't) replace Hyvä's server-rendered HTML approach with client-side React rendering while staying "on Hyvä." If you want React, you want PWA Studio or a custom Next.js storefront, not "Hyvä with React."
2. Running Hyvä without Tailwind
You can write Hyvä templates with plain CSS or another CSS framework, but you lose the design-system consistency Hyvä provides. Going against the grain creates ongoing maintenance pain.
3. Running Hyvä without Alpine.js
Same as above, you can avoid Alpine but you'd be rebuilding what Hyvä gives you for free. Not recommended.
4. Recreating the Luma checkout under Hyvä
If you want the Magento default multi-step checkout flow visually replicated in Hyvä, you're missing the point. Hyvä Checkout is opinionated about one-page flow because the conversion data supports it.
5. Magento UI Components under Hyvä
Hyvä deliberately doesn't use Magento UI Components. If you have customizations that depend on them, those don't carry over, they need re-implementation under Alpine.
The customization hierarchy
A simple rule of thumb for who should do what:
- Tailwind config changes (colors, fonts, spacing) → in-house generalist frontend dev
- Template edits, simple Alpine work → in-house dev with 2 weeks of Hyvä training
- Custom Alpine components, Hyvä module work → senior Hyvä developer (in-house or external)
- Compatibility modules, Hyvä Checkout work, B2B features → Hyvä specialist (probably external)
- Bespoke configurators, AR viewers, custom checkout flows → Hyvä specialist agency or experienced specialist team
Matching the right tier of skill to the right tier of work avoids both over-paying for simple work and under-resourcing complex work.
What to budget for ongoing Hyvä customization
A typical year of post-launch Hyvä work for a mid-size merchant:
- Brand evolution (small refreshes, seasonal): £2k–£5k
- Compatibility modules for newly-added extensions: £3k–£10k (depends on extension count)
- Performance maintenance + tag audits: £2k–£4k
- New features / pages / sections: £5k–£20k depending on ambition
- Hyvä version updates: £1k–£3k
Total typical year: £15k–£40k of ongoing Hyvä work, depending on store complexity + ambition.
This is normal commerce-frontend maintenance territory, comparable to what a Shopify Plus merchant pays for theme customization work. Hyvä isn't unusually expensive to maintain; it's not unusually cheap either.
Next steps
- See the Hyvä Theme Customization service page
- Read Hyvä for B2B Ecommerce for B2B-specific customization
- Read Hyvä compatibility: which extensions work for the compat-module guide
- Book a scoping call for a fixed-price quote on your specific customization