Shopify Checkout Extensibility 2026 — What you need to know in 15 seconds

• Deadline passed: August 28, 2025. The legacy checkout.liquid system is deprecated.

• What's broken right now (April 2026): Pixels and analytics on Thank You and Order Status pages, Additional Scripts you haven't migrated, and all checkout.liquid customizations.

• Auto-upgrades rolling since January 2026: Shopify has been migrating stores without opt-in. Your store may already be on the new system.

• Who needs to act: Every Plus store not confirmed on Checkout Extensibility. Every store with non-migrated Scripts. Every store with custom pixels on post-purchase pages.

• Scripts deadline is 62 days away: Shopify Scripts are discontinued June 30, 2026. If you haven't started that migration, it's your most urgent open item right now.

Shopify checkout extensibility has been breaking merchant tracking since August 2025 — quietly, invisibly, and at a cost that looks like underperforming ads until you dig into the Events Manager. It's April 2026 and this is still the most common undiagnosed revenue problem on Plus stores.

Your GA4 is showing a ROAS that makes no sense. Campaigns you haven't touched are converting at a fraction of what they were a year ago. The agency says the creative is fine. Nothing changed in the account. The budget is identical.

Here's what happened: the migration was sitting in your backlog, the August 2025 deadline passed, and at some point Shopify auto-upgraded your store. Your pixels still fire — but without PII, your ad platforms can't attribute the conversion to anyone.

A DTC apparel brand running mid-seven-figures saw Facebook ROAS drop from 4.2x to under 1x in a single quarter. Ads hadn't changed. Tracking had. Three weeks after completing their migration, ROAS was back above 3x.

This guide covers the full picture: what broke after the August 2025 deadline, how auto-upgrades work, the exact migration steps, and what's still ahead with the June 30, 2026 Scripts sunset.

The Checkout Extensibility Timeline (The Short Version)

Shopify's checkout extensibility rollout happened in two completed stages, with one live deadline — Shopify Scripts — still 62 days out. Here's every milestone that matters for a Plus store in April 2026:

The August 2025 deadline is what broke tracking for most stores. The June 30, 2026 Scripts deadline is the one that will break discount and shipping logic for any Plus store still running Script-based rules — and with 62 days left, it needs your attention now.

What Changed After the August 2025 Deadline

Three things broke or locked the moment the August 2025 deadline hit, and all three affect revenue either directly or through reporting.

Your Additional Scripts field locked. Open Settings → Checkout. On a legacy checkout, the Additional Scripts field is visible but read-only. Whatever pixels and scripts were there when the deadline hit are frozen — you can see them, you can't touch them.

PII was cut from legacy tracking. Shopify stopped passing personally identifiable information (email, phone, name, address) to tracking scripts on legacy Thank You and Order Status pages. Your pixels still fire on checkout_completed — but without PII, ad platforms can't match the conversion to a user. Meta CAPI can't attribute it. GA4 logs it as an anonymous session. The conversion happened; the attribution evaporates.

checkout.liquid customizations stopped working. Any visual changes built in checkout.liquid — brand elements, custom progress indicators, upsell blocks — are stranded. If Shopify's auto-upgrade already hit your store, your checkout may already look generic.

Shopify Thank You Page Auto Upgrades (January 2026)

Since January 2026, Shopify has been automatically migrating stores still on legacy checkout to Checkout Extensibility — with notification, but without opt-out. You receive an email with a scheduled window. You can't block it.

The auto-upgrade is a "best effort" migration. Official Shopify channel app integrations carry over. Custom pixels, GTM containers, and checkout.liquid logic don't.

What auto-upgrade handles:

• Switching Thank You and Order Status pages to the extensibility system

• Migrating official Shopify app integrations that support the new system

• Enabling the Checkout Editor for your store

What auto-upgrade does not handle:

• Custom pixel logic — rebuild this in Settings → Customer Events

• GTM containers — incompatible with the new sandbox

• Visual customizations from checkout.liquid

• Third-party scripts that relied on direct DOM access

Note: After the auto-upgrade, PII comes back. Your checkout_completed pixel events include customer email, phone, and address again — passed through the Web Pixel API. The goal is getting there without a data gap in between.

Why Broken Tracking Is Costing You Money

Broken checkout tracking doesn't just produce bad numbers — it makes every downstream decision wrong. Budget allocation, creative testing, audience targeting, LTV modeling: all of it runs on conversion data. When pixels can't attribute conversions, your ad platforms optimize toward the wrong signals.

On a $50k/month ad budget, a 30-day tracking gap isn't an analytics inconvenience — it's a real cash problem. The dangerous part is how invisible it is: the campaigns still run, the spend keeps going, and the only signal that something is wrong is ROAS numbers that don't match reality.

How to Migrate to Checkout Extensibility (Step by Step)

The migration takes 1 day to 1 week depending on how many custom pixels and scripts you're running. This sequence keeps your data clean throughout:

1. Check your status. Settings → Checkout. "Upgrade" button = legacy. Checkout Editor visible = already migrated.

2. Document your Additional Scripts field first. Copy everything to a text file — every pixel ID, every GTM container ID, every custom script. This is your migration inventory. Do this before touching anything.

3. Install official channel apps. Google Analytics → Google & YouTube app. Meta Pixel → Facebook & Instagram app. These replace Additional Scripts with native integrations that restore PII passing immediately.

4. Rebuild remaining pixels as Custom Pixels. Settings → Customer Events → Add custom pixel. The Web Pixel API gives you checkout_completed, payment_info_submitted, and other standard events. Use this for any platform without an official Shopify app.

5. Rebuild visual customizations in the Checkout Editor. Online Store → Checkout. Drag-and-drop blocks, brand colors, logo, typography. For most Plus stores this covers 80% of what checkout.liquid handled visually.

6. Execute the upgrade. Settings → Checkout → Upgrade. Your tracking is already rebuilt — no data gap.

7. Run a test transaction. Verify checkout_completed fires with PII in every pixel dashboard. Check GA4 and Meta Events Manager before calling it done.

Tip: Do the migration mid-week, never Friday. If something breaks, you want the team available to fix it the same day.

Google Tag Manager and Checkout Extensibility

Standard GTM containers don't work inside the Checkout Extensibility environment. The new checkout runs in a sandboxed iframe that blocks the DOM access GTM relies on — custom HTML tags, visibility triggers, and dataLayer pushes from checkout.liquid scripts all fail silently.

Alternatives:

• Google & YouTube app — the direct path for GA4 and Google Ads, no GTM required

• Server-side tag management — Elevar, Analyzify, or Stape route checkout events server-side, bypassing the sandbox entirely

• Custom pixels — rebuild key GTM triggers using the Web Pixel API in Settings → Customer Events

Server-side is the most involved option but delivers better attribution across the full funnel, not just checkout.

What Replaces Additional Scripts, GTM, and Custom Code

Checkout Branding and Customization After Migration

The Checkout Editor covers most of what checkout.liquid provided visually — without code. The common objection to migrating is "we'll lose our custom checkout look," which was fair 18 months ago. In April 2026, the Checkout Editor handles the majority of standard Plus brand requirements natively.

What you control without touching code:

• Logo, favicon, brand colors across all checkout steps

• Typography (font family, sizes, weights) for headings and body

• Background colors and images for the checkout container

• Custom content blocks — text, banners, and app-powered UI between native checkout sections

• Thank You page confirmation messages and upsell blocks

What still requires a Checkout UI Extension (developer work):

• Custom input fields tied to your own backend

• Complex conditional logic based on cart contents

• Deep third-party integrations mid-checkout

For most Plus stores, the Checkout Editor covers 80% of the checkout.liquid use cases. The remaining 20% that needs an extension typically takes a developer 2-3 days.

Shopify Markets and International Checkout

Merchants running Shopify Markets need to test their migration market-by-market. The new system handles internationalization natively, but market-specific pixel configurations and compliance requirements need to be verified separately for each active region.

Key things to check for Markets merchants:

• Address validation works correctly across regions, especially EU formats

• Region-specific pixel tracking fires correctly per market currency and language

• GDPR consent flows and VAT display still function after migration

• Any market-specific discount logic running in Shopify Scripts is documented for migration to Functions before June 30

Shopify Scripts vs. Checkout Extensibility — Two Separate Deadlines

Shopify Scripts and Checkout Extensibility are separate deprecation tracks with separate deadlines — and confusing them is the most expensive planning mistake a Plus store can make right now.

Checkout Extensibility replaced checkout.liquid. Deadline: August 28, 2025 — already passed. Shopify is actively auto-upgrading stores that haven't moved.

Shopify Scripts replaced the Ruby serverless runtime for custom discount logic, shipping rates, and cart transformation. Deadline: June 30, 2026 — 62 days from now.

If your store uses Scripts for discount combinations, tiered shipping, B2B pricing, or bundle logic — that logic stops working entirely on July 1, 2026. The migration path is Shopify Functions: JavaScript or Rust, packaged as an app. A complex Scripts setup takes 4-8 weeks to migrate.

Warning: 62 days is enough time to complete a Scripts migration if you start this week. It is not enough time if you start in June.

For the full technical walkthrough, see our Shopify Scripts to Functions migration guide.

Post-Purchase Order Editing After Migration

Completing your Checkout Extensibility migration clears the path for cleaner post-purchase experiences on the Thank You page. Before migration, checkout.liquid scripts and order confirmation logic were often tangled with post-purchase workflows in ways that made adding new functionality fragile.

On the new system, Thank You page apps use Checkout UI Extensions — meaning they integrate without conflicting with your tracking setup. Since this is the Revize blog: Revize is fully compatible with Checkout Extensibility. Several merchants have shared that completing the migration was the trigger that finally made them add self-service order editing — because the Thank You page was clean enough to build on without risking their tracking.

For more on what changes to order management after migration, see the Shopify Order Management Guide 2026.

The Bottom Line

Shopify checkout extensibility migration is not optional and not future-tense. The August 2025 deadline passed eight months ago. Auto-upgrades have been running since January 2026. The question now is whether you're on the new system with clean tracking, or still waiting while Shopify queues your store.

For merchants: check Settings → Checkout today. If you're on legacy, document your Additional Scripts field and install official channel apps before Shopify sets your upgrade window.

For developers and agencies: the live deadline is Shopify Scripts on June 30, 2026. That's the harder migration — 4-8 weeks for complex setups. If you have clients still running Script-based discount or shipping logic, that conversation needed to happen last month.

After migration, your checkout tracking will be better than it was before: PII passes natively, CAPI attribution improves, and your pixels get first-party data they couldn't access reliably on legacy checkout.liquid.

Here's what to do this week:

1. Settings → Checkout → confirm your status

2. If legacy: document Additional Scripts, install Google & YouTube and Facebook & Instagram apps, then upgrade

3. If already migrated: verify PII is passing in Meta Events Manager and GA4

4. If running Shopify Scripts: start the Functions migration now — June 30 is 62 days out

Frequently Asked Questions

How do I know if my store is still on legacy checkout?

Go to Settings → Checkout — if you see an "Upgrade" button or a scheduled-upgrade banner, you're still on legacy. If the Checkout Editor is visible with drag-and-drop sections, you've already been migrated. Shopify sends email notifications before auto-upgrades, so check your admin notification history if you're unsure.

Why did my Facebook ROAS and GA4 conversions drop after August 2025?

The August 2025 deadline caused Shopify to stop passing PII to tracking scripts on legacy Thank You pages, so pixels fire but ad platforms can't attribute the conversion. Without email or phone, Meta CAPI can't match checkout_completed to a user profile. GA4 logs it as an unidentified session. The purchase happened — the credit evaporates. After migration, PII passes again and attribution recovers.

What does Shopify's auto-upgrade actually do to my store?

Shopify's auto-upgrade switches your Thank You and Order Status pages to the extensibility system and migrates official app integrations — but it can't reconstruct custom pixels, GTM, or checkout.liquid logic. Those need to be rebuilt manually in Customer Events and the Checkout Editor. You receive an email before your scheduled window, but there's no opt-out. This is why migrating manually, on your schedule, is always the better path.

Can I roll back after an auto-upgrade?

No — there is no rollback option once Shopify completes an auto-upgrade. If your tracking breaks post-upgrade, you fix it by rebuilding pixels in Customer Events — you don't revert. This is the core argument for migrating yourself before Shopify sets the window: you control the timing and can test everything before going live.

Does Google Tag Manager work with Checkout Extensibility?

Standard GTM containers don't work inside the new checkout sandbox. The sandboxed iframe blocks DOM access, so custom HTML tags, visibility triggers, and checkout.liquid-injected dataLayer pushes all fail silently. Use the Google & YouTube app for GA4 and Google Ads, or a server-side platform (Elevar, Analyzify, Stape) if you need full GTM replacement.

How long does the migration take?

Most Plus stores complete the Checkout Extensibility migration in 1-5 business days. A store with 2-3 pixels using official apps can finish in a few hours. Heavy GTM customization and complex checkout.liquid UI changes push it toward a week. The Shopify Scripts migration to Functions is a separate track and takes 4-8 weeks for complex setups.

What is the Web Pixel API?

The Web Pixel API is Shopify's sandboxed environment for running tracking and analytics code on checkout and post-purchase pages. Unlike Additional Scripts — which ran arbitrary JavaScript directly in the page — Web Pixels run in an isolated iframe with access to standard Shopify events (checkout_completed, payment_info_submitted, etc.) but restricted DOM access. PII is passed through the API explicitly rather than scraped. Configure custom pixels at Settings → Customer Events.

Is Checkout Extensibility available on all Shopify plans?

Checkout extensibility for the core checkout flow is Plus-only. Standard plan merchants never had access to checkout.liquid, so the migration doesn't apply to them in the same way. Thank You and Order Status page extensibility is available on all plans, though the Checkout Editor for the core checkout steps remains Plus-exclusive.

What's the difference between Shopify Scripts and Checkout Extensibility?

They're separate systems on separate deprecation timelines that many Plus stores need to handle as two distinct projects. Checkout Extensibility replaced checkout.liquid — the visual and script layer on checkout pages. Shopify Scripts replaced the Ruby runtime for discount, shipping, and cart logic. Checkout Extensibility deadline: August 28, 2025 (passed). Scripts deadline: June 30, 2026 (62 days out).

What replaces Shopify Scripts after June 30?

Shopify Functions is the direct replacement. Functions run in a WebAssembly sandbox and cover the same use cases — custom discounts, shipping rates, cart transformation — using JavaScript or Rust instead of Ruby. They're deployed as apps rather than scripts entered in the admin. Full documentation and migration guides are at shopify.dev/docs/apps/build/functions.

After migration, will my post-purchase apps still work?

Apps built on Checkout UI Extensions work correctly on the new system. Apps that injected scripts through checkout.liquid or Additional Scripts need to update to the extension model. Check your app's changelog or support documentation for compatibility status before migrating — most major post-purchase apps have published their compatibility status publicly.

Related Articles

Once your Shopify checkout extensibility migration is complete, these are the natural next steps:

• How to Migrate Shopify Scripts to Functions: The Complete Code Tutorial — the June 30 deadline is your next migration after this one

• Shopify Order Management: The Complete 2026 Guide — what changes to order workflows after checkout migration

• How to Let Customers Cancel Orders on Shopify — self-service options on the new Thank You page

• The Universal Commerce Protocol (UCP) — the broader platform shift this migration is part of

• Advanced Shopify Flow Workflows — automation that works cleanly alongside Shopify checkout extensibility and the new system