Amasty sells around 150 Magento 2 extensions. Strongest on catalog, navigation and admin tooling; sold as an annual subscription that licenses Magento installations rather than domains.
Amasty has been building Magento extensions since 2009 and now sells roughly 150 of them for Magento 2. If you run a Magento store and have ever bought a paid extension, odds are it came from Amasty or from Mageplaza.
This page is not a mirror of their catalog. It is what we tell clients who ask whether to buy Amasty, which extensions are worth it, and what the licence actually gives them.
Catalog and navigation. Native Magento layered navigation starts to hurt once you pass a few thousand SKUs on a wide attribute set: filters get slow, and multi-select or price sliders mean custom work. Improved Layered Navigation is the paid Magento extension we install more often than any other, and on a large catalog it is usually the first one to pay for itself.
The second cluster worth money is admin operations. Mass Product Actions, Advanced Permissions, Store Locator, RMA. These solve the jobs a merchandiser or support agent repeats forty times a week, and the time saved is easy to check before you buy: count how long the manual version takes today, multiply by how often, compare with the licence.
Storefront widgets are the weakest case. Automatic Related Products and Quick View are fine extensions, but they are also the sort of thing a competent frontend developer builds into your theme without adding another vendor to your upgrade path.
Since 1 February 2022 Amasty sells annual subscriptions, and two details trip people up.
First, you keep the code. A subscription gives you lifetime access to the codebase you bought plus one year of updates, and you own those updates permanently. If the subscription lapses, nothing switches off. You simply stop receiving new versions.
Second, the licence counts Magento installations, not domains. Several storefronts running on one Magento instance need one licence. Two separate installations need two, even if the same company owns both. That catches merchants who split staging into its own install and assume it is covered.
Whether lapsing matters depends on your upgrade cadence. On a frozen store that nobody touches, letting it lapse is a reasonable saving. If you patch Magento on Adobe’s schedule, it is a bad trade: core keeps moving to the next 2.4.x, your extension stops receiving compatibility releases, and you pay a developer to fix on upgrade day what a renewal would have covered.
One more piece of housekeeping, and we insist on it: buy under the merchant’s own Amasty account, not the agency’s. Licences bought on an agency account become somebody else’s asset the day you change agency, and untangling that is a support ticket you do not want during a migration.
Amasty moved to a Hyva-first position and lists over a hundred Hyva-compatible extensions, which is more than most vendors. Compatibility is still per extension, not a blanket promise. If your store is on Hyva or heading there, verify the specific extension on the product page before the invoice, because the alternative is paying a frontend developer to rebuild its templates and losing the upgrade path you bought the extension for.
We use both and do not have a religion about it. Amasty is the stronger choice for catalog, navigation and admin tooling, and its code quality is more predictable on complex modules. Mageplaza is cheaper and lighter for marketing features, and if the extension is small the price difference is real.
The vendor is not the expensive decision anyway. The stacking is. Every extension you install is another plugin on the same rewrite chain, and a store carrying fifteen of them has a slower checkout and a much more expensive Magento upgrade than a store carrying four. Our rule for clients: an extension has to fix a problem you can point at with a number. If nobody can name the number, the answer is no.
We install and configure Amasty extensions as part of Magento builds and support retainers, including the parts vendors leave out: resolving conflicts with other modules, patching the extension against your Magento version, and keeping the configuration documented so the next developer does not start from zero. If you are still choosing a stack, our Magento development services page covers where that fits, and the Magento extensions library lists the other modules we work with regularly. Merchants selling to businesses should read the Adobe Commerce B2B Suite page first, since the edition decision changes which third-party suite makes sense.
The reason most stores buy Amasty at all. Multi-select filters, price sliders and brand pages that stay usable when the catalog runs to thousands of SKUs and native filtering has already slowed down.
Mass Product Actions turns a day of clicking through the product grid into a filtered selection and one update. Merchandisers feel this one within the first week.
Advanced Permissions scopes admin users to particular stores, categories or product sets, which matters as soon as more than three people share the backend.
RMA gives customers a return request flow inside their account instead of email threads your support team rebuilds by hand every time.
A map and search for physical locations, which is the standard requirement for any retailer running shops alongside the online store.
Over a hundred extensions ship Hyva-compatible builds. Verify per extension before purchase rather than assuming the whole catalog is covered.
We use this in real client projects — here's what we've learned.
Buy narrow, not broad. Amasty is the vendor we reach for for catalog work, filtering and back-office tooling, and Improved Layered Navigation alone justifies the relationship on a large catalog. The mistake is treating the catalog as a shopping trip. Pick the two or three extensions that fix a problem you can measure, check Hyva compatibility per extension before paying, and buy on the merchant’s own account so the licences stay yours when the agency changes.
Price is per extension and set by Amasty, so check the product page for the current figure rather than a number quoted on someone’s blog. What matters more for budgeting is the model: it is an annual subscription per Magento installation, so eight extensions across two separate installs is sixteen licences, not eight.
Nothing switches off. You keep lifetime access to the codebase you bought and permanent ownership of every update released while the subscription was active. You stop receiving new versions. On a store that stays on its current Magento release that is a fair saving; on a store that follows Adobe’s patch schedule it means paying a developer later for compatibility work the renewal would have covered.
Per Magento installation. Multiple domains or store views running on one instance are covered by a single licence. Two separate installations need two licences, which is the detail that catches merchants who put staging on its own install.
Many are. Amasty took a Hyva-first position and lists more than a hundred Hyva-compatible extensions, but it is per extension, not a blanket guarantee. Confirm the specific one on its product page before purchase. Buying a non-compatible extension for a Hyva storefront means paying a frontend developer to rebuild its templates and losing the upgrade path you were buying in the first place.
We use both. Amasty is stronger for filtering and back-office tooling and behaves more predictably on complex modules. Mageplaza is cheaper for smaller marketing features. Neither choice is the expensive one; the number of extensions you stack is. Fifteen modules on the rewrite chain costs you at checkout and again at every Magento upgrade.
The merchant, always. Licences bought on an agency account are the agency’s asset, and separating them later is a support ticket nobody wants during a migration or handover. Buy under your own account and add your developers as users.
For layered navigation and bulk catalog operations, buying is cheaper than building. For storefront widgets such as related products or quick view, a competent frontend developer builds it into your theme and you avoid adding another vendor to the upgrade path. We decide it feature by feature and will tell you when custom work is the better value.
We can install, configure, or customize it for you.
Don't want to install yourself? Our developer connects via FTP, installs, configures, tests with a real transaction. Usually takes one business day.
