A loyalty program that works perfectly in a quiet October demo can still break in a specific, expensive way in the first hour of Black Friday traffic. Checkout gets slower. A discount code cancels a reward it should have stacked with. An integration quietly stops syncing and nobody notices until a customer complains.

There are two QA passes worth running before that happens, together making up the BFCM loyalty QA checklist this post walks through. The first is a tech and ops check, done at least two weeks before BFCM traffic arrives: widget load time, discount-code compatibility, a full integration test purchase, and support prep. The second is a daily monitoring pass during BFCM week itself (Nov 27-30), watching whether your promotions fired on schedule and whether signups, redemptions, and technical issues are tracking normally.

This post covers both checklists, why load time and uptime matter more this week than any other, and what to actually watch once BFCM week starts.

TL;DR

• Two weeks before BFCM: stress-test widget load time, confirm discount-code compatibility, run a full test purchase, prep support for peak volume
• BFCM week (Nov 27-30): keep Double Points Day live for new signups the whole window, confirm VIP early access fired on schedule, run a quick reward-preference poll, track signups/redemptions/issues alongside revenue daily
• Conversion rates drop an average of 4.42% per additional second of load time. The best-converting pages load in 1-2 seconds (Salesforce)
• Global cart abandonment already runs above 70% in normal conditions. BFCM traffic just gives every extra second of friction more room to make that worse
• A November 2025 infrastructure outage took down roughly 99.3% of Shopify storefronts globally, right before Black Friday, a reminder that some risk isn’t even in a merchant’s own code

Why QA is its own step, separate from setup

Setting up points, tiers, and a BFCM multiplier is different work from confirming all of it survives real BFCM traffic and interacts correctly with a sitewide discount. That confirmation is what this checklist is for.

This calendar phase exists so testing happens in October, with time to fix what breaks, instead of getting discovered live on November 27th. A setup mistake found in October costs a support ticket. The same mistake found during BFCM week costs the sale, and possibly the customer’s trust in the program going forward.

If you haven’t locked your program’s foundation yet, the setup checklist this QA pass follows covers that groundwork first. This post picks up once that’s done.

Two weeks out: the tech and ops checklist

Run these four checks at least two weeks before BFCM traffic hits. That gives you time to fix anything that turns up before it matters.

• Stress-test your loyalty widget’s load time under simulated BFCM-level traffic. It should not add noticeable delay to checkout
• Check that loyalty discount codes work as intended alongside your sitewide BFCM offers and any affiliate codes. This is the most common place a “free” reward silently breaks or double-stacks
• Run a full test purchase to confirm email, SMS, and review-platform integrations are all passing data correctly. Don’t assume yesterday’s test still holds after a promo change
• Review support ticket volume from your last peak period, last BFCM or your biggest sale day, and prepare extra coverage and response templates in advance. Loyalty questions like points not appearing or a reward not applying spike alongside order volume

This builds directly on the general pre-launch checklist this builds on, which covers the broader site-readiness pass BFCM week depends on.

Why load time and uptime matter more this week than any other

Conversion rates drop an average of 4.42% for every additional second of page load time, and the highest-converting pages load in 1-2 seconds (Salesforce). A loyalty widget that adds even a second of latency at checkout is a measurable conversion cost, at the exact moment traffic, and the cost of losing it, is highest.

The baseline is already unforgiving before BFCM adds anything. Global cart abandonment sits above 70% even in ordinary conditions (Statista). BFCM doesn’t need extra friction to lose sales. It already has a high bar working against it.

A recent event makes the uptime risk concrete. In November 2025, a single infrastructure provider outage took down services across roughly 99.3% of Shopify storefronts worldwide, timed right before Black Friday (via eMarketer). It wasn’t caused by any merchant’s own code, which is exactly the argument for testing everything within your control, your widget, your integrations, your codes, since some risk sits outside it entirely.

None of this means every risk is preventable. It means the risks inside your control, widget speed, code compatibility, integration accuracy, are worth removing before the ones outside your control show up too.

BFCM week itself (Nov 27-30): what to monitor daily

Once BFCM week starts, the work shifts from testing to watching. Run through these four checks daily.

• Keep Double Points Day live for new signups for the entire BFCM window, not just one day. Every new member during this week is a potential repeat customer, not a one-time sale
• Confirm VIP early access actually fired on schedule. Don’t assume the automation ran, check it
• Run a quick one- or two-question poll, on-site or in a post-purchase email, asking members what rewards they actually want, then use the answers to adjust your reward mix in January
• Track new signups, reward redemptions, and technical issues daily, alongside revenue, not as an afterthought after the sale ends. A technical issue caught on November 28th is fixable. The same issue discovered in January is a quarter of lost data

Signups and redemptions are worth tracking against a real baseline, not just watching the raw numbers move. The KPIs worth tracking daily during BFCM covers what normal looks like by tier and channel.

The full two-week timeline at a glance

Here’s both checklists combined into one timeline, so you can see at a glance what happens two weeks out versus what happens during BFCM week itself.

When	Check	Why it matters
2+ weeks before BFCM	Stress-test widget load time	A slow widget at checkout costs conversions right when traffic is highest
2+ weeks before BFCM	Confirm discount-code compatibility	The most common place a reward silently breaks or double-stacks
2+ weeks before BFCM	Run a full integration test purchase	Confirms email, SMS, and review-platform data is passing correctly after your latest promo change
2+ weeks before BFCM	Prep support for peak volume	Loyalty questions spike alongside order volume during BFCM
Nov 27-30	Keep Double Points Day live for signups	Every new member this week is a potential repeat customer
Nov 27-30	Confirm VIP early access fired on schedule	Automations should be checked, not assumed
Nov 27-30	Run a quick reward-preference poll	Feeds directly into adjusting your reward mix come January
Nov 27-30	Track signups, redemptions, and issues daily	Catches problems while they’re still fixable, not after the sale ends

This timeline is exactly what your BFCM multiplier and reward math depend on holding up. Finalizing the multiplier this QA pass protects is worth locking in alongside this checklist, not after it.

FAQ

When should I start QA testing my loyalty program for BFCM?

At least two weeks before BFCM traffic arrives, so there’s time to fix anything the tests turn up. Testing during BFCM week itself is monitoring, not QA. By then, the setup should already be confirmed working.

What’s the most common loyalty program bug during BFCM?

A discount code interacting badly with a loyalty reward, either canceling it, double-stacking it, or applying it incorrectly at checkout. Test this combination specifically, not just the loyalty program in isolation.

Does loyalty widget load time really affect BFCM sales?

Yes. Conversion rates drop an average of 4.42% for every additional second of page load time, and BFCM is exactly the week when the traffic, and the cost of losing it, is highest.

What should I monitor once BFCM week starts?

Track new signups, reward redemptions, and any technical issues daily, alongside revenue. Also confirm time-sensitive automations, like VIP early access, actually fired on schedule rather than assuming they did.

What if an infrastructure outage outside my control happens during BFCM?

It can happen. A November 2025 outage at a major infrastructure provider affected the vast majority of Shopify storefronts globally right before Black Friday. You can’t prevent that kind of event, but testing everything within your own control, widget, codes, integrations, means it’s the only thing that can go wrong.

Two QA passes, and the mechanics you built keep working

Setting up a BFCM loyalty program is a strategy exercise. Making sure it survives contact with BFCM traffic is an operations exercise, and it’s the one that decides whether the strategy actually pays off. Run the tech checks two weeks out, watch the program daily once BFCM week starts, and the mechanics you spent September and October designing will still be working on November 30th.

P.S. The full 2026 BFCM Loyalty Setup Checklist (all 8 sections, printable) is available as a free download, including the setup steps this post’s QA checklist assumes are already in place.