Shopify create_customer form not creating customers

01Why the form saves no one

The create_customer form posts to /account, and Shopify’s docs describe it as a form “for creating a new customer account” that belongs to the customers/register template (Shopify, form tag). That template is part of legacy customer accounts. On the current version, customer accounts run apart from the theme: “Legacy customer account templates are deprecated,” and customers/register is among the templates that “no longer need to be included in your theme” (Shopify, Templates).

Signing in changed with it. Customers “enter their email address and receive a one-time 6-digit verification code”, “A password isn’t required to sign in”, and an email with no profile behind it gets one: “a new customer profile is created automatically” (Shopify Help, Customer accounts). There’s no registration step left for a theme form to feed.

When we tested a create_customer form on a store running the current customer accounts (16 Oct 2026), Shopify redirected to the sign-in page and dropped the tags, the note and the VAT number the form carried. No customer was created.

More stores will meet this. Since 26 Feb 2026, legacy accounts are “no longer available to new stores and existing stores not using it”, and Shopify says a final sunset date will be announced later in 2026 (Shopify changelog). A registration form that works today on legacy accounts stops when the store upgrades, and a store on legacy accounts that moves to a theme without the legacy templates is upgraded automatically (same changelog).

On the Shopify Community, a waitlist built on create_customer redirected to the home page and added no one (Aug 2022); the thread has no answer. On a newer thread (Apr 2026), a store moving off legacy accounts asks how to keep a registration form that tags customers for special pricing, and the reply is that the new account pages need an app to change.

02Choose a route: the customer form, a small function or B2B

For store owners

1. 1

   Check which customer accounts you’re on

   In Settings > Customer accounts. On the current version, a theme sign-up form with a password field, or one that sets tags or a note, won’t create the account.

2. 2

   Test the form

   Fill it in with an address you own, then search for that address under Customers. If no customer appears, or it appears without its tags and details, the form needs rebuilding.

3. 3

   Choose the route

   An email and a tag only: your developer can switch the form to Shopify’s customer form. Anything more (several fields, a VAT number, approval): a small function, below. An app that adds custom fields to sign-up is the third way.

4. 4

   Selling trade through Shopify B2B? Use its request form

   If your trade prices come from B2B companies and catalogs rather than customer tags, Shopify has this built in. Company account requests use a Shopify Forms form, can save extra fields as customer or company metafields, and hold each new company until you approve it (Shopify Help). B2B is on the Basic plan and up (Shopify Help).

5. 5

   Tell people how to sign in

   With the current accounts, customers sign in with an emailed code, not a password. Say so where the form says thanks.

For developers: the `customer` form, or a small function

Shopify’s customer form creates “a new customer without registering a new account” (Shopify, form tag). It takes an email and tags (Shopify, the password template’s sign-up form), and the customer it creates has accepts_marketing set to true (Shopify, Email consent). That suits a newsletter or a waitlist. It doesn’t suit a trade application, where people haven’t asked for marketing and you need more than an email.

For that, the form posts to a function you host (ours run on Vercel), and the function creates or updates the customer through the Admin API, with an app token that holds write_customers only. Shopify no longer lets you create custom apps in the admin (Shopify), so the app comes from the Dev Dashboard; ours is installed on the one store by custom distribution. The applicant then signs in by emailed code like any other customer. The theme side:

form.addEventListener('submit', async (event) => {
  event.preventDefault();
  const data = Object.fromEntries(new FormData(form));
  try {
    const res = await fetch(form.action, {
      method: 'POST',
      headers: { 'Content-Type': 'text/plain' }, // a simple request: no CORS preflight
      body: JSON.stringify(data),
    });
    const out = res.ok ? await res.json() : null;
    if (out && out.ok) showDone(out.status); // 'approved' or 'pending', shown in place
    else showError();
  } catch (error) {
    showError();
  }
});

// Env: SHOPIFY_STORE_DOMAIN (the .myshopify.com domain), SHOPIFY_ADMIN_TOKEN (write_customers only)
const ADMIN = `https://${process.env.SHOPIFY_STORE_DOMAIN}/admin/api/2026-07/graphql.json`;

async function admin(query, variables) {
  const res = await fetch(ADMIN, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json', 'X-Shopify-Access-Token': process.env.SHOPIFY_ADMIN_TOKEN },
    body: JSON.stringify({ query, variables }),
  });
  const json = await res.json();
  if (!res.ok || json.errors) throw new Error('Shopify answered ' + res.status);
  return json.data;
}

const CREATE = `mutation ($input: CustomerInput!) {
  customerCreate(input: $input) { customer { id } userErrors { field message } }
}`;

export default async function handler(req, res) {
  if (req.method !== 'POST') return res.status(405).end();
  const a = typeof req.body === 'string' ? JSON.parse(req.body || '{}') : req.body;
  if (a.website) return res.status(200).json({ ok: true, status: 'pending' }); // honeypot: write nothing

  const approved = passesYourCheck(a.vat); // your rule for instant approval
  const input = {
    email: a.email,
    firstName: a.firstName,
    lastName: a.lastName,
    tags: [approved ? 'trade' : 'trade-pending'],
    metafields: [
      { namespace: 'trade', key: 'business_name', type: 'single_line_text_field', value: a.business },
    ],
  };
  const r = await admin(CREATE, { input });
  if (r.customerCreate.userErrors.length) return res.status(422).json({ error: 'check' });
  return res.status(200).json({ ok: true, status: approved ? 'approved' : 'pending' });
}

• Check the request’s origin against your store’s domains, cap the body size and keep a hidden honeypot field. The function writes customers, so treat every field as untrusted.
• Answer with CORS headers for your store’s domains, or the page can’t read the reply.
• Look the email up first. If the customer exists, update them instead, and decide what you never overwrite (on the store we built: a trade tier already on the record, and email marketing consent).
• Set email marketing consent only when the applicant ticked a box for it.
• Straight after a create, the Admin API’s customer search can lag a second or two behind: a quick double submit can be refused as a taken email and then not find the customer. Wait and look again before giving up.
• To email the shop when an application arrives, Shopify Flow can do it: a workflow on Customer tags added with Send internal email. On the store we built, the function adds the alert tag in a separate step after the create, because a tag set inside customerCreate didn’t count as added for Flow.

03Apply as a new customer, then sign in as them

1. 1

   Apply as a new customer

   Use an address you own, send the form, then find the customer under Customers, with the tags and details you expect.

2. 2

   Sign in as them

   Use Sign in on the store, enter the address and the code from your inbox. You should land in the same customer, not a second one.

3. 3

   Apply again with the same email

   Nothing you meant to keep on that customer should change.

4. 4

   Check what the tag switches on

   If tags turn on trade prices or hidden pages, check a product page and the basket while signed in. On the store we built, a tag change reached a shopper who was already signed in only after they signed in again.

5. 5

   Delete your test customers

   So they don’t land in your marketing or your reports.