Black Friday is November 27 this year, and most freeze guides put the lock on theme, app and checkout changes between November 13 and 20. Today is the 13th. If your team treats "freeze" as "stop thinking about the storefront", you are about to spend the busiest two weeks of the year leaving known checkout problems in place.
This article argues that a freeze should lock code, not design. It shows which checkout and product page fixes are safe because they are content, not code, ranks them by what the research says costs you orders, and gives a plan for the 14 days left.
A freeze protects code, and that is all it protects
The reason for a freeze is simple. A new bug in browsing or checkout costs the most when traffic peaks. The Good's holiday code freeze guide says it plainly. Feature changes that need code wait until the freeze ends.
Look at how those guides define the line, though. The Shopify-focused Craftshift 2026 plan sorts work by how fast you can undo it. Theme code, app installs, checkout customizations and Shopify Functions are red, because rollback takes hours. App settings and styling are amber, with rollback in minutes. Prices, banners, product copy, images and collection membership are green, and you can undo them in seconds. Its dates are one vendor's recommendation, not Shopify policy, but the logic holds. Risk follows rollback time, not whether a designer touched it.
The same Craftshift plan locks configuration on Friday, November 13 and code on November 20. So you have a week where content and data stay open, and a few days where only critical fixes ship. Too many teams spend that week waiting.
That is a mistake, because checkout problems are mostly not exotic. They are well documented, and several of them live in copy and data.
Rank the fixes by what actually loses orders
Start from the evidence instead of the backlog. Baymard's cart abandonment research averages 50 studies at a 70.22% abandonment rate. Among shoppers who intended to buy, it lists the reasons. 40% cite extra costs such as shipping, tax and fees, 20% slow delivery, 19% distrust of the site with card details, 18% forced account creation, 17% a long or complicated checkout, 12% a total cost that was not visible up front, and 13% an unsatisfactory returns policy.
Now sort those by rollback speed. Extra costs and a hidden total are a data and copy problem for many stores. Think shipping thresholds, delivery estimates, a line on the product page. Delivery speed is partly a promise you can state more clearly. Returns policy is a page. Trust is wording, badges and payment method labels. Account creation is a setting on Shopify and most other platforms. Only a long checkout is a real code problem.
Baymard also says that fixing solvable checkout usability issues could raise conversion by 35.26% for a large site. Treat that as an upper bound for sites with many unfixed problems, not a forecast. Baymard has also said it is retesting its checkout research and expects new findings in the second quarter of 2027, so the exact percentages may move. The ranking of reasons has been stable for years, which is why I trust it for a two-week decision.
The point is that most of the top reasons for abandonment can be addressed with changes your freeze policy already calls green or amber.
Show the total cost before the cart
Since extra costs are the top reason, start there. A shopper who sees a $9 shipping fee for the first time on the payment step reads it as a trick, however fair the fee is.
The no-code fixes are boring and effective. Put the free shipping threshold in the announcement bar and on the cart drawer with a live "you are $14 away" line, which is a content block on most themes. Add estimated delivery dates by region to the product page, because for Black Friday orders the question "will it arrive by December 24?" is the one on people's minds. State your holiday returns window in one sentence near the buy button. Make guest checkout the default and hide account creation until after payment.
If you cannot show exact tax, show a range and say it is an estimate. A range that is roughly right beats a surprise that is exactly right.
Check each change against one question. Could this break a payment? Copy, banners and threshold messages do not touch the payment flow. A new fee calculator does, so it waits until December.
Test less, but do not stop looking
Many guides argue about whether to run A/B tests during the holidays. The honest answer is that most stores should not start new ones now. Convert's guide says Black Friday through Cyber Monday is a two to four day window of hyper-shopping, and that conversion rate, average order value and revenue per visitor swing sharply, with flash deals, ad spend and competitor offers all changing the conditions. A test that starts on November 24 and ends on November 30 tells you about Black Friday, not about your store in March.
The Good takes the opposite line. More traffic means faster significance, and "your biggest risk is doing nothing". Both can be right. That article is from 2021 and gives no data, so I read it as a reminder, not as proof. Traffic does speed things up, but only for questions that matter in a normal week.
My rule is this. If a test can reach a readable result by about November 20, let it finish. If not, ship the obviously better version to everyone only when you have a documented reason, not a hunch, and write it down. Baymard's reasons are such a reason. A hidden shipping cost is not a hypothesis to test during Black Friday.
What you should do is watch. Heatmaps, session recordings and customer service tickets cost nothing in risk terms. Set up your conversion tracking before traffic arrives, as The Good advises, so that you have clean data for the first week of December.
A plan for the next 14 days
Here is the sequence I would run, assuming a Shopify store and a team of one to three people.
Today and tomorrow, take a snapshot. Duplicate the live theme as a restore point, export your settings and list who can publish. The Craftshift plan recommends the same, plus one monitoring dashboard and a rollback rule agreed in advance, such as "revert if checkout completion drops by a set amount over an hour".
By Monday, audit the green list against Baymard's reasons. Open your store on a phone, add a product to the cart and go through checkout as a stranger. Write down every moment where you learned a cost, a date or a policy for the first time. Each one is a copy or data fix.
By Wednesday, ship the fixes. That means a threshold message, delivery dates, returns line, guest checkout default, and payment method icons. Log each change with a time and the person who made it, so a bad hour is easy to explain.
From November 20, touch nothing in code. Content stays open, including prices, stock, banners and emails. Keep the thaw date at December 1 or later, since Cyber Monday orders arrive until midnight.
Last, keep a list of the red items you wanted and could not ship, such as a faster checkout step, a new cart design or an app. That list is your January plan, and it will be better informed because you watched real peak traffic first. For help judging whether your conversion numbers are healthy when peak week ends, my Shopify conversion benchmarks piece explains why published figures disagree.
Originally published on kireev.us.
