The rewards catalog is what your members see when they decide whether your loyalty program is worth participating in. It's the promise that the points they're accumulating will eventually be exchangeable for something they actually want. A catalog that's thin, confusing, or loaded with frustrating redemption restrictions will drive breakage — not because members are forgetting their points, but because they're giving up on them. That's a different and more serious problem.
Catalog design involves trade-offs between program economics, operational simplicity, and member desirability. None of these optimize in the same direction. This post works through the key design decisions.
Reward Type Mix: Dollar-Off vs. Product vs. Experience
Retail loyalty catalogs typically offer some combination of three reward types:
- Dollar-off or percentage-off discounts: The most operationally simple. A member redeems 500 points for $5 off their next purchase. Easy to understand, easy to process at checkout. The economics are entirely predictable — the cost to the program is exactly the face value of the discount.
- Specific product rewards: A member redeems 1,200 points for a specific SKU from the catalog (a branded water bottle, a $20 gift set). These have higher perceived value than an equivalent dollar-off discount because members perceive tangible items as more premium. The cost to the program is the wholesale/cost-of-goods value of the item, which is often lower than the dollar-off equivalent.
- Experience rewards: Early access to sales, exclusive member events, free services (alterations, custom engraving). These are the highest-perceived-value, lowest-direct-cost reward type for retailers who have services to offer. They're also the hardest to operationalize — you need to manage inventory of experiences, booking flows, and fulfillment.
For most regional retail chains, a catalog that's 60–70% dollar-off, 25–30% product rewards, and 5–10% experiences is a reasonable starting distribution. The dollar-off portion provides the baseline "I can always redeem" reliability, the product rewards drive aspiration, and the experience tier creates something that competitors can't easily replicate.
SKU Eligibility Rules
Not every item in your store inventory should be redeemable with points. Gift cards are almost universally excluded — redeeming points for gift cards enables a points-laundering pattern where members convert loyalty currency back into general-purpose payment value. Items sold at a loss or deep promotion may also be excluded to prevent the program from compounding already-thin margins.
SKU eligibility should be managed at the catalog level, not the store level. That means your catalog API needs to evaluate eligibility at redemption time against a current eligibility list, not at catalog display time. Display is informational — redemption is the transaction. Showing a product in the catalog that fails eligibility at checkout creates a support ticket every time it happens.
Eligibility rules that cause the most operational friction:
- Clearance exclusions: Items on clearance are often excluded from point redemption to protect margin. But clearance status changes daily, and if your catalog system doesn't sync clearance flags in near-real-time, members will attempt to redeem against items that have been marked clearance since the catalog was last refreshed.
- Bundle exclusions: Items that are part of promotional bundles may be ineligible for separate point redemption. The eligibility check needs to inspect the full order context, not just the individual line item.
- Tier-gated rewards: Higher-tier members have access to a broader catalog. The eligibility check must validate both SKU eligibility and member tier at time of redemption.
Burn-Rate Controls
Burn-rate controls limit how many points a member can redeem per transaction or per period. They serve two purposes: liability management (preventing a member from burning their entire balance in a single transaction during a high-value promotional event) and fraud mitigation (limiting the damage from a compromised account).
Typical burn-rate controls:
- Per-transaction point cap: A member can redeem no more than X points per transaction. Common values: 2,000–5,000 points for programs where 1,000 points = $5–$10.
- Redemption frequency limit: No more than one redemption per 24 hours per member. This primarily addresses fraud, not economics.
- Redemption percentage cap: Points can cover no more than 50% of a transaction's total. Prevents members from building a cart specifically to maximize point redemption against low-margin items.
We're not saying burn-rate controls are free from member experience cost. They create friction for legitimate members who want to cash out a large balance. The design goal is setting limits that catch fraud patterns and prevent liability spikes without triggering meaningful friction for normal redemption behavior. A 5,000-point-per-transaction cap on a program where the median redemption is 800 points hits almost no legitimate member — but would stop a fraud pattern involving account takeover and immediate bulk redemption.
Catalog Expiry and Balance Expiry
Points that expire are a feature of program economics — breakage from expiry contributes to the program's liability reserve. But expiry that feels arbitrary or punitive drives member anger disproportionate to the dollar value at stake. A member who loses 300 points ($3 equivalent) is more likely to complain about the expiry than they were likely to redeem those 300 points.
Two distinct expiry models:
- Activity-based expiry: Points expire after N months of member inactivity. If the member makes any qualifying purchase within the window, the clock resets. This is the most member-friendly model — active members never lose points, and the expiry serves as a genuine re-engagement signal for disengaged members.
- Rolling point expiry: Points earned more than N months ago expire, regardless of activity. This drives higher burn rates and reduces the long-term outstanding liability in your points ledger, but creates friction for members who are active but prefer to accumulate before redeeming.
For most retail programs targeting regional chains, activity-based expiry with a 12–18 month inactivity window is the standard. It protects the program against dormant accounts accumulating indefinite liability while punishing only members who have genuinely disengaged.
Catalog API Design
If you're exposing catalog redemption through a mobile app or e-commerce checkout, the catalog API needs to handle two distinct request types: catalog browse (show me what's available for a member with X points and tier Y) and redemption execution (apply N points to order ID Z for reward item W).
Keep these as separate endpoints. Catalog browse can be cached aggressively — catalog contents don't change per-minute. Redemption execution must be synchronous and must execute against a real-time point balance with a hold/reserve pattern: when a member initiates redemption at checkout, the engine places a temporary hold on the points being redeemed. If the checkout completes successfully, the hold becomes a committed redemption. If the checkout is abandoned or fails, the hold expires and the points are returned. This prevents race conditions where a member's balance is decremented before a successful transaction is confirmed.
A catalog that doesn't implement the hold/reserve pattern will occasionally deduct points for transactions that don't complete. Those are among the most frustrating support tickets a loyalty team handles, because the resolution requires both investigating a failed transaction and manually reversing a point deduction.
Catalog Health Metrics
A catalog that's not being used is a liability, not a benefit. Metrics worth tracking regularly:
- Redemption rate by reward type: What percentage of members with sufficient balance are redeeming? Broken down by dollar-off, product, and experience rewards. Low redemption rates on product rewards may indicate pricing (too many points per item) or catalog relevance.
- Time-to-first-redemption: How long after earning their first significant point balance does a member make their first redemption? Long first-redemption windows indicate discovery or trust issues with the catalog.
- Abandoned redemption rate: Members who started a redemption flow but didn't complete it. High abandonment at the SKU eligibility step is a catalog configuration problem. High abandonment at the balance confirmation step may indicate the point cost is too high.
Revlance's analytics module surfaces these metrics as part of the catalog health dashboard, giving program managers a clear signal of whether catalog changes are driving meaningful engagement shifts — or just cosmetic variation.