Shopify's checkout extensibility deadline for non-Plus stores lands on August 26, 2026, and it is a hard one. If you run a Basic, Shopify or Advanced plan store, that is the date your Thank you and Order status pages get auto-upgraded whether the store is ready or not. Anything still living in checkout.liquid or the Additional Scripts box, your Google Ads conversion tag, your Meta pixel, your GTM container, stops running the moment the upgrade fires. There is no storefront error and no warning banner for shoppers. The tracking simply goes quiet, and the first sign is usually a gap in your conversion data the week after.
What changes on August 26, 2026
Non-Plus stores that have not upgraded by August 26, 2026 will have their Thank you and Order status pages auto-upgraded to the new checkout, and any legacy customization on those pages is dropped in the process. Shopify's own guidance is explicit that if you do not upgrade the pages before that date, they get upgraded for you, per the non-Plus upgrade guide. The Additional Scripts section already became view-only for merchants on August 28, 2025, so the editing window on the old surface has been closed for almost a year. August 26 is the point where the code stops executing, not just the point where you can no longer touch it. For a premium store, the risk is not the storefront breaking visibly. It is the invisible failure of the marketing and analytics stack that sits in those scripts.
checkout.liquid vs checkout extensibility: what replaces what
Checkout extensibility replaces the old code-in-theme model with a set of managed surfaces rather than a single Liquid file. Design and functionality move to Checkout UI extensions and app blocks, tracking moves to Web Pixels and app pixels, custom logic moves to Shopify Functions, and layout is edited through the Checkout Editor, per Shopify's upgrade documentation. The trade is the same one Shopify keeps making across the platform. You give up direct control of a high-risk surface and gain a sandboxed, upgrade-safe one that Shopify secures and maintains. For most merchants that is the right call, because checkout was the single most fragile place to be hand-editing Liquid and injecting third-party scripts, and a broken checkout costs revenue by the hour. The cost lands on stores with genuinely custom checkout logic, since a bespoke discount rule or a hand-rolled tracking snippet has to be rebuilt as a Function or a pixel rather than copied across. That rebuild is real work, and it is why the August date matters more than it looks.
Plus vs non-Plus: two deadlines, same direction
Plus stores already passed their checkout.liquid cutoff on August 28, 2025, and non-Plus stores get one extra year to August 26, 2026, but both land in the same place. The staggering is a runway, not a reprieve. Shopify has been pulling checkout out of merchant-owned code for two years, and this deadline closes the last editable door for the smaller plans. It also sits alongside a related cutoff we covered when Shopify Scripts reached end of life on June 30, 2026, which already forced discount and shipping logic off the Script Editor and onto Shopify Functions. Read together, the two dates mean a non-Plus store that has done nothing since spring is now running deprecated discount logic and about to lose its checkout tracking in the same quarter. The direction is consistent and it is not reversing, so treating August 26 as a one-off chore misreads it. It is the second half of a migration that started in June.
What we would change this quarter
Audit the Additional Scripts box today, list every tag in it, and rebuild each one as a Web Pixel or an app before the forced upgrade instead of after. Three concrete moves follow. First, inventory what is actually in checkout.liquid and Additional Scripts, because most teams do not have that written down and the auto-upgrade will not ask before removing it. The usual suspects are Google Ads conversion tracking, Meta pixel purchase events and a GTM container, and each needs a home in Web Pixels or a server-side setup. Second, move conversion tracking to Web Pixels or the Customer Events API now, so you have a clean week of overlapping data to confirm the new tags fire before the old ones die, rather than discovering a reporting hole in September. Third, run the upgrade in preview and click through a real order before August 26, since the forced upgrade gives you no rehearsal. We fold this into our Shopify Plus and storefront work, and we treat the tracking rebuild as an analytics and automation task rather than a theme edit, because that is where the data integrity actually lives. Deferring is the expensive option. A store that lets the auto-upgrade fire is not saving time, it is trading a planned migration for an unplanned data outage on its highest-intent page.