How to protect a Black Friday SaaS deal from repeat claims
Black Friday coupon abuse can empty a SaaS campaign budget overnight. A pre-launch checklist for caps, staged rewards, off switches and what won't hold.
On Monday you shipped the fix you'd wanted since last November: one redemption per email address, enforced by a unique index, so nobody could claim your Black Friday code twice. You tested it with your own address, watched the second attempt fail and dropped a screenshot in the team chat. It was the first part of this sale that felt finished.
It's now 7:12 a.m. on Saturday. That rule is five days old, and your model provider has just started returning quota errors to everyone using your product.
This is a scenario, and the numbers are there to be checked. Your code gives new accounts 5,000 credits, and a fully used claim costs you $6 in model spend. You set aside $3,000 for the sale, which funds 500 claims. You'd already spent $1,500 with your provider this month, so you set November's cap at $4,500 to make sure the campaign couldn't run past its budget.
At 11:40 last night your co-founder posted the signup chart with the words "best night we've ever had". There were 310 claims on it, against a forecast of 125 a day. This morning there are 568, so you export them and scroll. 480 of those addresses open the same Gmail inbox. Dots alone give a ten-character Gmail name 512 spellings (2 to the power of 9), and Gmail delivers all of them to one mailbox. Your rule compared text, the text was different every time, and every address passed your email verification because every address works.
That's the morning that sends people to a search bar to type Black Friday coupon abuse SaaS. By breakfast the sums look like this:
- 480 accounts × $6 = $2,880, paid out to one person
- 88 real claims have used about $120 so far
- $2,880 + $120 = $3,000, the whole budget, 22 hours into an 87-hour sale
Your cap did what you set it to do. At $1,500 + $3,000 = $4,500 it cut off the provider for everyone, including the customers who pay you $240 a year. By 9:30 a.m. you have 14 support messages and three refund requests, which is another $720 (3 × $240). You could delete the 480 accounts, but that gets you nothing back. The credits were spent within minutes of each claim, and your provider has already billed you for them.
If your company spends $12,000 a month, $2,880 is about a week of runway ($2,880 ÷ $12,000 × 30 = 7.2 days). The chart in the team chat says 568 new accounts. The real number is 88, and about 85% of the best night you've ever had was one person (480 ÷ 568).
Now you have to choose, and the email you sent 11,000 people on Friday says the deal runs until Monday at midnight. Real claims have been arriving at 4 an hour (88 ÷ 22). Keeping that promise for the remaining 65 hours means about 260 more claims, or up to $1,560 you never budgeted (260 × $6). Or you pull the deal on the biggest weekend of your year and explain why to everyone who got that email.
That weekend on one line, with illustrative numbers:
Why Black Friday coupon abuse moves so fast
A Black Friday deal is built to travel. You email it, post it and make it easy to redeem, so when the code lands on a deal site it's doing what you asked of it. The benefit usually arrives the second someone claims it. And it all runs on a deadline, so there's no quiet week to fix anything.
Monday's rule asked whether this email address had redeemed the code. What you meant to ask was whether this person had, and an address can't tell you that. Gmail is only the easy case. Personal Gmail ignores dots, and mail sent to a name with a plus sign and a label reaches the same inbox, which is simply how those addresses work. A second real mailbox from any provider gets past all of it.
So the obvious next move is a stricter rule. The catch is that you've just spent a month persuading real people to turn up in the same four days, and a stricter rule lands on them too.
The basic checks, and what a sale does to them
Each of these catches something real.
| Basic check | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any working mailbox | People whose code lands in spam | Deliverability work |
| Unique emails | The exact address twice | Any address written differently | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| CAPTCHA | Simple scripts | People claiming by hand | Screen reader users | Fees and lost claims |
| Phone or card requirement | Casual second accounts | Anyone with another number or card | People without either, or who wanted to try first | A charge per text and fewer claims |
| One claim per IP address | Repeats on one connection | Any other network | Offices, campuses and households | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | Privacy-minded customers and staff on company VPNs | Another list to maintain |
| Rate limits | Bursts from one source | Claims spread out over the night | Real buyers when your email lands | Tuning per route |
| Manual review | What a person can spot | Anything after hours | Whoever looks odd to a tired reviewer | Hours at the worst time |
In a normal month you'd have time to notice one of these had stopped working. A sale gives you 87 hours. The domain list you refreshed on Wednesday doesn't know Saturday's new domains, and the rate limit you tuned in October fires at 9 a.m. when your own email reaches 11,000 people. Review by hand at one minute per claim is 568 minutes, or about 9.5 hours, for a single night, and the credits had gone before anyone could look. Stack the lot and your one big deal has a puzzle, a text message and a card in front of it.
Your Black Friday pre-launch checklist
None of this identifies anyone. It limits what a bad night can cost.
Three weeks out: write down the deal. Who it's for, what they get and how many times. "One per new customer" needs a definition your support inbox can repeat, so start from a one-account-per-person policy. Then size it:
In the scenario, that's $3,000 ÷ $6 = 500.
Two weeks out: cap redemptions. Keep the count in your database and stop at 500, with a page that says the deal's fully claimed. If you can, send each subscriber their own single-use code, because a public code travels.
Ten days out: pay the reward in stages. Give 1,000 credits at claim and the rest at 1,000 a week. Night one now costs $1.20 a claim, so 480 accounts come to $576 instead of $2,880. Hold any cash reward, such as an affiliate payout, until your refund window closes.
One week out: separate the spend. Put promotional usage on its own provider project with its own hard cap where your provider allows it, and give paying customers' jobs their own queue. If the deal runs dry at 7 a.m., the deal stops and the product keeps working.
Three days out: build the off switch. One flag that stops new grants and leaves the sale page up, reachable from your phone. Turn it on for real, claim with a test account and confirm no credits arrive.
The day before: set alerts and name a person. 500 claims over 87 hours is about 6 an hour, so alert at three times that, 18 an hour. Put someone's name against each overnight slot, and draft two messages now: one for when the deal fills up and one for someone you turn away.
During the sale: read spend, not signups. Compare spend with budget four times a day. If it jumps, go to the first-hour runbook.
The week after: take it down and count properly. Expire the code, remove the temporary blocks and clean the duplicates out of your numbers before anyone quotes them.
The question a redemption cap can't answer
That list keeps the loss small and your paying customers online. Even so, one person can still take 480 of your 500 capped claims, leaving 20 for the 11,000 people you emailed. Every check in the table looks at one thing about a signup. Your deal depends on something else, which is whether this claim looks like a repeat, and building the answer yourself is a product of its own, three weeks before your biggest sale.
A unique index reads one column. AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and those signals are read together, never one at a time. AbuseZero uses a proprietary algorithm, with AI that checks the claim again. AbuseZero also checks mailbox aliases, disposable domains and mail routing. Your VPN list goes stale; AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. It recognizes repeat devices across new accounts, even when email addresses keep changing. Creating a fresh account isn't enough to erase previous activity, which is what you wanted Monday's rule to mean.
Before the credits move, your server makes one API call and gets a clear allow or deny, under rules you control. Once per user suits a deal like this one. Start in Observe mode the week before to see what would be denied before anyone is blocked, then work through the go-live checklist. You'll still want the cap and the off switch. You don't have to build your own abuse prevention system as well.
Frequently asked questions
How do I stop someone using a Black Friday coupon twice?
A unique rule on code and account stops the same account redeeming it again. A new account isn't covered by that rule. AbuseZero evaluates each claim and returns a clear allow or deny at the moment of the claim.
Should I require a card for a Black Friday deal?
It cuts casual second accounts, and it cuts real claims too. A four-day sale doesn't give you time to learn how many.
What if the budget runs out in the middle of the sale?
Stop new grants with the off switch, honor what's already been claimed and say plainly on the sale page that the deal's fully claimed.
Get your deal ready before the email goes out
Start with Builder
Pay as you go. Protect your first benefit today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High-volume sales and custom terms.