Your Black Friday code freeze starts soon. Your coupon decisions are due now
A Black Friday code freeze is the right call. It also means any fix for leaked codes and coupon extensions has to be decided in October, before it starts.
Jump to a section
In short
For store owners
You made the sale. A coupon extension took a cut.
Add Benson free to see what coupon extensions took from your orders over two weeks. Set rules to hide pop-ups and control which codes work in extension sessions.
We'll email you about getting started. Unsubscribe any time.
It's October. Your developer posts the date in the team channel: the code freeze starts in a few weeks. No theme edits, no new apps, no tag manager publishes until January.
Everyone nods. It's the sensible thing to do.
Then you look at the list you've been meaning to get to. The coupon extension pop-ups that appear on your product pages. The influencer code that ended up on a code site last spring and still turns up in orders. The vague plan to "sort out discounts before Black Friday". You realise that anything on that list not shipped before that date waits until January. Black Friday is 27 November. January is after the busiest week of your year.
This guide is about the weeks before it: why the freeze is right, why it moves your deadline, and what to get done before it starts.
Why does everyone freeze the site before Black Friday?#
Because changes are what break sites. Google's site reliability team found that roughly 70% of its outages came from changes to a live system [Google, Apr 2016] (opens the source). A freeze removes the most common cause of an outage during the weeks when one costs the most.
And when something does break in peak week, whoever caused it, the damage lands at the worst moment.
Some teams now argue the freeze should start earlier than most people assume.
Freezes differ. Some teams freeze everything, including app installs. Others allow configuration changes in tools already live, with sign-off. Find out which kind you have, and the exact date, before you plan anything else.
Why do the frozen weeks matter so much?#
Because a large share of your year happens inside them, at the deepest discounts you'll run all year, with the most deal-seekers and the most automation on your site.
$47.5B
Adobe's forecast for US online spend in Cyber Week 2026, the five days from Thanksgiving to Cyber Monday: 17.3% of the whole two-month holiday season.
The same pattern shows up for independent stores. Shopify merchants sold $14.6 billion over the 2025 Black Friday Cyber Monday weekend, and more than 94,900 of them had their highest-selling day ever [Shopify, Dec 2025] (opens the source).
$5.1M
Sales per minute across Shopify stores at the 2025 peak, just after midday Eastern on Black Friday.
The discounts are at their deepest. Adobe expects discounts of up to 30% off listed price during Cyber Week this year [Adobe Digital Insights, Sep 2026] (opens the source). Last season apparel discounts peaked at 25.1% [Adobe Digital Insights, Jan 2026] (opens the source). Every extra code that stacks on top of a sale price comes straight off a margin that is already thin, and the discount strategy guide works out how many extra orders each step deeper has to find.
That stacking is easy to miss in the rush.
Deal-seekers bring their tools. Shoppers who ignore coupon extensions the rest of the year go hunting for codes in sale week. Adobe's forecast says cashback and rewards partners lead affiliate traffic this season, with a 36% share [Adobe Digital Insights, Sep 2026] (opens the source). That category includes the cashback sites and browser extensions that sit between a shopper and your checkout. When one of your sale codes reaches a code site, extensions such as Honey and Capital One Shopping can try it at checkout for every user who has them installed, for the rest of the week.
Codes don't have to be public to travel.
AI shopping agents are arriving at the same time. Adobe expects traffic from AI tools to US retail sites to rise 130% this holiday season, with Black Friday up 95% [Adobe Digital Insights, Sep 2026] (opens the source). Last season it rose 693.4% on the year before, from a small base [Adobe Digital Insights, Jan 2026] (opens the source). HUMAN Security found retail and ecommerce took 46.6% of the agentic AI traffic it saw in 2025 [HUMAN Security, Apr 2026] (opens the source). Adobe says shoppers now use these tools to find deals [Adobe Digital Insights, Jan 2026] (opens the source), and a deal often means a code. The guide to agentic commerce and your discount codes covers where each AI channel takes them.
130%
Adobe's forecast rise in AI traffic to US retail sites this holiday season, year on year.
Why is this an October decision, not a November one?#
Because the freeze turns every "we'll sort it before the sale" into "we'll sort it before the freeze". Put the three facts together:
- The weeks you can't change the site are the weeks that carry the most revenue at the thinnest margin.
- Coupon extension and AI agent traffic peaks in exactly those weeks.
- Anything that needs your theme, your tag manager or your developer has to land before the freeze, or it waits until January.
It's bigger than one team, too. Finance reads the sale in January, which is when below-cost orders and stray discounts show up. Affiliate and partner managers pay commission on orders where a code was applied at the last step, often by an extension. Your developer owns the freeze and has to sign off on anything that ships before it.
There's a measurement reason as well. A sale changes how everyone shops. If you want to know whether a change to how you handle codes is worth it, test it on ordinary traffic. The only ordinary weeks left before Black Friday are the ones before your freeze.
What can you get done before the freeze?#
Here's a pre-freeze list that works whatever tools you use. Each step has a catch.
1. Ship everything that changes what loads. New scripts and tags, apps, and tag manager publishes all count as releases. In Google Tag Manager, preview mode only shows a tag to you; publishing the container is the release. If your site sends a Content Security Policy, any new tool's hosts have to be added to it in the same change. If you run a cookie banner, check how the new tool fits it. The catch: a tool you install in November is usually a tool you don't have until January.
2. Install any checkout pieces now. Some controls need an app, a plugin or a checkout integration before they can work. Install them before the freeze, even if you only switch them on for the sale. The catch: this is the step people leave for later, and later is inside the freeze.
3. Clean up your codes. List every live code. Expire the ones nobody should still be using. Give sale codes an end date, and set usage limits where they make sense; Shopify supports both on discount codes. Move email offers to unique or single-use codes, and give each influencer a named code of their own, as the guide to unique and shared discount codes sets out. The catch: a public sale code is meant to be shared, so none of this stops it reaching code sites. And switching off a code that has spread mid-sale also switches it off for the customers you gave it to.
4. Test every discount together. Build one cart that hits every discount you'll run during the sale, on mobile, and check what it actually costs you, including whether a code drops it below your free shipping threshold. Set each discount's combination rules on purpose. The catch: it only covers the discounts you know about, not the codes an extension finds for a shopper.
5. Measure while traffic is ordinary. Record how many sessions involve coupon extensions, how often codes are tried at checkout, and your discount rate on a normal week. If you're considering a change, test it now against a control group. The catch: doing this by hand from your analytics and order exports is slow, and most analytics tools don't tell you when an extension is present.
6. Turn your sale plans into dated settings. Anything you want to switch on for the sale and off afterwards should be scheduled now, in a tool already installed, so nothing needs a deploy during the freeze. The catch: only works for tools that support schedules.
7. Set up monitoring. Alerts on order volume, a scheduled test checkout, and someone watching which codes are being used. The catch: monitoring tells you something went wrong. You still need a way to act that doesn't require a release.
8. Agree who decides. Write down who can change what during the freeze, where changes are recorded, who hears about them, and what would make you switch something off. The catch: without this, the first hard decision on Black Friday becomes a meeting.
How does Benson fit a code freeze?#
Benson was built so that peak season is a settings job. On Shopify it's one app from the App Store, with no code to paste; on other platforms it's one tag, plus a checkout piece on some. After that, every pop-up rule, checkout rule and offer is a setting in Benson, so you can act during the freeze without a deploy. The code freeze playbook walks through it step by step.
Before the freeze. On Shopify, install the app and switch on its app embed in your theme editor while changes are still allowed; the same install lets the strict code policy work at checkout, and you switch it on later as a setting. Elsewhere, add the tag through your theme, Google Tag Manager or your developer; the install guides cover each platform. If you have a Content Security Policy or a cookie banner, the CSP notes and consent guide say what to add in the same change. If you want the strict code policy on another platform, install its checkout piece now: on WooCommerce it's the Benson plugin; on Magento and BigCommerce, follow the checkout guide.
In the ordinary weeks. Observe mode records which coupon extensions and AI agents show up in your sessions and what Benson would hide, without hiding anything. It's included on every plan, Free too. A few normal weeks give you a baseline to read the sale against. On Pro, put the rule you're considering behind a holdout in October, and decide before the freeze whether it stays on for peak.
Your sale, set up as dated settings. The peak season playbook covers this part:
- Mark your sale period, so Benson reads the sale against a sale baseline, not an ordinary week. Your storefront doesn't change.
- Open the readiness report. It checks your protection, compares the same moment last year and lists sale codes extension users could apply, so you can decide which stay public.
- Schedule a rule that hides extension pop-ups on your storefront only while the sale runs, then switches itself off.
- Make checkout rules strict (on Pro), so only the codes you allow work in extension sessions. Leaked and auto-tried codes are turned away with a friendly message.
- Put your sale offer in the widget (on Pro), so shoppers see your code first and don't go looking for another one.
During the freeze. Watch the live feed and change settings only when the numbers ask for it. If a code starts spreading where it shouldn't, mark it private and strict checkout rules stop it working in extension sessions. That's a setting, not a release. The leak guide has the first-hour steps for everything else. Observe mode is the undo for pop-up rules: Benson stops hiding anything and keeps recording what it would have hidden. Don't start a new holdout mid-sale; it would measure the sale, not the change.
After it. The moment recap shows extension share, excess discount and money protected against your baseline. Decide which rules stay on in January.
On Shopify, no app can change what an extension shows inside checkout, so Benson works in two places: it hides pop-ups on storefront pages (home, product, collection, search, cart and the cart drawer), and at checkout its protection is code-level. AI agents that never run JavaScript don't load any storefront script, so the codes they could find need eligibility rules of their own, as the agentic commerce guide sets out. The Shopify storefront and checkout guide explains the split.
If your developer or finance lead needs convincing, give them the short version: one tag before the freeze, settings after it, and a holdout behind every change that matters. Before your freeze date, install the Shopify app if you sell on Shopify, see Benson on your store if you don't, or start with the code freeze playbook.
Questions merchants ask
- When should our code freeze start?
- Advice in merchant forums ranges from two to six weeks before Black Friday, which is 27 November this year. Tracking changes may need to stop earlier, because a sale-day order can be credited to an ad click from weeks before. Ask whoever owns the freeze for the exact date and what it covers.
- Does a Benson setting count as a release during a freeze?
- Once the tag is live, pop-up rules, schedules, checkout rules and offers are settings in Benson, not code on your site, and they take effect without a deploy. Some teams still want sign-off for configuration changes, so agree who can change what before the freeze starts.
- Can we install Benson during the freeze?
- Installing means adding a tag or, on Shopify, switching on the app embed in your theme, which is a site change, so most freezes rule it out. If you missed the window, use observe mode from January to build a baseline for your next sale.
- Should we test a new rule during Black Friday?
- No. Sale traffic isn't ordinary traffic, so a test started in sale week measures the sale rather than your change. Test in the ordinary weeks before your freeze, or after the sale.
- What if a sale code leaks during the sale?
- Without a tool already in place, your options are to switch the code off, which also hits genuine customers, or to let it run. With Benson's checkout rules set to strict before the freeze, you can mark the code private and it stops working in extension sessions, as a setting rather than a release.
Sources#
- Google: Site Reliability Engineering, Introduction
- Adobe: US holiday shopping season to hit record $275.1 billion online (Sep 2026)
- Adobe: Holiday shopping season drove a record $257.8 billion online (Jan 2026)
- Shopify: Merchants generate record-breaking $14.6 billion in Black Friday Cyber Monday sales (Dec 2025)
- HUMAN Security: 2026 State of AI Traffic and Cyberthreat Benchmark Report
- Shopify Help Center: Discount codes
- Shopify Community: Your BFCM tracking freeze date is October 28
- Shopify Community: What's the one thing that broke in your store last BFCM?
- Shopify Community: Check your theme ASAP, BFCM disaster
- Shopify Community: Influencer promo codes on discount sharing sites
- Benson playbook: Before your code freeze
- Benson playbook: Peak season
- Benson: The BFCM playbook, free as a PDF
- Benson learn track: Peak season
- Benson guide: Your coupon control worked. How do you know?
- Benson guide: Coupon control on Shopify storefront and checkout
- Benson docs: Install
- Benson docs: Content Security Policy
- Benson docs: Consent and storage
- Benson guide: What agentic commerce does to your discount codes
- Benson guide: How to block Honey on your Shopify store
- Benson guide: What the Capital One Shopping extension does on your Shopify store
- Benson guide: Stopping discount code leaks
- Benson docs: Install on Shopify




