--- title: "How it works - Built the Shopify way" url: "https://zendra.com/how-it-works/" description: "" published: "2025-12-05T20:05:30+00:00" modified: "2026-10-13T03:58:13+00:00" --- How it works / built the Shopify way # A Shopify app shouldn’t build a second store. Many membership apps keep member data on a private island only they can read. Zendra is fully Shopify-native; it lives in the data, segments, and metafields your stack already understands. [Install on Shopify](/app-store/zendra?utm_term=how-it-works) [See where the data lives](#native-surfaces) --- **4.9 ★** App Store rating **0%** transaction fees **$0** Up to 75 members **Field survey: where the data lives**No islands found Sales Real products & ordersShopify analytics Status Member since, plan, activeCustomer metafields Audiences Active members, per planShopify segments Automation 13 triggers, 9 actionsShopify Flow Relationship Perks, access, lifecycleZendra One store, one system Built for Shopify **•** Native checkout, billing & accounts **•** No membership data island 01\. --- The problem ## Avoid member data islands Shared context spurs growth. Every membership app decides where its records live. Choose one that keeps them to itself, and the symptoms arrive one at a time. Symptom 01 #### Reporting splits in two Shopify’s reports show the rest of your catalog while membership sales live in a separate dashboard with different definitions. “How much membership revenue last quarter?” becomes a research project. Symptom 02 #### Automations go blind Order automations recognize products and variants, but a membership purchase invisible to Shopify needs a custom bridge before anything else can react to it. Symptom 03 #### Tools can’t tell members apart Your email platform, analytics, and discounts have no idea who’s an active member — that answer sits inside the app, out of reach. Symptom 04 #### Prices drift apart The same price gets maintained in the app, then recreated in every tool that needs it. If you restructure your tiers, you’re updating several versions of one idea and hoping none drift. **A membership app should add a system to your store, not create a second store beside it.** That’s the principle Zendra is built on — we wrote up the full argument in [Will your membership app create a data island?](/blog/membership-app-data-island/) 02\. --- The payoff ## Shared members data Useful to your whole stack. Zendra publishes membership state to the surfaces Shopify tools already understand — so email platforms, analytics, and automations act on memberships without special integrations. 001 / analytics #### Sales reports that include memberships Because memberships are real products and variants, Shopify’s own sales reports show program revenue at the product level and per-tier sales at the variant level. No separate dashboard with unique definitions. 002 / segments #### Customer segments, auto-managed Zendra maintains a Shopify segment of all active members, plus one per plan — ready for targeting with email, discounts, or any app that reads segments. 003 / metafields #### Status in customer metafields Member status, active plans, and member-since dates sync to queryable customer metafields — usable in Liquid, email personalization, reports, and integrations with other apps. 004 / tags #### Smart customer & order tags Customers and their orders are tagged by membership automatically. Tools that read Shopify orders — like Metorik — can split member from non-member revenue with zero custom work. 005 / flow #### Shopify Flow, first-class Thirteen membership triggers and nine actions plug the whole lifecycle into Flow: grant a membership when lifetime spend crosses $500, add store credit on renewal, react to failed payments — your rules, native automation. 006 / checkout & accounts #### Native checkout, billing, POS & portal Purchases run through Shopify checkout and Shopify’s native subscription billing. Members manage everything in Shopify customer accounts, staff see membership info in POS, and even Shopify Sidekick can answer membership questions. 03\. --- The lifecycle ## First plan to mature program Zendra does it effortlessly. No manual tagging, custom Liquid, or API integration. Zendra creates the discount rules, tags, checkout validations, and template restrictions behind the scenes. ⦿ --- 01 / create a plan #### Define the program Decide how customers become members — purchasing or subscribing to a product, signing up for an account, or by your invitation. You can also describe your goal to Zendra Assistant, and it drafts plans, pricing, and perks for you to review. ⦿ --- 02 / billing & perks #### Set the terms One-time fees, subscriptions, or both — with full control over intervals, trials, and signup fees. Attach perks: discounts, free shipping, gated content, exclusive products. ⦿ --- 03 / add the blocks #### Launch on your theme Drop the purchase widget onto product pages and enable the member portal in customer accounts — theme app blocks, no code. ⦿ --- » 04 / zendra runs it #### Lifecycle, automated Activation, renewals, failed-payment retries, graceful cancellation, lifecycle emails, tags, and segments all happen automatically — while you watch it in the dashboard. 04\. --- Questions ## Questions about the architecture The practical version of “is it really native?” — what other tools can see, and where your data ends up. 01 #### Is a membership a real Shopify product?+ Yes. Paid memberships are sold as normal Shopify products and variants, with selling plans describing the billing cadence — so they appear on orders and in product reporting like everything else you sell. 02 #### Can my email platform tell who’s a member?+ Yes, three ways: auto-managed customer segments (all members, plus per plan), automatic customer tags, and customer metafields with status, plans, and member-since dates for personalization. 03 #### Does Zendra run its own checkout or billing?+ No. Purchases go through Shopify checkout, and recurring billing uses Shopify’s native subscription system. There’s no separate payment flow to reconcile. 04 #### Can I see membership revenue in Shopify analytics?+ Yes. Product-level reports show total program sales; variant-level reports separate the tiers. Order tags also let order-aware tools split member from non-member revenue. 05 #### What can I automate with Shopify Flow?+ Zendra ships 13 membership triggers (started, trial converted, renewed, cancelled, ended, billing failure, and more) and 9 actions (create or extend memberships, add store credit, generate member discount codes). If Flow can express it, memberships can drive it. 06 #### What does Zendra keep to itself?+ The relationship: perks, access rules, renewal state, and lifecycle handling. That’s specialist membership data a product record shouldn’t pretend to answer — and Zendra publishes its conclusions (status, tags, segments) back to Shopify. start with a clear promise Make a place worth belonging to. Start free with up to 75 active members. Launch your first plan in minutes, then add the perks that make people want to stay. [**Install on Shopify**](/app-store/zendra) [Talk through your program](https://zendra.com/contact/)