The Magento extension market is large and uneven. A store owner can find a module for nearly any feature, but quality varies by an order of magnitude between vendors. This guide is the checklist we run on every module before installing it in a customer's store.
Read this before you buy your next Magento extension. The fifteen minutes spent on due diligence saves the average team a week of debugging.
The seven questions that matter
Most extension-buying disasters trace to skipping one of these:
1. What is the Lighthouse impact?
Install the module on a reference store and run Lighthouse before and after. A 5-point drop is acceptable. A 10-point drop is the ceiling. A 20-point drop means the module is shipping unused JavaScript or blocking the main thread.
Vendors should publish their Lighthouse score. If they don't, ask for it. If they can't produce one, that is a signal in itself.
2. What versions of Magento and Hyvä is it tested against?
Magento 2.4.x has minor releases every few months. Modules compatible with 2.4.4 sometimes break on 2.4.7. A current module should declare exact tested versions, not a wildcard like "2.4+".
Hyvä compatibility specifically: a module that works on Luma does not automatically work on Hyvä. Look for a Hyvä compatibility module or a single codebase that supports both.
3. What is the update cadence?
Check the changelog. A healthy module ships fixes every 2 to 4 weeks. A module that has not shipped an update in 9 months is either feature-complete (rare) or abandoned (common).
Critical-path modules (search, cart, checkout) should be in active maintenance. Niche modules with no recent updates are usable but risky.
4. How do they handle support?
Read the support policy. Specifically: what response-time SLA does the vendor commit to, and what is excluded? Most module vendors offer 12 months of support included in the price, then a renewal fee. Some bury that renewal as a recurring subscription you opted into during checkout.
Read the small print on auto-renewal. If "Lifetime" actually means 12 months of updates and you must re-buy after that, the vendor's pricing page is misleading.
5. Where does the source code live?
After purchase, you should receive the full source code. If the vendor distributes only an obfuscated build, walk away. You cannot debug, patch, or audit obfuscated code, and you will not be the first store to need to.
Composer install is the cleanest delivery method. ZIP downloads are acceptable but create more friction at upgrade time.
6. What does the refund policy actually say?
A real refund policy is no-questions-asked, within 30 days, by email to a published address. Anything more elaborate (refund forms, screenshots required, must explain why) is a friction ladder designed to deflect refund requests.
Test it on the cheapest module the vendor sells. If you cannot easily refund a £49 module, you will not be able to refund a £499 one.
7. Are there real reviews?
Look for verified-purchase reviews with specific technical detail. "Great extension, easy to use" tells you nothing. "Replaced our Algolia setup, search latency dropped from 280ms to 90ms" tells you the reviewer actually used it.
Be skeptical of vendors with 100 percent five-star reviews and no critical feedback. Real catalogs have 3-star reviews about specific limitations. Their absence is more suspicious than their presence.
Red flags worth walking away from
- No public changelog. If the vendor cannot show you the version history, the version history is not pretty.
- Monthly subscription for what should be a one-time purchase. Some module features warrant subscription pricing (AI inference, SaaS data sync). Most do not. A subscription for a one-shot module is rent-seeking.
- Compatibility claims that don't match version dates.A module that claims "Magento 2.4.7 compatible" but was last updated 18 months ago has not been tested against 2.4.7. The claim is theoretical.
- Module names that are SEO-keyword strings. "Best Free Magento Cart Abandonment Email Marketing Pro" is not a product name. It is a search snippet. The vendor is gaming rankings rather than naming a product.
- License keys tied to the order email, not the domain. Means the license is portable across stores you do not own. Sounds like a feature; in practice it is a signal that the vendor is not tracking activations and won't honor support boundaries.
The total cost of a module
Sticker price is the start. The real cost includes:
- Engineering time to install. Plan 1 to 4 hours for a Composer module with admin config. Plan 8 to 16 hours for a module requiring custom configuration or theme overrides.
- Performance regression debugging. If the module drops Lighthouse, expect 4 to 16 hours of investigation.
- Magento upgrade compatibility. Each Magento minor release may require module updates. Budget 2 hours per module per Magento upgrade.
- Support renewal. After 12 months, most vendors charge 50 to 100 percent of the original price for another year of updates.
A £349 module realistically costs £500 to £1,500 in the first year. Compare on total cost, not sticker.
The build vs buy threshold
Custom development costs roughly 8 to 15 hours of engineering time per feature, at agency rates of £80 to £150 an hour. So a custom Magento module costs £640 to £2,250 to build, more for complex features.
Buy if: the off-the-shelf module covers more than 80 percent of your requirements. The remaining 20 percent can be customized via admin config or a small theme override.
Build if: the off-the-shelf modules cover less than 60 percent of your requirements, you have specific compliance constraints (data residency, custom audit trails), or the feature is core to your differentiation.
Where to find good modules
The Adobe Commerce Marketplace is the official channel. Quality varies but every listed module has been through a basic technical review. Hyvä Themes maintains a public list of Hyvä-compatible modules, updated continuously. Independent module marketplaces (eTechFlow Modules, and a small number of others) curate their catalogs against a published quality standard.
Cheap aggregator sites that resell modules from multiple vendors at a discount often strip license validation or ship outdated versions. The savings are not worth the risk.
FAQ
How do I evaluate a module without buying it?
Most reputable vendors offer a 30-day refund. Buy, install on staging, evaluate, refund if it does not meet your criteria. If the refund process is friction-free, the vendor is confident in the product.
What about free Magento extensions on GitHub?
Excellent for niche use cases and team-internal tooling. Less suitable for production storefront features. Free maintenance is unpredictable and security patches lag. Reserve open-source modules for non-critical-path features.
Should I prefer modules from large vendors or specialists?
Large vendors have wider catalog coverage but average lower per-module quality. Specialists ship deeper features and faster fixes for their narrow domain. We use a mix.
What if I need to customize a purchased module?
Verify before purchase that the module has a documented extension point or plugin API. Customizing via direct file edits creates an upgrade headache. Modules with a public plugin API let you override behaviors cleanly.
Quick checklist
- Lighthouse score declared and verified.
- Magento and Hyvä versions explicitly listed.
- Update cadence visible (changelog with dates).
- Support SLA stated, not hidden.
- Source code delivered.
- 30-day refund, no friction.
- Verified reviews with specifics, not just five-star.
If a module passes all seven, you are dealing with a serious vendor. If it fails three or more, find another option. There are usually 3 to 5 modules in any given category — you can afford to be selective.
If you want to talk through a specific module choice, the sales team is happy to advise unbiased on the right tool, even if it is not one we sell.