Algoshop AI Sales Chatbot helps answer shoppers' questions. A loyalty program creates another question worth answering clearly: what does a customer get by returning? Mage brings points, referrals and VIP tools to that task, with different routes for a next purchase, a friend's introduction and an ongoing customer relationship.
Mage supports points, rewards, referrals and VIP tiers, with additional retention features such as wishlist and save for later. The useful starting point is not activating every feature. It is choosing one behavior to reward and making the cost and customer promise intelligible.
Choose the behavior before choosing the reward
A loyalty program can encourage a second purchase, repeated replenishment or a referral. Those objectives do not call for identical incentives.
For a consumable product, the next natural purchase may arrive in a few weeks. A points balance that takes years to redeem may not feel useful. For a high-value item bought infrequently, a relevant referral benefit may make more sense than frequent purchase rewards.
Write the first objective as a behavior: “Give a customer a clear reason to return for their next replenishment order.” That is more actionable than “increase loyalty,” because it tells the team what the program should make easier.
Do not begin with a complex ladder of tiers unless those tiers describe meaningful customer relationships. More rules create more explanations, exceptions and potential support questions.
Match Mage capabilities to that objective
The Mage listing describes points and store-credit rewards, custom rewards including discounts, shipping and products, VIP tiers, referrals, customizable earning campaigns, wishlist/save-for-later features and integrations with tools such as Klaviyo, Judge.me and Omnisend.
Features differ by plan. The listing's plan structure separates the basic program, VIP capabilities and store-credit/cashback features. Confirm the current tier that supports your intended setup rather than assuming every reward is included everywhere.
Points and rewards give customers a clear reason to return.
For the replenishment objective, a straightforward points-to-discount rule is a useful candidate. Wishlist and save for later address a different stage—remembering a product before purchase—and should not be presented as points redemption.
Choose the retention problem before the reward
The next replenishment order needs a reason to return
Candidate Mage route: Purchase points and a reachable reward
Customer value to explain: Today's purchase leads to a usable future benefit
Satisfied customers can introduce suitable new buyers
Candidate Mage route: Referral program
Customer value to explain: A clear qualifying introduction and reward
Continuing relationships deserve distinct treatment
Candidate Mage route: VIP tiers
Customer value to explain: Understandable qualification and meaningful ongoing benefits
For a replenishment-focused program, a purchase reward is a candidate to evaluate. Wishlist and save for later keep a considered product accessible before purchase; a saved item is not evidence of a completed order.
The reward format should fit the next purchase. A discount gives a straightforward benefit on an eligible order. Free shipping can address delivery cost, while a free-product reward can introduce a relevant item. Store credit is another supported route, but its plan and redemption rules need to match the program you intend to offer. These choices create different customer promises; calling all of them “points” makes the experience harder to understand.
Mage's stated integrations also matter when the store already uses a retention stack. Check which supported connection serves your actual task—for example, whether the relevant loyalty information can be used in an existing customer communication workflow. Do not assume every integration exposes the same fields or sends the same messages. The benefit is fitting the program into the tools the team already uses, not introducing a second set of contradictory reward explanations.
The design decision is equally practical: the customer should be able to see what they have earned, identify a reachable benefit and understand the next action. A polished loyalty widget is valuable when it makes that choice easier. Review the actual rule and reward cost before adding more campaigns.
Calculate the cost of a simple points rule
Start with your own reward policy and order costs, not a hypothetical profit table. Mage's loyalty overview describes configurable earning rules, several reward formats and configurable points expiry. It does not establish what reward your particular store can afford.
Swipe horizontally to read the full table.
| Program decision | Information to collect from your business | Customer promise to check |
|---|---|---|
| Purchase earning | Eligible spending and the actual configured earning rule | Which purchases earn a benefit |
| Discount reward | Redeemed discount and any applicable conditions | How the customer uses it on a qualifying order |
| Shipping reward | Your eligible services, destinations and delivery cost | What shipping the benefit actually covers |
| Product reward | Product cost, availability and fulfillment requirements | Which item can be redeemed and when |
| Points expiry | The configured expiry rule and customer communication | Whether the balance remains available |
The table is a merchant planning checklist, not an app-generated profitability report. Points issued and rewards redeemed are different stages; do not call every issued point a redeemed discount. Ask your finance team how to monitor the program's costs consistently, including fulfillment and other order costs where relevant.
Keep the first rule simple enough to explain and review. A reward that is cheap to fund but difficult to reach may offer little customer value; a generous reward needs a sustainable commercial policy. Neither conclusion requires inventing an app performance percentage.
Explain earning and redemption in plain language
A customer should know how points are earned, what they can get and where they act. Avoid requiring them to decode an internal reward name.
Explain the actual configured rule: which actions earn a benefit, which reward is available and where to redeem it. Confirm exclusions and timing with the team before publishing terms. Do not put a guessed tax, shipping or refund rule into customer copy.
Mage's official overview describes both reward codes and checkout application. The current Listing places checkout extensions and store-credit/cashback features in Growth, so confirm the supported redemption experience for your plan and Shopify setup before promising one-click checkout redemption to every customer.
Write separate explanations for discounts, free shipping and free products. They create different expectations. A free-shipping reward does not mean every destination or delivery service is covered.
Review the experience on a phone. The reward widget should make the next action evident and display understandable terms, not just an attractive number.
Add referrals or VIP tiers only when they have a job
Referrals reward an introduction to another customer. VIP tiers recognize a continuing relationship. Neither should be added merely to make a launch look sophisticated.
VIP tiers organize loyalty benefits into different membership levels.
For a referral program, define who qualifies and what happens after the referred customer completes the relevant action. Verify the app's controls rather than inventing an automatic rule for every edge case.
The official referral page describes unique sharing links or codes, rewards for the advocate and friend, and configurable reward timing. It also describes safeguards for self-referrals, duplicate accounts and suspicious activity. These are controls to review, not a guarantee that referral fraud is impossible.
Decide whether rewards should be issued immediately or after a waiting period, then make that timing clear in the invitation and confirmation. A successful referral has a qualifying action; merely sharing a link should not be described as earning the purchase reward. Use the referral history to investigate a question rather than asking support to reconstruct the introduction from memory.
For VIP tiers, choose benefits the team can deliver consistently. A high-spending tier promising personal service needs an operational owner. A reward that looks generous but is rarely available can weaken trust.
Returns also need a clear policy. Check the actual point and reward handling and explain it to support. Do not assume that every adjustment or reversal follows the same behavior across reward types.
Evaluate repeat purchasing and reward cost together
Enrollment alone does not prove the program is helping. Compare repeat purchase behavior, redeemed reward cost and the margin of eligible orders over an appropriate period.
A program may attract many members but few redemptions because the reward is difficult to reach. Alternatively, redemptions may be frequent while discounts erode the margin of purchases that would have happened anyway. These are different issues and require different changes.
Use a defined customer group and time window when evaluating. An uncontrolled before-and-after comparison should not be described as proof that the app caused an improvement.
For a wallet-oriented experience, see the Webplanex guide; for giving a gift to someone else, Kartuu's personalized cards solve a different task.
Explore Mage on Shopify and its official website. Begin with a rule the team can explain, a reward the business can afford and a customer action worth encouraging.
