By this week, the building is done. The offers are set, the pages are live and the checkout has been tested. What is left is running the weekend calmly: protecting what works, spotting problems early, and fixing them without making things worse.
This guide covers the freeze, the people, the numbers to watch and what to do first when something breaks. It is the final stage of our Shopify BFCM 2026 Playbook.
The code freeze
Freeze theme code at the end of Friday 20 November and keep it frozen until after Cyber Monday on 30 November.
| During the freeze you can | During the freeze you should not |
|---|---|
| Edit products, prices and stock | Edit theme code or templates |
| Change banners, images and text | Install or update apps that change the storefront |
| Create and schedule discounts | Add new tracking or marketing scripts |
| Update collections and menus | Change checkout extensions or integrations |
| Send emails and change flows | Run new A/B tests that change code |
The exception is a fix for something that is stopping customers from buying. Even then, make the smallest change that solves the problem, and test it on a copy of the theme first if you can.
Who does what
Most incidents are made worse by confusion about who decides. Write down, before the weekend:
- The incident lead — the one person who decides what to do when something breaks, and who can authorise a rollback.
- Who is on call, and when: store owner or manager, a developer, the customer support lead.
- Your external contacts: your agency or developers, and the support routes for your payment providers, key apps, warehouse or 3PL and carriers.
- How you will talk: one channel or group for the weekend, so updates are not scattered across inboxes.
Share it as a one-page runbook, with the backup theme’s name, where the status pages are, and the steps below.
What to monitor
Watch a short list of numbers every few hours, and compare each with the same hour last week or last year. Peaks and dips are normal; sudden changes are what matter.
| Signal | Where to see it | What a problem looks like |
|---|---|---|
| Orders per hour | Shopify Live View and order reports | A sharp drop while traffic holds up |
| Conversion rate | Shopify analytics | Falls well below the same hour last week |
| Checkout completion | Shopify analytics | More checkouts started than completed |
| Payment declines and errors | Your payment provider’s dashboard | A rise for one method or one market |
| Page speed | Your speed test on key templates | Pages much slower than your baseline |
| Stock on hero products | Products and inventory | Best sellers about to sell out |
| Support volume | Your helpdesk | A spike in one type of question |
Bookmark the Shopify status page and the status pages of your payment, shipping and review apps. If something breaks, check them first.
When something breaks: switch off first
For most problems the fastest, safest fix is to switch something off rather than write new code.
| Symptom | First action |
|---|---|
| Orders stop or drop sharply | Check status pages, then place a test order yourself to find where it fails |
| One payment method failing | Hide or deprioritise it, make sure an alternative works, contact the provider |
| A discount giving too much or too little | Edit or disable the discount, then check its combination settings |
| An app breaks the layout or slows pages | Turn off its app embed or block in the theme editor, or republish your backup theme |
| Pages suddenly slow | Disable the heaviest recent widget or script, then re-test |
| A best seller oversold | Correct the stock, pause the product in ads and emails, contact affected customers |
| An email or SMS sent wrongly | Pause the flow, then decide whether a correction message is needed |
Then tell customers if they are affected: a short banner on the store, a saved reply for your support team, and an honest post if the problem is visible on social media.
Write it down
Keep a simple log through the weekend: what happened, when you noticed, what you did and when it was fixed. It takes a minute per entry and it is the raw material for the December post-mortem — the meeting where next year’s BFCM gets better.
After Cyber Monday
- Lift the freeze on Tuesday 1 December and work through the list of non-urgent issues you logged.
- Move straight to retention: welcome flows and review requests for every new customer — see why customer retention matters more than acquisition.
- Book the post-mortem in the first week of December, while the numbers and memories are fresh.
If you are still preparing, the checks that prevent most weekend problems are in our guides to store speed before Black Friday and peak-season checkout and payments. And if you would like experienced hands on the weekend itself, our Shopify development and conversion rate optimisation teams can be on call from 27 to 30 November.
Frequently asked questions
When should I freeze my Shopify theme before Black Friday?
About a week before. For Black Friday on 27 November 2026, we suggest freezing theme code at the end of Friday 20 November and lifting the freeze after Cyber Monday on 30 November. During the freeze you can still change products, prices, banners, discounts and emails.
What should I monitor on my Shopify store during BFCM?
Orders per hour, conversion rate, checkout completion, payment declines and errors, page speed on key templates, and stock on your best sellers. Compare each with the same hour last week or last year, so you spot changes rather than reacting to normal peaks and dips.
What do I do if a Shopify app breaks my store during Black Friday?
Turn off the app's embed or block in the theme editor, or republish the backup copy of your theme you made before the freeze. Then contact the app developer. Avoid writing new code mid-weekend unless the problem is stopping orders.
How do I know if a problem is Shopify or my store?
Check the Shopify status page and your payment and app providers' status pages first. If they are clear, the problem is more likely in your theme, apps, integrations or settings — start with whatever changed most recently.
