A loyalty program looks like an obvious win until you realize how easy it is to misconfigure. Wrong earning rates create unsustainable point liability. Wrong redemption tiers fail to motivate. Wrong expiry rules feel punitive. This SOP configures Yotpo Loyalty without the common mistakes.
Loyalty programs work over 6-12 months. By the time you see the impact, your earning rates are baked in and hard to change. Get the configuration right at launch or pay for it for years.
Industry standard. Easy to communicate. Easy to scale.
100 points = $5 off. 250 points = $15 off. 500 points = $35 off (bonus reward at higher tiers). Avoid weird fractions.
Not 12 months from earning. Reset on each engagement. This balances liability with customer fairness.
50 points for review. 100 points for referral. 200 points for first subscription. Drive the behaviors you want.
Stacking multiple rewards per order creates margin disasters at scale.
Bronze, Silver, Gold based on annual spend. Gives customers a status carrot. Skip if under $5M ARR.
Show points earned, balance, and how close to next reward. Don't bury this.
Total unredeemed points × redemption value = your liability. Track this against revenue. Healthy is 1-2 percent of monthly revenue.
Record your screen while performing the yotpo loyalty points configuration. ReccordSOP turns the recording into a SOP with timestamped screenshots. When your live setup changes, drift detection flags it.
Generate this SOP free1 point per dollar is the safe default. Some brands do 5 points per dollar with smaller-denomination rewards. The math has to balance against your margin.
Yes, but on inactivity not on earning date. 12 months of no engagement and points expire. This balances liability with fairness.
1-2 percent of monthly revenue in outstanding redeemable value. Above 5 percent and you have a scaling problem coming.
I built ReccordSOP after watching too many DTC ops teams lose months to undocumented workflows. These SOPs are battle-tested with Shopify operators running $1M to $50M brands.
Last reviewed June 1, 2026