accountcraft Install free
All articles

AccountCraft Journal

No Code Shopify Account UI Extensions That Stay GDPR Ready

No code Shopify setup for wishlists, profile fields, and GDPR consent in New Customer Accounts. Check Customer Privacy API integration.

9 min read

Account UI extensions for Shopify let you add wishlists, editable profile fields, and consent tools to New Customer Accounts without touching theme code. You build and place these features using the checkout and accounts editor, choosing from app blocks that plug directly into the customer portal. The immediate step is picking a compatible app and testing its blocks inside that editor before you commit to a layout.

TL;DR:

  • App blocks for customer accounts require compatible apps and must be tested within the checkout and accounts editor before layout implementation.
  • Customizations made through theme files do not transfer to the new account system, which is sandboxed and relies on app-based extensions.
  • Most features like wishlists and custom profile fields need third-party apps, as Shopify’s native offerings cover only basic profile editing and order history.
  • Extensions handling personal data must utilize Shopify’s Customer Privacy API and request appropriate consent capabilities to stay GDPR compliant.
  • Rebuilding account pages involves inventorying existing features, creating metafields with proper API access, and thoroughly testing all configurations before deployment.
Accountcraft
Build GDPR Ready Customer Accounts
Create personalized Shopify account pages with editable customer data, consent management, wishlists, and no coding or theme alterations.
Visit AccountCraft

Table of Contents

New Customer Accounts versus legacy accounts: what changed

New Customer Accounts live on a Shopify-hosted subdomain rather than inside your theme, and customers sign in without a password, using a one-time code instead. That shift gives every store the same secure, unified account portal regardless of theme, but it also means the old rules for customization no longer apply.

If you previously edited account pages through Liquid templates in your theme, those customizations will not carry over. Legacy account architecture has to be rebuilt using apps or Customer Account UI Extensions, since the new system renders blocks through a sandboxed extension framework instead of theme files. This is widely cited as the main hurdle merchants face when upgrading from legacy accounts.

The upside is that app-based blocks are upgrade-safe. You configure everything from your Shopify admin through the checkout and accounts editor, where you add, rearrange, and toggle blocks much like customizing a checkout page. No developer handoff is required for most changes, and future Shopify platform updates won’t break your layout the way theme edits used to.

What account UI extension blocks can actually add

Once you’re in the checkout and accounts editor, app blocks can render into several account targets: the order index, individual order status pages, the profile page, and custom pages you create inside the account portal. Shopify’s own rollout of Customer Account Extensions framed these blocks as additions you can place in minutes, with multiple launch partners building for order tracking, loyalty, and personalization on launch day.

Practical use cases merchants ask for most often include:

  • A wishlist page where customers save products and revisit them from their account.
  • A loyalty or rewards panel showing point balances and redemption options.
  • A self-service returns flow attached to the order status page.
  • Enhanced order pages with tracking details, reorder buttons, or subscription management.
  • Custom profile fields for preferences, sizing, or other data specific to your store.

Not every feature needs an app. Shopify’s own documentation distinguishes between what’s built into the platform by default, what requires an App Store app, and what demands a custom or headless build. Basic profile editing and order history are native; wishlists, loyalty, and custom data fields almost always require an app because Shopify doesn’t ship them out of the box.

Account extensions that collect or display personal data need a way to check and respect consent, and that’s what the Customer Privacy API is for. It gives extensions functions to read a buyer’s current consent state, determine whether a consent banner should appear with shouldShowBanner, and apply consent changes a customer makes inside the account portal.

For an app to write consent changes rather than just read them, it has to request the collect_buyer_consent capability. Without that capability, an extension can display consent status but cannot update it, which matters if you’re relying on an app to manage opt-ins and opt-outs on your behalf. Shopify’s developer documentation also recommends checking region flags such as saleOfDataRegion before showing data-sale opt-out controls, since consent requirements differ by market and a one-size banner can misrepresent a customer’s actual rights.

Two practical checks keep you compliant. First, confirm that any app you install for account customization actually calls shopify.customerPrivacy rather than rolling its own consent logic, since the former stays synced with Shopify’s platform-level settings. Second, pair that app-level check with your store’s own configuration under Settings > Customer privacy, where Shopify exposes cookie banners, opt-out controls, and regional templates you control directly. Because these extensions run in a sandboxed environment using vetted platform APIs, they carry less compliance risk than custom Liquid code that touches customer data directly.

GDPR consent checks for account extensions

Step-by-step: rebuilding and launching your account pages

Moving from legacy accounts to a fully customized New Customer Accounts setup follows a predictable sequence. Here’s the order that avoids rework.

  1. Inventory what you’re replacing. List every custom field, layout element, or account feature from your old setup and match each to an equivalent app block or native feature.
  2. Create metafield definitions for editable data. For any field a customer should edit themselves, such as birthday or preferences, set the metafield definition’s Customer Account API access to Read and write. Without that setting, the field either won’t appear or will be read-only in the account portal.
  3. Install your chosen app and add its blocks. Open the checkout and accounts editor, then drag the app’s blocks into place, for example adding a dedicated wishlist page to the account navigation.
  4. Configure and verify consent handling. Confirm the app reads and applies consent through the Customer Privacy API, and cross-check your Settings > Customer privacy configuration so banners and opt-outs match your target markets.
  5. Test before you rely on it. Walk through sign-in, profile editing, consent prompts, and order views as a test customer. Shopify preserves a rollback window if a configuration change breaks something, so test changes before peak traffic rather than during it.

Pro Tip: Test metafield edits with a real customer account, not just the admin preview, since write access behaves differently once a customer is actually signed in.

Designing account pages that customers actually use

A block builder gives you flexibility, but flexibility without structure leads to cluttered account pages. Put order status and recent purchases near the top, since that’s the single most common reason customers log in. Wishlist or saved items come next, followed by editable profile fields toward the bottom where they’re available but not distracting.

Hierarchical customer account page blocks

Conditional visibility is worth using deliberately rather than everywhere. A B2B account might show net payment terms and a reorder tool that a B2C customer never needs, and hiding irrelevant blocks per customer type keeps the page focused.

A few other habits separate account pages that get used from ones that get ignored:

  • Match the visual style of your checkout so the account portal feels like a continuation of the brand, not a separate app.
  • Label actions plainly: “Edit shipping address” works better than vague icons or abbreviations.
  • Keep each block to one clear action rather than stacking multiple decisions into a single panel.

Profile completion, repeat purchase rate, and wishlist-to-cart conversion are the three metrics worth tracking once your account pages go live, since they directly reflect whether customers are engaging with the new blocks rather than ignoring them.

Why AccountCraft fits this setup

AccountCraft is built as a visual Block Builder specifically for New Customer Accounts, so the workflow described above, placing blocks through the checkout and accounts editor, handling metafields, adding a wishlist, maps directly to how it works. It’s positioned as a no-code tool: you build editable profile fields, repeatable lists, and conditional visibility rules without writing extension code or touching your theme.

On the privacy side, the app includes consent management tied to Shopify’s Customer Privacy API, and customer data stays inside Shopify rather than syncing to an external database. Plans run as Free, Pro, and Plus, scaling with how much customization a store needs. For merchants without in-house developer time, this kind of setup typically means a faster rollout than a custom extension build.

Our honest take on no-code versus custom builds

A no-code block builder is the right call for most stores: wishlists, editable profile fields, and consent UIs are standard needs that don’t justify a developer contract. Hire a developer instead when you need bespoke data flows, deep ERP integration, or a headless storefront where standard extensions don’t apply.

Our practical next step: pick an app, test its blocks live in the checkout and accounts editor, and confirm its consent handling before you launch.

— Barikreativa

Try AccountCraft on your own account pages

The app is a visual Block Builder for New Customer Accounts, so you can add wishlists, editable fields, and GDPR-ready consent management while your customer data stays inside Shopify. No theme edits, no extension code, just blocks you place yourself.

Accountcraft

Plan What it’s for
Free Getting started with basic account customization
Pro Expanded block options for growing stores
Plus Full customization for stores with advanced needs

Visit the AccountCraft landing page to start on the Free plan or request a demo.

FAQ

What are Customer Account UI Extensions in Shopify?

They’re app-based blocks you add to Shopify’s New Customer Accounts through the checkout and accounts editor, letting you build wishlists, editable fields, and other account features without code. Shopify introduced this extension framework to replace theme-based account customization.

Do legacy account customizations carry over to New Customer Accounts?

No, legacy Liquid-based account customizations do not migrate automatically. You need to rebuild custom fields and layouts using compatible apps or UI extensions.

How do I let customers edit their own profile data?

You create a metafield definition for that data and set its Customer Account API access to Read and write. Without that setting, the field stays read-only or doesn’t appear in the account portal at all.

Compatible extensions use Shopify’s Customer Privacy API to read a customer’s consent state, check whether a banner should display, and apply any changes the customer makes. Look for an app that calls shopify.customerPrivacy directly rather than managing consent outside Shopify’s system.

Is AccountCraft a good fit for adding a wishlist to customer accounts?

AccountCraft’s Block Builder is designed for exactly this kind of addition, letting you place a wishlist page, editable fields, and consent tools through the checkout and accounts editor without code. Plans are available as Free, Pro, and Plus, depending on how much customization your store needs.

Sources