What Is Shopify Checkout Extensibility?
Learn what Shopify Checkout Extensibility does, which features need Shopify Plus, and how UI extensions, Functions, pixels and branding work together.
Shopify Checkout Extensibility is the set of tools used to customise Shopify checkout through apps, extensions and supported APIs. It lets you add features and change parts of the checkout experience without editing the old checkout.liquid template.
For a merchant, that might mean adding a gift message field, showing a relevant product recommendation or applying a custom discount rule. Each change uses a different part of the platform. Your Shopify plan and the page you want to change determine what is available.
The key distinction: adding app blocks to the information, shipping and payment steps requires Shopify Plus. Eligible apps on the Thank you and Order status pages are available on Basic and higher plans.
What you can customise on each Shopify plan
Checkout Extensibility is not a single feature with one eligibility rule. Start with the change you want to make.
Change | Plan or access requirement |
|---|---|
Add a logo and adjust standard checkout colours and fonts | Basic or higher |
Add app blocks to information, shipping and payment | Shopify Plus |
Add eligible app blocks to Thank you and Order status | Basic or higher |
Use advanced checkout branding through the API | Shopify Plus |
Use Functions through a public Shopify App Store app | Available across plans, subject to the specific Function API |
Use Functions in a custom app | Shopify Plus |
App pricing is separate from your Shopify subscription. A supported Shopify plan also does not mean every app provides every feature. Check both the app’s requirements and the checkout location it supports.
Shopify maintains the current checkout customisation plan comparison and Function API availability.
How the main tools work
UI extensions add what customers see and use
Checkout UI extensions add interface elements at supported locations. Examples include a message, a custom input or a product offer. Shopify provides the components and APIs an app can use. Some blocks can be positioned in the checkout and accounts editor; other extensions have fixed locations.
For example, a gift message input collects information. It still needs somewhere to save that information and a way for your fulfilment team to use it. Decide what happens after the customer fills in the field before adding it.
Shopify Functions apply business rules
Functions customise backend behaviour, such as discounts, delivery or payment customisations, and cart validation. They do not create a visible checkout block.
A message explaining an offer and the rule applying its discount may need separate pieces. Showing “free shipping” in a banner does not create a free-shipping rule. Check that the message matches the actual conditions and resulting checkout total.
Pixels measure customer events
Web pixels collect customer events for analytics and marketing. They run in a sandbox and are not a way to add fields or redesign checkout. App pixels respect Shopify’s customer privacy consent signals.
Moving old tracking code into a new setup needs verification. Test the events your reporting depends on, including purchases, and check that two integrations are not counting the same purchase twice. A working checkout does not prove that every analytics integration is working.
Branding controls the appearance
Standard branding covers familiar changes such as your logo, colours and fonts. Shopify Plus also provides API-based styling options for more detailed checkout branding. Shopify’s checkout styling documentation describes the supported controls.
Choose styling that makes the checkout feel consistent with your store without making labels, errors or buttons harder to read.
Checkout upsells and post-purchase offers are different
A checkout upsell appears before the customer completes the order. A post-purchase offer appears after checkout, before the Thank you page. These use different extension surfaces.
Post-purchase offers have their own access and eligibility requirements. Shopify currently documents the extension API as beta, with access required for live-store use. Offers are also subject to payment, currency and order restrictions, and only one app can be selected for that post-purchase surface. A Thank you page block is not automatically a one-click post-purchase offer.
Check the app’s supported flows against Shopify’s product offer requirements before planning a campaign.
What Checkout Extensibility does not let you do
You cannot treat checkout like an unrestricted theme template. UI extensions run separately from the checkout page and cannot directly edit its HTML. They work within Shopify’s exposed components, APIs and extension locations.
That means a design from a theme page may need to be adapted. An app also cannot remove Shopify’s plan restrictions or guarantee that a particular feature works in every payment flow.
There is no automatic conversion lift from using extensions. A useful message may answer a customer’s question. An unnecessary field or an irrelevant offer may add friction. Start with a specific problem and measure whether the change helps.
How it differs from checkout liquid
The legacy checkout.liquid approach relied on direct template customisations. The current approach uses supported extensions and APIs, which Shopify describes as upgrade-safe. That reduces reliance on the underlying checkout page structure, but apps still need maintenance and testing.
If you are reviewing an older implementation, inventory what it actually did: visible content, fields, discount rules and tracking. Map each requirement to the appropriate current tool rather than trying to copy the old code.
For legacy Thank you and Order status customisations, check the configuration and upgrade guidance in your Shopify admin. Old scripts and incompatible apps may need replacing. Shopify’s upgrade guide explains how to review a non-Plus store’s current status.
How to get started
- Choose one customer problem. For example, shoppers may need to know that a preorder ships separately, or your team may need a gift message attached to the order.
- Confirm the location and plan. Decide whether the feature belongs before payment, after purchase or on the Order status page.
- Choose an app or a custom build. Use an existing app when it covers the requirement. Consider a developer when the workflow needs logic or integrations the app does not support.
- Configure and test before publishing. Review mobile layouts, relevant markets, payment flows, field storage and interactions with other apps.
- Measure the change. Pick a relevant metric, such as checkout completion or gift-message capture. For an upsell, review order value alongside completion and margin, not in isolation.
Using Checkout Components
Checkout Components gives Shopify Plus merchants ready-made components for checkout upsells, content and custom fields. You can start with a component that fits the job rather than building the interface from scratch.
Explore checkout upsells for product recommendations before payment, or browse the component library for messages, banners and inputs.
Start with the smallest change that solves the problem. Add it, test the full customer journey and decide what to keep based on the result.
Blake Waldron
A software engineer with over a decade in ecommerce and 400 Shopify builds delivered under his leadership at a Shopify Platinum Partner. Created Checkout Components out of pure passion which now supports over 600 Shopify Plus stores around the world.
