Ecommerce Code Freezes: What Should Yours Cover?

“We don't touch anything during peak.”

It sounds professional, and it might even have come from your agency. It lasts right up until someone needs to correct a delivery message, replace an offer on a sold-out product, or fix something that's costing you sales. Then you do it anyway, in a hurry, without anyone having agreed who gets to make that call.

So before you agree to your Q4 freeze, ask your agency or developer what you'll still be able to change once it starts. The point of a freeze is to stop new faults from coming in while you're busy taking orders, but you still have promotions to run.

For many Shopify sites, we think a total freeze is overkill.

What can still change during your freeze

Your developer might leave the theme alone, but an app you install can still change the site. Some apps add scripts or tracking pixels as soon as they're installed. Before installing one during the freeze, ask your developer what it could affect and whether it can wait.

The apps you've already installed can change too. App developers can release updates that reach your store without your approval. Ask your agency which apps your checkout and orders rely on, and what you'd do if one stopped working. They can check with the suppliers about planned updates and whether those can wait. Any custom apps your agency looks after should be covered by its freeze.

Include changes to the software that updates your stock or sends orders to your warehouse, as well as tracking. A pixel or consent change can leave the site looking fine while skewing the figures you use to judge a promotion or adjust your ad spend. If someone else looks after your ads or analytics, tell them about the freeze too. They need to check the figures still come through correctly after any change.

Be specific about checkout settings, too. “Don't touch the checkout” doesn't tell you whether you can correct a shipping rule. Get your developer to explain which changes you can make yourself and which need their help.

Can you still run your offers?

Shopify's theme editor and BigCommerce's Page Builder let you edit content without a developer. Whether you can change a particular banner depends on how your site was built. The wording might be in the code, with no setting to edit.

Take the offers you've got planned and try setting them up with the access you'll have during the freeze. Can you get each one ready, put it live, change it and end it? Can you pull it early if the featured product sells out? If you get stuck, your developer may be able to add the missing setting before peak. Otherwise, agree that they'll help with that particular change during the freeze, or keep the offer simpler.

Being able to edit something doesn't make every change safe. Replacing a banner and changing how a product page adds items to the basket need very different testing. Even a new hero video can slow the homepage down on a phone. Check it before publishing.

A duplicate Shopify theme lets you preview theme changes, but it still shares your store's products, discounts and integrations. Ask your developer how to test an offer without customers getting hold of it early. If you have to test on the live site, make sure customers can't use the test offer and remove the temporary settings afterwards.

Try the offer on a product it should apply to and one it shouldn't. Check what happens when you use it with another discount, and confirm it starts and ends when your copy says it does. Whoever puts it live needs to know those checks are done.

When should the freeze start and end?

A nearly finished feature isn't a reason to release it just before your busiest weeks. Review the unfinished work with your developer and decide what can wait until you've both had time to check it properly. A fault stopping customers from ordering needs fixing now.

Leave enough time after the last code change to get through a busy day and fix what comes up. If weekends are your busiest days, go live with a weekend to spare and make sure your developer is available if something goes wrong. You don't want Black Friday to be the first busy day your new code has to deal with.

You don't have to start changing everything again on the same date. You might change the look of the site in December, but leave the returns system alone until you've dealt with Christmas returns. Agree those dates with your developer, including the offers you still need to run and when they'll be available if something breaks.

When something needs fixing anyway

If customers can't pay on a Saturday morning, you should already know who to call. Check when your agency is available, who else you can call if your usual contact is away, and whether they can start fixing an urgent problem straight away. If someone at your end has to approve the work first, they need to be reachable too.

Ask your developer how they'll check the fix and what they'll do if it makes things worse. If faulty code has changed your stock figures, putting the old code back won't restore them. They also need to stop the faulty updates and agree with you on how to correct the stock figures.

Ask them to leave a note about what they changed and whether it worked, so you don't have to explain it all again on the next call.

After peak

Note what held you up, and agree with your agency what you'll sort before the next busy period. If simple edits kept taking longer than expected, our piece on why ecommerce development slows down more than it should covers what could be behind it.

The Shopify and BigCommerce editing capabilities described here were checked on 12 October 2026.