Casa Loyalty now supports Last Activity expiry — the points-expiry model that's effectively the industry default: a customer's whole balance expires N months after their last activity, and any qualifying activity moves that date forward. It's a new fourth strategy alongside the existing joining-date, fixed-date, and per-batch options, bringing Casa to other apps.
How it works
Pick a window of 3–36 months (or a custom value) in Settings > Platform > Points Expiry. If that window passes with no qualifying activity, the customer's entire balance zeroes out.
What counts as activity
The clock moves forward on real engagement:
Order points
Redemptions
Manual adjustments
Imports
Referral payouts
Review / social earns
Automatic system credits — birthday, anniversary, and the expiry rows themselves — are excluded by default, so an inactive customer can't be kept "alive" purely by an auto-credit.
Earnings-only toggle
By default, only earning points resets the clock — spending a balance down isn't treated as engagement. If you'd rather have redemptions count as activity too, uncheck the earnings-only toggle.
Safe to turn on
Switching to Last Activity won't cause any surprises:
Enabling it never expires anyone on day one or retroactively — an activity floor is stamped when you turn it on.
Lengthening the window re-derives each customer's expiry date from their own activity anchor.
Shortening the window moves the floor forward instead of wiping people out immediately.
Disabling it pauses the expiry sweep and clears the rolling configuration.
Re-arming after expiry
A customer who expires stays expired until new qualifying activity sets a fresh date — there's no double-zeroing and no permanent lockout. Once they're active again, the cycle restarts cleanly.
Warning emails
The existing warning and last-chance email templates are reused for this strategy. Each customer's send record clears when their clock resets, so a returning customer who later goes inactive again will be warned on the next cycle too.
Where the expiry date shows up
The expiry date surfaces everywhere the other strategies already show it:
The account page
The widget
Reward terms
Under the hood
Last Activity runs inside the existing 01:00 UTC expiry sweep — no new cron job is added. Accounting stays FIFO-safe, with the activity anchor stamped in the same transaction as the balance write. The feature is fully localized across all 25 admin locales.
Important: strategy compatibility
Last Activity is a balance-mode strategy. It's mutually exclusive with per-batch/FIFO expiry and fixed-date expiry — a program can only use one points-expiry strategy at a time.
Quick recap
Where to find it: Settings > Platform > Points Expiry > select Last Activity.