
Mage keeps points expiry off by default, a useful starting point for loyalty program terms and conditions that customers can live with. The setting matters because your terms should describe the program customers actually experience, not a generic legal document copied from somewhere else.
Short answer: Explain how customers earn, use, lose, and dispute rewards in plain English. Cover expiry, refunds, tier changes, fraud, account closure, program changes, and customer notice, then check that every rule matches your live Shopify configuration. This is a planning framework, not legal advice. Have qualified counsel review the final document for your business and jurisdiction.
Start with loyalty program terms and conditions customers need to understand
| Rule area | Customer question | What the terms should state | Operational setting to verify |
|---|---|---|---|
| Membership | Who can join and how? | Eligibility, enrollment and account requirements | Signup and account flow |
| Earning | How do I earn rewards? | Eligible actions, exclusions and timing | Earning rules |
| Redemption | How do I use rewards? | Reward types, limits and checkout restrictions | Reward catalog and checkout |
| Expiry | Can I lose my balance? | Trigger, dates, reminders and exceptions | Expiry settings |
| Status | How do VIP tiers work? | Qualification, retention and downgrade rules | Tier configuration |
| Changes | What happens if the program changes? | Notice, effective date and transition treatment | Change-management process |
Separate loyalty rules from your general terms and privacy policy
A loyalty terms page should govern the program: points or store credit, rewards, referral credits, VIP status, expiry, and account treatment.
Keep broader website terms, refund rules, marketing consent, and privacy disclosures separate. Link to them where they affect the program. If you collect birthdays, social actions, referral details, or other customer data, explain the loyalty rules here and address data handling in your loyalty program data privacy policy.
Write the customer promise before the legal protection
Start with a short “How the program works” summary. For example: customers earn rewards on eligible purchases and selected actions, then redeem eligible rewards at checkout.
That summary forces you to state the value exchange clearly before adding protections for refunds, abuse, and program changes.
Define key terms
Define words that carry financial consequences. A qualifying purchase might exclude canceled orders, refunded orders, gift cards, sale items, or specific collections. A reward may mean a discount, free shipping, free product, or store credit.
Also state whether the loyalty currency is points or store credit. Do not describe a loyalty ledger as Shopify-native store credit unless that is genuinely the mechanism you use.
“Cannot say enough good things about the team at Mage Loyalty, one of the absolute best organizations we have ever worked with, full stop! So glad we connected with them, completely redid our loyalty program, new concepts, use of loyalty, increasing user engagement, showing us where we were not valuing our best customers, just WOW, amazing team!”


Read the West Coast Goalkeeping case study →
Step 1: Document how customers earn and redeem rewards
List every earning action
Only list actions your store actually offers. That may include purchases, account creation, birthdays, reviews, social follows, wishlist saves, referrals, receipt submissions, or subscription milestones.
For each action, state the reward amount or calculation, whether it can be earned more than once, and any approval requirement.
Explain qualifying purchases and exclusions
Define when an order qualifies. Is it when payment is captured, when the order is fulfilled, or after the return period closes? Are taxes, shipping, discounts, gift cards, subscriptions, sale products, or certain collections excluded?
Your rules should explain reversals too. In Mage, partially refunded orders reverse points proportionally, rounded down, and spend-based tier totals are reduced too. Describe the refund behavior customers will see, including partial refunds and chargebacks.
State when points or rewards become available
Give customers a specific event: “Points become available after your order is paid,” or “Referral rewards are issued after the return period.” Mage referral rewards can be issued immediately or after a delay, so the terms should mirror the chosen timing.
Describe redemption limits and checkout use
State minimum purchase requirements, excluded products, whether rewards can be combined, and whether one reward can be used per order. Explain what happens if a reward expires after it has been issued but before it is redeemed.
A simple journey is enough: “Earn points on an eligible order, choose an available reward, and apply it at checkout if the order meets the reward conditions.” Your Shopify loyalty program settings must support that promise.
Step 2: Write a points expiry policy customers can predict
| Expiry model | How it works | Best fit | Customer risk | What to disclose |
|---|---|---|---|---|
| No expiry | Balances remain available | Infrequent purchase categories | Old balances can accumulate | That points do not expire |
| Time after acquired | Each earning event has its own deadline | Programs with clear earning dates | Customers may miss separate deadlines | Exact window and calculation |
| Last purchase date | A purchase resets the balance clock | Repeat-purchase programs | Customers may not realize inactivity matters | Exact inactivity window and reset event |
Choose the expiry trigger
Points expiry and VIP tier progress expiry are different rules. Put them under separate headings so customers do not confuse losing points with losing status.
Mage supports “Time after acquired,” where each award expires on its own schedule, and “Customer’s last purchase date,” where a new purchase resets the clock for the customer’s balance. Say which model you use, the exact number of days, the timezone used for calculation, and whether each earning event has its own expiry date.
Set a window that fits purchase frequency
An expiry policy should reflect how customers naturally buy. A replenishment business may have a shorter cycle than a high-AOV jewelry brand where customers may purchase only once or twice a year. Review your loyalty programs by industry assumptions before choosing a deadline.
Expiry is also a trust issue. In one consumer survey, 47% of respondents identified points that disappear before use as their top loyalty-program frustration. Do not use expiry to quietly manufacture loyalty breakage.
Explain reminders and missed notifications
Say whether you send reminders, when they are sent, and through which channel. Also say whether a missed email, an unsubscribed customer, or a delivery failure changes the expiry date, subject to applicable law and your approved exception process.
Mage can show expiry dates in the customer account sidebar and Rewards Widget. If you offer goodwill reinstatement, state who can approve it and whether it is discretionary.
State what happens after expiry
Be explicit: expired points are removed from the balance, cannot be redeemed, and are not automatically restored. If you introduce expiry after launch, state whether it applies only to future earnings or to existing balances.
Treat Shopify-native store credit separately. Shopify says store-credit expiration is set per issuance, not through one store-wide default, and merchants should check local laws before setting an expiration date.
Step 3: Explain VIP tier progress, upgrades, and downgrades
| Decision | Possible rule | Customer impact | Required disclosure |
|---|---|---|---|
| Qualification | Spend, points earned or order count | Defines how customers advance | Metric and threshold |
| Progress period | Lifetime, calendar year or rolling year | Defines how long activity counts | Start date and measurement period |
| Recalculation | Ongoing or scheduled review | Status can change over time | Timing and refund treatment |
| Protection | No protection, fixed protection or top-tier protection | Limits downgrades | Scope and duration |
| Tier rewards | Entry reward or tier-only reward | Benefits can depend on current status | What happens after downgrade |
Define the qualification metric
State whether customers qualify through spend, points earned, number of orders, or another clearly defined measure. Define what counts toward the total and include the program start date if historical activity does not count.
Choose lifetime, calendar-year, or rolling-year progress
Mage supports Lifetime, Calendar Year, and Rolling Year tier-progress models. Lifetime is easiest to explain. Calendar-year progress creates a shared reset point. A rolling year reflects recent activity but needs clearer communication because older purchases fall out of the calculation over time.
Set downgrade protection
Separate earning a tier from retaining it. State whether status is protected for a period, whether the highest tier is protected, or whether tiers recalculate without protection.
Status has emotional value as well as discount value, which is why VIP tier psychology matters when writing downgrade language.
Explain refunds and recalculation
State that refunds can reduce qualifying spend, order totals, or points, which may affect tier status. Also explain what happens to tier-specific rewards after a downgrade.
If your program removes unused entry rewards or tier-specific benefits after a downgrade, state that directly in the terms. Do not promise permanent status if the live program recalculates it.
Step 4: Add clauses for value changes, refunds, and program changes
Protect future changes without rewriting the past
Specify which changes apply only to future earning, which affect existing balances, and what notice or transition period applies.
For example: “We may change earning rates for future purchases” is clearer than a blanket right to alter everything without explanation.
Give notice for material changes
Material changes deserve visible notice before they take effect. Put the effective date beside the change, update the terms version date, and communicate through the channels customers actually use.
A stronger clause says: “We may change earning rates, reward costs, or eligible products. We will publish material changes before they take effect and state whether they apply to rewards or points already earned.”
Handle existing balances fairly
Decide what happens to balances during a transition. You may allow redemption under the old reward cost for a limited period, preserve existing expiry dates, or apply new rules only to future earnings.
Version every terms document and archive prior versions. When a customer disputes an expired balance or changed reward, your team needs to identify the terms in force when the benefit was earned.
Also state that canceled, refunded, fraudulent, or chargeback transactions can result in reversed points, rewards, or tier progress.
Step 5: Write a fraud and abuse clause that is specific, not threatening
Define prohibited behavior
Name the behavior you actually need to prevent: duplicate accounts, self-referrals, email aliases used to claim repeat referral rewards, false receipts, automated activity, chargebacks, resale of rewards, or attempts to bypass published limits.
Describe the business response
State the possible response: withholding a pending reward, reversing an issued reward, canceling a discount code, restricting loyalty-program access, or closing a loyalty membership after review.
Clarify whether restrictions affect only the loyalty program or also prevent ordinary shopping.
Use evidence-based language
Avoid declaring that a customer “is fraudulent.” Say that you may review activity that reasonably appears inconsistent with the rules.
Mage’s referral settings can block self-referrals and email aliases. Referral rewards can also be delayed until after a return window, reducing the need to claw back rewards from returned orders.
Create a review path for disputes
Give customers a support route and ask them to provide the email address, order number, or referral details involved. A short review process makes the clause feel proportionate while protecting the program from obvious abuse.
Step 6: Cover account closure, inactivity, and unused rewards
Customer-requested closure
State whether a customer can leave the loyalty program without deleting their store account. If closing the account removes points, rewards, referral credits, and VIP status, say so before the customer confirms closure.
Merchant-initiated closure
Reserve the ability to remove a customer from the loyalty program for abuse, account errors, or other stated reasons. If you close a loyalty membership, say whether the customer can still place ordinary orders.
Inactive accounts and program closure
Do not create a hidden inactivity rule. If inactivity causes points to expire, describe it as an expiry policy, including the trigger and timeline.
State what happens if the program ends, the store closes, or you change platforms. Customers need to know whether they have a redemption period, whether balances expire on a stated date, and where to contact support.
Keep Shopify-native store credit separate from loyalty points or an internal store-credit ledger. Shopify says signed-in customers can use store credit at checkout through customer accounts or Shop Pay, but that does not define how your loyalty balance works.
Run a readability and implementation check before publishing
Use a two-layer format
Put a short program summary first, then the full terms below it. Descriptive headings, short paragraphs, examples, and effective dates make difficult clauses easier to find.
This matters because only 5% of consumers in one cited body of research said they read software terms and conditions in full.
Test the hard clauses with real customers
Ask someone outside the program team to answer practical questions from the document: When do my points expire? What happens after a partial refund? Can I lose my tier? Can I appeal a removed referral reward?
If they cannot answer quickly, rewrite the clause.
Match the document to the platform settings
Compare the terms against the live configuration before launch and after each program change. Test partial refunds, expired balances, referral returns, tier recalculations, account closure, and reward redemption limits.
Mage Test Mode can help merchants check earning, redemption, and integration behavior with a test list before exposing a rule to customers.
Review with qualified legal counsel
Ask counsel to review jurisdiction-specific consumer protection, privacy, marketing consent, tax, gift cards, store credit, and dispute provisions.
Your terms should identify the applicable governing law, the process for raising and resolving a dispute, and any venue or arbitration approach that applies where appropriate. They should also identify required local disclosures. There is no universal legal formula, so this section needs review for your business and jurisdiction.
Before publishing, confirm that the terms name the earning rules, redemption rules, expiry trigger, refund treatment, tier period, fraud process, closure treatment, support route, version date, and change-notice process.
Frequently asked questions
What should loyalty program terms and conditions include?
Loyalty program terms and conditions should include eligibility, earning, redemption, expiry, refunds, reward restrictions, VIP tiers, program changes, fraud, account closure, support, and applicable dispute provisions.
Can loyalty points expire?
Loyalty points can expire if the program clearly states the expiry trigger, window, calculation method, reminder process, and treatment after expiry. Terms should distinguish points expiry from VIP tier-progress expiry.
How do you write a fair points expiry policy?
A fair points expiry policy uses a window that fits natural purchase frequency, states the exact trigger, shows customers when balances expire, and explains reminders and exceptions.
Can a loyalty program change the value of points?
A loyalty program can change earning rates, reward costs, or eligible products if its terms explain how and when changes take effect. The terms should distinguish future earning from already-earned balances and provide notice for material changes.
Can VIP members be downgraded?
VIP members can be downgraded when the program clearly explains qualification periods, recalculation timing, downgrade protection, refund treatment, and the effect on tier-specific rewards.
What happens to loyalty rewards when a customer closes their account?
Loyalty rewards on account closure depend on the published program rules, which should state whether points, referral credits, rewards, and VIP status are canceled. The terms should also explain how customers can dispute a balance issue.
Before publishing, test the terms against your live program, make the customer consequences easy to find, and have qualified counsel review the final version.
Graeme is the co-founder at Mage Loyalty. He heads product development, from complex loyalty migrations and large-scale data handling to building the features shaping the future of loyalty on Shopify.
















