All articles

AccountCraft Journal

Shopify Customer Account Extensions: Your Options Compared

Compare your options for Shopify customer account extensions: build a custom UI extension, use native settings, or install an app. Includes targets, limits and GDPR notes.

11 min read

Shopify customer account extensions are blocks, pages and buttons that add functionality to New Customer Accounts. You have three ways to get them: build a customer account UI extension yourself, rely on Shopify’s built-in customization settings, or install an app that ships the extension for you. If you want editable customer fields, a wishlist and consent controls without writing code, an app is the shortest path. We built AccountCraft for exactly that case.

This guide explains what the extensions are, where they can appear, what they cannot do, and how the three options compare, with Shopify admin paths where they apply.

AccountCraft
Customize customer accounts without code
AccountCraft lets you build personalized Shopify account pages with editable customer fields, wishlists, and consent controls, without changing your theme.
Install free

TL;DR

  • Customer account UI extensions only work on New Customer Accounts. Legacy customer accounts do not support them, and merchants are migrating away from legacy.
  • Extensions render at three kinds of targets: block, full page and static. They run in a sandbox and use only components Shopify provides.
  • Custom development gives the most control but needs a developer. Native settings cover basics. An app covers the middle ground without code.
  • AccountCraft is a no-code Block Builder with 14 block types, metafield-bound fields, a wishlist and consent blocks. Customer data stays in Shopify.
  • Compliance stays your responsibility. Consent tools help you collect, record and honor choices, but they do not make a store compliant on their own.

Table of Contents

What customer account extensions are

A customer account UI extension is a small piece of app-built interface that a merchant installs at a defined point in the customer account. According to Shopify’s developer documentation, each one is built from three parts: targets that decide where it appears, target APIs that give access to customer and order data, and web components that define which interface elements you can use.

Shopify describes the same idea for merchants in its announcement of customer account extensions: blocks that can sit on pages such as Order index and Order status, or add brand new pages, all behind a single passwordless login.

How they differ from checkout extensions

Checkout UI extensions change the checkout: custom fields, upsells and thank-you page content. Customer account extensions live after sign-in, on order, profile and custom pages. Both use Shopify-provided components, but they have different targets and APIs, so an extension built for one does not drop into the other. Because account pages do not capture payments, the surface is less constrained than checkout, though customer data still needs careful handling, as Power Commerce’s changelog analysis points out.

The three target types

Shopify’s documentation lists three:

Target type Where it renders Typical use
Block Merchant-defined locations on customer account pages Loyalty summary, profile fields, promotional card
Full page A custom page with its own route in the account Wishlist page, warranty registration, saved items
Static Fixed spots tied to a page feature, such as order action buttons or announcement banners Return request button, order notice

Blocks are the ones merchants place themselves in the checkout and customer accounts editor, which is why they suit no-code apps well.

Requirements and limits to know first

New Customer Accounts only. Shopify states that customer account UI extensions are supported only on the new version of customer accounts. Legacy customer accounts do not support them, and since February 26, 2026 legacy accounts are deprecated and unavailable to new stores. If your store still uses legacy customer accounts, migrating is step one. Our guide to Shopify New Customer Accounts covers how to restore the features customers were used to.

Sandboxed rendering. Extensions run in an isolated sandbox, separate from the account page and from other extensions. They cannot reach payment information or the page’s HTML, and they are limited to the components and APIs Shopify exposes (Shopify developer docs).

Styling follows your brand settings. You cannot override the CSS of the UI components, and the account always renders the merchant’s own branding. Extensions cannot render arbitrary HTML, only the elements Shopify provides (web components reference). This is why a pasted HTML snippet will not work and why extensions look consistent with the rest of the account.

Protected customer data needs approval. Apps that want protected customer data must apply for access and pass Shopify’s security review (Shopify developer docs).

Hiding built-in elements is not supported. Per the Shopify Help Center, you can show or hide your own extension content based on customer data, but you cannot hide Shopify’s built-in elements.

Requirements and limits to know first

Option 1: Build a custom extension

A custom extension is the right choice when you need logic no app offers, such as a connection to your own back-office system. Shopify’s docs say the project needs a shopify.extension.toml configuration file plus TSX or JSX files with Preact-based code, and you scaffold it with Shopify CLI (Shopify developer docs).

What that means for a merchant or agency:

  1. You need a developer, a Shopify app to host the extension, and a deploy process.
  2. Plan one extension per target. Shopify staff have suggested this structure in the developer community, so keep targets in separate extensions from the start.
  3. Expect preview quirks. Developers report that a block may show in the shopify app dev preview but not on the live store until it is deployed, released and placed in the editor.
  4. You own maintenance when API versions change.

Performance habits worth copying

Shopify’s performance guidance recommends storing app data in metafields or metaobjects instead of fetching it from your server, running independent requests in parallel with Promise.all, setting a timeout so a slow upstream does not leave the extension hidden, and fetching data before first paint so the block renders once with minimal layout shift. These apply to any extension, including ones you buy. When you evaluate an app, favor those that keep data in Shopify for the same reason.

Option 2: Use Shopify’s native customization

Before adding anything, check what New Customer Accounts already do. The Shopify Help Center says customers can edit their name, email and addresses on the Profile page, and you can set up a cookie banner for selected regions. The same page lists apps and custom solutions as the way to go further.

To adjust branding and placement, go to Settings > Checkout in your Shopify admin and open the customization editor for customer accounts. From there you can set branding and add app blocks to supported pages.

Native settings are free and need no setup. They stop where you want extra data fields, a wishlist, repeatable records or conditional content.

Option 2: Use Shopify's native customization

Option 3: Install an app

An app packages a customer account UI extension and gives you a configuration screen. The App Store has several customer account apps, including AccountCraft, Custlo, Growave and Instant. They differ in focus, so match the tool to the job:

  • You need account pages with editable data, consent and a wishlist: look at a block builder.
  • You need a broad loyalty and reviews suite: look at a platform built around that.
  • Your needs are narrow, such as one banner: a lightweight app or native settings may do.

For each candidate, read the App Store listing for current features and pricing, confirm it supports New Customer Accounts, and check where it stores customer data. Our guide on whether Shopify apps work with New Customer Accounts walks through that check.

How the three options compare

Criteria Custom extension Native settings App (such as AccountCraft)
Coding needed Yes No No
Editable customer fields Yes, you build them Name, email, addresses Yes, configured in the app
Wishlist, repeatable lists Build yourself No Depends on the app
Conditional content Build yourself Limited Depends on the app
Maintenance You Shopify App developer
Best for Unique logic Basics Most merchants and agencies

Where AccountCraft fits

AccountCraft is a Shopify app with a visual Block Builder for New Customer Accounts. It uses official Shopify Customer Account UI Extensions, so there are no theme changes and no code. Here is what exists in the product:

  • 14 block types: text, banner, button, card, update form, single field, record list, SMS consent, privacy consent, wishlist, image, video, spacer and divider.
  • Customer fields bound to customer metafields. Customers view and edit their own data, and it is saved in Shopify. There is no separate customer database. Details are in our guide to letting customers edit metafields.
  • Repeatable record lists for things like pets or vehicles.
  • A built-in wishlist.
  • Conditional rendering by customer tag, metafield, market, B2B and account age.
  • Translations for multilingual stores.

Set up your first block

  1. In your Shopify admin, open Settings > Apps and sales channels and confirm AccountCraft is installed from the Shopify App Store.
  2. Create a customer metafield definition under Settings > Custom data > Customers, for example a text field named “Favorite size”.
  3. In AccountCraft, add an update form or single field block and bind it to that metafield.
  4. Open Settings > Checkout, choose the customer accounts customization editor, and place the block on the Profile page.
  5. Preview with a test customer, then publish. Our walkthrough on adding, testing and measuring account blocks goes deeper.

For layout choices, see what you can change on the account page and our overview of no-code account UI extensions.

Perspective

Most merchants we talk to do not want to run a software project to let a customer update a shoe size. They want the data in Shopify, in a metafield they already use for segmentation and flows, and they want customers to maintain it themselves.

That is why we build on official Customer Account UI Extensions and keep everything inside Shopify. There is no second database to secure, sync or explain in a privacy notice. The block is native to the account, inherits your branding and works with your existing metafields.

We also think consent belongs next to the data it governs. Privacy and SMS consent blocks sit in the same builder as the fields, so the customer sees one coherent account page and you record choices through Shopify’s customer privacy APIs.

Start with the one field or list that would change how you serve customers, ship it, and add blocks from there.

Ivan Signorile

Customer data and privacy responsibilities

An extension that shows or edits personal data raises privacy questions, so decide ownership up front. Under Shopify’s Data Processing Addendum, the merchant acts as data controller and Shopify as data processor for customer personal data, and the merchant is solely responsible for working out its legal and regulatory obligations. Shopify commits to technical and organizational measures to protect that data.

Practical habits for any extension you run:

  • Collect only the fields you need and keep retention short.
  • Use clear consent flows for marketing and tracking, and honor data requests. Power Commerce’s guidance lists these alongside GDPR and CCPA.
  • Review any external service an extension calls and the data it receives.

For a broader view of setting up privacy-minded data collection, see this privacy-first data collection setup.

AccountCraft helps you collect, record and honor customer consent through Shopify’s customer privacy APIs. It does not make a store compliant by itself, and this article is not legal advice. If you sell in the EU, UK or California, ask your own counsel what your consent and data-request flows must include.

Install AccountCraft free

AccountCraft has a free plan, and paid plans (Pro and Plus) are billed through Shopify. Check the Shopify App Store listing for current pricing and plan limits.

If you are migrating from legacy customer accounts, or you want customers to manage their own data and wishlist on New Customer Accounts, you can see the plans on our site and install AccountCraft free from the Shopify App Store.

AccountCraft

FAQ

Do customer account UI extensions work on legacy customer accounts?

No. Shopify’s documentation says they are supported only on New Customer Accounts. Legacy customer accounts were also deprecated for new stores as of February 26, 2026, so migration is the first step.

Can I add a customer account extension without coding?

Yes. Extensions are installed from apps and placed in the customization editor, so no code is needed for blocks that an app provides. Custom logic that no app offers needs a developer using Shopify CLI.

Can an extension change the look of the account page?

Only within Shopify’s rules. Extensions use Shopify-provided components, cannot override component CSS and always render with your own branding (web components reference).

Where should an extension store customer data?

Shopify recommends metafields or metaobjects over fetching from your own server for performance (extension performance guide). AccountCraft binds its fields to customer metafields, so the data stays in Shopify.

Sources