If you run a Shopify store in Israel, you have probably scrolled past four versions of the same warning this month. August 26. Checkout is changing. Your checkout.liquid is going away.
Here is the part nobody put in the headline: checkout.liquid is a Shopify Plus feature. It always was. If you are on Basic, Shopify, or Advanced, you never had it, you never edited it, and you cannot lose it.
So a lot of store owners read that warning, concluded it was somebody else’s problem, and closed the tab.
The deadline is real. The date is right. The noun is wrong, and the wrong noun is exactly what let you dismiss it.
What actually expires on August 26, and where
The change is narrower than the panic suggests, and that is what makes it dangerous. It does not touch your product pages, your cart, or your checkout flow. It touches two pages: the Thank you page and the Order status page. The two pages a customer sees after they have already paid.
On August 26, 2026, Shopify retires three ways of customizing those two pages for stores that are not on Plus:
- Additional scripts. The box in Settings > Checkout where a developer, an agency, or you at 1am once pasted a block of JavaScript.
- Script tag based customizations. Code injected by apps through the older script tag method.
- Third-party apps that still rely on the deprecated methods and have not shipped a compatible version.
Plus stores went through this on August 28, 2025. Non-Plus stores are next, and the calendar says eight days.
If you do nothing, Shopify upgrades those two pages for you on the date and replaces the existing customizations. Not “flags them for review.” Replaces them.
The reason you will not notice
Think about what usually lives in that Additional scripts box.
For most small and mid-size stores, it is the purchase event. The GA4 purchase tag. The Meta pixel purchase event. The Google Ads conversion tag. A TikTok pixel someone added during a campaign and never removed. Maybe an affiliate postback, a review-request script, a survey that asks how the customer found you.
Every one of those fires on the page the customer lands on after paying. Which is precisely the page being upgraded.
Now picture August 27. Your storefront looks perfect. Products load, the cart works, the checkout completes, the money arrives in the bank. Nothing is broken in any way a customer, or you, would see.
The only thing that changed is that the systems you use to decide where your budget goes stopped being told about the sales.
Your ad platforms stop counting conversions, so their optimization drifts toward the wrong audiences. Your ROAS reports collapse on paper while the actual revenue holds. GA4 shows sessions and no purchases. And the natural reaction, when the dashboard says the campaigns died, is to cut spend on campaigns that were working fine.
That is the real cost of this deadline. Not downtime. A month of decisions made on numbers that quietly stopped being true.
The ten minute check that ends the guessing
You do not need a developer to find out where you stand. You need about ten minutes and access to your own admin.
Go to Settings > Checkout. If your store is affected, there is an upgrade notice on that page with a Review customizations button.
That button is the whole point of this article. It does not give you a generic warning. It reads your specific store and returns a personalized list: the customizations you actually have, the apps you actually installed, which of them already have a compatible version, and what each one needs.
Three outcomes, and all three are useful:
– The list is empty. Some stores never had anything in that box. You are done, and you now know it instead of assuming it. – The list is all apps. This is the common case, and it is the easy one. Most serious apps shipped compatible versions months ago. Updating them, or reconnecting them through the app’s own settings, is usually the entire fix. – The list has custom code. Someone wrote something specific for you. This is the one that needs real attention, and it is also the one where eight days is tight, so find out today rather than on the 25th.
What replaces the scripts
The replacement path is not “paste your code somewhere else.” Shopify moved this to a structured system: blocks and web pixels to rebuild customizations, and app pixels to keep tracking customer events. All of it works on every plan, including yours.
For tracking specifically, the mechanism is a pixel that subscribes to events rather than a script that runs on a page. Instead of a snippet sitting on the thank-you page waiting to execute, you register a pixel that listens for the checkout-completed event and reports it. Same purchase, same destination, different plumbing:
analytics.subscribe("checkout_completed", (event) => {
// send the purchase to your analytics or ad platform here
});Treat that as the shape of the thing, not as code to paste. The exact payload depends on which platform you are feeding, and most store owners will never write it, because the app they already pay for now does it for them. Meta, Google, GA4 and the major analytics tools all have current Shopify apps that handle this natively.
The practical version of this section: your job is usually to update apps and confirm the events are arriving. Writing custom pixel code is the exception, not the default.
The trap nobody is writing about
Here is the one that will catch Israeli stores specifically.
If you pause your store, the upgrade happens automatically. And it cannot be reverted, even after you unpause.
Read that again with a local calendar in mind. Stores pause. They pause over the חגים. They pause when the owner is on מילואים. They pause between seasons, or for a month while a rebrand finishes, or because a supplier fell through and there is nothing to ship.
Every one of those merchants thinks they have bought themselves time. They have done the opposite: pausing performs the irreversible step for them, and they come back to a store whose thank-you page has been rebuilt and whose tracking scripts are gone, with no path back to how it was.
If you are planning to pause, run the review first. Ten minutes now versus an unrecoverable state later is not a close call.
What this does not mean
It is worth saying plainly, because the tone of the coverage this month invites the wrong reaction.
Your checkout is not breaking. Your store is not going offline. The change is scoped to two post-purchase pages, so the checkout and the order flow itself sit outside it. This is not an emergency migration, and if someone quotes you a large project to “handle the checkout deadline,” ask them specifically which of your customizations they found in the review, because that list is generated for free in your own admin.
It is also not nothing. The failure mode is invisible, it lands on the page where revenue is counted, and the fix window is eight days for a check that takes ten minutes.
Both of those are true at once, and holding both is the entire skill here.
