YITH Points and Rewards builds the loyalty loop: customers earn points per purchase (and per action – reviews, signups), points convert to discounts at redemption rates you set, and the balance lives in the customer account – the retention mechanic that turns one-time buyers into accumulating regulars. The economics are configurable per store: earning rates (points per dollar), redemption values (points to currency), expiration policies, role-based bonuses, and maximum-redemption caps protecting margins. Against campaign tools like YITH Coupon Email System (pushed discount events) and the WooCommerce family, points are the continuous currency – earned every order, always redeemable – the loyalty model research consistently ties to repeat-purchase frequency.
The 3.x line is mature at steady cadence. For repeat-purchase businesses, it’s the retention engine with measurable effect on order frequency.
Competitive Features
- Earning rules – points per purchase, review, signup
- Redemption at checkout – points become discounts
- Configurable rates – earn and burn values per store
- Expiration policies – points age out on schedule
- Role bonuses – members earn faster
- Points logs – customers see full history
- Max-redemption caps – margin protection
Key Features
- Product-level multipliers – promoted products earn more
- Category earning rules – group-level rates
- Points on registration – welcome incentives
- Refund handling – points adjusted on returns
- Admin adjustments – manual credit/debit
- My-account display – balances visible
- Translation ready – multilingual compatible
Comparison with Competitors
YITH Points and Rewards vs SUMO Rewards
| Aspect | YITH Points and Rewards | SUMO Rewards |
|---|---|---|
| Vendor | YITH (GPL) | Fantastic Plugins |
| Core model | Same (earn/redeem points) | Same |
| Earning events | Purchases + actions | Purchase-focused |
| Price model | GPL license | License |
| Best for | YITH-stack stores | Independent loyalty needs |
Bottom line: Functionally parallel loyalty engines – YITH’s integrates the YITH ecosystem at GPL pricing, SUMO’s stands independent. Stack alignment decides.
YITH Points and Rewards vs coupons
| Aspect | Points program | Coupon campaigns |
|---|---|---|
| Engagement model | Continuous accumulation | Event-based pushes |
| Customer psychology | Banking value | Chasing deals |
| Margin control | Redemption caps | Per-campaign design |
| Retention effect | Frequency lift | Spike and fade |
Bottom line: Coupons spike; points compound. The loyalty model fits stores whose economics depend on repeat frequency – and it coexists with campaigns for the spike moments.
Recommended Stack – points pair with account hubs: combine with WooCommerce Subscriptions so subscribers earn points on every renewal – loyalty compounding on top of recurring billing.
Official Changelog
Version 4.29.0
Release Date: August 24, 2026
- Feature release: earning-rule and redemption refinements.
Version 4.22.0
Release Date: June 15, 2026
- Maintenance release: WooCommerce compatibility updates.
Frequently Asked Questions
How do customers earn points?
Purchases earn at your configured rate (points per currency unit), with bonus rules for reviews, registrations, and specific products or categories – role multipliers let members earn faster.
How do points become discounts?
At checkout, customers apply available points toward the order at your redemption rate – with caps limiting how much of an order points can cover, protecting margins.
Can points expire?
Yes – expiration policies age points out on schedules, the use-it-or-lose-it dynamic that drives redemption while managing liability.
What happens on refunds?
Points adjust automatically – refunded orders claw back earned points, and redeemed points on refunded items return, keeping balances honest.
How is this different from a coupon program?
Currency versus campaigns: coupons are pushed events with spike-and-fade effects; points are a continuous balance that makes every purchase feel like banking value – the frequency-lift mechanic retention programs need.
Leave a Reply