Tender is now Andeo.

A new name. The same focus on helping you build and ship better customer experiences.

Andeo
Blog

Vibe Coding Shopify Customer Accounts

Customer accounts have become the home for post-purchase work in Shopify.

Customers use them to check orders, manage returns, update preferences, handle subscriptions, join loyalty programs, and come back for the next purchase. For years, many of those jobs lived in separate portals with separate flows. The customer left the Shopify account. The merchant lost control of the experience.

Customer Account Extensions change the account page itself. They let apps show up as native blocks and pages inside Shopify customer accounts. Shopify also deprecated legacy customer accounts on February 26, 2026, with a final sunset date to be announced later in 2026.

Many Shopify apps now ship account blocks and full-page extensions. Recharge, for example, offers customer account extensions for subscription pages, upcoming orders, payment methods, addresses, and credits. Subscription management can stay closer to the Shopify account instead of sending the customer into a separate portal.

Apps extensions work when the app matches the job. But many times your Customer Account journey need a different path. A coffee merchant may want customers to save a taste profile. A pet brand may want customers to save pet details and get better recommendations. A membership business may need a page that explains benefits, status, and next steps.

Those jobs are good candidates for a custom Customer Account UI extension.

The challenge is that the customer account model is different to the old theme model. You cannot drop arbitrary HTML into the account page. The app has to run as a native Shopify Customer Account UI extension.

We have talked with many merchants who flagged the following two as the main blockers to migrate:

  1. They have invested time and effort in customizing their legacy customer accounts pages with custom components and pages.
  2. Customer account apps have to use Shopify’s supported extension UI, which limits what you can bring over directly.

Andeo helps move custom account components and pages into the new model. A merchant can describe the account experience they want, and Andeo turns that request into a Shopify-native extension with the right surface and data model, merchants can even point to their legacy customer accounnts and it will migrate those for you.

What you can build

Start with the customer moment. A coffee subscription brand could give customers a profile page for roast preference, brew method, grind size, tasting notes, and caffeine preference. That profile can shape recommendations before the next order.

A pet brand could let customers keep pet profiles with age, breed, diet, allergies, and product needs. The account page can support better reorder prompts, care instructions, and support conversations.

An apparel brand could save sizes, fit preferences, family profiles, care instructions, and exchange guidance. The merchant can use that data to reduce repeat questions and make the next purchase easier.

Then choose the surface. If the app belongs next to an order, use an order status block. That is a good fit for care instructions, warranty guidance, returns, setup steps, loyalty context, or reorder prompts. The customer sees it where they are already checking the order.

If the app needs more room, use a full customer account page. That is a good fit for profiles, preferences, product finders, wishlists, subscriptions, or reorder flows. The customer gets a native account page, and the merchant gets structured data they can use later.

If the job is small, use a profile or preference block. Ask one question. Show a saved status. Let the customer edit one field.

The target matters because Shopify gives each one different context. Order status extensions can use order data. Full pages can support larger flows. Profile blocks should stay focused.

Where customer data should live

Each Andeo app can store data in its own database. For customer-owned data, Shopify is usually the better home.

That means taste profiles, pet details, saved sizes, preferences, care reminders, and product interests should usually live on the Shopify customer record. Metafields and metaobjects keep that data close to the account where the customer entered it.

That also makes the data useful outside the account page. The merchant can use it in Shopify Flow, support workflows, email segmentation, recommendation logic, or discount rules, depending on the rest of the stack.

The practical rule:

  • Customer-owned profile data lives on the Shopify customer record.
  • Andeo-owned runtime state stays in Andeo.
  • Admin-only work, discount setup, and cross-customer reads go through the Andeo backend and Shopify app.

For sensitive preferences, decide what should be collected, how consent is handled, and where the data can be used. Pet health details, medical claims, discounts, and marketing use all need a store-specific review before launch.

What Andeo handles

Andeo is useful here because writing the extension is only one part of the job. The hard part is maintaining your app, the Shopify runtime, data model, and merchant setup in sync.

Andeo handles the app source, preview, Shopify extension build, and the customer-facing flow.

The Andeo and Shopify split lets a merchant ask for the app in business language:

  • Show care instructions after purchase.
  • Let customers save family sizing preferences.
  • Let customers set product interest or target price alerts.
  • Give account customers a guided product finder.
  • Save a profile that can drive future recommendations or discounts.

Andeo turns that into the right Shopify surface and data path.

Before launch

A custom account extension should have a short launch checklist:

  • New Shopify customer accounts are enabled.
  • The target is clear: order status block, profile block, or full account page.
  • Customer fields are defined before data is collected.
  • Consent, privacy, discounts, and any health or compliance claims are reviewed.
  • Subscription, returns, loyalty, email, and support tools are checked if the app needs to work with them.
  • The merchant knows where the extension will be placed in the account editor.
  • Customer-facing copy is approved.

Demo

Most coffee brands know what a customer bought. They do not know when that coffee will run out.

The demo adds a small survey to the order page in Customer Accounts. It asks two questions:

  • What brewing method do you use?
  • How many cups do you drink each day?

That is enough to make repurchase timing smarter. If a customer drinks three cups a day, the store can send a reorder reminder before the bag is empty. If the customer keeps coming back, the same flow can point them toward a subscription.

The request to Andeo is simple:

Create an order page survey that asks customers for their brewing method and how many cups of coffee they drink per day. Store the answers on the customer profile so we can send better repurchase reminders.

Sources