Shopify deprecated useBuyerJourneyIntercept and its dependent block_progress capability starting in API version 2026-07, in a changelog entry dated July 2, 2026. Both are scheduled for removal in a future API version. Shopify directs developers to move rule enforcement to cart and checkout validation Functions and discount code rejection to the Discount Function API. Stores running holiday promotions on unmigrated checkout extensions still need an inventory and a migration plan. A second change is landing now: Shopify has blocked bulk queries and mutations from public apps without an IP allowlist since November 12, 2026, and non-compliant public apps are delisted from new installs after November 20, 2026.
The checkout migration itself belongs to your developers and app vendors. Kopa works on the Google Ads side. It writes fact-checked search ads grounded in your live pages, monitors conversion tracking guardrails, and executes only the changes you approve. That covers the advertiser half of the job: making sure what your ads promise still matches what checkout enforces.
The checkout rule changes at a glance
| Update | Effective date | Default behavior | Risk for online stores | What to do |
|---|---|---|---|---|
| Buyer-journey interception deprecated | API 2026-07, entry dated Jul 2, 2026 | Deprecated, removal in a future API version | Promo rules enforced by checkout extensions may stop working | Inventory rules, plan migration to validation or Discount Functions |
| IP allowlist: bulk operations | Nov 12, 2026, already passed | Bulk queries and mutations blocked for non-compliant public apps | Bulk order or product syncs may fail now | Ask each vendor to confirm compliance |
| IP allowlist: all public apps | Nov 20, 2026 | Non-compliant apps delisted from new installs and flagged in Settings > Apps | New installs blocked mid-season | Confirm before adding or reinstalling apps |
| Checkout and Accounts Configuration API | API 2026-04, entry dated May 13, 2026 | Consolidates checkout and account branding and settings for Plus | Market branding can drift from localized offers | Check each market's checkout against its live ads |
Only the allowlist dates fall inside the holiday window. The deprecation has been on the books since July, so any extension that still depends on it is carrying your biggest promotions on a capability Shopify has already marked for removal.
- Interception deprecated
API 2026-07, removal in a future version
- Bulk operations blocked
Public apps without an IP allowlist
- Delisting begins
Non-compliant public apps lose new installs
- Admin API requests fail
Existing installs of non-compliant apps
- Your move
Inventory promo rules and app owners
1. Buyer-journey interception is deprecated
useBuyerJourneyIntercept is the checkout UI extension capability that lets an app step in while a buyer moves through checkout. Combined with block_progress, it lets the app stop the buyer from continuing when a condition fails. According to the 2026-07 release notes, both are deprecated and scheduled for removal in a future API version.
Shopify draws a specific line for the migration. Rule enforcement moves to a cart and checkout validation Function, and discount code rejection moves to the Discount Function API, which added support for rejecting discount codes with a custom message. The release notes do not give a removal date, so plan to migrate on your own schedule rather than Shopify's.
This is a quiet change from an advertiser's point of view. Nothing in your ads account will flag it. If a promotion's rules live in a checkout extension that depends on interception, you may not learn it stopped enforcing until margins, order counts, or customer complaints tell you.
2. Inventory the campaigns that depend on checkout rules
Start with your ads. Every live or scheduled holiday campaign that promises a condition is a candidate. Look for language about who qualifies, how much someone can buy, and which codes or products a discount excludes. Then trace each promise back to the system that enforces it.
Use this sequence:
- Export every active and scheduled promotion across Google, Meta, email, and affiliate placements.
- Mark each one that carries a condition: ad-specific offer eligibility, per-order purchase limits, discount code restrictions, or minimum cart rules.
- For each condition, name the enforcing system: native Shopify discount settings, a Shopify Function, or a third-party checkout app.
- Flag any rule enforced by a checkout extension that uses useBuyerJourneyIntercept or block_progress. If you are unsure, ask the app vendor directly.
- Rank flagged rules by revenue at risk during the holiday window.
The chart below is our editorial mapping of common promo mechanics to Shopify's two named paths. Use it to open the conversation with your developer, who should confirm the right path for each rule.
The right-hand column holds for every row. Whatever path a rule takes, the ad that advertises it needs a fresh check after the change.
3. Coordinate the migration with developers and app vendors
Most merchants do not own the code that enforces these rules. It sits in a custom extension built by an agency or freelancer, or in a public app. Either way, the deprecation creates a short list of questions for whoever owns that code.
Ask each owner for the following, in writing:
- Dependency: whether the extension uses useBuyerJourneyIntercept or block_progress today.
- Target path: whether each rule moves to a validation Function or, for discount code rejection, the Discount Function API.
- Timing: whether the move happens before or after your peak promotion dates.
- Behavior parity: whether the buyer sees the same messages and blocks after the migration.
- Test plan: how they will confirm the rule works on a test order before go-live.
Timing deserves careful thought. Changing checkout logic in the middle of a sale carries its own risk. For many stores, the safer plan is to freeze promo logic through the peak weekend, keep the current extension running while it is still supported, and schedule the migration for the first quiet window afterward. Make that choice on purpose, and write it down.
4. IP allowlisting enforcement is already underway
The second change affects a different set of apps. Shopify announced on November 5, 2026 that IP allowlisting is required for public apps, with enforcement in stages.
The first stage is already live. Since November 12, 2026, bulk queries and mutations from public apps without an allowlist are blocked. After November 20, non-compliant public apps are delisted from the App Store and flagged in Settings > Apps. Existing installs keep regular Admin API access until April 1, 2027.
For advertisers, the near-term risk sits in bulk syncs. If a marketing or attribution app you rely on uses bulk operations and has not added an allowlist, its bulk order or product syncs may already be failing. That can leave gaps in what reaches your ad platforms while sales continue, and bidding systems learn from whatever data they receive.
Add every app that touches orders, pixels, or product data to the same vendor list you built for the checkout migration. Ask each one to confirm allowlist compliance, and avoid installing a new app mid-season until you know it is compliant. Then compare conversion counts in each ad platform against Shopify orders daily through the holidays.
5. Plus merchants have a consolidated checkout configuration API
The 2026-04 release notes describe the Checkout and Accounts Configuration API, in an entry dated May 13, 2026. For Shopify Plus merchants, it brings checkout and account branding and settings together, including market-specific branding.
This is a useful change, and it also introduces a dependency. If your team runs localized promotions by market, checkout branding is easier to manage centrally, which also makes it easier to change several markets at once without noticing. When a checkout configuration change goes out, compare each market's checkout against the ads and offer pages that send traffic to it.
The check for each market: the buyer who clicks a localized ad should see the same offer, currency, and brand treatment all the way through checkout.
6. Keep ads, offer pages, and checkout in agreement through the holidays
Migrating the code is only half the work. The other half is confirming that every promoted offer still behaves at checkout the way the ad describes it. Run a short check on a fixed schedule from now through the end of the holiday period.
For each flagged promotion:
- Click the live ad and land on the page it points to.
- Build a cart that should qualify, and confirm the discount or eligibility applies.
- Build a cart that should not qualify, and confirm checkout blocks it or rejects the code as advertised.
- Test any purchase limit by exceeding it.
- Place a test order and confirm the conversion appears in each ad platform.
If a rule changes, update the ad the same day. A dedicated campaign offer page for each promotion makes this easier, because the terms live in one place that both the ad and the checkout test can reference. In Google Ads, Kopa can rewrite affected ads from your live pages and queue them for your approval, so the ad copy follows checkout behavior instead of an old brief.
What good looks like
- Every holiday promotion with a condition is listed alongside the system that enforces it.
- Each checkout extension that depends on useBuyerJourneyIntercept or block_progress has a named owner, a target replacement, and a migration date.
- Promo logic is frozen through peak weekends, and migrations are scheduled for quieter windows.
- Every app that touches orders or attribution has confirmed IP allowlist compliance, with bulk syncs checked now and full access secured before April 1, 2027.
- Ad platform conversions are reconciled against Shopify orders daily through the holidays.
- Plus merchants compare each market's checkout branding with its localized ads after any configuration change.
- Ads that state offer terms get updated the same day a checkout rule changes.
Get started for free at kopa.ai.
