Build a Shopify Preference Center in New Customer Accounts

Shopify has no single “preference center” screen you switch on. What you get is a set of pieces: marketing consent, the customer Profile page, cookie preferences and customer metafields. You assemble them into one place where customers say what they want to hear about and what you may know about them. This guide shows what Shopify gives you natively, what it leaves out, and how to build the missing part inside New Customer Accounts without touching your theme.

TL;DR

• A preference center is the page where customers change what communications they get and what details you store. In Shopify, it lives on the New Customer Accounts Profile page.
• Store each preference in a customer metafield. Structured metafields are more reliable than free-text notes or tags.
• Shopify’s native Profile page covers names, emails and addresses. Custom preferences need a customer account UI extension, which an app like AccountCraft provides without code.
• Let customers withdraw consent as easily as they gave it, and keep a record. Compliance remains your responsibility.
• Use customer tags and metafields to decide who sees which account content.

Table of Contents

• What a preference center means for a Shopify store
• What Shopify gives customers out of the box
• What preference data you can collect
• Three ways to build the preference center
• Step by step: build it with AccountCraft
• Using customer tags and metafields to show the right content
• Consent, withdrawal and records
• Where the data goes after customers save it
• Our perspective
• Try it on your store
• FAQ
• Sources

What a preference center means for a Shopify store

In email marketing, a preference center is the place where customers change what communications they receive, usually reached from their account profile. On Shopify the idea is wider, because the same account can also hold data you collect for personalization: a shoe size, a preferred pickup location, a pet’s name, a birthday.

That gives you two kinds of preferences to plan for:

1. Communication preferences. Email, SMS and WhatsApp consent, plus any topics or frequency you offer.
2. Profile preferences. Details that shape the shopping experience, such as sizes, interests, or the vehicles and pets a customer owns.

Both need the same three things: a place customers can find, a storage location you can read from other tools, and a record of what they agreed to.

What Shopify gives customers out of the box

Before building anything, know what already exists.

The Profile page. Customers can update their name, email address and shipping addresses in their account by clicking their initials and choosing Profile. Shopify describes this page as intended for personal information such as names and addresses, per its customer accounts developer documentation. It has no field for “I want product news but not sale alerts” or “my size is M”.

Marketing consent at checkout and sign-in. Shopify can show an email marketing consent checkbox at checkout or sign-in, with a setting for whether it is preselected by region. Forms created with Shopify’s forms app can collect consent for email, SMS and WhatsApp through a consent checkbox or implicit sign-up on submission.

Cookie and data-collection preferences. In the Customer privacy section of the admin you can manage automated privacy policies and cookie banners. Customers reach their data-collection choices through the banner link or, where the banner is not active on checkout, a Cookie preferences link in the footer.

That is a solid base for consent. The gap is everything in between: a dedicated, branded page in the account where customers see and edit the preferences you collect.

What preference data you can collect

Shopify’s own guidance on customer data says businesses can collect demographic, preferential, behavioral, identity and engagement data to segment and personalize. It also notes that gathering first-party data directly from customers clarifies shopping behavior, and that explicit consent helps merchants stay on the right side of privacy rules.

For storage, the right container is a customer metafield. Shopify’s POS guidance shows how customer metafields hold structured details such as preferences, birthdays, loyalty data and clothing sizes, and argues that generic notes or tags are error-prone and rarely scale for marketing. Tags still have a job, which we cover below, but they should label groups, not store values.

A practical starting list:

Keep the list short. Power Commerce advises keeping preference centers simple to avoid friction and starting with the distinctions customers actually care about. Three or four well-chosen fields beat fifteen that nobody fills in.

Three ways to build the preference center

Option 1: Native settings only

Use the consent checkbox, cookie banner and Profile page as they come. It costs nothing and needs no setup, but customers cannot edit custom data, and you will end up collecting preferences through forms and support emails.

Option 2: A custom customer account UI extension

Shopify’s documentation describes the official route. You define a customer metafield and expose it through a customer account UI extension on the Profile page. The definition sets a customer-facing name and description, a data type, and customer account access of read_write, while admin access can be set separately to merchant_read. The extension renders a section, a link that opens a modal and a text input, then writes the change with the Customer Account API’s metafieldsSet mutation. Shopify’s example collects a preferred nickname and ships localization files for several languages.

Two requirements matter for developers. Reading or writing customer metafields needs the customer_read_customers and customer_write_customers scopes, and the API requires Level 1 Protected Customer Data access, which the app must request. Writes are supported from the 2024-07 API version.

This route gives full control, but you need a developer, an app to host the extension, and ongoing maintenance for every new field.

Option 3: A block builder app

AccountCraft builds that same kind of extension for you. It uses Shopify’s official Customer Account UI Extensions, so there are no theme changes and no code. Customer data stays in Shopify, because fields are bound to customer metafields and there is no separate customer database. For most merchants, this is the fastest way to a working preference center.

Step by step: build it with AccountCraft

These steps assume you already use New Customer Accounts. If you are still moving over from legacy customer accounts, start with our migration overview first.

1. Create the metafield definitions

In the Shopify admin, go to Settings > Custom data > Customers and add a definition for each preference. Give each a clear name and pick the type that fits: a true or false value for a topic opt-in, single line text for a nickname, a date for a birthday. Set customer account access to read and write, and leave admin access at read only if staff should not edit these values by hand.

Our guide on letting customers edit Shopify customer metafields walks through the access settings in more detail.

2. Install the app and open the builder

Install AccountCraft from the Shopify App Store, then open it from Apps in the admin. A free plan exists, and the paid Pro and Plus plans are billed through Shopify; check the App Store listing for current pricing.

3. Add blocks to your account page

The Block Builder offers 14 block types: text, banner, button, card, update form, single field, record list, SMS consent, privacy consent, wishlist, image, video, spacer and divider. For a preference center, the useful ones are:

• Update form. Groups several metafield-bound fields so customers edit them together and save once.
• Single field. One editable value, such as a preferred contact channel.
• Privacy consent. Lets customers see and change their consent through Shopify’s consent APIs.
• SMS consent. The same, for text messages.
• Record list. Repeatable entries, for example several pets or vehicles.
• Text, banner and card. Explain why you ask and what customers get in return.

Bind each field to the metafield you defined in step 1. Add a short sentence under each explaining its purpose. People fill in fields when they understand the benefit.

4. Add translations

If you sell in more than one language, add translations for every label and description so the preference center matches the language of the account. Consent wording especially should be clear in the customer’s own language.

5. Preview and test with a real account

Sign in to your storefront as a test customer, open the account, change a value, then check the customer record in Customers in the admin to confirm the metafield updated. Repeat for consent toggles. Our article on testing Shopify customer consent and adding account consent without code covers how to verify that tracking pixels respect the choice.

Using customer tags and metafields to show the right content

Customer tags are labels. Shopify’s help center describes them as a way to categorize customers into groups such as VIP and use them to segment for targeted marketing. Forms can also add tags automatically: the Tags setting determines which tags are applied to customers who complete a form.

AccountCraft turns those labels into account content. Blocks support conditional rendering by customer tag, metafield, market, B2B status and account age. Some examples:

• Show a wholesale ordering banner only to customers tagged as wholesale.
• Show the pet profile section only to customers who said they own a pet.
• Show a different consent explanation to customers in a specific market.
• Show a welcome card to accounts under 30 days old.

The result is a preference center that stays short for each person, even if your store collects many kinds of data. It is the cleanest way to follow the advice to keep things simple without dropping the data you need.

Consent, withdrawal and records

A preference center is also where customers exercise control, so design the consent parts carefully. We are not lawyers, and what applies to you depends on where you sell and who your customers are. Talk to a qualified privacy professional about your own obligations.

Some points from authoritative sources:

• In Germany, Shopify notes that customers must confirm subscriptions when the store’s email and SMS setup requires confirmation messages; double opt-in can help meet GDPR requirements.
• The UK ICO says that, for consent to storage and access technologies, users must be able to withdraw consent at any time, as easily as they gave it, and you should explain how withdrawal works and what it changes.
• Power Commerce reports that easily accessible withdrawal and record features decrease complaint rates.

For broader background on building privacy controls that honor consent and withdrawal choices, this piece on consent management controls is worth a read.

What to do in practice:

1. Put the consent toggle in the account, not buried in an email footer alone.
2. Make turning it off one click, with a plain sentence about what changes.
3. Make sure your email and SMS tools read the same consent status from Shopify, so a withdrawal in the account is respected everywhere. Check each connected tool, because some sync on a schedule.
4. Keep the consent record in Shopify rather than in a spreadsheet.

AccountCraft’s privacy consent and SMS consent blocks help you collect, record and honor choices through Shopify’s customer privacy APIs. They do not make a store compliant by themselves; that stays with you as the merchant. For region-specific setups, see our guides on the GDPR checkbox for New Customer Accounts, consent expiry for EU stores and CCPA admin steps.

Where the data goes after customers save it

Once a preference is in a customer metafield, it is not trapped in the account page. Shopify states that extensions can persist preferences, feedback and profile details on Shopify resources, making the data available to the Shopify admin, other extensions and Shopify Flow. Practical uses:

• Build a customer segment from a metafield value, then send a campaign to it.
• Trigger a Flow automation when a preference changes.
• Give support staff the answer in the customer record instead of a chat thread.

Because Shopify’s unified data model connects activity across online and in-store channels into a single customer profile, a preference set online is visible to staff at the register too, as long as your setup surfaces it.

Our perspective

Most preference center projects stall for one of two reasons: the merchant assumes it needs a developer, or it ends up as a long form nobody finishes. We built AccountCraft around the opposite approach. Start from the handful of things you will really use, store each one in a metafield so it stays in Shopify, and show each customer only the blocks that apply to them.

We also think consent belongs next to the data it governs. When a customer sees their birthday field and their email consent on the same page, it is obvious what they are agreeing to, and withdrawing is easy. That is better for trust and, in our experience of how merchants talk about it, for fewer angry support emails.

Finally, avoid the temptation to copy a big enterprise preference center. A small store with five clear options and a visible unsubscribe path will usually serve customers better than an exhaustive one.

— Ivan Signorile

Try it on your store

If you want the preference center without a developer, AccountCraft lets you build it in the Block Builder on top of New Customer Accounts. There is a free plan to start, and the paid Pro and Plus plans are billed through Shopify. Check the listing for current pricing.

Install AccountCraft free from the Shopify App Store, or see the plans on the AccountCraft site. If you also want customers to keep wishlists and sign in more often, our notes on raising account signups while keeping guest checkout are a good next step.

FAQ

Does Shopify have a built-in preference center?

Not as a single page. Shopify provides marketing consent at checkout and sign-in, a cookie preferences link and a Profile page for names, emails and addresses. Custom preferences such as topics or sizes need a customer account UI extension or an app that provides one.

Where do customers manage their email preferences?

Customers sign in to their account and open Profile for basic details. Marketing consent can also be changed wherever you expose it, for instance through a consent block in the account page. Make sure your email tool reads the same consent status so a change takes effect everywhere.

Can I collect customer preferences without coding?

Yes. Define customer metafields in Settings > Custom data > Customers, then use an app such as AccountCraft to bind them to fields in New Customer Accounts. Customers edit the values themselves, and the data stays in Shopify.

Should I use tags or metafields for preferences?

Use metafields for values you need to read back, such as a size or a topic list, and tags for group labels such as VIP. Shopify’s own guidance points out that notes and tags can invite errors and often do not scale for marketing.

Does a preference center make my store GDPR compliant?

No tool does that on its own. A preference center helps you collect, record and honor consent, but compliance is your responsibility as the merchant. For your specific obligations, speak with a privacy lawyer or data protection professional.

Sources

• Shopify Help Center: Customer accounts
• Shopify.dev: Building apps for customer accounts
• Shopify.dev: Building metafield writes into extensions
• Shopify.dev: About metafields in customer accounts
• Shopify Help Center: Collecting customer contact information
• Shopify Help Center: Forms app settings
• Shopify Help Center: Configuring customer privacy settings
• Shopify Help Center: Managing customers
• Shopify blog: Customer data
• Shopify blog: POS customer metafields
• ICO: How do we manage consent in practice?
• Power Commerce: Marketing consent on the customer sign-in page

Recommended

• How to Customize Shopify Accounts With New Customer Accounts
• Shopify Customer Consent: Test Pixels, Add Account Consent Without Code
• Customer Self-Service on Shopify: What to Set Up and Which Blocks to Add
• GDPR Checkbox for Shopify New Customer Accounts