How to promote your loyalty program during BFCM
1 September, 20268 essential loyalty program checks before Black Friday
2 September, 2026Reactivate BFCM shoppers who never came back by leading with the points balance they already earned, asking for one more order instead of a full repeat-purchase streak, and timing the push to a real deadline instead of a manufactured one. This works because someone who bought exactly once during a discount event never built a repeat-purchase habit to lapse from in the first place, so a generic win-back email treats them like any other lapsed member and misses the actual problem.
This post covers what to lead with, how to size the ask, when to send it, and the exact point where BFCM-specific effort should stop, before non-responders fold into your standard win-back flow.
TL;DR
- This campaign targets the Dormant bucket from your cohort split, members who bought once during BFCM with no engagement signal in the 30 to 45 days since, not your whole BFCM cohort
- Lead with the points balance they already have instead of a new discount. A dormant balance, especially one that’s about to expire, is a warmer hook than another percentage off
- Ask for one more order, not a full three-orders-in-60-days streak. Most of this bucket has never proven a repeat-purchase habit to begin with
- Time it to a real deadline, the points-expiry date set to land around your January sale, not invented urgency
- Set an explicit endpoint. Members who don’t respond fold into your standard win-back flow. This campaign doesn’t run forever
The campaign at a glance
| Step | What to do | When |
|---|---|---|
| 1. Target | Dormant bucket only: one BFCM purchase, no engagement signal in 30–45 days | Right after the cohort split runs |
| 2. Lead | Points balance already earned, not a new discount | Jan 18 |
| 3. Ask | One more order, not a repeat-purchase streak | Jan 18 |
| 4. Deadline | The real points-expiry date, not invented urgency | Jan 18 (+ Jan 26 for AU/NZ) |
| 5. Sunset | No response fold into your standard, always-on win-back flow | After the Jan 26 follow-up |
Why this campaign is different from a generic win-back email
A member who bought once during BFCM and never returned hasn’t lapsed from a purchase habit. They never built one. Reactivating a formerly-repeat customer means reminding them of a relationship that already exists. Reactivating this group means asking them to prove, for the first time, that a second order is even something they’ll do.
This campaign targets exactly the Dormant bucket defined in the cohort split this campaign’s audience comes from: no engagement signal in the 30 to 45 days since BFCM. It isn’t for the Active bucket, which gets a lighter nudge, or the Redeemed bucket, which is already on a path toward VIP status. Sending this message to the wrong bucket wastes a campaign that only works because it’s aimed precisely.
The timing isn’t arbitrary either. This campaign launches Jan 18, right after the cohort split identifies exactly who belongs in it. Sequencing it any earlier means guessing at an audience you haven’t actually confirmed yet.
Lead with the points balance, especially one that’s expiring
The same principle behind this pipeline’s win-back approach in general holds here. A member’s existing points balance is a warmer hook than a new discount. The balance is already theirs, tied to a purchase they already made. A discount is generic and could come from any brand running a sale that week.
It’s sharper for this cohort specifically. If the points-expiry date set around your January sale, per the points-expiry timing set in December, applies to this group, the message stops being a vague “come back” and becomes something with a real deadline attached: you have this many points, worth this much, expiring on this date.
Don’t lead with a fresh percentage-off discount instead. This series has spent months moving your BFCM cohort away from a deal-only relationship, and reaching for a discount at the last real chance to reactivate this group undoes that work exactly when it matters most.
Size the ask: one more order, not a streak
The standard win-back ladder used elsewhere in this pipeline asks for a short streak. For a member whose only history is one BFCM purchase, that’s the wrong first rung. It assumes a purchase habit that was never established.
Offer a bonus-points reward for one more order instead. No streak, no window to string together multiple purchases in. The goal isn’t building a habit inside a single campaign. It’s proving a second purchase is possible at all.
A member who takes that offer graduates into your standard retention flows, the same December campaigns and VIP-tier tracking already running for the rest of your program. This campaign’s only job is getting them to that second purchase. Everything after it is handled elsewhere.
Time it to Jan 18, and to a real deadline
Launch this campaign Jan 18, per the calendar, right after the cohort analysis identifies exactly who belongs in the Dormant bucket. Sending earlier means guessing at an audience you haven’t confirmed.
Pair it with the expiry deadline instead of inventing a separate one. If points expire around your January sale, per this series’ December guidance, align this campaign’s own deadline to that same date. One real countdown does more than a second, unrelated one running alongside it.
A real deadline is honest urgency. Research on loyalty program hurdles found members can lose up to a third of potential savings to barriers like expiration dates (Harvard Business Review).
That distinction is the whole point of this section. The reminder gives a member one more chance to use what they’ve already earned before the deadline decides for them. Sizing the bonus-points offer itself should follow the cost math behind sizing this bonus-points offer: run the same issued-value-times-redemption-rate formula before you set the reward, rather than picking a number that feels generous.
Use Australia Day as a secondary regional touch
The calendar flags Jan 26, Australia Day, as a regional redemption moment for AU/NZ members specifically.
For AU/NZ members in the Dormant bucket who didn’t respond to the Jan 18 push, a regionally relevant second moment reads as a natural follow-up instead of a repeat of the same message.
Keep it proportionate. This is a second, targeted touch for one region, not a second full campaign. Scale the effort to the size of your actual AU/NZ segment inside the Dormant bucket, and skip it entirely if that segment is too small to justify a dedicated send.
Know when to stop: the sunset point
Not everyone in this bucket will reactivate. That’s an expected outcome of a time-boxed campaign, not a failure of it.
Once the Jan 18 campaign, and the Jan 26 regional follow-up where relevant, has run its course, suppress members who still haven’t responded from further BFCM-specific messaging. Fold them into your standard, always-on win-back flow instead.
Continuing to send BFCM-themed urgency to the same non-responders past this point has diminishing returns, and it risks reading as noise instead of a considered message. See reporting on this campaign’s response rate before folding the rest into standard flows for how to close that reporting loop, then hand the remainder off to lifecycle marketing that isn’t tied to a discount event three months in the past.
FAQ
Should I use the same win-back tactic for this group as for any other lapsed customer?
Lead with the same principle, existing points over a new discount, but size the ask differently. Most of this cohort has only one purchase on record, so ask for one more order rather than a full repeat-purchase streak. The mechanic stays the same, the rung you’re asking them to climb doesn’t.
When should this reactivation campaign launch?
Per the calendar, launch on Jan 18, right after the cohort analysis identifies exactly who’s in the Dormant bucket. Launching earlier means sending to an audience you haven’t confirmed yet, which risks reaching members who don’t actually belong in this segment, like Active or Redeemed members who need a different message entirely. If you’re running the Jan 26 Australia Day follow-up for AU/NZ members, that touch comes after this initial send, not instead of it.
What if the member’s points aren’t set to expire?
The core move, leading with the existing balance, still works without an expiry deadline. It’s just less urgent messaging. Focus on the value they already have instead of manufacturing a countdown that isn’t real: show the points balance and what it’s worth, and let that be reason enough to come back, rather than inventing a deadline your program doesn’t actually enforce.
What do I do with members who don’t respond to this campaign?
Stop sending them BFCM-specific messaging once the Jan 18 push, and the Jan 26 regional follow-up where relevant, has run its course. Fold them into your standard, always-on win-back flow instead. Continuing a BFCM-themed push past this point has diminishing returns and starts reading as repetition rather than a considered message.
Is Australia Day worth building a specific touch around?
Only if you have a meaningful AU/NZ segment inside the Dormant bucket. It’s a regionally relevant secondary touch for members who didn’t respond to the Jan 18 push, not a second campaign for everyone in the segment. Scale the effort to the size of that segment, and skip it entirely if too few Dormant members are AU/NZ-based to justify a dedicated send.
One order, a real deadline, then a clean handoff
The BFCM buyers who never came back aren’t a lost cause, but they’re not a generic win-back target either. They’re first-time buyers who haven’t proven a second purchase is possible yet. Lead with what they already have, ask for one order instead of a habit, and give them a real deadline instead of an invented one. Then let the members who don’t respond move on to your standard lifecycle marketing instead of staying stuck in BFCM messaging indefinitely.
That’s the campaign that closes the loop this whole BFCM sequence was built to run.
P.S. BON shows each member’s exact points balance and expiry date, so this campaign’s core message is a data pull, not a guess, and BON can automate the suppression step once the window closes.
