Shopify subscriptions: the pillar guide for 2026

What 'subscriptions on Shopify' means in 2026

Five years ago, running subscriptions on Shopify meant installing Recharge, accepting a parallel checkout flow on a Recharge-hosted domain, and watching your subscription data live outside of Shopify entirely. That's no longer how it works. Since Shopify shipped the native Subscription Contracts API in 2021 and made it the only supported model in 2023, subscriptions are first-class objects inside Shopify itself — the contract, the customer, the payment method, the discount, and every renewal order all live in the same database that powers your one-time orders.

What an app does today is much narrower. It creates selling plans, drops a widget on the product page, runs the renewal cron, sends dunning emails when cards fail, and gives subscribers a portal to manage themselves. The checkout, the payment vaulting, the order objects, and the storefront discounts are all native Shopify. That separation matters because it means switching apps is much less painful than it used to be, your subscription data shows up in Shopify analytics natively, and you don't pay extra checkout fees just because the order is recurring.

The four business models that work on Shopify

Almost every subscription store on Shopify ends up in one of four buckets. The model determines the widget UX, the discount structure, the fulfillment workflow, and the retention curve — picking the right one upfront is the single highest-leverage decision before you install anything.

• Subscribe-and-save — the customer picks a product, a cadence, and gets a discount for committing. Same SKU every cycle. The dominant model for consumables (coffee, supplements, pet food). Go deeper: launch playbook.
• Curated box — the merchant picks what ships each cycle, often themed. The product is the experience of opening it. Higher perceived value, faster churn if the curation gets stale.
• Membership — recurring fee for access (perks, exclusive content, member-only discounts, free shipping) rather than a physical product on a schedule. Often paired with a subscribe-and-save catalog.
• Build-a-box — the customer assembles each cycle's contents from a curated pool. Highest engagement and best retention of the four, but the most complex to set up and the most fulfillment friction.

Most stores either pick one model or run two in parallel — for example, subscribe-and-save on the hero SKUs plus a curated discovery box for new variants. Membership is often layered on top of either: pay $9/mo to unlock the subscriber discount on top of the catalog. The choice should follow the product: consumables with predictable consumption fit subscribe-and-save naturally, while artisan goods with shifting preferences need the curation of a box or build-a-box to keep subscribers from cancelling out of boredom.

The Shopify-native pieces (the foundation)

Whether you build your own subscription system or install an app, four Shopify primitives are doing the heavy lifting underneath. Knowing what each one does makes every weird edge case later (price mismatches, discount stacking, mixed carts, B2B pricing) much easier to reason about.

• Selling plans — the recipe for a recurring purchase: billing policy (how often to charge), delivery policy (how often to ship), and pricing policy (the discount applied). Attached to product variants via selling plan groups. Go deeper: selling plans explained.
• Subscription contracts — created at checkout when a customer buys a subscription. Stores the customer, the payment method, the selling plan, the renewal date, and the line items. Owned by the app that created it (which matters for migrations).
• Customer payment methods — the vaulted card token. Shopify Payments stores the card; the app never sees raw card data. This is why subscriptions work via Shopify Payments and not arbitrary third-party gateways.
• Checkout extensions — let apps customize the checkout (e.g., bundle a subscription-only upsell, swap the post-purchase step). Largely optional for a basic subscribe-and-save store.

These pieces work together via a small but well-defined API surface. When a customer subscribes, the app calls subscriptionContractCreate, Shopify stores the contract, and from then on the app schedules renewals by calling subscriptionContractAtomicCreate (the renewal-order primitive) on the appropriate dates. Everything else — the actual charge, the order creation, the inventory deduction, the tax calculation, the discount application — is handled by Shopify natively. Go deeper: the full API surface and what each call does.

The app layer — what subscription apps add on top

If Shopify ships the primitives, why do you need an app at all? Because the primitives don't include the workflow. Shopify doesn't run the renewal cron, doesn't ship a widget, doesn't email subscribers when their card fails, doesn't give them a portal to skip a delivery, doesn't track MRR or churn. The app is the orchestration layer that turns 'Shopify has selling plans' into 'a working subscription business.'

Different apps put their effort in different places — some prioritize the widget and conversion, some prioritize the portal and retention, some compete on price and operate as a no-frills billing engine. Almost all of them now use Shopify's native Subscription Contracts API under the hood (the few that still run parallel databases are migrating away or losing market share). Go deeper: how the major apps compare.

• The widget — what customers see on the product page. Drives the subscribe conversion rate.
• The billing engine — runs the renewal cron, handles retries on failure, manages skip/pause/swap state changes.
• The customer portal — self-service for subscribers. The single biggest determinant of support load and churn.
• Dunning — the retry-and-email flow when a card fails. Recovers 5-10% of MRR that would otherwise vanish.
• Analytics + merchant dashboard — MRR, churn, cohort retention, payment health.

The merchant journey at a glance

From an empty store to a working subscription business takes about a week of decisions and roughly an hour of actual technical setup. The technical part is fast because the app handles most of it via theme app extensions; the decisions are slow because picking the wrong cadence, discount, or fulfillment policy is expensive to undo later.

1. Decide cadence, discount, and which products are subscribable (not all SKUs should be)
2. Pick an app and install it from the Shopify App Store
3. Create one or two selling plans (e.g., monthly with 10% off)
4. Attach selling plans to the right product variants
5. Add the subscribe widget to the product page via theme editor
6. Configure the customer portal (branding, allowed actions)
7. Set up dunning policy (retry schedule, email templates)
8. Test with a real card in test mode — checkout, renewal, portal, cancel
9. Disclose auto-renewal terms in cart, checkout, and confirmation email
10. Go live, monitor first 20 subscribers closely

The end-to-end walkthrough with the operational details (stockout policy, fulfillment spikes, legal disclosure, pricing math) lives in the launch playbook. Go deeper: how to sell subscriptions on Shopify, end to end.

Pricing the app stack — what subscriptions actually cost to run

The headline monthly price on the App Store is rarely what you actually pay. Most subscription apps charge a monthly base fee plus a transaction fee on each renewal — and the transaction fee is what dominates the bill once you're past about $5k MRR. Apps that look cheap at install ($19-99/mo base) often become the most expensive line item in your stack at scale.

• Base monthly fee — typically $39-499/mo depending on the app and tier. Predictable.
• Transaction fee — often 1-2% of subscription revenue, plus 19-25¢ per renewal. Scales with success. This is where apps quietly take more as you grow.
• Tiered subscriber pricing — some apps add per-subscriber charges above a low threshold (e.g., free up to 100 subscribers, then $0.10/subscriber/mo). Cheap to start, expensive to grow.
• Flat-fee apps — a fixed monthly cost regardless of MRR or subscriber count. Cheaper than transaction-fee apps past about $8k MRR. Go deeper: no transaction fee comparison.

Run the math on your 12-month MRR projection, not your install-day number. An app that's $99/mo + 1% looks cheap at $2k MRR ($119/mo total) and brutal at $50k MRR ($599/mo). Past about $8k MRR, a flat-fee app at $79-299/mo typically wins by a wide margin. The structural takeaway: transaction-fee apps optimize for low entry, flat-fee apps optimize for scale — pick the one that matches your trajectory.

Retention — why this matters more than acquisition

Most subscription businesses obsess over the subscribe conversion rate on the product page. That's the wrong lever past month one. A subscriber who stays 6 months is worth roughly 3x a subscriber who stays 2 months, and the difference between those outcomes is almost entirely about retention mechanics — the portal, the cancel flow, the dunning policy, the stockout handling — not the acquisition funnel.

The math: if you spend $25 to acquire a subscriber and they churn after 2 orders, you've paid $25 for $36 of gross profit (assuming $30 AOV, 60% margin). If they stay 6 orders, you've paid $25 for $108. Doubling your retention from 2 to 4 orders is mathematically equivalent to doubling your ad budget at constant CAC — and it costs nothing because the levers are mostly operational.

Go deeper: the full retention playbook.

Operational considerations — fulfillment, support, dunning

Subscription orders behave differently from one-time orders in three ways that consistently surprise first-time merchants: renewal-day concentration creates fulfillment spikes, recurring charges create predictable support volume (skip, swap, address change), and roughly 5-10% of cards fail every cycle which means dunning isn't optional.

Fulfillment spikes. If most subscribers sign up on the 1st of the month, your renewal volume concentrates on the 1st — you'll see a 200-400% volume spike on a single day. Most 3PLs are set up for steady-state volume and a Monday-morning spike is a real fulfillment risk. Two fixes: spread renewals across the month by offering multiple cadences (weekly + biweekly + monthly), or charge on signup-date anniversary instead of a calendar-date default (most apps support this).

Support volume. Subscription support volume falls into 5 categories: skip next delivery, update payment method, change shipping address, pause, cancel. A self-service portal handles all 5 without a ticket. Stores that launch without a portal typically run 40-60% higher support volume than stores that launch with one.

Dunning. 5-10% of card-on-file charges fail every cycle — expired cards, fraud blocks, temporary holds. Without retries, that's 5-10% of MRR vanishing every month as 'passive churn.' Smart dunning (retry on day 1, 3, and 7 with a branded email each time) recovers most of it. Go deeper: dunning playbook.

Legal and compliance — the overview

Subscription commerce is regulated in ways one-time commerce isn't, primarily because auto-renewal is the part regulators care about. The big-ticket items: US auto-renewal disclosure laws (California's AB-390, plus similar in New York, Illinois, Vermont), the EU Consumer Rights Directive, and the FTC's 'Click-to-Cancel' rule.

• US auto-renewal disclosure — recurring price, renewal frequency, and how to cancel must be disclosed before the customer clicks 'subscribe' AND in the confirmation email. California mandates a one-click cancel mechanism in the portal.
• EU CRD — confirmation of subscription terms before checkout completes, 14-day cooling-off period for the first order.
• FTC Click-to-Cancel — cancellation must be at least as easy as signup (no phone-only cancellation if signup was online).
• Tax — Shopify Tax handles US state tax and EU VAT automatically; renewals are taxed at the renewal-date jurisdiction.

The depth on each requirement, with the disclosure copy patterns that satisfy regulators, lives in the launch guide. Go deeper: auto-renewal disclosure, tax, and the legal side.

When subscriptions are the wrong answer

Subscription apps make money when you install them. They don't make money telling you not to. So here's the honest view: subscriptions amplify products that customers already want to repurchase. They don't manufacture demand that isn't there, and pushing them on the wrong product can damage the rest of your store's reputation.

Good fit: consumables with predictable repurchase (coffee, supplements, pet food, household), curated discovery products where the experience IS the product (boxes), refills (razor blades, contact lenses), and any product with a known natural consumption interval.

Bad fit: long-replacement-cycle goods (cookware, electronics, furniture), apparel where size and style shift, gift items, artisan goods bought 'for the experience' of choosing them, and high-ticket items where the recurring charge will trigger a customer's monthly statement scan. If a typical customer would think twice about whether to keep the subscription every month, the model is wrong for the product.

Go deeper: when subscriptions are the wrong answer (detailed).