A sale badge is useful only when it describes the product the shopper is actually looking at. A label that stays visible after a promotion ends, covers the selected color swatch or advertises the wrong saving creates confusion. Choosing a product-label extension therefore involves rule accuracy, placement and maintenance as much as visual design.
This comparison examines Amasty Product Labels, Mageplaza Product Labels and Mirasvit Product Labels for Magento catalogs. Official sources were checked on October 21, 2026. The analysis is based on documentation and current release information; it does not present original conversion measurements, hands-on results or vendor performance claims as verified facts.
Define what a product label should mean
Product labels are conditional merchandising messages placed around product imagery or information. They can highlight a promotion, a new arrival or an attribute, but should not become a second pricing system. Decide which source controls the displayed saving, how configurable products behave and what should happen when several campaigns qualify at once.
Separate three decisions: the rule that selects products, the template that renders the message and the placement that attaches it to your theme. A strong rule builder cannot fix an incorrect gallery selector. A beautiful template cannot make an expired campaign accurate. The most useful comparison follows all three layers.
| Product | Documented approach | Purchase and implementation checkpoint |
|---|---|---|
| Amasty Product Labels | Conditional labels, priorities, configurable containers and edition-specific integrations. | Selected price/renewal unconfirmed; check active-subscription packages and Live Search requirements. |
| Mageplaza Product Labels | Designed badges with automated rules and multiple storefront placements. | Displayed base $149; Hyvä/API claims need exact package and support entitlement confirmation. |
| Mirasvit Product Labels | Labels organized through placeholders and templates, with built-in Hyvä support in recent versions. | Displayed base $149, then $90 yearly support/updates; custom templates still require integration work. |
Amasty Product Labels
Amasty’s manual describes customer-group conditions, scheduled display, multiple labels and priority handling. It also exposes container selectors for product images, names and other placements. This is relevant to stores whose galleries and product cards differ from the default layout: the extension needs a reliable attachment point rather than merely an attractive image asset.
The strength is granular presentation control. Its limitation is that selectors and compatibility packages become part of the store’s maintained configuration. When a theme changes its gallery markup, include label placement in the release review. A rule can still be valid while its output has moved, disappeared or started covering another control.
The product changelog includes Magento 2.4.9 and PHP 8.5 compatibility. The guide documents amasty/module-product-labels-hyva, along with separate packages for Hyvä Checkout, Enterprise Live Search and Product Recommendations. Some introductory wording says compatibility is available by default, while the detailed package section specifies installation and entitlement conditions. Obtain the actual package list for your edition and storefront before treating the setup as complete.
The accessible product text did not establish a reliable selected initial or renewal price. Request a quote covering Magento Open Source or Adobe Commerce, support/update duration and required integrations. The license is per Magento installation. Optional AI image-generation integration is another product dependency, not a reason to assume image generation is included in a basic labels purchase.
Mageplaza Product Labels
Mageplaza emphasizes configurable badges with rule-driven placement across product listings, product detail and related products. This is a straightforward shortlist option when the merchandising team wants reusable designs for ordinary campaign work. Assess the editor with your own label copy and translated text rather than deciding from a short English demo badge.
The current retrieved page identifies version 4.5.4, a displayed Magento range of 2.4.4–2.4.9, Hyvä support and API/GraphQL compatibility. Its release notes include PHP 8.5 support. Confirm the selected Community or Enterprise/Magento Cloud edition and the compatibility package for your precise theme version. A general API claim does not tell a headless team where to place labels or how to refresh them after option selection.
The displayed base price is $149, with one year of support selected. The page says an active subscription is needed for Hyvä support access and warns that additional customization can cost extra. Exact renewal and Commerce totals were not confirmed in the reviewed material. Ask for a written bill including the next support period rather than assuming the displayed entry amount is the full ownership cost.
Mageplaza’s license covers one live Magento installation and unlimited test installations. Confirm the mapping for multiple websites or store views. The benefit is an approachable campaign-oriented scope; the limitation is that your specific gallery, related-product blocks and customized card templates still need a demonstration. Include your longest translated label and a product with several simultaneously eligible campaigns.
Mirasvit Product Labels
Mirasvit separates labels, placeholders and templates. A placeholder defines where labels can appear and how many are allowed; conditions decide which products qualify. This structure is useful when the same campaign must work across several layouts without forcing every rule to duplicate presentation settings. It also gives developers a concrete integration model for custom product cards.
Current product documentation says Hyvä support has been built into the extension since version 2.6.0, without a separate compatibility package. Older quick-start guidance still discusses manual template work for Hyvä and custom themes. Treat the version-specific changelog as essential reading and ask which instructions apply to the supplied release. The current page calls for regenerating Hyvä configuration and rebuilding Tailwind after installation or update.
The vendor lists Open Source and Adobe Commerce 2.3–2.4.9. A precise supported PHP matrix was not confirmed in the reviewed product material, and PWA rendering was not established. Do not infer headless label support from another Mirasvit extension. Ask for the data contract and storefront implementation if your product listings are rendered outside Magento’s normal theme system.
The displayed base is $149, including one year of support and updates, then $90 per year for those services. Edition selectors can change the total. Licensing is per Magento installation and purchased edition. The advantage is an explicit placement model; the operational cost is managing templates, indexing and theme overrides so campaign changes appear when intended.
Evaluate accuracy before artwork
Create a small acceptance set: a simple discounted item, a configurable product whose children have different prices, a bundle, an out-of-stock product and a product that belongs to two campaigns. Define whether a saving refers to the selected variant or a parent-level value. Verify the expected result with the vendor rather than extrapolating from a simple-product screenshot.
Schedule one label to begin and end at known times. Ask how the rule index and full-page cache are refreshed, and whether a saved change requires a scheduled job, manual application or reindex. This matters to campaign accuracy even when the extension renders quickly. A store cannot promise a promotion ends at midnight if its publishing process leaves old labels visible afterward.
Inspect placements independently: category grid, search results, product gallery, related products and any cart or checkout surface you plan to use. Switch swatches and gallery images. A label that covers a wishlist button or intercepts a product link can undermine a carefully designed card. Check keyboard navigation, readable contrast, zoom and a narrow mobile viewport as part of acceptance.
Plan licensing, responsibilities and the decision
These are paid products; a demo, free installation or a subscription promotion is not a separate free edition. Record the supported Magento patch, PHP branch, Luma/custom theme or Hyvä version, any PWA requirement, production-installation count and renewal date. Ask which compatibility fixes are covered by support and which are custom development.
Define ownership inside your team too. Merchandising should control campaign eligibility and text, while a developer owns placement templates and gallery integration. Agree on one priority policy so overlapping badges do not obscure imagery. Preserve the original product price as the authority; avoid marketing copy that implies an unverified saving or popularity ranking.
Shortlist Amasty when its detailed containers and Commerce integrations match your catalog stack. Consider Mageplaza when the campaign editor and standard placement scope meet the merchandising team’s needs. Favor Mirasvit when placeholders and templates fit your development workflow, after checking the recent Hyvä packaging change. Choose the product that can demonstrate correct messages on your difficult products, not the one with the most decorative shapes.
Related comparisons cover search-result rendering and filtered catalog layouts, two places where product badges also need to remain accurate.
Official sources
Checked October 21, 2026: Amasty product/changelog, Amasty guide, Amasty license, Mageplaza product/release notes, Mageplaza license, Mirasvit product/changelog, Mirasvit setup guide, and Mirasvit license.