Hyvä module development: When do you need custom modules?
Custom Hyvä module development is one of those things merchants reach for too quickly. Often the right answer is "use a vendor module" or "use the off-the-shelf Hyvä solution", custom builds are expensive + ongoing-maintenance-heavy, and should be the last resort, not the first.
This post is the honest guide: when custom Hyvä module development is genuinely needed, what it costs, and when it's a sign you should be solving the problem differently.
What "custom Hyvä module" actually means
Three categories of "custom Hyvä module":
1. Custom Hyvä compatibility module
A new Magento module that re-templates a third-party extension's frontend under Hyvä. The extension's backend logic is unchanged; only the frontend rendering moves to Tailwind + Alpine.
Use case: a paid Magento extension on your store has no vendor-supplied Hyvä compat.
Typical cost: £1.5k–£8k per extension. See Hyvä compatibility: which extensions work for full guide.
2. Custom Hyvä Checkout payment-method module
Building a Hyvä Checkout integration for a payment gateway without vendor-supplied Hyvä Checkout integration.
Use case: a payment gateway your store uses doesn't ship Hyvä Checkout integration.
Typical cost: £2k–£6k per gateway.
3. Bespoke Hyvä module for unique functionality
A net-new Magento module that adds functionality unique to your store, custom configurator, custom B2B workflow, custom integration with a niche service.
Use case: functionality that doesn't exist as a paid extension and isn't satisfied by Hyvä's defaults.
Typical cost: £5k–£25k+ depending on scope.
When custom Hyvä module is genuinely the right answer
In rough order of "you definitely need custom":
1. Paid Magento extension on your store, no vendor Hyvä compat
The most common scenario. Your store depends on, say, a custom email-marketing extension from a small vendor that hasn't shipped Hyvä compat. You need the extension's frontend to render correctly under Hyvä → custom compat module.
Cost-benefit: clear. £1.5k–£8k vs replacing the extension entirely or losing the functionality.
2. Niche regional payment gateway
Your store uses Authorize.Net, Sage Pay, or a specific UK / EU regional payment gateway that doesn't ship Hyvä Checkout integration. You need a custom Hyvä Checkout payment-method module.
Cost-benefit: clear if the gateway is core to the business. £2k–£6k vs switching payment providers.
3. Bespoke business logic with no off-the-shelf equivalent
You have specific functionality that's central to your business model and doesn't exist as a paid extension, e.g., a custom vehicle compatibility lookup for auto parts, a custom subscription-billing logic, a custom B2B trade-account onboarding workflow.
Cost-benefit: clear if the functionality drives revenue. £5k–£25k+.
4. Integration with proprietary internal systems
Custom ERP, CRM, or PIM systems that aren't covered by paid Magento integration extensions. You need a custom module to bridge Magento and the internal system.
Cost-benefit: usually clear. Integration cost is typically dwarfed by the value of unified data.
When custom Hyvä module is the wrong answer
Common scenarios where merchants reach for custom but shouldn't:
1. "We don't like how the default Hyvä [X] looks"
Custom-styled minor UI elements (button shapes, form layouts, badges). Don't build a custom module for this, adjust the Tailwind config and edit the template.
Custom module cost: £3k+. Tailwind config + template edit cost: half a day.
2. "There's a paid extension that does this but we want to build it ourselves"
Unless your requirements genuinely differ from the paid extension, building from scratch is more expensive over time. The paid extension is maintained by its vendor; your custom module is maintained by you.
Custom module cost: £10k+ plus ongoing maintenance. Paid extension: £100–£500/year.
3. "We want to replace Magento's [X] with our own implementation"
Custom checkout, custom cart, custom search, these are dangerous patterns. Magento's core code handles edge cases your custom code won't. Hyvä's templates are surface-level customisations; replacing core flows is a different magnitude of project.
Custom module cost: £20k+ plus ongoing failure modes. Use the existing system.
4. "We want to integrate with a service that has a Magento extension already"
Don't build a custom integration for a service that already has a maintained paid Magento extension. The paid extension handles edge cases your custom one will miss. Use the paid extension; build Hyvä compat for it if needed (which is cheaper than full integration).
5. "We want to add custom fields to PDP / cart / checkout"
Magento has attribute systems for this. Use them. Adding custom attributes via the admin → Stores → Attributes is free. Rendering them in Hyvä templates is a template edit, not a custom module.
The decision framework
For any "should we build custom?" question, work through:
Does this functionality exist as a paid Magento extension? → Yes: use the extension (with Hyvä compat if needed). No: continue.
Does Magento core handle this with configuration? → Yes: use the configuration. No: continue.
Can this be solved with a template edit + Tailwind config? → Yes: do that. No: continue.
Can this be solved with an Alpine component on top of existing templates? → Yes: do that. No: continue.
Is this functionality unique to your business and central to your revenue model? → Yes: custom module is justified. No: reconsider whether you actually need it.
If you get to step 5 with "yes", custom Hyvä module development is the right answer. Otherwise, simpler approaches usually win.
What custom module development actually costs
For different scopes:
| Scope | Cost | Timeline |
|---|---|---|
| Hyvä compat for display-only paid extension | £1.5k–£3k | 1–3 days |
| Hyvä compat for PDP-touching paid extension | £2.5k–£5k | 3–5 days |
| Hyvä compat for checkout-touching paid extension | £4k–£8k | 5–10 days |
| Hyvä Checkout payment-method module (simple gateway) | £2k–£4k | 3–5 days |
| Hyvä Checkout payment-method module (complex gateway with 3DS) | £4k–£8k | 7–14 days |
| Custom bespoke functional module (simple) | £5k–£10k | 7–14 days |
| Custom bespoke functional module (medium) | £10k–£20k | 14–28 days |
| Custom bespoke functional module (large, e.g. vehicle lookup, configurator) | £15k–£35k | 21–42 days |
These are typical bands. Specific projects can be cheaper (well-specified scope + reusable patterns) or more expensive (significant integration work + edge-case handling).
Hidden costs to budget for
Custom module development has costs beyond the initial build:
1. Ongoing maintenance
When Magento upgrades, when Hyvä upgrades, when paid extensions upgrade, your custom module needs verifying + sometimes updating. Budget 10–20% of initial build cost per year for maintenance.
For a £10k custom module: £1k–£2k/year ongoing.
2. Documentation
The custom module needs handover docs so future developers can extend it. Some agencies include this; some don't. Budget extra if it's not included.
3. Testing
QA for custom modules is more expensive than QA for off-the-shelf solutions because the test scenarios are unique. Budget 15–25% of build cost for proper QA.
4. Bug fixes post-launch
Production bugs in custom code are common in the first 60 days. Budget a 1–2 day bug-fix sprint within the first 60 days.
The "build vs buy" dollar threshold
A rough rule of thumb: if a paid Magento extension costs <£1k/year and does what you need (or close to what you need), buy it. If you need more than £5k of customisation on top of the paid extension to make it fit, the build-from-scratch maths starts to win.
For functionality unique to your business: build is clearly the answer, but start with a simple v1, ship it, iterate. Don't try to build a perfect v1, the requirements will evolve once it's in production.
When to open-source your custom modules
If you've built a custom Hyvä compat module for a widely-used commercial Magento extension, publishing it open-source under MIT helps the community and gives you reputation upside. The cost: a few hours of code-cleanup + documentation.
We open-source our compatibility module work for common commercial extensions whenever the client agrees. Client-specific bespoke modules stay private by default.
Bottom line
- Custom Hyvä compatibility module: clear win when a paid extension on your store has no vendor Hyvä compat. £1.5k–£8k per extension.
- Custom Hyvä Checkout payment-method module: clear win when your gateway has no vendor Hyvä Checkout integration. £2k–£6k.
- Custom bespoke functional module: clear win when the functionality is unique to your business and revenue-critical. £5k–£35k+.
- Otherwise: check if paid extension exists, then Magento config, then template edit, then Alpine component, before reaching for custom module.
Next steps
- Read Hyvä compatibility: which extensions work for the compat-module-specific guide
- Read Hyvä Theme customization: what's possible for non-custom-module customisation patterns
- See the Hyvä Compatibility services page
- Book a scoping call, we'll tell you whether custom is genuinely needed for your specific case