Key Insights in 60 Seconds
Two different deadlines, two different stories. Skim the highlights, then find the section that matches your plan and your checkout.
What You'll Learn
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.
Find Your Row Before You Do Anything
| You are on… | Had checkout.liquid? | Deadline (Thank you / Order status) | Status as of July 2026 | Your move |
|---|---|---|---|---|
| Shopify Plus | Yes — it was a Plus-only file | August 28, 2025 | Passed. Automatic upgrades began January 2026; customizations were lost. | Assess the damage and rebuild with apps or extensions |
| Basic, Grow, or Advanced | No — never had access | August 26, 2026 | Still ahead. Additional scripts and script-tag apps keep working until then. | Replace them before the date, not after |
| No checkout customization | n/a | Auto-upgrade only | You are likely fine either way. | Confirm status in the admin and move on |
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.
checkout.liquid vs Checkout Extensibility
| checkout.liquid (legacy) | Checkout extensibility | |
|---|---|---|
| Where the code lives | A layout file inside your theme | Apps and extensions in a Shopify-hosted sandbox |
| Who maintains it | You — it can break on checkout updates | Shopify updates the checkout around your extensions |
| Upgrade-safe | No | Yes |
| Who could use it | Shopify Plus only | All plans (in-checkout steps still need Plus) |
Shopify frames the switch as a net gain for merchants, not just a deprecation:
an easier way to customize Shopify Checkout in a way that's app-based, upgrade-safe, higher-converting, and integrated with Shop Pay
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.
The term you search for — checkout.liquid — is a legacy, Plus-only concept. Shopify's current wording is checkout extensibility and checkout UI extensions. Checkout also deliberately sits outside the theme layer: it isn't part of Online Store 2.0 architecture, which is exactly why theme updates can't reach it and why it needed its own system.
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. Notice how the Plus dates are behind us while the non-Plus date is still ahead as of July 2026.
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.
On a legacy checkout, the additional scripts field goes read-only, and at the deadline every script in it simply stops. As one agency describes it, “every script in that field stops firing. No warning popup, no gradual sunset.”
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.
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.
Checkout Customization by Plan
| Surface / tool | What it does | Plan needed |
|---|---|---|
| UI extensions — Information, Shipping, Payment | Customize the three in-checkout steps | Shopify Plus only |
| UI extensions — Thank you & Order status | Customize the post-checkout pages | All plans except Shopify Starter |
| Web pixels | Track customer events for analytics and ads | All plans (opened to non-Plus on May 21, 2024) |
| App Store Functions apps | Discount, shipping, payment, and validation logic from an installed app | All plans |
| Custom Functions (your own app) | Custom back-end checkout logic you build | Shopify Plus only |
Thank You & Order Status
The Thank you and Order status pages are the surface non-Plus stores are migrating right now. They're available on every plan except Shopify Starter, they carry 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.
Three Ways to Migrate
| Path | What it is | Rough cost | Typical time |
|---|---|---|---|
| No-code / app | Rebuild in the Checkout Editor plus one app; covers most legacy tweaks | App subscription — many free tiers; paid from about $29–$99/month | Days |
| Custom development | A developer builds a checkout UI extension or a Function | $5,000–$10,000 simple; complex builds can exceed $50,000 (one agency) | 2–4 weeks simple; 8–16 weeks complex (one agency) |
| Drop the customization | Accept the standard checkout and the automatic upgrade | No spend | None |
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.
Checkout Customization Apps
| App | Starting price (observed) | Notable for |
|---|---|---|
| Shopify Checkout Blocks | Free | Add content, fields, and upsells in the Checkout Editor |
| Checkout Upsell & Rules — MT | Free; $40/mo Enterprise | Upsells and conditional checkout rules |
| Qikify Checkout Customizer | Free; $99/mo Premium | Broad checkout and Thank-you customization |
| Checkout Customizer Ninja | From $49/mo | Blocks and content editing without code |
| Checkout Boost: Rules & Upsell | Free; from $29/mo | Checkout rules and upsell offers |
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.
Migrate Your Checkout Off the Legacy Setup
A shared path for both routes: confirm your status, inventory what you have, rebuild in a safe draft, test, restore tracking, and publish.
Open Settings, then Checkout, then Configurations, and run the upgrade report to see whether your store is still on the legacy setup.
Before you tick this off
- Opened Settings, then Checkout, then Configurations
- Ran the upgrade report
- Noted whether an 'upgrade by August 26, 2026' banner appears
List every customization: custom fields, banners, shipping or discount logic, additional scripts, and any apps that use script tags.
Before you tick this off
- Listed all checkout and Thank-you customizations
- Found every tracking script in the additional scripts field
- Flagged apps that rely on script tags
Decide whether your needs fit the no-code app-level route or require a developer to build a custom extension.
Before you tick this off
- Matched your needs to the app-level or custom-development route
- Confirmed which parts need a Shopify Plus plan
- Set a target date ahead of your deadline
App-level: assemble the change in a draft configuration with a Checkout Editor app. Custom: a developer builds and previews the extension on a dev store with the Shopify CLI.
Before you tick this off
- Created a draft configuration or a dev-store preview
- Added the app or extension without touching live traffic
- Left the current active configuration untouched
Test in the simulated checkout environment and, for custom extensions, across every placement and against Shop Pay in test mode.
Before you tick this off
- Tested in the simulated checkout (no real orders placed)
- Checked every placement the extension uses
- Ran a guest test order against Shop Pay in test mode
Re-implement GTM, Meta, and Klaviyo tracking through the Web Pixels API and customer events so checkout conversions report again.
Before you tick this off
- Moved tracking to Web Pixels and customer events
- Confirmed checkout and purchase events fire
- Compared order counts against ad-platform conversions
Publish the draft to replace your active configuration, then re-run the upgrade report to confirm the legacy banner is gone.
Before you tick this off
- Published the draft configuration
- Re-ran the upgrade report
- Confirmed the upgrade banner no longer appears
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
Front-end developer specializing in Shopify since 2017. Experienced in building custom Liquid themes, optimizing storefront performance, and integrating third-party apps. Writes in-depth, data-driven e-commerce guides based on hands-on experience with real merchant stores.
What to Read Next
Shopify Enterprise: What It Means, When Plus Earns Its Place, and Where It Loses
An honest enterprise decision guide for Shopify — what Plus actually unlocks, how it stacks up against Adobe Commerce and SFCC, true 3-year TCO, headless realities, replatform timelines and the merchant profiles where Plus wins or loses.
Read articleShopify Horizon Theme: Should You Migrate from Dawn?
Is Shopify's Horizon theme worth migrating to from Dawn? What changed, what breaks, migration costs, customization limits, and when Dawn is still fine.
Read articleShopify Development: Costs, Hiring & Where to Start
Who to hire for a Shopify store, what development costs, and where to start — a fast guide that routes you to the right specialist and budget.
Read article