Loyalty Program Optimization

Loyalty Program Optimization

Overview

A well-designed loyalty program increases repeat purchase rate by 20–40% and CLV by giving customers a compelling reason to consolidate their spending with your brand. Dedicated loyalty apps handle the entire points engine, tier management, redemption mechanics, and customer-facing portal without custom code. The strategic decisions — which tiers to create, what benefits to offer, and how to avoid training customers to wait for redemptions — are where the real work is.

When to Use This Skill

• When launching a new loyalty program from scratch
• When an existing points program has low redemption rates or member engagement
• When wanting to add tiered VIP benefits to an existing points program
• When diagnosing whether your loyalty program is driving incremental revenue or just rewarding purchases that would have happened anyway

Core Instructions

Step 1: Choose the right loyalty platform

Recommend Smile.io for most stores — it has the best balance of features and simplicity, works on all major platforms, and has a free tier to start.

Step 2: Design your program structure

Before installing anything, define:

Points earn rate:

• 1 point per $1 spent (= 1% cashback equivalent at 100 points = $1)
• Adjust based on your margins — consumer goods (30%+ margin): 1 point per $1 is fine; lower margin products: 0.5 points per $1

Tier thresholds (use annual spend):

Redemption rate: 100 points = $1 discount (set a minimum of 500 points to redeem)

Non-purchase earn actions (makes program stickier at no revenue cost):

• Account sign-up: 100 points
• Leave a review: 50 points
• Refer a friend: 200 points (if they purchase)
• Birthday month bonus: 2x points on all purchases

Step 3: Set up your loyalty program

---

Shopify with Smile.io

1. Install Smile.io from the Shopify App Store 2. Go to Smile.io → Points → Ways to Earn and configure:

• "Place an order": points per dollar (set your earn rate)
• "Create an account": 100 points
• "Happy birthday": 2x points in birthday month
• "Write a review": 50 points (connects to Judge.me or Stamped Reviews)
• "Refer a friend": 200 points per successful referral

3. Go to Smile.io → Points → Ways to Redeem and configure:

• "Discount on order": 100 points = $1 off
• Set minimum order value for redemption ($30 recommended)

4. Go to Smile.io → VIP → Create Program and set up your tiers:

• Enter the tier names, point thresholds, and benefits (free shipping, multipliers, etc.)

5. Go to Smile.io → Rewards Panel to customize the widget that appears on your storefront 6. Connect Smile.io to Klaviyo under Smile.io → Integrations — this enables sending points balance in Klaviyo emails

---

WooCommerce with YITH WooCommerce Points and Rewards

1. Install YITH WooCommerce Points and Rewards from the WordPress plugin directory ($149/yr) 2. Go to YITH → Points and Rewards → Points → Earn Points and configure:

• Points per currency unit: 1 point per $1
• Registration bonus: 100 points
• Review bonus: 50 points

3. Go to YITH → Points and Rewards → Redemption and set:

• Points per currency: 100 points = $1 off
• Maximum discount allowed: 20% of cart value (prevents 100% discount gaming)

4. For tiers: install YITH WooCommerce Membership to create VIP tiers based on spend level

Alternative: Use Gratisfaction plugin (more feature-rich, $99/yr) which includes gamification, social sharing rewards, and birthday bonuses.

---

BigCommerce with Smile.io

1. Install Smile.io from the BigCommerce App Marketplace 2. Configuration is identical to the Shopify setup described above 3. Smile.io integrates with BigCommerce's native coupon system for redemption

---

Custom / Headless

Use a loyalty API platform like Voucherify or Loyaltycrm.com rather than building from scratch. These provide:

• Points ledger and transaction API
• Tier management
• Redemption code generation
• Webhooks for earn/redeem events

If you must build custom:

// Core points earn function — call this from your order webhook
async function earnPoints(params: {
  customerId: string;
  orderId: string;
  orderValue: number; // subtotal, not including tax/shipping
  reason: 'purchase' | 'review' | 'referral' | 'signup';
}) {
  const customer = await db.customers.findById(params.customerId);
  const tier = customer.loyaltyTier; // 'member', 'silver', 'gold', 'platinum'
  const multiplier = { member: 1.0, silver: 1.5, gold: 2.0, platinum: 3.0 }[tier];

  const basePoints = Math.floor(params.orderValue * 1); // 1 point per $1
  const pointsToAward = Math.floor(basePoints * multiplier);

  await db.loyaltyTransactions.create({
    customerId: params.customerId,
    orderId: params.orderId,
    type: 'earn',
    points: pointsToAward,
    reason: params.reason,
  });

  await db.customers.increment(params.customerId, { loyaltyPoints: pointsToAward });
}

Step 4: Connect loyalty to email marketing

The highest-ROI loyalty email is the points balance email — it drives repurchases by reminding customers they have value waiting.

In Klaviyo (connected to Smile.io): 1. Add points balance to every post-purchase email: You earned {{ event.SmilePointsEarned }} points. Balance: {{ profile.SmilePointsBalance }} points 2. Create a flow triggered by: Smile.io Points Balance Threshold → Balance reaches 500 points 3. Email: "You have enough points to redeem for $5 off your next order" 4. Create a flow triggered by: Approaching Tier Upgrade → 100 points away from Silver 5. Email: "You're almost Silver! Spend $X more to unlock free shipping"

Points expiry email: 1. Create a flow triggered by 30 days before point expiry 2. Email: "Your 320 points ($3.20) expire in 30 days — use them before they're gone" 3. This is one of the highest-converting loyalty emails

Step 5: Measure program performance

If redemption rate is below 15%, the redemption threshold is too high or customers are unaware of their balance. Lower the minimum redemption threshold or add a points balance widget to the account page.

Best Practices

• Announce points balance in every post-purchase email — "You earned 45 points — you now have 320 points ($3.20 to redeem)" drives engagement; most loyalty apps include this via email integration
• Use annual spend for tier qualification, not current balance — rewards consistent spend, not balance gaming
• Add non-purchase earning actions — reviews, referrals, and social shares make the program stickier without pure revenue cost
• Create "double points" events — point multiplier promotions drive purchase without the perceived cheapness of a discount code
• Set a minimum redemption threshold ($5 minimum / 500 points) — prevents micro-redemptions that create operational overhead
• Email members 30 days before points expire — expiry warning emails are among the highest-converting loyalty emails

Common Pitfalls

Related Skills

• @customer-retention-engine
• @lifecycle-marketing-automation
• @referral-viral-loops
• @email-marketing-automation
• @review-generation-engine

Loyalty Points Engine Implementation

Problem/Feature Description

A growing direct-to-consumer apparel brand, ThreadCo, is launching their first customer loyalty program. Their engineering team has built out the customer and order database layer, but needs the core points engine that determines how many points customers earn for different types of interactions with the brand.

The brand wants to reward customers not just for purchases, but for community engagement activities as well — writing product reviews, referring friends, and signing up for the program. They also want a special bonus during a customer's birthday month to drive engagement. Every interaction should be fully auditable, with a complete record of how a customer's balance changed over time. After points are awarded, the system should assess whether the customer qualifies for a new tier.

The team also wants to protect against points abuse from very small orders — customers should only earn points on orders above a meaningful purchase threshold.

Output Specification

Implement the earnPoints function in TypeScript as loyalty-engine.ts. The function should:

• Accept parameters for customerId, orderId, orderValue, and the reason for earning points
• Calculate points based on the type of earning event
• Apply any applicable multipliers for the customer's tier and birthday month
• Record the transaction in the database with a full before/after balance snapshot
• Update the customer's running points total
• Trigger a tier status check after awarding points
• Return the number of points awarded

Also write a loyalty-engine.test.ts file with at least 4 test cases covering different earn scenarios (you may stub database calls).

You should stub the database layer and helper functions (db, getCustomerTier, isCustomerBirthdayMonth, evaluateTierStatus) — you do not need to implement them fully.

Loyalty Program Lifecycle Management and Analytics

Problem/Feature Description

NaturalBloom, a health and wellness DTC brand, has been running a loyalty program for 18 months. The marketing team is concerned that the program feels stale — members are accumulating points but not redeeming them, and the team has no visibility into whether the program is actually driving incremental revenue. The engineering team has been asked to implement the operational infrastructure that keeps the program healthy over time.

There are three main gaps to close: (1) the brand has never expired old points, and the liability on the balance sheet is growing; (2) there's no regular process to demote members who no longer meet their tier threshold after a period of inactivity; (3) the marketing team has no dashboard metrics to work from. Additionally, the CRM team wants to redesign post-purchase emails to make the loyalty value more tangible for members, and the promotions team is planning a product launch campaign and wants to know the best promotional mechanic to drive purchases.

Output Specification

Produce the following in a file called loyalty-lifecycle.ts:

1. An expireStalePoints function implementing the monthly points expiry process, including advance notification logic. 2. A runAnnualTierReview function that re-evaluates all customers' tier status and handles downgrades. 3. A getLoyaltyMetrics function returning key program health indicators.

Also produce a loyalty-recommendations.md file (max 400 words) covering:

• The recommended format/content for post-purchase loyalty emails
• The recommended promotional mechanic for the upcoming product launch (choose between point multiplier events vs. discount codes, and justify your choice)
• A decision framework for when the brand should consider adjusting the redemption threshold (include a specific metric threshold that should trigger a review)

Loyalty Tier System and Points Redemption

Problem/Feature Description

StyleVault, a mid-market fashion retailer, is upgrading their basic points program into a full tiered loyalty system with checkout redemption. Their customers have been accumulating points for over a year, and now the brand wants to introduce meaningful status tiers with differentiated perks, so that high-spending customers feel recognized and rewarded.

At checkout, customers should be able to apply their points balance as a discount. The redemption system needs to be airtight — preventing customers from redeeming more than they have, and ensuring the resulting discount code can only be used once and doesn't stay valid indefinitely.

The team also needs the tier qualification logic to correctly evaluate customers when their points balance changes. They want to reward customers who achieve a new tier with a surprise bonus, and send them an email celebrating their new status. Separately, the returns team has flagged that when orders are refunded, the points that were earned from those orders need to be clawed back.

Output Specification

Implement the following in a file called loyalty-system.ts:

1. A LOYALTY_TIERS constant defining the full tier structure with names, qualification thresholds, earn multipliers, and available benefit types. 2. A redeemPoints function that validates the redemption request, generates a discount code, logs the transaction, and updates the customer balance. 3. An evaluateTierStatus function that determines whether a customer should change tiers and handles the upgrade flow. 4. A reverseOrderPoints function that debits points when an order is refunded.

You may stub db, createUniqueDiscount, sendTierUpgradeEmail, earnPoints, subDays, and addDays.

Also produce a loyalty-system-design.md file (max 300 words) explaining the key design decisions in your implementation — specifically how tier qualification works and how redemption codes are protected.