Five extensions, no longer sold
Installed modules keep running
The same engineers build to order
Five retired modules
What Changed
Five Modules, One Decision
For years we sold a small catalogue of Magento 2 extensions alongside our development work. Each one solved a gap we kept meeting on client stores. As the agency grew, the stores we build became too different from one another for a boxed module to fit them well, so we stopped selling the catalogue and put the same engineers on custom builds instead. These are the five modules that have been retired.
Why the Catalogue Closed
A boxed module has to suit every store it is sold to, and every Magento release asks for a compatibility round on each one. Both pulled senior engineers away from the custom work our clients were asking for, so we made the choice rather than let the modules fall behind quietly.
If you run one of them today
What Retirement Means for Your Store
Installed modules keep working
A module you installed carries on doing its job until a Magento upgrade changes the ground under it. Nothing is turned off remotely.
No new licences, no new releases
The catalogue is closed. We do not sell new copies, and we do not publish compatibility releases for new Magento versions.
The people who wrote it are still here
The engineers who built and supported these modules are the ones you reach through the form below, not a ticket queue that has to read the code first.
A compatibility review
We check the module against the Magento version you are moving to and tell you plainly whether it will survive the upgrade untouched.
Patch, replace or retire
A small patch, a custom replacement built for your store, or a clean removal if the feature has moved into Magento itself. You choose with the costs in front of you.
A written estimate first
Whatever the option, the scope, the price and the date are written down before any work starts, so the upgrade stays on your schedule and your budget.
Custom Magento modules
What We Build to Order
The same kinds of module we once sold off the shelf, written for one store at a time. Each starts from the feature you need and the Magento version you run, not from a settings page that tries to cover everyone.
Checkout and address validation
Address checks against the carrier or postal service you use, custom checkout steps, and delivery rules that follow your own logistics.
Content import, export and backup
Tools that move CMS pages, blocks, products and attributes between environments and stores, with the backup step that Magento leaves out.
Store locator and pickup
Maps of stores, dealers and pickup points on Google Maps or HERE, radius search, and in-store pickup wired into your checkout and inventory.
AI product content
Product descriptions, attributes and image tagging generated from your own catalogue data and brand rules, reviewed before anything is published.
AI upsell and recommendations
Cross-sell, upsell and search assistance driven by your sales history and stock, on Luma and Hyvä storefronts, with the rules you set.
Integrations with ERP, PIM and shipping
Modules that exchange orders, stock, prices and customers with the systems around the store, built on the platform's own APIs.
How it works
How a Custom Module Gets Built
One call about the feature
Your Magento version and installed extensions checked
A fixed quote and a date
Admin and storefront screens sketched first
Written to the Magento 2 coding standard
Tested on a copy of your store
Luma and Hyvä storefronts
Source in your repository
Deployed in your release window
Documentation handed over
Kept compatible through Magento upgrades
One team for the fixes that follow
Verified reviews
What Our Clients Say
2.1s
faster largest contentful paint
This team consistently goes above and beyond in terms of helping to ascertain the most viable and feasible outputs and outcomes for our evergrowing business needs.
Anthony Perrotta
E-Commerce Operations Manager
4 yrs
as their sole technical partner
They designed for where the product was going, not just what we asked for. Early on we described a single-company setup; they built the data model and permission layer so multi-tenancy wouldn’t require a rewrite later.
Alex Tee
CTO
Trusted by 100+ companies
Keep reading
Our Magento Knowledge Hub
FAQ
Frequently Asked Questions
Still have questions?
Tell us about your store and we will come back with straight answers.
Talk to us
Can I still buy Address Validation, CMS Import-Export, Store Locator, AI Sales Booster or Product Creation Assistant?
No. The five extensions were retired and are no longer sold or updated. If you need one of these features, we build a module for your store to the same brief, written for your Magento version and storefront rather than for a catalogue.
I already run one of these modules. Will it stop working?
Not because of the retirement. The module files on your server keep doing their job, and nothing is switched off remotely. What can break a module is a Magento upgrade, so write to us before you upgrade and we will review the module against the new version.
Will the retired modules work on Magento 2.4.8 and later?
We no longer publish compatibility releases, so there is no guarantee for versions released after the catalogue closed. For a specific store we can review the module, patch it, replace it with a custom build or remove it cleanly, with a written estimate for each option before you decide.
Can you build the same feature as one of the retired extensions for my store?
Yes. The engineers who wrote the original modules build custom ones to order: address validation, content import and export, store locators, AI product content, AI upsell and integrations are the most common requests. Each starts with a scope call and a fixed quote.
How long does a custom Magento module take?
It depends on the feature. A focused module such as a checkout validation step or a store locator is usually delivered within a few weeks from the signed scope. Larger builds with integrations are planned in milestones. The scope call gives you the date before any work starts.
Do you build for Adobe Commerce as well as Magento Open Source?
Yes. Our team is Adobe certified and builds for Magento Open Source, Adobe Commerce and Adobe Commerce on cloud infrastructure, on both Luma and Hyvä storefronts.
Who owns the code of a custom module?
You do. The module lives in your repository from the first commit, with documentation handed over at delivery, so any Magento developer can maintain it after us.
Let’s build something great together!
Need a Module Built for Your Store?
Tell us what the module should do and which Magento version you run. We will reply with a scope, a fixed quote and a delivery date before any work starts.