Checkout UI extensions without Shopify Plus: what's actually possible in 2026

Checkout extensibility used to be Plus-only. In 2026 the picture is more nuanced, and most non-Plus stores are leaving easy wins on the table.

Davey Zaal

Co-founder, Montagne Agency

Checkout UI extensions without Shopify Plus: what's actually possible in 2026

Checkout extensibility used to be Plus-only. In 2026 the picture is more nuanced, and most non-Plus stores are leaving easy wins on the table.

Davey Zaal

Co-founder, Montagne Agency

A practical breakdown of what Checkout UI Extensions you can ship without Shopify Plus in 2026, what still requires the upgrade, and how to get most of the value at a fraction of the cost.


For years the answer was simple: if you wanted to customise Shopify's checkout, you needed Plus. Period. That answer is no longer correct in 2026, but the new reality is messier than most merchants realise. Some Checkout UI Extensions now run on any paid plan. Others are still gated behind Plus. And there's a deadline on the calendar that makes this conversation urgent rather than academic.

Here's the practical breakdown for non-Plus stores: what you can ship today, what you can't, and where the smart workarounds sit.

The short version

Shopify split the checkout into pieces a few years ago. The information step, shipping step and payment step are the "core" checkout pages. The Thank you page and Order status page sit on the other side of the purchase. The rules in 2026 differ per zone.


Surface

Non-Plus access

Plus required

Information step

No

Yes

Shipping step

No

Yes

Payment step

No

Yes

Thank you page

Yes

-

Order status page

Yes

-

Third-party app extensions on any step

Yes

-

Branding API (deep checkout styling)

No

Yes

Shopify Functions on checkout

Limited

Full

In other words: the parts of checkout where the customer actually pays still need Plus to touch directly. Everything that happens after the order is placed is open to Basic, Shopify and Advanced.



What you can ship without Plus

The two surfaces that opened up are the Thank you page and the Order status page. That sounds small, but in conversion and retention work these are two of the most underused pages in the funnel. Most stores treat them as dead ends. They're not.


A few concrete things we ship for non-Plus stores using Checkout UI Extensions:

  • Post-purchase upsells and cross-sells rendered natively on the Thank you page, with one-click add-to-order before the customer leaves

  • Account creation prompts that prefill the email and turn guest checkouts into accounts at the highest-intent moment

  • Order tracking widgets embedded on the Order status page instead of a separate email or 3PL portal

  • Referral and loyalty enrolment at the moment of highest dopamine

  • Custom delivery instructions or gift messages captured post-purchase and synced to the order via metafields

  • Trust and reassurance content (delivery promise, returns policy, support contact) that reduces "where is my order" tickets

None of this requires Plus. All of it is built on the same Checkout UI Extensions framework Plus stores use on the rest of the checkout.

Third-party apps are the second door

The other route most non-Plus merchants miss: apps from the Shopify App Store that use Checkout UI Extensions internally are available on every paid plan, regardless of what surface they target. That includes apps that render on the information, shipping or payment steps.

So a non-Plus store can install a Checkout Extensibility app for, say, a custom trust badge in the payment step, or a dynamic shipping message in the shipping step, even though direct, custom-built extensions on those steps require Plus. You're renting the extension instead of building it, but the result on the customer side is the same.

This is the most common gap we see. Stores assume Plus is the only way and either pay for an upgrade they don't need or skip the optimisation entirely. The right move in most cases is to use App Store apps for the core checkout surfaces, and only build custom extensions on the Thank you and Order status pages where you have full freedom on any plan.


What's still Plus-only and probably will stay that way

Three things are still gated and worth being honest about:

  1. Custom logic directly on the information, shipping or payment step. If you want to render your own React-style component inside the address form, that still needs Plus.

  2. The Branding API. Deep visual customisation of the checkout (typography, colour, layout proportions, button radii) is Plus-only. You can use the standard checkout settings on lower plans, but you can't programmatically override them.

  3. Shopify Functions on checkout at full depth. Things like custom discount logic, custom delivery customisations and payment customisations have limits on lower plans. If your business rules are complex, you'll hit the ceiling.

If any of those are blocking real revenue, the Plus upgrade pays for itself. If they're not, you're paying $2,300+ a month for features you don't actually need.


The deadline you can't ignore

There's a date that pulls this conversation forward whether you're ready or not. Shopify is auto-upgrading all remaining non-Plus stores to Checkout Extensibility on **August 26, 2026**. The old `checkout.liquid` flow is already gone for Plus and is being retired across the rest of the platform. Shopify Scripts disappear entirely on **June 30, 2026**.


What this means practically:

  • If your store still relies on legacy checkout customisations through scripts or `checkout.liquid` hacks, they'll stop working on those dates

  • Any app that hasn't been updated to Checkout Extensibility will silently fail or get removed from your checkout

  • Your post-purchase surfaces (Thank you, Order status) will be running the new extension framework whether you've built anything for them or not

The right way to read those deadlines is not as a threat but as a free unlock. The Thank you and Order status pages are about to become first-class extension surfaces on your store, and most of your competitors won't have done anything with them.


What to do on a non-Plus plan, today

A pragmatic checklist:

  1. Audit your checkout apps and confirm every one uses Checkout UI Extensions, not the legacy framework. Anything that doesn't is on borrowed time.

  2. Map the Thank you and Order status pages and decide what you'd actually do with two extension surfaces you control. Post-purchase upsells, referral enrolment and account creation are usually the highest-ROI starts.

  3. Use App Store apps for the information / shipping / payment steps where direct extension building requires Plus, and treat that as a deliberate decision rather than a missed opportunity.

  4. Build the Thank you and Order status extensions yourself** (or with a partner) since you get the same toolkit Plus merchants have for those surfaces, and the on-page real estate is wide open.

  5. Hold the Plus upgrade conversation until you have a concrete extension or branding need that the lower tier genuinely blocks. The upgrade math gets a lot clearer once you know exactly what you can't do on your current plan.


The big shift in 2026 is that "Checkout extensibility" is no longer a Plus-only feature flag. It's a platform default with a Plus tier on top. Treat it that way, and there's a lot of work non-Plus stores can be doing right now that they're not.

*Running Shopify on a non-Plus plan and unsure what your checkout can actually do? [Get in touch](https://montagneagency.com/contact) - we'll map the extensions that are worth building on your store before the August deadline hits.*

Sources:

  • [Shopify dev docs - Checkout UI Extensions](https://shopify.dev/docs/api/checkout-ui-extensions/latest)

  • [Shopify dev docs - Checkout app extensions](https://shopify.dev/docs/api/checkout-extensions)

  • [Shopify community - Checkout UI extensions without Plus](https://community.shopify.com/t/checkout-ui-extensions-without-shopify-plus/267769)

Want to stay updated?

Discover the latest meaningfull insights about high-performance webdevelopments.