Fishing tackle, UK and worldwideMagento 2 and Hyvä
Total Fishing Tackle
A full redesign and Hyvä rebuild for a store with more than 11,000 products, selling across the UK and worldwide.
Hyvä development for Magento and Adobe Commerce.
Themes, components and extension compatibility by engineers who have built on Hyvä since 2020.
Ongoing development for stores already on Hyvä, and new Hyvä builds for Magento Open Source, Adobe Commerce and Mage-OS: templates, components, extension compatibility and features, from a Hyvä Silver Partner. For merchants whose Hyvä store needs to keep moving, or whose last agency built it and left. Work with us ad hoc or on a monthly development retainer.
Is your Hyvä store stuck?
What merchants tell us when they bring a Hyvä theme to us.
-
Our Hyvä store was fast at launch and now it is getting slower.
What it usually meansScripts and libraries have been added one at a time. Each change needs weighing for what it ships.
-
The agency that built our theme has moved on and nobody knows how it works.
What it usually meansA theme with no owner gathers overrides. A short read of it tells you what to keep and what to fix first.
-
We want an extension, but it does not support Hyvä.
What it usually meansIts frontend needs a compatibility module. We write them, or tell you when a better-maintained module would be cheaper.
What we build on Hyvä.
Six kinds of work, all by the same senior engineers.
Theme and component work
Templates, product layouts, navigation and landing sections as Tailwind and Alpine.js components.
Extension compatibility modules
An extension's frontend rebuilt for Hyvä, its backend left to the vendor's updates.
New Hyvä builds
A new Magento store on Hyvä from the start: design, theme, checkout, content and integrations.
Speed kept, not just promised
Every change weighed for the JavaScript and CSS it adds; third-party scripts behind consent.
Taking over a theme
A written account of the theme you have, and a plan for what to change first.
Hyvä version upgrades
Hyvä releases tested and deployed, planned with Magento upgrades so both move in step.
The same store, with and without us.
Without us
- A fast store slowed by one script at a time
- A theme nobody on the current team understands
- Extensions avoided because they lack Hyvä support
- Hyvä releases left several versions behind
- Changes built on live and fixed on live
- Invoices you cannot trace to a piece of work
With Refined Commerce
- Every change weighed for what it ships
- A written account of the theme, then a plan
- Compatibility modules written where none exist
- Hyvä kept current, alongside the Magento release
- Built and tested on staging before it goes live
- Every piece of work itemised on your invoice
Proof, from real stores.
… The quality of their work is second to none. Everything they’ve delivered has been polished, professional, and done to a very high standard. You can tell they really care about the end result and take pride in what they do. …
How Hyvä work reaches your storefront.
The same route for a single template change and a complete new theme.
-
Step 1: The free health check
Send us the store address. A senior engineer reads its release, support status, PHP, headers, hosting and any sign of a hijack.
Within two working days- Access we need
- None. Publicly served pages only; nothing is tested.
- What you receive
- One page by email, with no obligation.
-
Step 2: A brief, with a sketch where it helps
Tell us what the storefront should do, by email. For anything visual we agree a sketch or a design before a component is written.
Same day- What you receive
- A written brief you have confirmed.
-
Step 3: An estimate for larger pieces
A small change to a template is simply done. A new build, a redesign or a compatibility module gets a written estimate from the engineer who will build it.
Within two working days- Access we need
- Read access to the theme repository and a staging copy.
- What you receive
- A written estimate before work starts.
-
Step 4: Components built on staging
Built in Tailwind CSS and Alpine.js on a copy of your store with your real catalogue, checked on every screen size and for the weight it adds to the page.
In order of priority- What you receive
- A staging address to try as the work progresses.
-
Step 5: You approve the look, then it goes live
You try it on a phone and a desktop; it goes live at a quiet hour with the previous theme version kept to return to.
At a time agreed with you- Access we need
- Deployment access to the live store.
- What you receive
- A note of what changed, and the work itemised on your next invoice.
Where Hyvä work ends and Magento work begins.
Merchants ask which page their task belongs on. It rarely matters, because the same engineers do both, but here is the line.
Hyvä development: this page
- Templates, layouts and page sections
- Components built with Tailwind CSS and Alpine.js
- Extension compatibility modules
- Theme performance and script hygiene
- Hyvä version upgrades
- New Hyvä builds and redesigns
Magento development: the backend
- Integrations with ERP, payment, shipping, email and search
- Pricing, promotions, B2B and catalogue logic
- Imports, exports, feeds and scheduled tasks
- Admin tools and reporting
- Fixes found in the logs rather than on the page
We price the work, not the clock.
- This service
- Each request priced as a whole, with an estimate first where you want one.
- How you pay
- Ad hoc, invoiced at the end of the month, or as part of a monthly retainer.
- Our rate
- £80 an hour plus VAT, the same for every merchant.
- Never charged
- Account management, or the first look at your store.
Hyvä work, ad hoc or on a development retainer.
Template and component changes can be requested as you need them and are itemised on one invoice at the end of the month. If the storefront is always moving, a monthly development retainer keeps a senior Hyvä team on it. A new Hyvä theme, a redesign or a large compatibility project is estimated in writing as a project. The Hyvä Theme itself is free and open source.
- A written estimate for new builds and redesigns
- Small changes itemised monthly
- No licence fee for the Hyvä Theme
What happens first
How our pricing works - We confirm access and check the staging copy works.
- The work is read against the code, the logs and the release you run.
- You get an estimate, or a question, in writing before anything else is done.
Is this the right service for your store?
This is for you if
- Your store uses Hyvä, or you are starting a new Magento build
- You want changes that keep the store fast
- Your previous Hyvä agency has moved on
- You want one senior team for the theme and the Magento underneath
If your situation is different
- Still on Luma? Start with the Luma to Hyvä migration.
- Need backend work? Integrations, pricing logic and admin tools are under Magento development.
- Mostly need upkeep? See support and maintenance.
Why merchants bring this work to us.
About Refined Commerce- 2020
Working with Hyvä since its first year
We adopted Hyvä when it launched and have built on it ever since. It is now the only frontend we build new Magento stores on.
- Silver
Hyvä Silver Partner
Recognised by Hyvä for the stores we have delivered, with direct access to Hyvä's own team when a project needs it.
- 1.1s
Fast for real customers, not only in a test
The main content of a Hyvä store on our case pages loads in 1.1 seconds on a phone, measured by Google on real visits.
Questions merchants ask about this.
Do we need to be on Hyvä already?
No. This page covers two things: ongoing development for stores already using Hyvä, and new Hyvä builds for Magento Open Source, Adobe Commerce and Mage-OS stores starting fresh. If you are on Luma and want to move, the Luma to Hyvä migration page is the one to read first.
An extension we rely on has no Hyvä compatibility module. What then?
We write one. A compatibility module rebuilds the extension's frontend parts as Hyvä components and leaves its backend untouched, so the vendor's updates keep working. Where an extension is poorly maintained or does more than you need, we will say so and suggest a replacement instead.
Can you take over a Hyvä theme another agency built?
Yes, and we do it often. We start with a read of the theme: how it was structured, what was overridden, which compatibility modules are in place and whether the Hyvä version is current. You get a short written account of what we found and what we would change first. Nothing is rewritten for the sake of it.
Will new features slow the site down again?
Not if they are built the Hyvä way. The speed of a Hyvä store comes from shipping very little JavaScript and CSS, and it is lost one heavy script at a time. We build with Alpine.js and Tailwind rather than bolting in libraries, keep third-party scripts behind consent and off the critical path, and check the weight of every page we touch.
Does Hyvä itself need updating?
Yes. Hyvä publishes releases with fixes, new components and support for new Magento releases, and a theme that falls several versions behind becomes harder to upgrade. We keep the Hyvä version current as part of ongoing development, tested on staging, and plan it alongside Magento upgrades so the two move together.
How is this different from Magento development?
The backend is the same work on any frontend: integrations, pricing logic, imports and admin tools live under Magento development. This page is the frontend: templates, components, Tailwind, Alpine.js and compatibility modules. The same engineers do both.
Can you build a new Magento store on Hyvä from scratch?
Yes, and it is how we build every new Magento store. Design, theme, checkout, content and integrations are planned together, built on staging and launched with your catalogue and customers in place. A start-up and an established retailer begin the same way: with a written plan and estimate.
Can Hyvä be customised to match our brand?
Completely. Hyvä is a foundation rather than a template: every page is built from components styled to your brand, so two Hyvä stores need not look alike. Tailwind CSS makes a distinctive design quicker to build and easier to keep consistent.
Does Hyvä suit B2B and high-traffic stores?
Yes. Hyvä sends far less to the browser and asks less of the server per page, which helps most when traffic is heaviest. B2B features such as company accounts, quick order and customer-specific pricing work on Hyvä, with Hyvä Enterprise covering the Adobe Commerce B2B suite.
New to us? The free health check is a good first look at the store.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
- Magento Open Source, Adobe Commerce and Mage-OS stores
- No login, no access, no obligation
- Written by a person, not a scanner
Free store health checkOne page, by email
Example report Magento Security and Upgrade Health Check
example-store.co.ukNeeds attention
- Platform
- Magento Open Source 2.4.4-p3
- Adobe support
- ended 12th April 2025
- PHP
- 8.1, end of life 31st Dec 2025
- Frontend
- Luma
- Security headers
- 2 of 6 present
- Hijack indicators
- none found
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.