Checkout UI extensions: what you can and can't add to Shopify checkout

For a long time, “customizing the checkout” on Shopify meant editing checkout.liquid — and only Shopify Plus stores could do it, usually through fragile code that broke on updates. That era is ending. The supported way to add content and fields to the checkout now is checkout UI extensions, and they change what is realistic to build.

Here is a straight answer to the question we get most: what can you actually add, and what can’t you?

What checkout UI extensions are

A checkout UI extension is a small, sandboxed component that renders at a defined spot in the checkout — above the summary, near shipping, on the “thank you” and order-status pages, and other approved locations. They are built with Shopify’s components so they inherit the checkout’s styling and stay accessible and fast. Because they run in Shopify’s supported framework, they survive platform updates instead of breaking on them.

Think of them as approved slots you can place content into, not a blank canvas you can repaint.

What you can add

Plenty of the things merchants actually want:

• Trust and reassurance content — delivery promises, guarantees, support links, review snippets.
• Custom fields — a gift message, a PO number, delivery instructions, a VAT field — captured and saved to the order.
• Upsells and offers — a relevant add-on before payment, or a one-click offer on the post-purchase page.
• Dynamic messaging — a free-shipping progress bar, or a banner that appears based on cart contents.
• Content on the order-status page — where customers spend real time after buying, and where most stores show nothing useful.

This is the bulk of checkout UI extension work: high-value, low-risk additions in supported slots.

What you can’t (or shouldn’t) do

Being honest about the boundaries saves everyone time:

• You can’t freely restyle the whole checkout. Layout and structure are Shopify’s. For brand controls — logo, colours, fonts, corner styles — you use the checkout branding settings, not an extension.
• You can’t place a component anywhere you like. Extensions render at defined targets. If the slot you want does not exist, no amount of code creates it.
• Logic belongs in Functions, not UI. If the goal is to change discounts, payments, delivery or validation, that is a Function — the UI extension only handles what the customer sees and enters.
• Extensions run sandboxed. They cannot reach into the page arbitrarily or run unrestricted scripts. That is a feature: it is why they are fast and safe.

Why the constraints are worth it

The old checkout.liquid approach gave more raw freedom and a lot more pain: every Shopify update was a potential outage, and only Plus stores could play. UI extensions trade some freedom for reliability, accessibility, performance, and a checkout that keeps working through platform changes. For most stores that is a very good trade.

The skill is in knowing which of your requirements map cleanly onto a supported slot, which belong in Functions, and which need a rethink because the platform genuinely will not do them. That triage is where a project starts.

The short version

You can add reassurance, custom fields, upsells and dynamic messaging into defined checkout slots — and you should, because most of that space sits empty today. You can’t repaint the whole checkout or invent new slots, and logic changes live in Functions, not the UI. Work with those lines and the checkout becomes a real conversion surface again.

If you have a list of things you want in your checkout, we can tell you quickly what is a supported extension, what is branding, what is a Function, and what is not possible — and then build the ones that are.