Skip to content

What Are Checkout UI Extensions?

Definition

Checkout UI extensions are app components that add custom interface elements, such as fields, banners and product offers, to Shopify checkout. They run in an isolated sandbox and render with Shopify components at fixed or merchant-placed targets. Thank you and Order status extensions work on every plan; information, shipping and payment steps need Shopify Plus.

How checkout UI extensions work

Shopify's checkout is closed: you cannot edit its HTML, CSS or JavaScript. Checkout UI extensions are the supported way to add your own interface to it, such as a banner, an extra field, a product offer or a delivery note. Each extension runs in an isolated sandbox, separate from the checkout page and from other extensions. Technically it runs in a Web Worker with no access to window or the DOM, and it renders through Polaris web components written with Preact.[1]

That sandbox is the whole point. An extension can only use the UI components and APIs that Shopify exposes, and it cannot read the checkout's HTML or other assets.[1] In return, Shopify keeps checkout fast, secure and upgradable, and your customisation survives every checkout update. Two practical limits follow: the compiled bundle may not exceed 64 KB, and an extension needs the network_access capability before it may call any external service.[1]

Extensions are delivered inside apps. After an app is installed, the merchant places its extensions in the checkout and accounts editor, which is separate from the theme editor.[2] The developer decides what the extension does; the merchant decides where block extensions appear.

Extension targets and which plans can use them

A target is the place in checkout where an extension renders. There are three kinds:[1]

  • Block targets can be positioned by the merchant in the editor. Up to three extensions can share the same block location.
  • Static targets render at a fixed point, for example right after the payment method list, and cannot be moved.
  • Runnable targets return data without rendering any UI.

Targets are grouped by area. Checkout has groups for the address, header, footer, information, shipping, payment, order summary, local pickup and pickup points, and the Thank you page has its own groups. Target names describe the location, for example purchase.checkout.block.render, purchase.checkout.delivery-address.render-before or purchase.thank-you.block.render.[3] The Order status page is extended through customer account UI extensions, with targets such as customer-account.order-status.block.render.[4]

The plan decides which of those targets you can actually use:

Where the extension appearsBasic, Grow, AdvancedShopify Plus
Thank you page and Order status pageYes[2]Yes
Information, shipping and payment stepsNoYes[1][2]
Checkout Branding API (deeper styling)NoYes[2]
Pickup points targets (beta)NoCustom apps only[3]

In practice this means a non-Plus store can add post-purchase content such as surveys, upsells or tracking information, but everything before the order is placed belongs to Plus. Our guide to checkout extensibility in 2026 covers the wider upgrade, including the checkout.liquid deadlines.

Example: collecting a company tax number at checkout

Take a hypothetical Serbian B2B and B2C store where around 15% of buyers are companies that need an invoice with their PIB, the company tax number. Today those buyers type the PIB into the order note, half of them forget, and the team emails them after every order.

On Shopify Plus, a checkout UI extension adds a "Buying as a company?" checkbox and two fields, company name and PIB, to the information step. The extension writes the values to a cart metafield, which is how Shopify recommends storing custom checkout data, so they travel with the order to the invoicing or ERP integration.[5] The bundle stays well under the 64 KB limit because it uses Shopify's own components.[1] A cart and checkout validation function can then block the order if the PIB field is filled with something other than nine digits.

On Basic, Grow or Advanced, the same extension can only run on the Thank you page.[2] The buyer sees the fields after paying, which helps a little, but the data arrives after the order is created and your team still has to match it by hand. For a store with 1,000 orders a month, that is about 150 orders a month where the difference matters.

Checkout UI extensions vs Shopify Functions

Both are part of checkout extensibility, alongside web pixel extensions and payments extensions.[6] They are built to work together:

Checkout UI extensionsShopify Functions
What it changesWhat the buyer sees: fields, banners, offers, messagesBackend logic: discounts, delivery and payment options, validation
Runs whereIn the buyer's browser, in a sandboxed Web Worker[1]On Shopify's servers, as WebAssembly[7]
Plan ruleInformation, shipping and payment steps need Plus; Thank you and Order status work on Basic and up[2]Public apps on any plan; custom apps with functions need Plus[7]
Typical exampleA gift message field on the shipping stepHide cash on delivery above a cart value

FAQ

Do checkout UI extensions require Shopify Plus?

Only for the information, shipping and payment steps. Stores on Basic and higher can add eligible apps to the Thank you and Order status pages through the checkout and accounts editor.[2]

Can a checkout UI extension change the checkout's CSS?

No. Extensions can only use the UI components and APIs Shopify exposes and cannot access the checkout page's HTML or assets. Plus stores can change checkout styling through the Checkout Branding API instead.[1][2]

What happened to checkout.liquid?

checkout.liquid is no longer supported for the information, shipping and payment steps, and it was sunset for the Thank you and Order status pages on August 28, 2025. Checkout UI extensions are the replacement.[6]

How big can a checkout UI extension be?

The compiled bundle can't exceed 64 KB. External calls also need the network_access capability.[1]

Can I build a checkout UI extension without an app?

No. Extensions are always part of an app. You either install an App Store app that contains them or have a developer build a custom app for your store.[2]

The bottom line

Checkout UI extensions are the supported way to add your own fields, messages and offers to Shopify checkout without touching its code. They run in a sandbox, render with Shopify's components and are placed by the merchant in the checkout and accounts editor. Every plan can extend the Thank you and Order status pages, but the information, shipping and payment steps are reserved for Shopify Plus. Our checkout customization team builds these extensions and the functions behind them.

Article sources

We use primary sources only: official documentation, product pages and laws. Each link was checked on the date shown.

  1. Shopify Dev. Checkout UI extensions. Accessed 17th Nov 2026.
  2. Shopify Help Center. Checkout extensibility. Accessed 17th Nov 2026.
  3. Shopify Dev. Checkout UI extension targets. Accessed 17th Nov 2026.
  4. Shopify Dev. Customer account UI extensions. Accessed 17th Nov 2026.
  5. Shopify Dev. Attributes API (checkout UI extensions). Accessed 17th Nov 2026.
  6. Shopify Dev. Build for checkout. Accessed 17th Nov 2026.
  7. Shopify Dev. Shopify Functions. Accessed 17th Nov 2026.

Need this on your store?

See the service

The checklist we run before touching a client's code

Get it by email, plus a few short notes over the next two weeks: what we see most often on Shopify stores and what actually fixes it.

No spam. Unsubscribe anytime. Privacy Policy