The BFCM checklist for brands with a mobile app
Most BFCM checklists give your app one line. This one covers the release freeze, push permissions, app-only offers, deep links and new installs.
October 23, 2026
8 min read
Subscribe to Our Newsletter
Get mobile commerce insights. No fluff, just what you need to build smarter.

Short on time? Start here
- Get your final app build approved before your freeze date.
- Test every BFCM offer at checkout inside the app, on iOS and Android.
- Make sure your app-only offer doesn’t work on the website.
- Count your push-enabled users today, and ask for permission with a reason.
- Check that email, SMS and ad links open the right screen in the app.
- Schedule at least three pushes: teaser, launch and last chance.
- Name one person who owns the app over the weekend.
- Plan the first message for new installs, and make it something other than a discount.
Most BFCM checklists give your app a single line, somewhere between “schedule your emails” and “check your site speed.” That undersells it. Your app is the one channel where you don’t bid against every other brand for the click or fight for space in a crowded inbox. Push still competes on the lock screen, but nobody can outbid you for it.
The app also has failure modes your website doesn’t. You can’t hotfix it the way you can a theme. iOS shows the notification permission prompt once. And an “app-exclusive” code that also works on the website isn’t exclusive.
This checklist covers those parts, week by week. It assumes you’ve already done the standard prep: offers, inventory, shipping cut-offs and support coverage. If you’re already on Reactiv, your team’s own readiness checklist is in the docs.
BFCM 2026 key dates
| When | Date | What happens in the app |
|---|---|---|
| Six weeks out | Mid-October | Decide the app’s job, the offer and your targets |
| Release freeze | Friday, November 13 | Last app store build and promo changes approved |
| Thanksgiving (US) | Thursday, November 26 | Teaser, plus early access if that’s the app’s job |
| Black Friday | Friday, November 27 | Launch push and BFCM home screen go live |
| The weekend | November 28–29 | Targeted reminders, not blasts |
| Cyber Monday | Monday, November 30 | Cyber Monday push, then last chance in the evening |
| After | December | Welcome flow for new installs, then your debrief |
Treat the freeze date as a guide. Two weeks before Black Friday leaves room for one app review rejection and a resubmit.
Six weeks out: give the app one job
- Pick the app’s role for the weekend. It could be early access for app users, an app-only bundle, or simply the fastest place to check out. Choose one and build the calendar around it. Five half-promises read as noise in a push.
- Make the app-only offer actually app-only. The complaint we hear most from brands with an app is that their “app-exclusive” code also works on the website. That’s because it’s a plain discount code, and anyone can copy one. Instead, tie the offer to something only the app can verify: a first app order, a signed-in account or an install. On Reactiv, in-app offers apply at checkout for eligible shoppers, and the code is obfuscated so it can’t be shared.
- Set app targets separately from web. Track app revenue share, push-enabled users, weekend installs and app conversion rate. Pull last month’s numbers now so you have a baseline in December.
- Brief creative in app sizes. You’ll need a home screen hero, push images, a sale collection banner and, if you plan to update them, App Store screenshots. These are different crops from your email and social assets, and they’re the ones that get forgotten.
Four weeks out: test the app like a shopper
- Ship your last app store build early. Most App Store reviews come back within a day, but a rejection restarts the clock. Get the final build approved before the freeze, with time for one rejection and a resubmit.
- Know what you can change without a release. Home screen content, banners and collections should change from your dashboard. Anything that needs a new build has to land before the freeze.
- Run every offer through app checkout. That includes discounts, tiered offers, gifts with purchase, bundles and free shipping thresholds. Test on iOS and Android, on an older phone and on a slow connection. Then do it all again signed out.
- Check the payment buttons. Apple Pay, Shop Pay and any other express checkout you rely on should work in the app exactly as they do on your site.
- Test deep links from where shoppers will tap them. Every email, SMS and ad link should open the right screen in the app for people who have it. People who don’t should land on the right page of your site. Test from Gmail and from inside Instagram, where links often open in an in-app browser instead of your app.
- If you sell on iOS, set up an In-App Event. It promotes your sale on your App Store page and in App Store search. Events go through App Review, so submit yours alongside your final build.
Three weeks out: build your push audience before you need it
- Count your push-enabled users now. Pull the number from Klaviyo, OneSignal or Firebase. It’s the ceiling on what push can do over the weekend, so find it while you can still raise it.
- Ask for permission with a reason. iOS shows the system permission prompt once. If a shopper taps “Don’t Allow,” the only way back is through their Settings. Show your own screen first, saying what they’ll get (early access to your Black Friday sale, for example). Then show the system prompt only to people who tap yes.
- Use your own channels to drive installs. Add a smart app banner to your mobile site, a line to your email footer and a link to the order confirmation page. Send an SMS to your list and put a QR code on the packing slip. Every order you ship in November is a chance to get that customer into the app before next year.
- Give paid traffic a native landing. If you’re running paid social to mobile, the jump from ad to mobile site is where a lot of that spend is lost. With App Clips, an iPhone shopper who taps your ad opens a native screen without downloading anything. You can also send them notifications for up to eight hours after each launch, with no permission prompt.
In Reactiv customer data, App Clips convert ad traffic at up to 3x the rate of mobile web, and an average of 15% of Clip visitors go on to install the full app. During BFCM 2024, merchants using Reactiv Clips saw a 60% click rate on those notifications. Android shoppers fall back to your mobile site, so the ad itself doesn’t change. For BFCM landing pages and push ideas, see Reactiv Clips and push notifications for peak season.
Two weeks out: freeze the build and load the calendar
- Freeze. After the freeze date, no new app binary goes out unless something is broken. Content changes keep going through your dashboard.
- Write the push calendar. Plan at least three sends: teaser, launch and last chance. Most brands do better with a few more, each sent to a narrower audience. Here’s a starting point:
| Moment | Who gets it | Where it opens |
|---|---|---|
| Teaser (Tuesday or Wednesday before Thanksgiving) | All push-enabled users | A sale preview or their wishlist |
| Early access (Thanksgiving evening) | App users, if early access is the app’s job | The sale collection |
| Launch (Black Friday morning) | All push-enabled users | The sale collection, not the home screen |
| Weekend reminder (Saturday or Sunday) | Shoppers who browsed or added to cart and didn’t buy | The product or cart they left |
| Cyber Monday (Monday morning) | All push-enabled users | The Cyber Monday collection |
| Last chance (Monday evening) | Engaged non-buyers from the weekend | The sale collection |
- Don’t paste your email calendar into push. If a shopper gets your email, your SMS and your push for the same offer, that’s three interruptions for one message. Set a daily cap per shopper, and save push for the messages where timing matters.
- Segment before you send. Active app users, lapsed users (no app open in 30 days or more), top spenders and cart abandoners each need a different message. A lapsed user is better served by one strong reason to come back than by six sale alerts.
- Turn on your automations. Abandoned cart, browse abandonment, back-in-stock and wishlist price-drop pushes keep working all weekend without anyone scheduling them. Pause or update any flow whose discount code could clash with your BFCM offer.
- Schedule the home screen. Set the BFCM home screen (hero, sale collection and countdown) to go live at launch time. Also decide what replaces it when the sale ends, so Tuesday’s shoppers don’t open the app to a countdown stuck at zero.
- Test rich push on both platforms. Images crop differently on iOS and Android, so send every BFCM push to a test device first.
- Hold the rating prompt. Apple shows the review prompt at most three times a year per user. Don’t spend one on a shopper fighting a sold-out size. Trigger it after a delivered order instead.
BFCM weekend: run the app as its own channel
- Name one owner for the app. One person watches crash reports, app store reviews and the push schedule. They can also swap the home screen if something sells out.
- Watch app numbers separately. Track sessions, conversion rate, orders from push and crash-free sessions alongside your web dashboard. If the app is converting and web isn’t, or the reverse, you want to know on Friday, not on Tuesday.
- Keep a backup push ready. If your hero product sells out, have a pre-written push ready that sends shoppers to an alternative collection. It beats writing one at midnight.
- Brief support on app questions. Expect “Why doesn’t my app code work on the website?” Expect “Where’s my order?” too, from shoppers who assume they can track it in the app.
After Cyber Monday: keep the people who installed
BFCM brings in a wave of new app users. What you send them next decides whether the app stays on their phone.
- Send a welcome that isn’t a discount. Point them to order tracking, holiday shipping cut-offs, a gift guide, or back-in-stock alerts for anything they missed.
- Measure the app on its own. Compare push-enabled users before and after BFCM, plus app revenue share and app versus web AOV. Track installs by source (banner, email, SMS, packing slip, App Clips) and 30-day repeat purchases from weekend installers.
- Check your app-only offer for leaks. Count redemptions by channel. Any web redemptions tell you what to change next year.
- Write the debrief while it’s fresh. Record your best push (copy, send time, audience), what sold out and how you handled it, any crash or checkout issues, and which install sources worked. Next year’s checklist starts there.
Want a second set of eyes before the freeze?
Book a pre-peak mobile review. We’ll walk through your mobile funnel with you before the freeze, and you’ll leave with a plan to be live in January.

See Reactiv on your storefront.
Book a demo and we'll walk you through native apps and App Clips running on your Shopify store.


