Why coupon extensions still reach your Shopify checkout

Your blocker hides the pop-ups but not the codes extensions apply at checkout. Why Shopify's checkout works this way, and the control that works in each.

Author:Benson
Merchant controlsUpdated 6 October 20269 min read
Jump to a section

In short

Shopify's checkout is sandboxed, so scripts that hide coupon-extension pop-ups on your product and cart pages can't follow shoppers into checkout. Extensions run in the browser and still try codes there. You need two controls: hide pop-ups on the storefront, and at checkout use a discount function to decide which codes work in coupon-extension sessions.

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.

See which of your codes coupon extensions hold

You installed a coupon-extension blocker last spring. It worked, or seemed to: the pop-ups stopped appearing on your product pages, and the cart looked clean when you tested it.

Then the Monday after a creator campaign, you scroll through the weekend's orders. Dozens carry her code, the one you made for her followers. Most of those shoppers came from Google, your own emails or nowhere you can see. One order stacks her code with your welcome code. A support ticket asks why "the code on the coupon site" stopped working, and it turns out to be the one you gave to staff.

The blocker didn't fail on the pages it covers. It was never on the page that mattered. On Shopify, your storefront and your checkout are two different places, and each one needs its own control.

Why does a blocker work on product pages but not at checkout?#

Because Shopify doesn't let anyone's scripts into checkout any more, including yours.

For years, Shopify Plus stores could edit checkout.liquid and add their own code to checkout pages. That's where the first coupon-extension blockers lived. In February 2023 Shopify announced that checkout.liquid was being deprecated, and from 13 August 2024 those customisations stopped working on the information, shipping and payment pages. Checkout moved to Checkout Extensibility, where apps add approved blocks and functions instead of free-running scripts.

The sandbox is deliberate. Shopify's documentation says checkout UI extensions don't have access to the real checkout DOM and can't render arbitrary HTML. The pages after checkout followed: since 28 August 2025 the additional scripts box in checkout settings is view-only, and stores not on Plus had until 26 August 2026 to move their thank-you and order status pages over. Script tags, the older way apps added code, only ever reached the storefront and the order status page.

A coupon extension doesn't care about any of that. It runs in the shopper's browser, so it sees the discount box like any other page and types codes into it. Your scripts are locked out of checkout. The extension isn't.

This ended a generation of tools. Benson was one of them: it launched in 2022 and stopped extensions auto-trying codes at Shopify Plus checkouts. Then Shopify closed the checkout to scripts, Benson's checkout protection went with it, and the product stalled. Modern Retail reported in 2024 that another app, Vigilance, shut down after Shopify's checkout changes left it incompatible with the checkout [Modern Retail, May 2024] (opens the source).

What does a leaked code actually cost?#

Two things, often on the same order.

The first is the discount itself, given to a shopper who was already at your checkout with a full basket. The second is the commission. If the code belonged to a creator or affiliate, you may pay them for an order they didn't send. If an extension also claimed the last click, you may pay its affiliate network too. One founder told Modern Retail that leaked codes mean paying the influencer out on a sale they didn't refer, calling it "a double whammy hit on margins" [Modern Retail, May 2024] (opens the source).

The codes that travel furthest are the ones you'd least like to see in public. A December 2025 investigation reported by PPC Land alleges that Honey collected staff, VIP, influencer and newsletter codes as shoppers typed them, and published them for everyone, and that it told at least one brand it typically doesn't remove codes without a working relationship [PPC Land, Dec 2025] (opens the source).

Merchants have been describing this on Shopify's own forum since 2019.

The scale is why this isn't a niche problem.

13M

Chrome users still run PayPal Honey, one of several extensions that try codes at checkout.

Chrome Web Store, Oct 2026(opens the source)
How codes leak, how to find the ones that have, and how to contain them.

Why is it bigger than one creator's code?#

Because of when it happens and who it touches.

Peak season is built on codes. Adobe expects US holiday discounts to reach up to 30% off listed price during Cyber Week 2026 [Adobe Digital Insights, Sep 2026] (opens the source). A private code that leaks in October gets tried on every order in your busiest weeks, and on Shopify a shopper can combine up to five product or order codes on one order if your combination settings allow it.

Most codes are built to travel. Seguno, which sells unique-code tools for Shopify, looked at 65,055 newsletters from Shopify brands and found that when an email carried a code, it was far more likely to be a generic code anyone can reuse than a unique one.

Nearly 3 to 1

Generic codes outnumbered unique, one-per-person codes in Shopify brands' newsletters, May 2024 to May 2025.

Seguno, Aug 2025(opens the source)

And codes with an owner are a real share of what stores run. In Seguno's 2025 benchmark of 162,000 unique code sets, affiliate and influencer codes made up 15.11% and staff, friends and student codes 10.56% of identified use cases [Seguno, Aug 2025] (opens the source). Those brands issue them as unique codes for a reason: as one shared code, they're the ones that hurt most when they turn up somewhere else.

It isn't only your margin. Finance sees discount depth creep up with no campaign behind it. Your creators lose commission when their code is applied by a stranger's extension, or gain it on sales they never drove, and either way your attribution stops meaning much; which of the two happens depends on your creator code and link settings. Your support team fields complaints about codes you never offered.

What can you do with Shopify's own tools?#

Quite a lot, and every option has a catch.

  • Unique, single-use codes. A code that works once is worth little to a coupon site. The catch: generating them in bulk usually means an app or your email platform, and they don't suit a creator who reads one code out in a video, so match the code type to the channel.
  • Usage limits and one use per customer. Shopify lets you cap total uses and limit a code to one per customer. The catch: the first strangers to find a leaked code can still use it, and a total cap cuts off your real audience once the leak has used it up.
  • Customer eligibility. You can restrict a code to specific customers or segments. The catch: they have to be customers you already know.
  • Expiry dates and combination rules. Short windows limit how long a leak lasts, and turning off combinations stops stacking. The catch: both apply to everyone, including the people the code was for.
  • Deleting or rotating the code. It stops the leak today. The catch: the people you gave it to find it broken, and a replacement spreads the same way.
  • Takedown requests. You can ask code sites and extensions to remove your codes, and some will. The catch: it's one email per code per site, and the code still works for anyone who already has it.
  • A Shopify Function that rejects codes. Since December 2025, discount functions can reject entered codes with a message. This is the supported way to say no at checkout. The catch: you need an app, and only Plus stores can run custom apps that contain functions. On its own, a function sees the cart and the codes, not what's running in the shopper's browser, so it can't tell an extension's attempt from a loyal customer typing the code you sent them.

That last point is the gap. Shopify gives you the tools to refuse a code at checkout, but not the knowledge of when to.

How Benson handles each place#

Benson splits the job the way Shopify splits the store.

On the storefront, it hides the pop-ups. Benson's script runs on your home, product, collection, search and cart pages, and in the cart drawer. It recognises the coupon extensions in each session and hides their pop-ups by rule. Start in observe mode, which is free on every plan: it records what Benson would hide without hiding anything, so you can check a rule catches the extension and never your own offer. Switching to Block needs Pro.

Sample store
A coupon extension's pop-up hidden on a product page. Sample data.

At checkout, it controls which codes work. Benson can't change what an extension shows inside Shopify's checkout, and no app can. What it can do is work on the codes. When the storefront script sees a coupon extension, it notes that on the cart. At checkout, Benson's Shopify discount function reads the note, and when checkout rules are strict, only allowlisted codes work in coupon-extension sessions. Anything else gets a short message instead of a discount.

Sample store
Codes tried in coupon-extension sessions, and which ones your checkout rules allow. Sample data.

The allowlist is yours to set. Put your public welcome and loyalty codes on it, and any partner codes you pay for. Mark staff and apology codes as private, so they stay off it, and decide creator codes one by one. Because checkout rules only act in coupon-extension sessions, followers without an extension who type the creator's code themselves still get their discount. Code watch then follows each leaked code and shows whether it's contained, replaced, or its replacement is spreading too.

Every control can run against a holdout: a small share of extension sessions left unprotected, so the difference you see is measured on your own shoppers rather than estimated. The holdout guide explains how to read it.

Three things to set up around it:

  • Checkout rules are on Pro.
  • Checkout rules apply in coupon-extension sessions, so a shopper without an extension who copies a widely shared code from a coupon site can still use it. Retire or limit codes that have spread that far.
  • Benson reports on the sessions its script runs in, so put it on every page and check how your consent settings load it.
Observe, hide pop-ups, make checkout rules strict, then prove it with a holdout.

If you don't pay any coupon extension, the stop-paying playbook takes you through observe mode, Block, strict checkout rules and a holdout, in that order. If your problem right now is one code that's escaped, start with the leaked-codes playbook. Shopify merchants can install Benson from the Shopify App Store and see which extensions are in their sessions; other stores can see Benson on their store before they change anything.

Questions merchants ask

Can any app hide coupon extensions inside Shopify checkout?
No. Shopify checkout is sandboxed: apps add approved blocks and functions, and they can't reach the page itself or another extension's pop-up. Pop-ups can be hidden on storefront pages, and codes can be controlled at checkout through a discount function.
My old blocker used to work at checkout. What changed?
Shopify retired checkout.liquid. From August 2024, custom code stopped running on Shopify Plus checkout pages, and in August 2025 the additional scripts setting became view-only. Tools that relied on scripts in checkout lost that access.
Will strict checkout rules stop my real customers using their codes?
Only if they use a coupon extension and the code isn't on your allowlist. Put your public welcome, loyalty and partner codes on the allowlist before you make checkout rules strict. Shoppers without an extension aren't affected.
Should I delete a code that has leaked?
Not straight away. Deleting it breaks it for the people you made it for, and a replacement can spread the same way. Contain it in extension sessions first, then retire or limit it if it keeps spreading.
Do I need Shopify Plus?
Not for Benson's checkout rules. They run as a function inside the Benson Shopify app, a public app on the Shopify App Store, and Shopify lets stores on any plan use public apps that contain functions. Building your own code-rejecting function as a custom app does need Plus.

Sources#

Find out what's leaking. Free forever, no card.

Free forever up to 25,000 sessions a month. Every Pro feature free for your first 14 days. No card. We'll email you about getting started. Unsubscribe any time.