Shopify Customer Registration Fields: 5 Apps Compared

If you want to collect birthdays or phonetic name readings in Shopify, first separate the fields covered by built-in features from those that need an app. Alongside pricing, compare where customers enter information, where it is stored, and whether they can edit it later. This makes it easier to choose an app that fits your store’s operations.

With the new customer accounts, email verification and entering additional profile details are separate steps. Understand this distinction before building a registration form.

Sign-in and profile completion are separate steps

The standard sign-in method for the new customer accounts uses a six-digit verification code sent by email. When someone signs in with an email address that has no existing customer record, Shopify creates a customer profile automatically. This does not, however, collect the birthdays or preferences your store may want. (Shopify Help Center)

You cannot add app customization blocks to the new sign-in page. Instructions for editing a legacy Liquid registration form do not carry over directly, either. Collect additional information in a separate form before or after sign-in, or on the profile page. If you are considering switching account types, see our customer accounts migration guide. (Migration limitations)

Choose the fields and when to ask for them

First, write down who will use each answer and for which task, then keep only the information you need. For example, consider whether you need the year of birth for a birthday-month message, or whether phonetic name readings will reach a place your customer service team can access.

You can invite customers to provide optional details after purchase or on their profile page, without asking for everything at the start when it is not needed to place an order. Explain why you are asking for each detail, and keep profile answers separate from consent to receive marketing emails.

Also distinguish standard fields, such as names, from custom fields. Saving the same information in multiple places can cause values to diverge when someone edits them. If you use customer metafields to add custom information to Shopify customer records, check whether you can reuse existing fields.

What built-in features and Shopify Forms cover

Customers can edit their name, email address, and shipping addresses in the standard customer account. If these fields are enough, check the built-in profile before installing another app. If you want to add birthdays or phonetic name readings and let customers update them, consider an app that supports those requirements. (Built-in editing options)

Shopify Forms, Shopify’s free official app, suits collecting information through storefront popups or embedded forms. Displaying a form requires theme support and setup; it does not add fields directly to the sign-in page. It also does not support multi-step forms or conditional logic that changes questions based on answers. (Forms overview; Form types and requirements)

When the same person submits another Forms response, customer metafields for additional information are updated with the latest values. Existing customers’ email addresses and phone numbers, however, are not changed through form responses. If you want customers to see and correct their profile details, compare the editing features of the five apps below. (Saving and updating additional fields; Limitations on updating existing customer information)

Features and pricing: three Japanese and two overseas apps

This comparison is based on official public information available on October 16, 2026. Our assessment of suitable uses reflects those specifications, rather than installation or hands-on testing by Popaz. After reviewing each app’s features and pricing, use the comparison tables later in the article to compare suitable uses, limitations, and data handling.

Prices are in US dollars (USD). Annual prices are the total paid for a yearly subscription and exclude Shopify platform fees and any separately used connected apps. Check both the plan that includes your required features and its usage conditions.

Howdy: help with the initial setup

Howdy, from Japanese developer macro micro Inc, is designed for the new customer accounts. You can ask its dedicated team to create customer metafields, configure forms, and place them on the profile page based on the information you want to collect. This support helps teams unfamiliar with the setup work through the whole process, from initial entry to later editing.

You can choose required or optional fields, and customers can view and edit additional information in their profile. Forms can appear before or after sign-in, but the official FAQ says the standard sign-in link at checkout is not supported. Confirm which entry points will lead customers to the form before implementation. (Form timing; Checkout limitation)

All plans offer a 14-day free trial. The published table does not identify feature differences among the four standard plans beyond customer limits. (App Store pricing; All plans from the developer)

Annual prices for the four standard plans follow the App Store listing. The developer’s page lists each annual price $0.09 lower, so check the amount shown when approving the subscription.

AL CustomerMetaSync: collect details at first sign-in and after purchase

AL CustomerMetaSync, from Japan-based Alquimista, can collect information immediately after sign-in with the new customer accounts, as well as on profile, Thank you, and Order status pages. This suits a process that asks only for essential details initially, then invites customers to add their preferences after a purchase. Its strength is collecting information at the relevant stage without asking too many questions at once.

Answers are stored in customer metafields. You can control display based on customer tags or answers, and allow or restrict later editing in the profile. You can also allow a field to be filled in only once, when it has no saved value. This supports arrangements such as keeping a birthday fixed while allowing preferences to change. The app does not support legacy customer accounts or legacy Thank you pages. Signing in from the cart requires an additional route to the form, and making completion mandatory before purchase also requires theme support. (Display and editing settings; Compatibility; Onboarding form limitations)

The onboarding form does not reappear for people who have already submitted it or already have data in every field. If you want every existing customer to re-enter or reconfirm their details, check whether this behavior meets your needs. (When the onboarding form appears)

A 14-day free trial is available. One plan is published, with no customer, form or submission limits specified in the pricing section. This does not confirm unlimited usage; check before implementation if you expect high volumes. (Pricing and conditions)

FormSync Customer Forms: reuse a form across several screens

FormSync Customer Forms, from Japanese developer Self Plus, uses one form definition in five places: before sign-in, immediately after sign-in, on the profile page, on the Thank you page, and on the Order status page. Its strength is managing fields and storage rules together even when customers enter information on several screens. It requires the new customer accounts. (Developer’s feature overview)

You can configure text, date, and choice fields in the editor, and save answers to standard fields such as first name, last name, and phone number, or to customer metafields. The developer also describes customer updates through the profile page. Email addresses are used for matching and are not changed by the form. The form shown before sign-in is placed in the store’s theme and requires Online Store 2.0 and an app embed. Available locations and integrations vary by plan, so decide where you need to collect information before comparing plans. (Features and plans; Form placement and storage)

Paid plans include a 7-day free trial. An allowlist is a list you prepare in advance to check submitted information against. Standard can match an email address, phone number, name or custom code; Premium can combine fields such as name and phone number. Compare the matching method and submission volume you need alongside form locations. The official materials do not confirm that matching alone can restrict every sign-in and purchase route. If you want only invited customers to purchase, check exactly which routes can be restricted. (Pricing and features)

Helium Customer Fields: detailed questions and input rules

Helium Customer Fields, from US-based Helium, offers detailed control over questions shown based on previous answers, required fields, and input validation such as text length or dates. You can tailor a form to the respondent—for example, asking for a company name only when someone selects “Business.” Conditional logic requires Pro or above, while account approval and the REST API for external integrations require Advanced or above. (Form rules; Input validation)

With the new customer accounts, you can use a card on the standard profile page or a dedicated page; legacy accounts support registration and editing forms. You can also place a form on the new Thank you page, but guest checkout is not supported. This form handles the signed-in customer’s information, rather than order information. (Form locations and limitations)

Standard fields are stored in Shopify customer records, while additional information is stored in the app database and customer metafields. Customers can edit details after signing in. If you use existing metafields, match their storage fields and data types. If you use an approval form, you need a separate form for editing. (Data storage; Using existing fields; Customer editing)

The developer provides instructions for translating customer-facing labels and error messages. We could not confirm a Japanese admin interface or Japanese-language support from the official materials reviewed, so consider whether your team can configure and operate the app. (Form translation)

All plans offer a 14-day trial. Enterprise customer ranges follow the official pricing table. We could not confirm published annual prices. (Official pricing; Features by plan)

Managed customers are customer records stored in the app through forms, syncing or imports. This differs from all Shopify customers or monthly active users. Exceeding the quota limits access to the app’s customer directory and exports, while registration, sign-in and customer editing can continue. (Managed customers and quotas)

Account approval does not automatically prevent unapproved customers from browsing or purchasing. Customers can proceed through the new standard sign-in without completing the form, so consider additional controls if restrictions are needed. Account/Checkout forms, which update the signed-in customer’s details, do not have an approval setting. For forms that use approval, pending information is held in the app and a customer record is created in Shopify after approval. (Approval settings and storage; Scope of access restrictions)

C:Hub Customer Accounts: customize the whole account experience

C:Hub Customer Accounts, from Australia-based CustomerHub, lets you organize order history and account menus alongside additional profile details. It supports new and legacy accounts and provides custom account pages and panels on the storefront. This is a different approach from adding a block to Shopify’s standard profile page, so consider whether you want to change the whole account experience. (Official product page)

Additional fields use supported Shopify customer custom data, and you configure which fields customers can update and which they can only view. You can make the profile accessible as customers browse their order history, which suits an account experience designed for ongoing use. The registration form controls available differ between new and legacy accounts. Changing menu visibility based on customer tags does not, by itself, control permission to browse or purchase. (Profiles and display rules)

Before implementation, check where customers return after sign-in and how existing data maps to editable fields. Labels and messages can be edited, but we could not confirm default Japanese translations or Japanese-language support from the official materials reviewed. (Language features)

All four plans include the account page and panel, visual editing, profile fields, order actions and supported app integrations, with a 14-day trial. Customer limits use the store’s total Shopify customer records, including people who have never used their account. Connected apps charge separately. (Official pricing and conditions)

The optional B2B add-on is free during beta. Future pricing of $19/month or $190/year has been announced, but it adds no charge to the base plan as of the verification date.

Check required fields, storage and later editing

Requiring a form field and preventing purchases without an answer are separate controls. A required field is a condition for submitting that particular form. If a sign-in or purchase route bypasses it, customers may proceed without answering. If an answer is needed before purchase, check the flows from your store’s sign-in, cart and checkout, as well as where the app’s form is placed. (Helium’s explanation of new customer accounts)

For ongoing use, check the service that consumes the information as well as the app that collects it. Saving to a customer metafield is not enough to use it for messaging conditions if your messaging app cannot read that field or format. Decide where and when updated values should appear after a customer edits them.

For example, you could invite customers to optionally enter their birth month after signing in and store it in a customer metafield. Check that your messaging app can read the month value, and send messages only to people who have consented to email marketing. Provide an editing link in the profile. This is an operational example; it does not mean every app can implement it with the same settings.

For phonetic name readings, creating an input field is also different from validating that it contains only kana or converting text automatically. Write down the input rules you need first, then check which plans support them.

Which uses suit each of the five apps?

Apps that add customer information can serve different roles. The assessments below are based on the official specifications described above. “Less suitable or needs additional work” includes unsupported features, screen designs that may not fit your requirements, and uses that need another mechanism alongside the app.

Benefits and limitations by use case

When comparing prices, make sure you understand what each app means by “customer count.” Some plans use the store’s total customers, others use customer records stored in the app, and others are limited by forms or submissions. Match your required features and expected usage to each pricing table to identify the appropriate plan.

Form locations, storage and customer editing

The storage table describes how the main operational data is handled. It does not imply that an app keeps no data of its own or automatically syncs with other services. The ability to save to customer metafields does not, on its own, confirm that your existing fields can be reused. Before implementation, match the destination fields, value formats and details customers may change. For the two overseas apps, also distinguish customer-facing translation and wording controls from the availability of a Japanese admin interface and support.

Narrow down the options for your store

For each additional field, decide its purpose, where customers enter it, whether it is required or optional, and where they can edit it. Use the comparison tables to shortlist apps that meet those requirements, then check the plan with the necessary features and its usage conditions. During a free trial, test whether customers can reach the form through your store’s sign-in and purchase routes, whether the destination service can read saved values, and whether customers can edit their details.

If you also need to carry over existing customer data, restrict purchases by customers who have not answered, or integrate external systems, define those requirements separately from adding fields. Custom development is an option for gaps that existing apps cannot fill. For account screen extensions, see our guide to extending customer account pages.

To start a conversation with Popaz, share the fields you want to add, how you will use them, and the apps you currently use. Discuss customer profile forms and operations.