Code freeze before Black Friday: what to lock and how to undo it
From the work/ 8 min read
What to freeze, what stays open, a guard script that blocks deploys during the freeze and a reversal plan for every exception. Dates for Black Friday 2026.
- Shopify
- QA
- Git
In this article (8)
A code freeze before Black Friday means that, from a set date, nothing changes on the storefront or checkout unless it stops a sale or charges the wrong amount. In 2026 the freeze runs from Friday, November 20 to Tuesday, December 1; Black Friday is November 27. Below: what to freeze, what stays open, how to undo changes.
The checkout smoke test and the freeze dates are in the smoke test article, and this one does not repeat them. It adds three things: how to decide which layers freeze, a script that enforces the freeze in your deploy pipeline, and the reversal for each type of change, using the method from the rollback plan. If you read this before Friday, November 13, that is the last day for large changes.
What a code freeze is, and why before Black Friday
A code freeze is an agreement, not a feature: for a fixed period, the people who can change the store agree not to. The reason is arithmetic. Every change has a small chance of breaking something. In an ordinary week you notice quickly and fix it with few customers affected. On Black Friday weekend the same break lands on the highest traffic of the year, and the hours you spend finding it are the hours with the most orders.
It is not a stop sign for the store either: orders keep coming, products sell out and merchandising moves. What stops is code and configuration, the things that can break checkout. The dates are the ones from the smoke test article; adapt them if your sale starts earlier.
| Date | Reference | What happens |
|---|---|---|
| Fri Nov 13 | BF-14 | The last large change ships, so it gets a week of real traffic |
| Fri Nov 20 | BF-7 | The freeze starts at the end of the working day |
| Fri Nov 27 | BF | Black Friday |
| Mon Nov 30 | BF+3 | Cyber Monday |
| Tue Dec 1 | BF+4 | The freeze ends |
Scroll the figure sideways to see all of it
What to freeze
Freeze by layer and write the list down. The test for each item is whether it can change what a shopper sees or pays on the path to checkout:
- Theme code and settings on the live theme. Editing a section in the theme editor is a theme change, even if you touch no code.
- Apps that touch the storefront or checkout: installing, removing or reconfiguring them.
- Checkout extensions and Functions. Each deploy creates an app version, and releasing it changes checkout; per Shopify's documentation, it can take several minutes to reach stores.
- Tracking scripts, pixels and tags.
- Navigation, URLs and redirects.
Two things the freeze cannot reach: an app's vendor can release changes you did not make, and any staff account with access can change an app's settings. Before the freeze, decide which apps stay: measure each app's weight to see what each one adds, remove what you do not use before November 20 and not during it, and leave access only to the people who need it.
Scroll the figure sideways to see all of it
Agreements loosen when nothing enforces them. For anything that deploys through a pipeline, a script as the first step of the deploy job turns the freeze into a failing check:
// Run this first in the deploy job.
const FREEZE_START = Date.parse("2026-11-20T18:00:00-06:00"); // Fri 20 Nov, end of the working day
const FREEZE_END = Date.parse("2026-12-01T00:00:00-06:00"); // lifted on Tue 1 Dec
const now = process.env.FREEZE_TEST_NOW ? Date.parse(process.env.FREEZE_TEST_NOW) : Date.now();
const ticket = process.env.URGENT_TICKET ?? "";
if (now >= FREEZE_START && now < FREEZE_END) {
if (!/^URG-\d+$/.test(ticket)) {
console.error("Code freeze until 1 December 2026: this deploy is blocked.");
console.error("Urgent fix? Set URGENT_TICKET=URG-<number> after the two approvals.");
process.exit(1);
}
console.log("Code freeze override logged: " + ticket);
}
console.log("Deploy allowed.");
- The two constants set the freeze window with an explicit UTC offset: this one is Mexico City time (UTC-6); change it to yours.
nowreads the real clock, orFREEZE_TEST_NOWso you can test it.URGENT_TICKETcarries the ticket of an approved urgent fix.- Inside the window, without a ticket shaped like
URG-number, it prints the reason and exits with code 1, which fails the job and blocks the deploy. - With a valid ticket it logs the override and lets the deploy through.
We ran it on nine cases, forcing the clock. Before the window and one minute before it, exit 0. At 18:00 on November 20, on the 27th and at 23:59 on the 30th, without a ticket, exit 1. With a ticket "fix", exit 1. With URG-42, exit 0 and the override logged. At midnight on December 1, exit 0. It only protects what goes through it: a change made in the Shopify admin does not pass through a pipeline, and there the freeze depends on the agreement and on who has access.
What you can still touch
A freeze of everything is a freeze nobody keeps. The store has to keep selling, so these stay open: product content (copy, prices, images and stock), collection order, and the Black Friday discounts, provided they were created and tested before the freeze and switch on by schedule.
Open does not mean careless. Product copy and images do not need a theme change, so keep them that way: if a product asks for a new section or a new field in the template, that is a theme change and waits for December 2.
And while the store is frozen, watch it. The checkout conversion alerts keep running through the freeze, and they are what tells you that an urgent fix, or an app update you did not make, changed something.
The reversal plan
Every urgent fix ships with its way back decided first. The method (a named version, a written way back, compatible migrations and a script that verifies afterward) is in the rollback plan article; this is the part specific to a Shopify store:
Scroll the figure sideways to see all of it
- Theme. Keep the backup theme untouched in the library. Per Shopify's help on publishing themes, when you publish one, the previously live theme moves to the drafts section and none of your theme changes are lost, so publishing the backup undoes a bad change. A store holds at most 20 themes (duplicating themes): count yours before the freeze.
- Checkout extension or Function. Releasing an earlier app version reverts it:
shopify app release --version=VERSION, with version names coming from theversions listcommand. Decide the version before you deploy, and remember it can take several minutes. - An app's embed. Turn the embed off in the theme editor; the app stays installed.
- Discount. Deactivate it.
- Script or pixel. Remove the snippet and keep the previous code.
The urgent-fix process in the smoke test article already ends with "roll back if either check fails"; this list is how to do it for each type. Write each exception's row in the ticket before the two approvers sign. If you cannot write it, the change does not go in during the freeze.
When to lift the freeze
On Tuesday, December 1. Lifting it is a decision, not a date that passes: first read the urgent-fix log (what changed, who approved it, how it was verified) and check that the smoke test is green on the live store.
Then do not release the whole backlog at once. The changes that waited since November 20 go out one at a time starting December 2, each with its smoke test and its reversal, so if something breaks you know which change did it. If another sale follows, write its freeze dates now, while the process is fresh.
Common mistakes
- A freeze with no end date. People stop respecting it. Write both dates.
- "One small app to try". The freeze covers apps too: it goes on the December 2 list.
- Freezing on paper only. Without a pipeline check or restricted access, anyone with admin access can still change the live theme.
- Approving an exception with no reversal. An approval with no way back is a second incident waiting.
- Starting late. If the last large change ships the day before, it has no week of real traffic to show its problems.
Frequently asked questions
How long should a code freeze last?
In this plan, from BF-7 (end of Friday, November 20) to the day after Cyber Monday (Tuesday, December 1). A smaller store with few changes can shorten it, but the last large change still needs a week of real traffic before it starts.
Can I still change prices or add products?
Yes. Copy, prices, images, stock and collection order are data, not code, and stay open.
What if an app updates itself during the freeze?
You cannot freeze a vendor's releases. Before the freeze, ask the vendors of apps that touch checkout whether they plan releases, keep the alerts running, run the smoke test after any change you notice, and know how to turn the app's embed off.
Does editing in the theme editor count as a change?
Yes. Saving in the theme editor changes the live theme, so settings and sections are frozen too, even if you write no code.
Checklist
- Both freeze dates are written down and everyone with access has confirmed them.
- The last large change shipped with a week of real traffic ahead of it.
- The list of what is frozen and what stays open is visible to the whole team.
- Apps you do not use are removed; access is reduced to who needs it.
- The freeze script runs first in every deploy job.
- Each exception carries a ticket, two approvals and its reversal row.
- The checkout alerts and the smoke test are active for the whole freeze.
For each exception's reversal, use the rollback plan; for the path to payment, the checkout smoke test; to know whether something changed, the conversion alerts; and to decide which apps stay, how to measure your apps' weight.
Saw this on Instagram? Comment FREEZE on the Reel and I'll send you the guide.
Written by

Published November 12, 2026 · updated November 18, 2026