Insights/Article

Shopify Checkout Customization: What Merchants Can Change and What They Cannot

Devina MohanDevina MohanShopify Development
Illustrated checkout layout with an order summary, form fields, and a highlighted custom content block

Shopify checkout customization is possible, but it works inside defined boundaries. Merchants can change branding, add supported app blocks, and adjust certain payment, delivery, and discount logic. They cannot freely edit checkout HTML, inject arbitrary scripts, or reach into payment fields. What is available also depends heavily on the plan, and on the checkout page you want to change.

This guide is for Shopify merchants and ecommerce managers scoping a checkout change. It reflects Shopify's documentation as checked in November 2026. Shopify revises these capabilities regularly, so confirm the details for any feature your project depends on.

Quick answer: what is possible on each plan

CapabilityBasic, Grow, and Advanced level plansShopify Plus
Logo, colors, fonts, and background in the checkout and accounts editorYesYes
Eligible apps on Thank you and Order status pagesYesYes
Apps on information, shipping, and payment stepsNoYes
Checkout Branding APINoYes
Public apps that use Shopify FunctionsYesYes
Custom apps that use Shopify FunctionsNoYes
Web pixels for measurementYesYes

Shopify's checkout technologies reference excludes the Starter plan from these developer technologies. Plan names change over time, so check the current wording against your own subscription before committing to a build.

Ready to improve your Shopify store?

Get a sharper plan for Shopify growth.

Talk through theme decisions, speed issues, merchandising, product discovery, and conversion improvements with the Zeroradius team.

What merchants can change without code

The checkout and accounts editor is separate from the theme editor. It manages the checkout, Thank you, Order status, and customer account pages in one place. Merchants can add a logo, set a background color or image, and change colors and fonts.

Shopify also provides settings and native tools for common requirements, including address autocomplete, shipping profiles, local delivery, in-store pickup, and translated checkout text. It is worth working through these first. Many requests that arrive as development tickets are really configuration tasks.

Shopify's Checkout Blocks app separates capabilities by plan. Basic and higher plans can use its static and dynamic content blocks on the Thank you and Order status pages; placement on checkout pages and the app's other features require Plus. Check the specific block and placement before estimating the work.

Diagram of a checkout page with marked slots for added blocks beside a locked payment panel
Custom content goes into supported locations. The page structure and payment fields stay under Shopify's control.

How checkout extensibility works

Checkout extensibility is a set of separate mechanisms, each with its own job. Choosing the right one is most of the scoping work.

Checkout UI extensions add interface elements

Checkout UI extensions add content or inputs, such as a delivery instruction field, a gift note, or a post-order survey. Block extensions are positioned by the merchant in the editor. Static extensions appear in fixed locations. Extensions on the information, shipping, and payment steps need Shopify Plus, while Thank you and Order status extensions are available more widely.

These extensions run in an isolated sandbox. They cannot access the checkout DOM, other page assets, or sensitive payment data. Shopify caps bundles at 64 KB, so a large embedded experience has to be rethought, not simply ported.

Shopify Functions change backend logic

Shopify Functions handle server-side rules: custom discount types, hiding or reordering payment options, renaming or sorting delivery options, and blocking checkout when validation fails. A store on any eligible plan can use a public app containing Functions. A bespoke app containing Functions requires Plus.

Payment rules have one further limit that surprises teams. In the US and Canada, non-Plus stores can customize only non-credit card payment methods. Payment terms and credit card field customization are Plus features.

Web pixels handle analytics

Marketing and conversion tracking now belongs in app pixels or custom pixels, not in code pasted into checkout pages. Pixels run separately from the page, so a tag written for the old approach may need rebuilding, not copying.

Branding API and post-purchase extensions

Plus merchants can use the Checkout Branding API for finer visual control than the editor offers, such as corner radius on form fields. Post-purchase extensions show an offer after payment and before the Thank you page. As of this review, Shopify still lists them as a beta: they work freely in development stores, but live stores must request access.

Deprecated methods you should no longer plan around

Older advice is the most common source of bad checkout scoping. Three changes matter here:

  • checkout.liquid: Shopify ended support on the information, shipping, and payment pages on August 13, 2024.
  • Shopify Scripts: Shopify's April 2026 notice set June 30, 2026 as the date Scripts stop executing. Discount, shipping, and payment logic should now live in Functions or suitable apps.
  • Script tags: Shopify's deprecation guide says Order status script tags stop working for all stores on August 26, 2026. Apps can no longer create or update script tags from October 1, 2026, and existing storefront script tags stop loading on March 1, 2027. Use customer account UI extensions or pixels for Order status page use cases, and theme app extensions or pixels on the storefront.

If your store still relies on any of these, check whether the behavior is actually running today. Tracking and post-order widgets can disappear quietly without any visible error on the storefront.

What Shopify checkout does not support

  • Editing checkout HTML or restructuring the page freely.
  • Adding arbitrary JavaScript through a theme file to change checkout behavior.
  • Reading or restyling card data outside the provided controls.
  • Running a customization from a theme and expecting it to apply in checkout. Checkout is managed separately.
  • Using custom in-checkout UI on a plan below Plus, even through a private app.

These limits are a design constraint, not a defect to route around. A proposal that promises to bypass them should explain exactly which supported mechanism it uses.

Three stacked tiers of checkout capability, with the top tier containing the most unlocked modules
Map each requirement to a plan and mechanism before estimating the work.

Payment, shipping, discount, and post-purchase considerations

Payments. Hiding a method can have commercial effects. Shopify warns that hiding accelerated checkout options may reduce conversion, so make such rules narrow and measure the result.

Shipping. Start with shipping profiles and native delivery settings. Use Functions for rules they cannot express. Our Shopify shipping strategy guide covers the commercial decisions that should come first.

Discounts. Check how a custom discount combines with existing codes and automatic discounts, including the cases where one should not apply.

Post-purchase offers. Shopify's documentation lists important eligibility limits: the page isn't shown when the initial order uses a gift card or a payment method other than a credit card, and only one post-purchase app can be active at a time. Check payment mix and app selection before estimating the likely reach.

Compatibility, accessibility, analytics, and testing

  • Compatibility: Confirm each app supports your checkout pages, plan, markets, and languages. Up to three extensions can share one block location, which can constrain crowded layouts.
  • Accessibility: Shopify maintains accessibility in its own checkout components, but added content is still your responsibility. Test labels, keyboard use, error messages, and reading order.
  • Analytics: Compare pixel events against orders before and after a change. Note that pixel-based analytics report only the initial purchase when a post-purchase offer is accepted.
  • Testing: Test on a development store or draft configuration. Cover mobile, guest and logged-in buyers, each payment method, each market, discount combinations, and failed validation.

A practical scoping checklist

  1. Write the requirement as a buyer or business outcome, not as a screen change.
  2. Identify which page it affects: information, shipping, payment, post-purchase, Thank you, or Order status.
  3. Check for a native setting or a free Shopify tool.
  4. Look for a maintained public app that supports your plan.
  5. Only then consider a custom extension or Function, and confirm plan eligibility.
  6. Audit any existing Scripts, checkout.liquid code, script tags, and pasted tracking.
  7. Define how you will measure the change and how you will roll it back.

Common mistakes to avoid

  • Assuming a theme developer can change checkout. Theme code and checkout extensions are different systems.
  • Upgrading to Plus for one small change. Confirm whether a public app or a Thank you page extension solves it first.
  • Adding too much to checkout. Every extra field and offer competes with completing the order. Our guide to why Shopify stores fail to convert looks at friction across the wider journey.
  • Treating app installation as finished work. Apps still need integration planning and testing, particularly when several touch checkout.
  • Relying on tutorials written before 2024. Many still recommend methods Shopify has since retired. Check the current deprecation dates and the replacement mechanism before reusing old instructions.

Plan a checkout change that stays supported

For requirements that go beyond settings and public apps, Zeroradius can audit your existing checkout code, map each need to a supported mechanism, and build what is justified. Explore our Shopify Plus Development Services for in-checkout extensions and bespoke Functions, or our custom Shopify development work if you are on another plan and need help with what it allows.

Frequently asked questions

Have questions?

Yes, within limits. Non-Plus merchants can adjust branding in the editor, use eligible apps on the Thank you and Order status pages, use web pixels, and install public apps that contain Functions. Apps on the information, shipping, and payment steps require Plus.

Not for the in-checkout pages. Shopify ended checkout.liquid customizations on the information, shipping, and payment pages on August 13, 2024. New work should use the checkout and accounts editor, extensions, and Functions.

Custom fields can be added through checkout UI extensions. On the information, shipping, and payment steps, this requires Shopify Plus. On other plans, consider collecting the information on the cart or product page, or on the Thank you page if it can wait until after purchase.

Generally yes, through Shopify Functions delivered by a public app, or by a custom app on Plus. In the US and Canada, non-Plus stores can customize only non-credit card payment methods.

Not as arbitrary page code. Interface additions run in sandboxed checkout UI extensions without DOM access, and tracking belongs in web pixels.

More insights

Keep reading