The Checkout.liquid Deprecation and the SOPs It Broke

The checkout.liquid deprecation is finished. Every deadline has passed, the last one on August 26, 2026. Any SOP written against the old checkout screens stopped matching reality on a fixed date, not gradually, and many teams have not re-checked them since.

Shopify's developer documentation now states that checkout.liquid is unsupported for the Information, Shipping and Payment steps. It was also sunset for the Thank you and Order status pages. So the question is no longer when to migrate. It is which written procedures to re-record first, and how to tell which steps actually went stale.

One point first. checkout.liquid was only ever available to Shopify Plus stores. If you are not on Plus, you never had that file. What changed for you was the additional scripts and script tags on the Thank you and Order status pages.

What exactly stopped working, and when?

Five dates matter, and all of them are in the past.

The first date comes from Shopify's changelog, the Scripts dates from Shopify's developer changelog, and the rest from Shopify's checkout.liquid documentation and Help Center. On that last point, Shopify's upgrade guide for non-Plus stores says: "As of August 28, 2025, the additional scripts section in the Checkout settings is view-only."

Which documented steps went stale when checkout moved to extensions?

SOP drift is the gap between what a procedure says and what the team actually does. The platform-driven kind is the version nobody on the team caused. Shopify changed the screen, and the written steps stopped matching it on a date set by someone else.

Four kinds of checkout procedure are the usual casualties:

• Discount steps. Anything that relied on a Shopify Script to apply or block a discount, or that described what the old checkout showed when two offers combined.
• Shipping rate steps. Instructions that relied on a Script to rename, hide or reorder rates.
• Post-purchase and Thank you page steps. Upsell checks, survey checks and "confirm the pixel fired" steps that pointed at additional scripts.
• Test-order walkthroughs. Any check that still tells someone to paste code into the additional scripts box, or to open the Script Editor app.

Do not judge a screenshot by how many pages the checkout has. Shopify's current checkout can still be set to one page or three, so a three-page screenshot proves nothing. The real warning signs are an instruction to type into the additional scripts box, or a step inside the Script Editor.

Where do discount and shipping rules live now?

In the Shopify admin, in apps, and in Shopify Functions. checkout.liquid never held those rules. On Plus stores, custom discount, shipping and payment logic ran on Shopify Scripts. Shopify's developer changelog says that "All Shopify Scripts will cease to execute entirely" on June 30, 2026, and Functions replace them.

Shopify Functions exist, in Shopify's words, so merchants can "implement specialized features that aren't available natively." There is one plan limit to write into the handoff notes. Running a custom app built with Function APIs needs a Shopify Plus plan. Public apps from the Shopify App Store that use Functions work on any plan.

So a discount SOP that used to say "the Script handles it" now has to name the app or Function that does, and the screen where its settings live.

What has to change on the Thank you and Order status pages?

Those two pages need their customizations rebuilt with blocks and pixels. Shopify's Help Center is explicit: if the pages were customized with incompatible apps, scripts or pixels, the store is required to upgrade and replace those customizations.

The upgrade guide gives a route an SOP can name exactly. Go to Settings, then Checkout, and check the Configurations section. If an upgrade notice shows, click Review to open the guide. Its Incompatible apps section lists installed apps whose developers have not updated them for the new pages. Shopify's advice there is to contact the developer or install a different app.

If no notice shows, Shopify says the store is already on the new pages. By now that is most stores. In that case, open the checkout and accounts editor and list what is actually there: each app block, its position, and each pixel.

An incompatible app is the part a documented procedure cannot solve on its own. If an app in the upsell step is listed, the SOP is blocked until someone else ships code. Record that as a dependency with a name attached, not as a step.

How do you find out which documented steps actually broke?

Re-record the procedure on the live checkout, then compare it line by line against the stored version. Reading the old document will not tell you. It reads as confidently as it did the day it was written.

A practical order for one procedure:

1. List the store's current checkout customizations, from the upgrade guide if a notice still shows, or from the checkout and accounts editor if not.
2. Record the procedure end to end as it is done today, including the admin screens, not just the storefront.
3. Put the new walkthrough beside the old one and mark each step as unchanged, moved, renamed or gone.
4. Hand the rewritten version to someone who has not done the task before.

That last step comes from Paula Holsberry's guide to documenting small business processes. She describes an entrepreneur who gives new process documents to a team member who has never done the task. Their questions show exactly where the document assumes knowledge nobody wrote down.

For a wider pass across the whole library rather than one procedure, our SOP gap audit method runs the same comparison in five steps.

What should a test order confirm after the checkout upgrade?

That the whole checkout chain still works, not just the payment screen. Check that the order processes, inventory updates, the right shipping rate shows, discounts apply, notification emails go out, and tax is correct.

After the cutover, that check matters more than before. The discount, shipping and Thank you page steps are the ones that moved onto extensions and Functions, and a test order touches exactly those steps. A procedure written for the old checkout can look complete and still skip a step that now runs through an app.

On a store that is already selling, place a real order through the storefront, check the admin record, then cancel and refund it. Shopify's simulated payment options get in the way of real customers while they are on. The Shopify test order guide covers the full routine and the trade-offs.

Who should own re-recording a checkout procedure, and when?

One named person, not a department. When a procedure belongs to the whole team, nobody notices the day it stops being true. Our guide to who owns updating SOPs makes the full case.

Our view is to review a checkout procedure every quarter, and again straight after any change to the checkout stack. Three events should trigger a re-record:

• An upgrade notice appears in, or disappears from, Settings, then Checkout.
• An app is added to or removed from the checkout and accounts editor.
• A discount or delivery Function is deployed or changed.

Those are events someone can see, unlike a feeling that the screen looks different.

Holsberry also recommends naming a single "keeper of the processes" who is responsible for the documentation. On a small store team, give it to whoever already holds the Shopify admin login. If that person leaves, hand off the role with a knowledge transfer plan. Name the next owner and the trigger list in it, not just the admin password.

What are the limits of recording and diffing a checkout procedure?

Re-recording and diffing documents a checkout surface a store may not fully control. It cannot replace code someone else has to write.

Three honest limits:

• Checkout UI extensions that customize the Information, Shipping and Payment steps run only on Shopify Plus. A non-Plus store has fewer checkout surfaces to document.
• A merchant can add up to three extensions to one block position in the checkout and accounts editor. Someone can move a block without touching the SOP, and the screenshots stop matching again.
• If the upgrade guide lists an app as incompatible, no amount of re-recording fixes it. The developer has to update the app, or the store has to switch apps.

A recording also only captures one person's way of doing the task. Someone still has to review it before it becomes the official version.

Next step

Pick one checkout procedure this week. Open Settings, then Checkout, and see whether an upgrade notice still shows. Record the procedure as it is actually done today, and mark every step in the old document as unchanged, moved, renamed or gone. Put one name against it.

ReccordSOP is an AI SOP tool built for Shopify direct-to-consumer brands. Record the checkout procedure once, and it writes the numbered steps with a screenshot for each one. Re-record it after a platform change, and it shows which steps drifted instead of overwriting the old version. It also emails workspace admins when a published SOP passes 90 days since its last review or edit.

It documents a process; it does not run the process, watch your store settings, or make decisions for you. The free plan covers 3 SOPs in total. Team is $19 per user per month, with a 3-user minimum.