Zendra connects a paid membership to a Shopify product or variant. The product records what the customer buys; the Zendra plan defines the access, perks, and membership lifecycle that purchase unlocks.
This keeps your membership offer inside the same commerce model as the rest of your store, where Shopify and product-aware apps can understand it.
When you’d use this
- Understand why a paid membership needs a Shopify product.
- Decide whether a plan should connect to a whole product or one of its variants.
- Keep membership sales useful in your existing reports, automations, and product-aware apps.
How it works
Shopify records what the customer buys
When someone purchases a paid membership, the Shopify product or variant appears in checkout and on the order like another item your store sells. Its product title, variant, price, and revenue remain part of Shopify’s structured commerce data.
This means tools that already read Shopify products or orders can often recognize the membership sale without a separate Zendra integration. For example, a product-aware email app may be able to use the purchased product in an automation, while Shopify reports can group sales by product or variant.
A custom landing page can still tell the richer story and sell the value of joining. The Shopify product remains the structured record behind the offer.
Zendra defines what the purchase unlocks
The Zendra plan adds the membership behavior that a product does not have on its own. It determines which perks the member receives, how long access lasts, and which purchase activates the membership.
This separation gives each system a clear job:
| Shopify manages | Zendra manages |
|---|---|
| The product or variant being sold | The membership plan connected to it |
| The catalog listing and base price | Perks and access rules |
| Checkout, orders, and product revenue | Membership activation and lifecycle |
| Product variants | Which plan each product or variant unlocks |
| Selling plans used at checkout | Membership billing configuration and behavior |
Variants keep related tiers together
If your membership has tiers, you can create one Shopify product with a variant for each tier, then connect a different Zendra plan to each variant.
For example, one Studio membership product might have Essential, Plus, and Complete variants. Each variant can have its own price and Zendra plan, while Shopify still recognizes them as parts of the same parent product.
That structure lets you review the program as a whole at the product level or inspect individual tiers at the variant level.
Selling plans describe how the customer pays
Billing intervals are purchase options attached to products or variants, not separate products. A customer might buy the same coffee variant every two weeks or every month; the product still describes the coffee, while the selling plan describes the schedule.
For subscribe-and-save programs, Zendra can use the current product or variant price as the base for each interval. You can add a percentage or fixed discount without defining a separate fixed price for every product, variant, and billing-frequency combination.
What other apps can see
An app that reads Shopify products and orders can often use the membership’s product, variant, price, and purchase data. Exact behavior depends on the app and the Shopify data it supports, so connecting a membership to a product does not guarantee compatibility with every integration.
Membership status is different from purchase data. When another tool needs to know whether someone is an active member now, use Zendra’s Shopify customer tags, customer segments, membership metafields, or Shopify Flow triggers and actions.
Common issues
- I already have a landing page for my membership. Keep it. The landing page explains the offer, while the Shopify product supplies the structured data used at checkout and elsewhere in your store.
- Another app sees the purchase but not the customer’s current membership status. Product and order data record the sale, not the full membership lifecycle. Use Zendra’s tags, segments, metafields, or Flow integration when another tool needs active-plan data.
- All tiers activate the same perks. Connect each tier’s Zendra plan to its specific product variant, not the parent product.
- Different variants are being charged the same subscription price. Check whether the billing plan has a price override. An override applies its fixed price instead of inheriting each variant’s price.