Picture a store owner three days before Black Friday. The sale emails are scheduled, the discount codes are ready, and someone installs a new countdown timer app to add urgency. By Friday morning, the add to cart button on mobile has stopped working. Nobody tested it.
Some version of that story plays out every peak season. The platform usually isn't the problem. Shopify handles hosting and checkout infrastructure. Your theme, apps, discounts, and inventory settings are on you, and peak traffic finds every weak spot in them at once.
It gets trickier when a store has custom work. Say your theme was built or heavily customized by a Shopify development team like The ShopNinjas. That custom code is the first thing to check before any update, because a theme update can overwrite it. A quick conversation with whoever wrote it, weeks before the sale, saves a lot of guessing later.
The timeline below covers the weeks before, during, and after your biggest sale. Follow it in order and you'll go into peak season with a store that's been tested, not just hoped for.
The Short Answer
Start six weeks out. Audit your apps and speed first, then test checkout, discounts, and inventory under real conditions. Freeze all changes about two weeks before the sale.
During the sale, watch the store instead of editing it. After the sale, clean up campaign leftovers and review what the data showed you.
The single most important rule is the freeze. Most peak-season disasters start with a "quick fix" pushed live on a busy day.
What Shopify Handles and What You Handle
Knowing where the line sits tells you where to spend your prep time.
Shopify handles:
Hosting and platform uptime
Checkout and payment infrastructure
Platform-level security
You handle:
Theme code and any custom Liquid
Every installed app and how they interact
Discount setup and how codes combine
Inventory and overselling settings
Page speed, images, and scripts
Order notification emails
A store can sit on solid infrastructure and still fail at the theme or app layer. That's where this checklist focuses.
Six Weeks Out: Audit and Fix
This is your window for real changes. Anything risky happens now or waits until after the sale.
Audit your apps. List every installed app and ask what it does for revenue. Remove anything you don't use. Each app can add scripts to your storefront, and deleting one doesn't always remove its code, so check your theme for leftover snippets afterward.
Record a speed baseline. Check Core Web Vitals on your homepage, a collection page, and your top product pages. Google's published "good" thresholds are a Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Fix the biggest offenders first, which are usually oversized images and unused apps.
Apply pending updates. Install theme and app updates now, on a duplicate theme first, so you have weeks to catch problems.
Fix broken links. Scan for 404s and set up redirects for removed products. Sale traffic often lands on old URLs from past campaigns.
Four Weeks Out: Test Under Real Conditions
Now you test the store the way a customer will use it on the busiest day of the year.
Run full checkout tests. Place orders on mobile and desktop. Use test mode if your payment provider supports it, or place a small real order and refund it.
Test every discount. Create your sale codes and automatic discounts now, then try them in checkout. Check how they combine with each other and with existing offers. A discount that stacks by accident can wipe out your margin in an hour.
Check inventory settings. Review which products allow selling when out of stock. That setting is useful for preorders and dangerous for limited stock during a rush.
Review notification emails. Order confirmations, shipping updates, and digital delivery emails should all show the right branding, links, and wording. Send each one to yourself.
Test on a slow connection. Load your key pages on a phone with weak signal. That's how many of your sale-day shoppers will see your store.
Two Weeks Out: Freeze Changes
Pick a freeze date and announce it to everyone who touches the store. From that day, no theme edits, no new apps, and no app updates unless something is actually broken.
What's still allowed:
Product and price changes for the sale
Banner and image swaps that use existing sections
Fixes for real bugs, tested on a copy first
Before the freeze starts:
Duplicate your live theme and label it as the pre-sale backup
Export products, customers, and orders
Write down which discounts go live and when
The backup theme is your rollback plan. If anything breaks during the sale, you republish it instead of debugging live.
Sale Week: Watch, Don't Tinker
On sale days, your job is monitoring, not building.
Check the storefront and checkout a few times a day, on mobile
Watch for spikes in support messages about the same problem
Confirm discounts apply and expire on schedule
Keep an eye on stock levels for your top sellers
Decide in advance who can make changes and who has to approve them. One person with publish access during a sale is safer than five.
If something breaks, restore first and diagnose second. Republish the backup theme or switch off the newest app, then investigate once the store is stable.
Keep a short incident log while the sale runs. Note the time, what broke, what you did, and how long it took to fix. It takes a minute per entry, and it turns a stressful weekend into a clear list of problems to fix before the next big sale.
After the Sale: Clean Up
The sale ends, but the leftovers don't remove themselves.
Remove expired banners, countdown timers, and sale-only apps
Turn off sale discounts that should no longer work
Redirect campaign landing pages to evergreen pages
Reset any inventory settings you changed for the rush
Then review the data while it's fresh. Look at which pages slowed down, where checkout dropped off, and which support questions came up most. That list becomes the starting point for your next peak season.
The Timeline at a Glance
When | Focus | Main tasks |
|---|---|---|
Six weeks out | Audit and fix | App audit, speed baseline, updates, broken links |
Four weeks out | Test | Checkout, discounts, inventory, emails, slow connections |
Two weeks out | Freeze | Backup theme, data export, no new changes |
Sale week | Monitor | Daily checks, single point of approval, rollback ready |
After the sale | Clean up | Remove campaign leftovers, review data |
These timings are suggested starting points, not a fixed rule. Larger stores often start earlier.
Short on Time? The Two-Week Version
If the sale is already close, skip the big changes and do only what lowers risk.
Duplicate your live theme as a backup today.
Remove apps you clearly don't use, then check the storefront still works.
Create and test every sale discount on mobile.
Place one full test order and check every email it triggers.
Review oversell settings on your top products.
Freeze everything else until the sale ends.
This won't make your store faster, but it removes the most common ways a sale goes wrong. Save the speed work and updates for after peak season, when a mistake costs less.
Mistakes That Cost Stores on Sale Day
Installing a new app the week before. New apps bring new scripts and new conflicts, with no time left to find them.
Testing discounts only on desktop. Mobile checkout can behave differently, and many sale shoppers arrive on phones.
Skipping the backup theme. Without it, every problem becomes a live repair under pressure.
Leaving sale settings on afterward. Old discounts and oversell settings keep working until someone turns them off.
Who Should Handle Pre-Peak Maintenance
A store owner can run this checklist for a simple store with a few apps. It takes time, but it's manageable.
The math changes as the store gets more complex. Take a store running a dozen apps, a custom bundle builder, and a big share of its revenue riding on one weekend. The owner has two options: block out several days for audits and testing, or hand the prep to a team that does it routinely through something like The ShopNinjas Shopify maintenance services and spend those days on marketing and stock instead.
Neither option is wrong. The right one depends on how much time you have and how much a broken checkout would cost you.
Whoever does the work, make sure they test on a copy, keep a backup theme, and respect the freeze date. Those three habits prevent most sale-day emergencies.
Questions Merchants Ask
When should I start preparing for Black Friday?
About six weeks before the sale is a comfortable starting point. It leaves time to fix what the audit finds.
Should I update my theme before the sale?
Only if you do it early and test it on a duplicate. Never during the freeze.
What's the fastest fix if checkout breaks during the sale?
Republish your pre-sale backup theme, then disable the newest app or change. Diagnose after the store is stable.
Wrapping Up
Peak season rewards boring preparation. Audit early, test like a customer, freeze changes on time, and keep a backup ready.
Do that, and your biggest sale becomes a busy weekend instead of an emergency.