A rewards program creates a balance that customers expect the store to honor. That makes the choice of a Magento points extension more consequential than adding a promotional badge. You need to decide when points become available, what happens after a refund and whether customers can understand the rules without contacting support.
Amasty Reward Points, Mageplaza Reward Points and Mirasvit Reward Points and Loyalty Program are three different Magento extensions for earning and redeeming loyalty points. This guide compares official product information, configuration manuals and licensing terms reviewed on October 20, 2026. We have not run a retention experiment, tested their financial calculations or measured a revenue uplift.
Define the program before selecting the module
Start with a written earning and spending policy. Specify qualifying order states, treatment of discounts and tax, minimum redemption, expiry and refund reversals. A module can expose many rules while still being the wrong fit for your particular policy. For Adobe Commerce, first map existing native reward functionality and any stored balances so that a new extension does not introduce two competing ledgers.
Checkout compatibility deserves equal attention. Customers need to apply and remove points, change shipping and payment choices, and see consistent totals. Our one step checkout comparison explains the separate checkout choice. A working account balance display is not enough to establish that redemption works with your payment flow.
| Product | Useful fit | Edition and cost boundary |
|---|---|---|
| Amasty Reward Points | Rule-based earning and spending within an Amasty implementation | Paid editions; confirm plan, renewal and active-subscription compatibility packages |
| Mageplaza Reward Points | Teams wanting a visible progression from basic configuration to advanced rules | Observed Standard $99, Professional $199, Ultimate $299 first year for displayed base selections |
| Mirasvit Reward Points and Loyalty Program | Programs combining points, loyalty tiers and referrals | Observed Open Source $199 first year, then $120 annually for updates and support; Commerce costs differ |
Amasty Reward Points
Amasty Reward Points documents earning actions, spending controls, balance administration, expiry notifications and customer transaction history. Its user guide provides the configuration context needed to turn those options into a program policy. Treat the different paid editions as editions of one product, rather than separate alternatives.
Release notes distinguish Pro-only earning actions, including points calculated as a percentage or by an amount spent. Suggested functionality packages can require an active product or support subscription. The product also advertises Hyvä Theme and Hyvä Checkout support, GraphQL and payment integrations. Adobe Payment Services has a specifically named package, amasty/module-rewards-adobe-payments; ask whether your selected release needs other payment or checkout packages.
The changelog reports Magento 2.4.9 and PHP 8.5 compatibility. Obtain confirmation for your exact Magento Open Source or Adobe Commerce patch and purchased edition. Luma, Hyvä and a custom PWA have different display and redemption paths; GraphQL availability should lead to a review of the actual operations your frontend needs, not an assumption of a complete headless integration.
The advantage is configurable program behavior with documented integration boundaries. The limitation is that plan and subscription details affect what you receive. We could not verify a stable selected-plan price and renewal amount from the reviewed page. Request a quote naming the edition, support/update term and compatibility modules. Amasty’s license policy uses one Magento installation as the licensing unit, including multiple domains within that instance.
Mageplaza Reward Points
Mageplaza Reward Points separates Standard, Professional and Ultimate. The displayed base first-year prices were $99, $199 and $299 respectively. Its feature matrix puts basic earning/spending configuration in Standard, more detailed rules in Professional, and additional interaction/reward features in Ultimate. Confirm the Community or Enterprise selection before relying on those headline prices.
The separate Standard, Professional and Ultimate manuals are useful for matching a policy to an edition. Ask for a demonstration of your actual earning condition rather than purchasing a tier because its name sounds comprehensive. A fixed store-wide conversion rate and a conditional catalog promotion are different requirements.
The product lists Magento 2.4.4–2.4.9, Hyvä Theme and Hyvä Checkout compatibility. Recent changelog entries also identify fixes for specific frontend and redemption behavior. That is a reason to select a maintained release and test your chosen checkout combination. We did not establish a complete product-specific PHP version matrix for all those Magento releases. Request Composer requirements and confirmation of the PHP version you run.
Mageplaza’s terms cover one live Magento installation and unlimited test installations, with a year of support and updates for paid extensions. The selected renewal amount was not independently confirmed. This product is a useful shortlist option when an edition maps cleanly to your program. Its limitation is the edition boundary: confirm that the rules and customer interactions you need are included, and separately validate PWA endpoints if your storefront is headless.
Mirasvit Reward Points and Loyalty Program
Mirasvit Reward Points and Loyalty Program combines points, loyalty tiers and referral functionality. The vendor lists Magento Open Source and Commerce 2.3 through 2.4.9 and advertises Hyvä and GraphQL support. The observed Open Source price was $199 for the first year, followed by $120 per year for updates and support; Commerce and Cloud selections cost more.
The earning-rules documentation separates cart and behavioral rules. Its spending guide covers redemption conditions. That separation is valuable when your team wants to change how points are earned without silently changing their spending value. It also requires an owner who understands which rules may combine.
The changelog records ongoing changes to tiers, referral attribution and transaction handling. Read the notes for the exact version being installed, particularly if importing balances or changing tier qualification. A vendor changelog is evidence of documented changes, not evidence that Magentrio has verified every edge case. A full Magento/PHP pairing matrix was not confirmed; obtain that answer with the package version.
The license agreement covers one installation and the purchased Magento edition, with one year of support and updates initially. The attraction is having several related loyalty mechanisms in one product. The limitation is operational complexity: tiers and referrals add decisions about qualification, expiry and abuse. Confirm Hyvä Checkout separately from a theme badge and review required modules for Luma or a PWA before committing.
Use a transaction scenario to evaluate each option
Write a proposed acceptance scenario with one normal order, a coupon, a partial shipment, a cancellation, a partial refund and an order paid partly with points. Record the intended balance after every event. Include a customer who changes store view or currency. These are recommended checks for your implementer, not results from a test we performed.
Ask when points are reserved, earned and spendable, and which event reverses them. Clarify rounding, the effect of shipping and tax, and whether imported points preserve expiration dates. Decide how support staff can correct a balance and how the correction is explained to the customer. For referrals, define attribution and self-referral rules before enabling incentives.
Compare three-year cost, including the required edition, annual support, checkout integration, migration and ongoing program administration. Paid support is not necessarily custom development. Obtain confirmation of the number of Magento installations, websites and store views covered, and whether staging can use the same license. None of the paid options reviewed here should be assumed to have a free edition containing the full program.
Which product fits your loyalty policy?
Consider Amasty when its documented rule configuration and integration packages match your existing stack. Consider Mageplaza when its edition matrix lets you buy the specific level of rules you need. Consider Mirasvit when points, tiers and referrals belong in one coordinated program and your team can maintain the policy.
The decision should follow an explainable balance calculation and a supported checkout path. It should not follow an unverified promise of repeat purchases. If a theme change is also planned, consult our storefront architecture comparison before budgeting the redemption interface twice.
Official sources and research scope
Official pages and manuals linked above were checked October 20, 2026. Prices are observations for stated selections; taxes, custom work and unconfirmed renewals need a current quote. No financial or retention results are claimed. The featured illustration is AI-generated conceptual artwork, not an extension interface.