Loyalty Program Terms and Conditions: 5 Clauses to Lock Before Launch

The short version: Devaluation, expiry, clawback and closure are all things you may do to member balances without their consent — and each one is only defensible if a clause written before launch authorises it. This article gives you the five clauses, the wording each must contain, and a 10-minute pre-launch review that traces every unilateral action you might take back to a clause.

Key takeaways

• A loyalty program's terms are an operating document: they authorise the four unilateral actions — change, expiry, reversal, closure — you may need to take later.
• The five clauses to lock before launch: change/devaluation, expiry, reversal/clawback, fraud/abuse, and closure with a redemption window.
• Change clauses need a notice period and a statement on whether existing balances are grandfathered; expiry clauses need a trigger your software can actually run.
• A clawback clause your point system cannot execute — no defined fraud, no hold mechanism — generates disputes instead of resolving them.
• Run a launch review that lists every unilateral action you might take and names the clause that authorises it; anything without a clause is a future support ticket.

Why your terms are an operating document, not boilerplate

Your loyalty program terms and conditions are the document that authorises unilateral action: changes to point value, expiry of balances, reversal of earned points, and shutdown of the program itself. Each of these is something you do to a member's balance without asking them first. A clause written before launch makes that action defensible; its absence makes it a negotiation with every affected customer at once.

A unilateral action is an operation you perform on member balances without individual consent — devaluing, expiring, clawing back, or closing. The distinction that matters: day-to-day disputes (a missing order, a returned item) get resolved case by case, but unilateral actions hit every balance simultaneously. Those four actions are the reason the terms exist as an operating document rather than legal decoration.

Note: this article is not legal advice. Have a qualified professional review your final terms for your jurisdiction before publishing.

The classic failure: a shop launches with a generic template copied from a competitor's site. Eighteen months later they need to cut earn rates and the template says nothing about changing point value. Every adjustment becomes a refund demand, and the shop either absorbs the cost or takes reputational damage it did not have to take.

The five clauses every points program needs

A points program needs five clauses before launch: change/devaluation, expiry, reversal/clawback, fraud/abuse, and closure. Naming the clause is not enough — each must state the specific mechanics that let your systems and your support team act without improvising.

Here is what each clause must actually say, one line at a time:

1. Change and devaluation. State that point values, earn rates and reward costs may change, the notice you will give (see §3), and whether balances already earned are honored at the old value.

2. Expiry. State whether points expire, what triggers expiry — account inactivity for a stated period is the common choice — and how members are warned before it happens. The inactivity period is illustrative; set it from your own purchase cycle, not from a template.

3. Reversal and clawback. State that points earned on a transaction can be deducted when that transaction is refunded, charged back, or found to be fraudulent, and that a redemption made against those points may create a negative balance or an equivalent charge.

4. Fraud and abuse. State that accounts used for fraud, self-referrals, or gaming of promotions can have points voided and the account closed — and define the behaviors, because "fraud" alone is unenforceable (see §4).

5. Closure. State how much notice you give before shutting the program, how long members have to redeem, and what happens to unredeemed balances on the shutdown date.

Change and expiry clauses: wording that survives a devaluation

A change clause that survives a devaluation does three things: it sets a notice period, it states whether existing balances are grandfathered, and it hands off to a migration plan when they are not. Miss any of the three and a routine margin adjustment becomes a public argument about broken promises.

Work an example so the stakes are concrete. Say 1,000 points redeems at $0.01 per point, so a member sitting on 1,000 points holds $1 of value [illustrative figures — replace with your own earn rate and redemption value]. If you cut earn rates from 5 points per dollar to 3, existing balances are untouched — but if you also raise the redemption cost of a $10 reward from 1,000 to 1,500 points, every balance just lost a third of its purchasing power. The clause determines whether that move was announced or sprung.

On notice period: pick a duration you can operationally honor — a workable floor is email plus an on-site banner, using channels your own cadence can honor — and write it into the clause. Treat the exact number as illustrative; set it from your own email cadence and program-terms update process. On grandfathering: the cheaper and safer wording is that the clause covers future earning, while balances already earned are honored for a stated window. That window is exactly the runway your migration plan needs — the 60–90-day sequence for announcing a value change, capping the old rate, and clearing redemptions is laid out in Loyalty Program Devaluation: A 60–90-Day Migration Plan.

Expiry wording has the same discipline. "Points may expire" is unenforceable vagueness; "points expire after 12 months of no qualifying purchase, and we email you 30 days before" is a rule your expiry job can run and a member can understand — but both figures are illustrative (12 and 30 — set them from your own purchase cycle and email cadence). The trigger has to match something your platform actually measures — last purchase date, last login, last redemption — or the clause promises a mechanism you do not have.

The classic failure: a shop writes "points never expire" during launch because it sounded generous, then discovers dormant balances compounding as liability. Changing that promise later requires exactly the grandfathering machinery the change clause was supposed to provide — and it no longer exists.

Clawback and fraud clauses: write them so the ledger can enforce them

A clawback clause is enforceable when its reversal triggers match what your point-hold and return rules actually do; a clause your system cannot execute is a dispute generator. The wording and the ledger have to describe the same world.

Reversal triggers are the events that deduct previously earned points: refunded orders, chargebacks, and canceled transactions. If your return policy refunds the cash but leaves the points, your clause and your ledger disagree, and the member will find the gap before your support team does. The hold-and-reverse mechanics — delaying points until the return window closes, deducting on refund — are set out in Loyalty Point Holds: Stop Unearned Redemptions Before Returns.

Now the arithmetic that makes clawbacks expensive to improvise. A member earns 500 points on a $100 order at a 5% earn rate, redeems them for $5 off a second order, then returns the first. The shop has paid out $5 on a transaction that no longer exists. The clause must say what happens next: deduct 500 points, letting the balance go negative, or collect the $5 equivalent. Which of those you choose is illustrative — pick the one your platform can enforce and write only that one down.

Fraud wording has a harder requirement: definition. "We may void points obtained fraudulently" names no behavior and proves nothing. The clause must list the conduct — self-referrals, multiple accounts, coordinated review abuse, exploiting a promotion bug — so a support agent can point to the line when voiding. If review rewards are part of your program, the abuse patterns worth defining are covered in Loyalty Program Fraud Prevention: Six Minimum Controls, which pairs each fraud vector with the control that catches it.

Watch for the same trap here: a clause that says "fraud" and nothing else. When the shop finally voids 80,000 points from a referral ring, the members demand a definition, the shop has none to give, and the void turns into a public thread about arbitrary punishment.

The closure clause and the pre-launch review

The closure clause must set a redemption window and state what happens to unredeemed balances when the program shuts down — because a shutdown with no wind-down terms converts every unredeemed point into a support ticket and, in some jurisdictions, a legal question about whether points were prepaid value. Redemption window: the notice period after which members can still redeem but no longer earn. Balance treatment: whether unredeemed points convert to a discount code, a gift card, or nothing — stated plainly, in advance.

The window length is illustrative; set it from your redemption velocity — long enough that an average member can act, short enough that the liability actually clears. If you want the accounting side of shutdown — how outstanding balances sit on your books and what controls keep that number honest — Loyalty Points Liability: Build Controls Before Campaigns covers the ledger before the launch, which is when a closure clause is cheapest to write.

Then run the 10-minute review. List every unilateral action you might ever take: change earn rates, change redemption costs, expire points, reverse points on returns, void for fraud, suspend an account, close the program. For each one, name the clause that authorises it. Anything you cannot trace to a clause is either an action you promise never to take or a clause you still need to write — and launch day is the last moment that choice is free.

Do this on a single page: action, clause number, notice given, system that executes it. If the "system that executes it" column is empty for a row, you have written a promise your software cannot keep — fix that before the first member signs up, not after the first devaluation.

Frequently asked questions

Can I add these clauses to my terms after launch?

You can change your terms going forward, but applying a new clause retroactively to balances earned under the old terms is exactly the unilateral action the clause was meant to authorise — and you had none. Expect resistance; some operators treat a post-launch addition as grandfathered to existing members and binding only on new ones.

Do the terms need to be a lawyer-written document?

This article is not legal advice, so treat the five clauses as an operating specification, not a finished contract. A common path: draft the mechanics yourself, then have a professional review jurisdiction-specific language — consumer protection rules around points and prepaid value vary.

What if my loyalty software cannot deduct points or let a balance go negative?

Then write the clause around what it can do — refund the cash equivalent, block future redemptions until the balance recovers — or change software before launch. The failure is promising a mechanism in writing that your ledger cannot execute, because members will hold you to the document, not your platform's limitations.