Shopify's August 26 Deadline Breaks Your Tracking, Not Your Checkout

The Shopify checkout deadline in 2026 falls on 26 August, when Shopify sunsets script tags on the Thank you and Order status pages for every non-Plus store and auto-upgrades those that have not moved. JustMarket.Me's read: your checkout keeps working, so the danger is conversion tracking that fails silently, not visibly.

That distinction is the whole story. Most coverage of this deadline warns that your checkout will break. It will not. Shopify upgrades the pages for you, they load, and customers keep buying. What stops is the custom code pasted into those pages years ago, and nothing in your admin will announce it.

The short version:

• 26 August 2026 is the sunset date for script tags on Thank you and Order status pages for non-Plus stores, per Shopify's developer documentation.
• Stores that have not upgraded by then are auto-upgraded by Shopify, and their customisations go with them.
• The Additional scripts box has been view-only since 28 August 2025, so you may already be looking at code you cannot edit.
• Conversion tracking, affiliate tags and post-purchase messaging usually live in those boxes.
• The replacement, custom pixels, runs in a restricted sandbox that Shopify itself says does not support all pixel functionality.

Table of Contents

What actually changed on Shopify's checkout?

Shopify is retiring the last of its legacy checkout customisation on 26 August 2026 for stores on the Basic, Shopify and Advanced plans. The change ends a three-year migration to a framework Shopify calls checkout extensibility.

Shopify's developer documentation is unambiguous. Its checkout.liquid reference page states that script tags "were sunset on those pages on August 28, 2025 for Plus stores, and are sunset for non-Plus stores on August 26, 2026". "Those pages" means the Thank you page and the Order status page, the two screens a customer sees straight after paying.

The Additional scripts field went view-only for everyone on 28 August 2025. Shopify's upgrade guide for non-Plus stores confirms merchants "can no longer manually edit scripts" there. You have been able to read that box for the past year but not change it. August 2026 is when its contents stop executing.

Who does the August 26 deadline actually hit?

The August 26 deadline hits every store on a non-Plus plan, which means Basic, Shopify and Advanced, regardless of revenue or store size. Shopify Plus merchants passed their equivalent deadline on 28 August 2025, and Shopify's Plus checkout upgrade guide notes that Shopify began auto-upgrading lagging Plus stores in January 2026 with 30 days of email notice.

One group deserves a specific warning. Shopify's upgrade guide states that stores on the Pause and Build plan are upgraded automatically, and that this "can't be reverted even after unpausing your store". If you paused a seasonal store, you may come back to a store whose post-purchase page has already been rewritten for you.

This is a live-store problem, not a new-build one. If you are still choosing a platform, our comparison of Shopify versus WooCommerce for small businesses matters more than this deadline does.

Why is the auto-upgrade the dangerous option, not the safety net?

The auto-upgrade is dangerous precisely because it prevents a visible failure. Shopify's non-Plus upgrade guide states that if you do not upgrade before 26 August 2026, your Thank you and Order status pages "will be auto-upgraded to the new pages". Read as reassurance, that sounds like Shopify has your back. Read as a practitioner, it is the worst available outcome.

A broken page gets fixed. A broken measurement does not.

If your checkout visibly failed, you would notice within the hour. Instead the page renders, the order completes, and the customer is happy. The only change is that the conversion event you have optimised against for years stops arriving. Reporting then shows a collapse in sales that never happened.

That is the failure mode nobody plans for, because it does not look like a failure. It looks like a bad month.

How do you find what will break? The Silent-Break Triage

The Silent-Break Triage is a three-box sort: open your Additional scripts box and your Thank you page customisations, then file every snippet as Measurement, Message or Mechanics. It is worth reusing on any platform migration, not just this one.

Measurement is the urgent box. Message is the one that quietly costs you repeat custom. Mechanics is the box most small stores do not have at all; if you do, Shopify publishes a guide to migrating from Scripts to Functions.

What usually goes wrong with custom pixels?

Custom pixels are not a drop-in replacement for pasted JavaScript, and assuming they are is the most common way this migration fails. Shopify's own custom pixels documentation says they run inside a "Lax sandbox, designed for improved security and control over the data that you send to third parties", and warns plainly that "not all pixel functionality works in the sandbox". The same page states that custom pixel support is unsupported and recommends hiring a Shopify Partner.

That is a vendor telling you, in its own help centre, that the replacement path has edges. Two consequences follow.

First, prefer an official app pixel over hand-written custom pixel code wherever the vendor publishes one. The vendor maintains those against sandbox changes; your snippet is your problem forever.

Second, budget for testing rather than pasting. The job is not moving code between boxes; it is proving the event still fires. That is the discipline behind ongoing SEO optimisation of an existing site, where a fix is not finished until a re-crawl confirms it.

What should you do before 26 August 2026?

1. Open Settings, then Checkout, and read your Additional scripts box today. Copy the contents into a document. The box is read-only, so this is an archive, not an edit.
2. Sort every snippet using the three boxes above. Most small stores find two to five snippets, and almost all are measurement.
3. For each tracking vendor you find, check the Shopify App Store for an official app pixel first. Install it, then retire your dependence on the pasted version.
4. Rebuild anything with no official app as a custom pixel, then test it against a real order rather than the editor preview.
5. Place one live test order and confirm the conversion appears in the destination platform, not only in Shopify. This is the single step that actually proves the migration worked.
6. Re-check your post-purchase page content. If your Thank you page carried delivery expectations or a review request, rebuild it as an extension before the auto-upgrade discards it.

Do steps 1 and 5 even if you believe you have nothing to migrate. Both take under an hour, and both are cheaper than discovering the gap in October.

What is hype and what is real about this deadline?

Three things about this deadline are real and checkable: the date, the auto-upgrade, and the sandbox limits. All three are stated in Shopify's own documentation, and all three can be verified in your admin this afternoon.

The panic framing is overstated. This is not a store-down event, and it does not require an emergency rebuild of your website. Plenty of small stores have never touched the Additional scripts box and are genuinely unaffected. You should confirm that by looking rather than by assuming.

Treat circulating migration-cost and conversion-loss figures with caution. Several trace back to agencies selling the migration rather than to published research, and none are numbers we can independently verify, so we will not repeat them. The honest answer: a typical small store with a handful of snippets is looking at an afternoon, and a heavily customised store is looking at a project. For what ongoing website and SEO work costs, our pricing page states it plainly, and our guide to e-commerce web design costs breaks down where the money goes.

What is the wider lesson for a small business website?

Every platform eventually retires the escape hatch it once handed you. The pasted script, the theme hack, the one piece of custom code nobody documented: these break on somebody else's timetable, not yours.

The defence is not avoiding customisation. It is knowing what runs on your own site. Most owners cannot list what fires on their pages, which is exactly why a deadline like this becomes a silent outage instead of a Tuesday task.

If you sell online, websites built for online retail brands should ship with tracking you can point to and explain. The same principle runs from SEO for a boutique online store to the post-purchase page: if you cannot verify it fired, you do not know that it did.