Change Freeze for Shopify Stores Over Black Friday

How to run a change freeze across several Shopify stores for BFCM 2026: what to freeze, what must still happen, approvals, checking changes landed and rollback.

In this guide
  1. Set the dates
  2. What to freeze
  3. What still has to happen
  4. Schedule what you can before the freeze
  5. An exception process that works
  6. Check that each change landed
  7. Rollback: know what can and can’t be undone
  8. Lifting the freeze
  9. Pitfalls
  10. Where Storefleet fits
  11. FAQ

Peak season is when your stores earn the most and when a broken change costs the most. A change freeze is a simple agreement: for a fixed period, nothing that can break checkout, pricing or the storefront goes live without a deliberate decision.

A freeze is not “stop working”. Orders still need fulfilling, refunds still need approving, and a stock count that turns out wrong on Black Friday morning still needs fixing. The aim is to sort changes into three groups: frozen, allowed with approval, and business as usual.

For BFCM 2026, Black Friday is November 27 and Cyber Monday November 30. This guide covers how to set the freeze dates, what to freeze, how to approve exceptions, how to check a change actually landed in each store, and how to roll back.

Set the dates

A typical freeze for BFCM 2026:

Phase Dates Rule
Build Until Nov 13 Theme, app and catalog work finishes
Soft freeze Nov 14 to Nov 22 Only fixes and planned promotion setup
Hard freeze Nov 23 to Dec 1 Only changes on the “allowed” list, each approved
Thaw From Dec 2 Lift in stages, one store first

Pick dates that fit your stores and share them in writing with everyone who has access, including agencies and freelancers. If you work across several stores, the freeze applies to every store at once; a store left out is where the surprise comes from.

The timeline leading up to these dates is in the BFCM 2026 checklist for multiple Shopify stores.

What to freeze

Freeze changes that can break many orders at once, or are hard to undo:

Change Why freeze it
Theme code and template edits A broken template affects every visitor
Installing, removing or updating apps New apps can change checkout, stock or orders
Payment and checkout settings A wrong setting can stop sales or change how payments are captured
Shipping rates and zones Shopify notes that deleting rates stops customers checking out
Catalog bulk edits and CSV imports One file can rewrite prices for hundreds of products
New discounts not in the promotion plan Unplanned stacking eats margin
Staff roles with wider permissions Peak week is not the time to widen access

The shipping point comes from Shopify’s own page on managing increased sales, which suggests checking that rate changes don’t break app or sales channel connections (Shopify Help Center).

What still has to happen

These continue during the freeze, under the approval rules below:

Change Control during freeze
Order fulfillment and tagging Normal routine
Customer notes and support replies Normal routine
Stock corrections Approval required
Planned promotion going live Pre-approved; check after it starts
Ending a promotion Pre-approved; check after it ends
Refunds and cancellations Owner only
Payment captures (manual capture stores) Owner only, on a set schedule
Urgent fixes to a broken page Approval by a named person, with a rollback plan

Two Shopify rules make the money items strict. Refunds started from Shopify admin can’t be cancelled or reversed, and Shopify Payments provides a 7-day authorization period for credit card payments, so a forgotten capture can mean money you can’t collect. Shopify holiday rules for refunds, captures and discount codes covers both.

Schedule what you can before the freeze

The safest change during the freeze is one that was set up and checked before it.

  • Discounts have their own active dates, so a BFCM discount can be created and tested in early November and start on its own.
  • Shopify Rollouts schedule changes to a store’s main theme, checkout and accounts pages, discounts and catalogs. A Launch merges changes permanently. An Event publishes changes for a set period and then rolls them back when the rollout ends, which suits a Black Friday to Cyber Monday promotion (Shopify Help Center).
  • Rollouts are available on the Basic plan or higher. They can’t be applied to vintage themes or change Liquid templates, and a discount can be part of only one unended rollout at a time (Shopify Help Center).

Rollouts are set up per store. With several stores, create each one and check each one.

An exception process that works

Something will need changing during the freeze. Decide the process now:

  1. Request in writing, in one place, naming the store, the change, the values before and after, and why it can’t wait.
  2. One store per request. “Raise prices on all stores” becomes one request per store, so each can be checked on its own.
  3. Named approvers per store. Write down who approves and who covers when they are offline.
  4. Fixed review times, for example 9:00 and 16:00, plus an urgent route for a broken checkout.
  5. Approval states the rollback. Before approving, know how to undo it. If it can’t be undone, say so and decide whether it is worth it.
  6. Record the decision: who asked, who approved, when, what changed.

The general approval setup is in approval workflows for changes to live Shopify stores.

Check that each change landed

“Saved” in an admin screen means the request was accepted. It does not always mean the store now shows what you meant. During the freeze, every approved change gets a check:

  1. Open the store’s admin and read the value you changed: the stock level at the right location, the discount’s status and dates, the price.
  2. Check from the customer side for anything visible: add the product to cart, apply the code.
  3. Repeat per store. A change approved for three stores is three checks.
  4. Note the result next to the approval.

If you change several stores in the same window, read changes across multiple Shopify stores for how to avoid the wrong store.

Rollback: know what can and can’t be undone

Change Rollback route
Theme edit Publish the backup theme you duplicated before the freeze
Event rollout Rolls back on its own when the rollout ends
Discount Deactivate it; Shopify lets you temporarily deactivate an unexpired discount
Stock correction Set the previous value, which you recorded before the change
Price change Re-apply the previous price from your export
Refund Can’t be reversed

The discount route comes from Shopify’s discount page: deactivated codes return an error at checkout, and reactivating an expired discount makes it active again with no end date, so set the end date again if you reactivate one (Shopify Help Center). For themes, duplicate before the freeze; Shopify allows 20 themes per store and you must delete one to duplicate past that (Shopify Help Center).

Recording the “before” value is what makes stock and price rollbacks possible. A stock change without the old number written down is a guess to undo.

Lifting the freeze

Don’t lift everything on December 1. Thaw in stages:

  1. One store first, with the backlog of waiting theme and app work.
  2. Watch it for a day.
  3. Then the rest.

Returns and refunds pick up in December, and January brings the stocktake. The post-holiday stocktake guide picks up from here, and seasonal staff access covers removing holiday access once it’s done.

Pitfalls

  • A freeze nobody outside the core team knows about. Agencies, freelancers and app vendors need the dates.
  • Exceptions decided in chat. Two days later nobody can say who approved what.
  • “Applied to all stores” without checking each one.
  • No before value recorded, so a rollback means guessing.
  • Money actions in too many hands during the busiest week.

Where Storefleet fits

In the Storefleet Store Ops web dashboard, stock, discount, refund, cancel and capture changes go through approval, with a level set for each store. A pending change shows its values before and after, how many objects it touches, and is flagged when it can’t be undone. Every store’s pending changes wait in one Approvals list, but each change belongs to one store and is approved for that store. After writing, StoreFleet reads the store back from Shopify to check the change landed, and rolls it back where Shopify allows. Refunds, cancellations and captures are owner-only, and nothing is synced between stores automatically. See the security page for roles and the audit log.

FAQ

What is a change freeze for a Shopify store?

A fixed period, usually around Black Friday and Cyber Monday, when changes that can break checkout, pricing or the storefront need a deliberate approval or wait until after. Order work and planned promotions continue.

When should a BFCM 2026 change freeze start?

Many teams finish build work by mid-November and start a hard freeze before Thanksgiving on November 26, 2026, running through Cyber Monday on November 30. Pick dates that fit your stores and share them with everyone who has access.

Can I still fix stock during a freeze?

Yes. Stock corrections are usually allowed with approval: request it for one store, record the old value, approve it, then check the store shows the new value.

How do I roll back a BFCM promotion automatically?

A Shopify Rollouts Event publishes changes for a set period and rolls them back when it ends. Discounts also have their own active dates. Both are set per store.

Which changes can’t be rolled back?

Refunds started from Shopify admin can’t be cancelled or reversed. Keep them owner-only during the freeze.

Sign in to your workspace

Each workspace has its own address: <workspace>.getstorefleet.com. Enter your workspace name, or paste its address, and we take you to its sign-in page.

You will go to

New to StoreFleet? Create a workspace