On August 26, 2026, every non-Plus Shopify store loses Additional Scripts and checkout.liquid on the Thank You and Order Status pages — Shopify auto-upgrades the pages and deletes whatever custom code was running there, it does not migrate it. If your GA4 tag, Meta Pixel, Google Ads conversion snippet, or affiliate script lives in that Additional Scripts box, it stops firing that day unless you move it to Shopify's supported system first: Checkout UI Extensions, Web Pixels, and Shopify Functions. This guide covers exactly what breaks, how to migrate before the deadline, and when it's a five-minute app install versus a real dev task.
This isn't a hypothetical future change — it's four days away from today's publish date, and it applies to every store on a non-Plus Shopify plan, regardless of revenue or size. Plus merchants already went through this a year earlier — their script-tag sunset landed August 28, 2025. Now it's everyone else's turn, and the deadline doesn't move for stores that aren't ready.
Prefer to skip the DIY route entirely? We migrate Shopify tracking and checkout customizations as part of our e-commerce automation service — see the framework below, then book a call if you'd rather hand it off.
What's Actually Changing on August 26
Shopify has been retiring checkout.liquid in stages since 2024, moving merchants toward a newer, more secure checkout architecture. The Information, Shipping, and Payment steps were upgraded first; the Thank You and Order Status pages — the last piece most merchants still touch — are what's sunsetting now for non-Plus stores. Three legacy tools go away on those two pages specifically:
- Additional Scripts — the free-text code box under Settings → Checkout where most merchants paste tracking pixels, GTM containers, and affiliate snippets.
- checkout.liquid customizations — any theme-level edits to those pages.
- Shopify Scripts — legacy Ruby-based scripts for discount and shipping logic on older plans.
According to migration research from Gadget's breakdown of the checkout.liquid deprecation, merchants can't run the old and new systems side by side — once the upgrade happens, everything in Additional Scripts is gone, not paused. There's no grace period to catch a missed pixel after the fact.
What Actually Breaks (and Who Notices First)
The pain shows up in three places, usually in this order:
- Ad platform tracking. Google Ads and Meta Pixel conversion events fired from Additional Scripts on the Thank You page stop reporting. Your campaigns don't crash, but your conversion data quietly goes dark — CPA looks worse, optimization gets dumber, and nobody notices until a weekly report looks off. Broken conversion tracking is wasted ad spend by another name; run the numbers in our automation ROI calculator if you want a sense of what a week of blind campaign optimization actually costs.
- Custom tracking and affiliate scripts. Any non-standard pixel, GTM container, or affiliate network snippet pasted directly into the box is deleted along with everything else.
- Order-status page customizations. Custom messaging, upsell widgets, or COD-specific logic built on the old system needs to be rebuilt as a Checkout UI Extension or Shopify Function — it won't silently degrade, it just won't be there.
For most stores in ReachRight's client base, the practical impact is almost entirely about tracking — the same GA4 and Meta Pixel setup most small businesses rely on for their whole reporting stack often has its most important conversion event (the purchase) sitting in exactly the field that's about to be wiped.
DIY vs. App vs. Custom Build: A Decision Framework
Not every store needs a developer for this. The right path depends on what's actually in your Additional Scripts box today — audit it before you decide.
| Standard tracking only | Non-standard scripts | Custom logic (COD, upsells, custom fields) | |
|---|---|---|---|
| What's in Additional Scripts | GA4 tag, Meta Pixel, Google Ads snippet | Affiliate networks, third-party analytics, custom event mapping | Order-status page widgets, discount/shipping rules, business-specific validation |
| Best-fit path | Shopify's official GA4 and Meta channel apps | A custom Web Pixels extension | A Shopify Function or Checkout UI Extension |
| Who can do it | Store owner or ops team, no code | Needs a developer familiar with Shopify's Web Pixels API | Needs a developer; touches checkout logic, so test thoroughly before go-live |
| Time to migrate | Under an hour | A few hours to a day | Several days depending on complexity |
Most merchants are in the first column and don't realize it — if your Additional Scripts box only ever held tracking pixels, the official apps solve it without touching code. The trap is assuming you're in that column without checking; open Settings → Checkout → Additional Scripts today and read what's actually in there.
The Migration Checklist
- Inventory everything in Additional Scripts. Copy the full contents out before you do anything else — you'll need it as a reference, and it disappears on upgrade day regardless of what you've done.
- Map each script to its replacement. Standard tracking → official app or Web Pixel. Custom scripts → custom Web Pixels extension. Checkout logic → Shopify Function. UI changes → Checkout UI Extension.
- Build and test in a duplicate or dev store first. Since you can't run checkout.liquid and checkout extensibility side by side, confirm the replacement actually fires before you commit on your live store.
- Verify conversion events land correctly. Place a real test order and confirm GA4 and Meta Pixel both register the purchase event with the right value — this is exactly the kind of gap our analytics dashboard work catches when reporting numbers stop matching reality.
- Trigger the upgrade before August 26, or let it auto-upgrade — but only after step 4 passes. You can manually upgrade early once testing is clean; don't wait for the automatic switch to find out something's broken.
If this touches order automation beyond tracking — notifications, returns logic, or app integrations tied to checkout — it's worth reviewing against our broader Shopify automation guide and the apps we recommend for 2026, since several of the tools already handle checkout extensibility natively.
Common Mistakes We See
- Assuming an app migration means tracking migrates automatically. Installing the GA4 or Meta channel app doesn't retroactively fix a broken setup — you still need to confirm the purchase event is configured and firing.
- Waiting for the automatic upgrade to "just handle it." The auto-upgrade removes the old code; it doesn't rebuild your tracking. Passive waiting guarantees a tracking gap, even if a short one.
- Testing on production instead of a duplicate store. Because the old and new systems can't run in parallel, a broken migration on your live store means broken checkout tracking until you fix it — test first.
Key Takeaways
- Non-Plus Shopify stores lose Additional Scripts, checkout.liquid, and Shopify Scripts on the Thank You and Order Status pages on August 26, 2026 — content is deleted, not migrated.
- Standard GA4 and Meta Pixel tracking usually migrates cleanly via Shopify's official apps with no code required.
- Custom scripts, affiliate tracking, and checkout logic need a Web Pixels extension or Shopify Function — a developer task.
- Audit your Additional Scripts box today, test the replacement in a dev store, and verify conversion events before the automatic upgrade runs.