All articles

AccountCraft Journal

Customer Account UI Limits: What Shopify Lets You Change

Shopify's customer account UI extensions have real limits: bundle size, targets, sandboxing, order status rules. Here is what they are and how to plan around them.

13 min read

Shopify’s New Customer Accounts can be customized, but only inside boundaries Shopify sets. Extensions sit in defined slots, run in a sandbox with no access to the page’s HTML, and must fit a compiled bundle of 64 KB (128 KB for full-page extensions). Once you know those boundaries, you can plan account pages that work inside them instead of fighting them.

This guide covers each limit in plain terms, shows what it means for your store, and gives you a practical way to build the account experience you want without code or theme changes.

AccountCraft
apps.shopify.com
Build Account Pages Within Shopify’s Limits
AccountCraft’s Block Builder lets you customize Shopify New Customer Accounts with editable fields, wishlists, and consent management, without code or theme changes.
Install AccountCraft

TL;DR

  • Customer account UI extensions only work on New Customer Accounts. Legacy customer accounts don’t support them, and Shopify has deprecated those accounts.
  • Extensions appear only in Shopify’s targets (Block, Full page and Static). They can’t touch the account page’s HTML, CSS or theme files.
  • Compiled bundles are capped at 64 KB, or 128 KB for full-page customer account extensions, enforced when the app is deployed.
  • App proxies don’t work inside the extension context. Data should come from the Customer Account API, metafields or metaobjects.
  • A no-code builder like AccountCraft works within these limits for you, so you get editable fields, wishlists and consent blocks without writing an extension.

Table of Contents

What customer account UI extensions are

Customer account UI extensions are small apps that render inside Shopify’s own customer account pages. According to Shopify’s developer documentation, they plug into order status pages, profile sections and order action buttons. Common uses include loyalty information, subscription interfaces, shipment tracking and return requests. Full-page extensions can power bigger things, such as a loyalty dashboard or a subscription management area.

The same page describes three interconnected parts:

  1. Targets decide where the extension appears.
  2. Target APIs give access to customer and order data.
  3. Web components define which interface elements you can use.

Every limit below traces back to one of these three. You can only put things where targets exist, read only the data the APIs expose, and build only with the components Shopify provides.

Limit 1: Only New Customer Accounts support extensions

The most basic limit is the account system itself. Per Shopify’s guide to building apps for customer accounts, extensions are supported only on the new version of customer accounts. As of February 26, 2026, legacy customer accounts are deprecated, are no longer available to new stores, and all merchants must upgrade.

If your store is still on legacy customer accounts, that is your first task. Check where you stand:

  1. In your Shopify admin, go to Settings > Customer accounts.
  2. Confirm that New Customer Accounts is the selected version.
  3. If you are mid-migration, review what you rely on today (custom fields, account page edits in the theme) so you can rebuild it with extensions.

If you are planning the move, our walkthrough on restoring legacy UX with New Customer Accounts lists what typically needs rebuilding.

Limit 2: Extensions live in targets, not anywhere you like

Shopify’s documentation on targets groups them into three types:

Target type Where it appears Typical use
Block Merchant-defined locations within customer account pages Extra sections on profile or order pages
Full page Custom pages with their own routes Loyalty dashboards, wishlists, subscription management
Static Fixed locations tied to specific page features Order action buttons, announcement banners

The Shopify Help Center puts the consequence simply: extensions can be placed only in defined slots within the built-in customer accounts UI. If you need total control of the front end, the Help Center points to using the Customer Account API with a headless storefront. That is a different project with its own build cost.

For most merchants, slots are enough. A profile block for preferences, a full page for a wishlist, a banner on order pages: these cover the bulk of account-page requests we see. For layout questions, see what you can change on the Shopify account page.

Scoping by market and B2B

Even when a target renders for every customer by default, the Targets documentation says you can use the checkout and accounts editor to scope an extension to specific markets, including B2B company locations. That is useful when a block should only appear for wholesale buyers or one region.

Limit 3: No access to the page’s HTML or assets

This is the limit that surprises people coming from theme work. Shopify states that extensions run in an isolated sandbox separate from the customer account page. They have no access to sensitive payment information, no access to the page’s HTML or other assets, and only limited access to global web APIs. They are restricted to the UI components and APIs Shopify exposes.

In practice:

  • You can’t inject a snippet of custom HTML or a script tag into the account page.
  • You can’t restyle the page with your own CSS file.
  • You can’t edit account templates in the theme, because New Customer Accounts are not rendered by your theme.

This explains the threads you see on the Shopify community forums from developers trying to drop custom HTML into the profile page. The answer is the same each time: build with the supported components inside a target.

The upside is consistency. Because every extension uses Shopify’s components, your account pages match the look of checkout and stay secure behind the single, passwordless login that Shopify describes in its introduction to customer account extensions.

Limit 4: Bundle size caps at 64 KB (128 KB for full page)

The limit most developers hit is bundle size. Shopify’s bundle size guidance says UI extensions on API version 2025-10 and later run on Remote DOM, which limits the JavaScript bundle to 64 KB compressed. Full-page customer account extensions get 128 KB, because they can support end-to-end account-management workflows. Shopify enforces the cap at deployment, so an oversized extension simply won’t ship.

What this means for you as a merchant:

  • One extension, one job. A single extension that tries to do wishlists, forms, loyalty and returns will outgrow the cap. Smaller blocks that each do one thing fit comfortably.
  • Avoid heavy libraries. Date pickers, charting packages and large utility libraries are the usual culprits for developers.
  • Rely on platform components. Shopify’s web components cost you nothing in bundle size.

Fast pages also help the customers who return to manage orders, and account-page speed feeds the same retention goals covered in these Shopify conversion strategies.

Agencies commissioning a custom extension should ask for the compiled, compressed size early in the project, not at the end.

Limit 5: Data access rules and no app proxies

A frequent developer question: can the extension call my backend through an app proxy path like /apps/api? No. App proxies aren’t supported in the customer account extension context, which is why those fetch calls fail.

What works instead:

  • Customer Account API. Shopify’s documentation says you can query the GraphQL Customer Account API directly from an extension using the global fetch function, with authentication handled automatically. The data available depends on the buyer’s authentication state and your app’s access scopes.
  • Metafields. According to Shopify’s performance guidance, all customer account targets can read and write metafields through the Customer Account API. On order status targets, you can read metafields without a network call using appMetafields.
  • Metafields or metaobjects over your own server. The same page recommends storing app data there instead of fetching from your server, and treating the Storefront API as a last resort for catalog data the Customer Account API doesn’t expose.
  • Session tokens for your backend. The Session Token API issues signed JWTs meant for your backend only. They expire after 5 minutes, and the sub claim appears only when the customer is signed in and the app has the read_customers scope.

The merchant takeaway: design your account data to live in Shopify. Customer fields bound to customer metafields are the cleanest pattern, and you can read more about it in our guide to custom fields on Shopify accounts.

Limit 6: Order status page and pending orders

The order status page has its own rules, and they explain many of the “why doesn’t my extension show up” questions.

  • Per Shopify’s order status page documentation, the unauthenticated order status page doesn’t support extensions.
  • In the pre-authenticated state (a customer arriving from an order notification link), the customer can see all data for that one order without logging in, but not customer data or other orders’ data. Navigating elsewhere or taking an action prompts a login.
  • In that state, buyerIdentity.customer.id is exposed only when the customer is logged in. Customer Account API queries must stick to fields marked as pre-auth accessible, or they return an “Access denied” error.
  • The Order index includes draft orders the customer has been invoiced for, per the customer accounts build guide. That is why developers asking about pending or draft orders find the behavior narrower than expected.
  • Shopify’s pre-auth extension guidance says all targets on the order status page render in both pre-authenticated and authenticated states, and each extension should include only one target.

If a block depends on knowing who the customer is (a loyalty balance, say), plan for the pre-authenticated case where that identity may not be available.

Account pages are a natural place to let customers see and change their marketing and tracking preferences. The Customer Privacy API gives extensions access to a buyer’s tracking consent preferences and lets them apply consent changes. Applying a change requires the collect_buyer_consent capability and access to protected customer data.

Customer reviewing consent preferences on phone

The documentation also suggests using shouldShowBanner for the initial state and saleOfDataRegion and region to decide whether extra opt-out controls apply for the buyer’s location, such as under CCPA in California.

Two practical points:

  • Collecting and recording consent is a technical task. Deciding what your store must collect is a legal one. Your counsel or privacy advisor owns that decision, and no app can settle it for you.
  • Keep consent controls on a page customers can find, such as the profile or a dedicated preferences page.

How to plan around the limits: a step-by-step checklist

Use this order when scoping account customization in your Shopify admin:

  1. Confirm New Customer Accounts under Settings > Customer accounts.
  2. List what customers need to do: update details, manage preferences, save products, view records such as pets or vehicles, manage consent.
  3. Map each need to a target. Profile additions are usually Block targets. A wishlist or preferences hub suits a full page. Order-page messages suit order status targets.
  4. Define data first. Go to Settings > Custom data > Customers and create the metafield definitions you need, so fields have a home in Shopify.
  5. Split large ideas into small blocks, each with one job, to stay well under bundle caps.
  6. Scope by audience with the checkout and accounts editor if wholesale or regional customers need different content.
  7. Test as a logged-in customer and as a pre-auth visitor from an order notification link.

For navigation specifics, see menus, quick links and extensions. For a broader UX plan, our step-by-step guide to improving Shopify account UX goes further.

Build, buy or no-code: what fits which team

Approach Best for Limits to manage
Custom extension Unique logic, deep backend integration Bundle caps, developer time, ongoing API version updates
Headless with Customer Account API Complete front-end control Full build and hosting of your own account UI
No-code builder Fast setup of fields, wishlists and consent Works with Shopify’s blocks and targets

Most stores that want editable fields, a wishlist and consent controls don’t need a custom build. The limits above are real for developers writing extensions from scratch, and a ready-made builder takes that work off your plate.

Perspective

Every limit in this article comes from one design decision: Shopify keeps the account page secure and consistent by running extensions in a sandbox. We think that is the right foundation, because it means customer data stays in Shopify and your account pages keep working when the platform updates.

That is why we built AccountCraft only on official Customer Account UI Extensions and Shopify’s own APIs. There is no theme editing and no separate customer database. Fields bind to customer metafields, so what a customer edits is the same data you see in your admin.

Our advice to merchants and agencies: stop asking how to get around the sandbox, and start asking which blocks your customers actually use. A well-chosen set of fields, a wishlist and a clear consent block usually beats a heavy custom build, and you can ship it in an afternoon.

Ivan Signorile

Build inside the limits with AccountCraft

AccountCraft is a Shopify app with a visual Block Builder for New Customer Accounts. You arrange 14 block types (text, banner, button, card, update form, single field, record list, SMS consent, privacy consent, wishlist, image, video, spacer and divider) without code or theme changes. Customer fields bind to customer metafields, record lists handle repeatable entries such as pets or vehicles, and blocks can show or hide by customer tag, metafield, market, B2B status or account age. Translations are supported too.

AccountCraft

There is a free plan, and paid plans (Pro and Plus) are billed through Shopify. For current pricing, check the Shopify App Store listing. You can see the plans on our site, or read our guide to customizing Shopify accounts first. Ready to start? Install AccountCraft free from the Shopify App Store.

The privacy consent and SMS consent blocks help you collect, record and honor customer consent through Shopify’s customer privacy APIs. Compliance remains your responsibility as the merchant.

FAQ

Can I add custom HTML or CSS to the New Customer Accounts page?

No. Extensions run in a sandbox with no access to the account page’s HTML or other assets, and are limited to the UI components and APIs Shopify exposes. To change what customers see, use supported blocks and targets, or a builder that works through them.

What is the size limit for a customer account UI extension?

On API version 2025-10 and later, a compiled extension is limited to 64 KB compressed. Full-page customer account extensions can be up to 128 KB. Shopify enforces this when the app is deployed.

Do customer account extensions work on legacy customer accounts?

No. They are supported only on New Customer Accounts. Shopify deprecated legacy customer accounts as of February 26, 2026, so merchants should complete the upgrade before planning account customization.

Can an extension use an app proxy to reach my server?

No, app proxies aren’t supported in this context. Read and write data through the Customer Account API, or store it in metafields or metaobjects. If you do call your own backend, use the session token, which is meant for your backend only.

Sources