Guides
Your BFCM prep should start in August: the 90-day timeline that actually works
Richard K. · August 17, 2026 · 9 min read
BFCM 2026 runs November 27 through 30. For most ecommerce stores, those four days will generate more revenue than the rest of the month combined, sometimes more than several months combined. That concentration is exactly why an outage, a broken checkout, or a stockout on November 28 costs so much more than the same problem on a random Tuesday in June.
Most merchants know this. Far fewer act on it early enough. The typical BFCM planning cycle starts in early November: a scramble to test the checkout, negotiate one more app integration, and hope the hosting plan holds. By then, there's no time left to fix what you find.
There's a better way to think about it. Work backward from November 27 using a 90-day window, and the starting line lands in late August. That's not a marketing gimmick, it's just enough runway to test, fix, freeze, and rehearse before the traffic arrives.
Why late August is the real BFCM start line
There's nothing magic about the number 90. It's just roughly how long it takes to do four things properly: audit what you have, fix what's broken, test the fix under load, and then leave the store alone long enough for the fix to prove stable before the busiest weekend of the year.
Compress that into three weeks in November and something gets skipped. Usually it's the testing step, because testing takes time and by November everyone is focused on creative and discounts. The infrastructure gets checked last, if at all, which is backward. A store that goes down for two hours on Black Friday loses more in that window than most stores lose in an entire slow week (see the real cost of an hour of downtime for how that math actually works out).
September planners have a structural advantage that has nothing to do with bigger budgets or smarter marketing. They simply have time. Time to run a real load test, get a bad plugin update out of the way in a quiet month, and fix a broken redirect before it costs a single order. November planners are working under pressure with no room for anything to go wrong twice.
August: weeks 1-4, fix the foundation
August is infrastructure month. Nothing customer-facing should change yet; the goal is to find out what would break under holiday-level traffic and fix it while nobody's watching.
Start with a full checkout test across devices and payment methods. Test the mobile checkout specifically, since a large share of BFCM traffic arrives on phones and checkout friction there is easy to miss on a desktop QA pass. Confirm your hosting or platform plan can handle a traffic multiple of your normal peak, not your average day.
Run a security scan and patch anything outstanding. A compromised store discovered in November is a crisis; the same issue found in August is a Tuesday afternoon fix. This is also the month to review your theme update history. Theme updates are a common, underrated source of lost orders when a script or app integration silently stops firing after an update (more on that pattern in why Shopify stores lose orders during theme updates). If you're planning any theme changes at all for BFCM, get them done and stress-tested in August, not October.
Finally, set your uptime and order-flow monitoring baseline now if you haven't already. You want alerts calibrated to normal traffic well before you need them calibrated to a five-times spike.
September: weeks 5-8, get the operational details locked
September is where inventory, pricing, and content work happens, while there's still time to correct course.
Forecast inventory by SKU, not just by category, and build in buffer for your top movers. A stockout on your best-selling item during Black Friday weekend isn't just a lost sale, it's often a lost customer who buys the same item from a competitor within the hour. If you run WooCommerce, this is also the month to finish any plugin updates and conflict testing well before your change freeze, since plugin conflicts are consistently the most common way WooCommerce stores break unexpectedly (see plugin conflicts and how to update safely).
Set up and test your promo codes and discount logic in a staging environment or during off-peak hours, checking that stacking rules work as intended and that pricing displays correctly across every currency and region you serve. Pricing errors that go unnoticed for even a few hours during a big sale can be expensive to unwind, and customers screenshot mistakes faster than support teams can fix them.
On the content side, confirm your sitemap is current and that your top category and product pages are indexed correctly. A stale or broken sitemap can quietly suppress the pages you're about to spend ad budget driving traffic toward (worth a direct check against how to tell if your sitemap is quietly broken). If you sell in multiple languages, verify translations on your key landing and checkout pages now, not after the first non-English customer hits a broken checkout string on November 27.
October and November: weeks 9-12, freeze and rehearse
By October, the building work should be mostly done. This phase is about protecting what's working, not adding more.
Set a change freeze date, commonly two to three weeks before Black Friday, after which no new apps, theme changes, or major plugin updates go live without a very good reason. This is the opposite instinct from most teams' November energy, which tends to be "let's add one more thing," but a freeze is what prevents an untested change from taking down checkout on November 26.
Run a final full-site QA pass: checkout, search, filters, cart abandonment flows, and any holiday-specific landing pages. Increase your monitoring cadence for the event window itself so that alerts for downtime, order-flow drops, or price errors reach you within minutes, not the next time someone happens to check the dashboard. Cassian™ customers typically tighten their alert thresholds for the BFCM window specifically, since a five-minute checkout outage on a normal Tuesday and a five-minute checkout outage at 9am on Black Friday are not the same event financially, even though the Cassian Score™ treats both as a health signal worth flagging immediately.
If you sell products that AI shopping agents can discover and purchase on a customer's behalf, this is also the window to confirm your product feed is accurate and complete, since a broken or stale feed can quietly cost you agent-driven orders you never see land (see is your product feed ready for AI shopping agents). Finally, have a rehearsed response plan ready: if sales suddenly drop mid-event, know who checks what first rather than improvising under pressure (the 48-hour checklist for diagnosing a sales drop is worth reading before the weekend, not during it).
The stores that have a calm Black Friday aren't the ones with the biggest budgets. They're the ones who did the boring infrastructure work in August, while everyone else was still writing ad copy.
Frequently asked questions
- When should I start preparing for Black Friday Cyber Monday?
- Ecommerce stores should start structured BFCM prep roughly 90 days out, which for BFCM 2026 (November 27-30) means late August. That window gives enough time to complete infrastructure and stress-testing work in August, inventory and pricing setup in September, and a final QA pass with a change freeze in October and November before traffic arrives. Starting in November instead compresses all of that into a few weeks with no room to fix problems you discover.
- What should be on my BFCM checklist besides marketing and discounts?
- A complete bfcm checklist needs to cover infrastructure and operations, not just promotions: checkout testing across devices, hosting capacity for peak traffic, security scanning, inventory forecasting by SKU, pricing and promo code testing, sitemap and translation checks, and a monitoring plan for the event itself. Marketing drives traffic to the store, but it's the operational layer, uptime, checkout, stock, pricing accuracy, that determines whether that traffic converts. Many of the costliest BFCM failures (a broken checkout, a stockout on a bestseller, a pricing display bug) have nothing to do with the marketing plan at all.
- Is it safe to update my theme or apps right before Black Friday?
- Updating a theme, plugin, or major app in the two to three weeks immediately before Black Friday carries meaningfully more risk than doing the same update in August or September, because there's little time left to catch and fix anything that breaks. Most experienced merchants set a change freeze roughly two to three weeks before BFCM, after which only urgent security patches go live, and even those get tested carefully before deployment. Any theme or app changes planned for the holiday season should be finished, tested under load, and stable well before the freeze date, not squeezed in during it.
Start the clock now
None of this requires a bigger team or a bigger budget. It requires starting earlier than feels necessary, which is the part most merchants skip because August still feels far from the holidays.
It isn't. BFCM 2026 is 90 days from late August, and the stores that treat that window as the real start of the season are the ones that spend Black Friday weekend watching sales come in instead of watching for the next thing to break. Build the timeline, do the boring infrastructure work first, freeze changes when the freeze date arrives, and keep monitoring tight through the event itself. That's the whole playbook, and it works precisely because almost nobody starts it in August.