Shopify Checkout Extensibility & the End of checkout.liquid

If you got an email about upgrading your checkout, watched a customization stop working, or heard that checkout.liquid is dead, the honest first question isn't “how do I migrate?” It's which side of the line you're on. Shopify Plus stores and everyone else face different dates, different exposure, and different work. This guide separates the two clearly, then tells you what breaks, what replaces it, and what it costs — in merchant language, not developer docs.

Which Side of the Line Are You On?

Almost every confusing thing written about checkout extensibility comes from mixing up two audiences. Your plan decides your deadline, what you had to lose, and what you do next. Find your row first — the rest of this guide follows from it.

What Checkout Extensibility Is

The change is physical, not cosmetic. checkout.liquid was a layout file that lived inside your theme. You (or a developer) owned that code, and because it sat in the theme, a Shopify checkout update could quietly break it. Checkout extensibility flips that: customization now lives in apps and extensions that run in a Shopify-hosted sandbox, and Shopify updates the checkout around them.

Shopify frames the switch as a net gain for merchants, not just a deprecation:

checkout.liquid Was Always Plus-Only

Here is the detail most articles get wrong. checkout.liquid was only ever available to Shopify Plus stores. If you're on Basic, Grow, or Advanced, you never had it — so you aren't “migrating off checkout.liquid” at all. Your real exposure is different: it's the additional scripts field and any apps that inject script tags on your Thank you and Order status pages. Getting this straight saves you from chasing a file you never had.

One thing has shifted underneath that answer, and it is worth knowing before you rebuild rather than after. Shopify has deprecated script tags across the whole platform: on March 1, 2027 it will stop injecting script tags into storefronts. Under the same deprecation, from October 1, 2026 the Admin API stops accepting new and updated ScriptTags. That is a different deadline from yours — the tags on your Thank you and Order status pages are covered by the earlier deprecation this guide is about, and your own date is still the one in your row above. Where it bites is the rebuild: an app that replaces your customization with a storefront script tag is building on a mechanism with an expiry of its own, so what you want shipped instead is an app embed block in a theme app extension, or a web pixel if what you lost was analytics or conversion tracking.

The Deadlines, Precisely

Sources contradict each other because they blur these dates together. Here is the actual sequence, each event tied to an official Shopify page. The Plus dates came first and the non-Plus deadline followed on August 26, 2026, so the whole sequence is now behind us.

One deadline that does not belong on this timeline is the retirement of legacy customer accounts: Shopify deprecated them in February 2026 but has not announced a sunset date (as of July 2026), and that switch touches account pages, not checkout — our customer accounts migration guide handles it separately.

What Actually Broke

“Does it really stop functioning?” Yes — for the in-checkout steps, checkout.liquid has been unsupported since August 2024, full stop. On the Thank you and Order status pages the failure is quieter, but it is just as real.

Analytics & Pixels: The Silent Gap

If ads and analytics drive your store, this is the part that hurts. Tracking scripts that lived in additional scripts break the moment a shopper enters the new checkout — middle-funnel events like begin_checkout and add_payment_info disappear, and after Shopify stopped passing personal data (email, phone, name) to legacy scripts, platforms like Meta can no longer match conversions.

One analytics team that audits these migrations reports that the gap between Shopify's order counts and ad-platform conversions can hit 30% or higher, and estimates high-volume stores lose 15% to 20% of revenue into that reporting gap. Treat those as one team's findings, not an industry benchmark — but the direction is clear: silent tracking loss is expensive.

The fix is to rebuild tracking on the Web Pixels API and customer events, the sandboxed channel Shopify provides in place of additional scripts. For the full playbook on wiring up GTM, GA4, and ad pixels the new way, see our guide to Google Tag Manager on Shopify.

The New Stack: What Replaces What

The replacement isn't one thing; it's a small toolkit, and each piece has its own job. These five cover everything checkout.liquid used to do. Branding — colors, fonts, and logos — is handled inside the Checkout Editor, not as a separate product. Whether you can remove Shopify's own branding from checkout is a separate question. For the post-purchase piece specifically, the buy-vs-build economics live in our post-purchase upsell apps-vs-custom guide.

Who Gets What: The Plus Line

The single question that decides most of this is your plan. Shopify opened UI extensions and web pixels on the Thank you and Order status pages to Basic, Shopify, and Advanced plans on May 21, 2024, but the three in-checkout steps stayed Plus-only. If you're on Basic, Grow, or Advanced, more checkout customization is open to you than the deadline noise suggests — the gate is only on those three in-checkout steps. Here is the full map.

Thank You & Order Status

The Thank you and Order status pages are the surface non-Plus stores had to migrate. They're available on every plan except Shopify Starter, they carried the August 26, 2026 deadline, and extensions on them can read metafields but not write them. This is where most non-Plus customization — order tracking widgets, cross- sells, review prompts — actually lived, through apps and additional scripts.

What the New Checkout Can't Do

The trade-off for upgrade-safe checkout is a set of hard boundaries. These aren't opinions or best practices; they're platform limits a developer will hit no matter how good they are. If a vendor promises you something past these lines, be skeptical.

The tightest one to plan around: a compiled extension bundle can't exceed 64 KB, which rules out heavy, do-everything widgets.

What It Costs & Who Does It

There's no official price list for this, and honest cost data is thin. The figures below come from individual agencies, not a survey — useful for orientation, not for setting a budget in stone. What's reliable is the shape of the choice: no-code, custom, or nothing.

Cost and time figures are one agency's published estimates (Speedboostr; senior developer rates of $150–$300/hour per WeArePresta), not a market benchmark. App prices observed July 2026.

For scale, one migration guide estimates the no-code Checkout Editor covers about 80% of former checkout.liquid use cases, and that a developer needs about 2–3 days to rebuild a typical customization as a UI extension. That's one source's number, but it points the right way: most stores don't need a five-figure project. Custom checkout extensions are a form of custom Shopify development, so budget them like any scoped build.

If you take the app-level route, these are common checkout apps and their observed starting prices. Confirm the current tiers on each listing before installing.

Source: Shopify App Store listings (observed July 2026). Prices and tiers change — confirm on each listing.

Not sure which specialist or budget fits your situation? Our Shopify development guide routes you to the right path — app, freelancer, or agency — in about a minute.

Which Route Is Yours?

You've seen the stack, the limits, and the cost of each path. Answer five quick questions about your plan, your checkout, and what you want it to do — and get the route that fits, from “you're probably fine” to “you'll need a developer.”

Your Migration Checklist

Whichever route the quiz gave you, steps 1–3 are the same. The split is at steps 4 and 5: the app-level route stays inside the Checkout Editor, while the custom-development route runs through a dev store and the Shopify CLI. Steps 6 and 7 apply to everyone. Tick each off as you go — your progress saves on this device.

The Bottom Line

There is no single “checkout migration” that applies to everyone. Your plan sets your deadline and your exposure; your customizations set how much work is ahead. Get those two facts straight and the path is obvious — miss them and you'll either panic early or get caught late.

Frequently Asked Questions