Shopify Subscription App — the complete 2026 guide

What a Shopify subscription app actually does

At the simplest level, a subscription app does three things: it lets a customer commit to receiving a product repeatedly (selling plans), it bills their saved payment method on a recurring schedule and creates a new Shopify order each time (recurring billing), and it gives both the customer and the merchant a way to manage that ongoing relationship without anyone needing to email support (the portal and admin). Every other feature — bundles, gifts, memberships, win-back campaigns, churn analytics — is a layer built on top of those three primitives.

What separates a good subscription app from a basic one is how completely it covers the edge cases. What happens when a renewal payment fails — does the app retry intelligently, send dunning emails in the right tone, and recover the revenue silently, or does it just cancel the subscription on the first failure? What happens when a customer wants to skip one delivery — is it a single click in the portal, or do they have to email support? What happens when you change the price of a product — do existing subscribers stay on the old price (locked-in pricing) or get migrated to the new one? The basics are commoditized; the edge cases are where merchant time and customer trust actually live.

• Selling plans: The schedule + discount combinations a customer can choose at the product page (every 4 weeks 10% off, every 8 weeks 15% off, etc.)
• Recurring billing: Charges the saved payment method, creates a Shopify order, fulfills like any other order, retries failures
• Customer portal: Where the subscriber skips, pauses, swaps, updates payment/address/frequency without contacting you
• Merchant admin: The view of all active subscriptions with filters, search, bulk actions, and analytics
• Retention tooling: Cancel-save flows, win-back campaigns, smart pause offers, discount automations
• Analytics: MRR, churn, LTV, cohort retention, billing success rate, at-risk subscriber prediction

How Shopify subscriptions actually work under the hood

Modern Shopify subscription apps are built on the Subscription Contract API that Shopify launched in 2021. The contract is a native Shopify object — it lives in Shopify's database, not the app's — and it stores the line items, the next billing date, the customer, the payment method, the delivery schedule, and the discount applied. Every modern third-party app reads and writes the same underlying data structure. That is why migration between apps is usually painless: the subscriber data isn't trapped inside the old app, it's stored in Shopify.

When a renewal date arrives, the app's billing engine queries Shopify for contracts due today, asks Shopify to charge the saved payment method, and on success creates a Shopify order linked to the contract. The order moves through the same fulfillment flow as any one-time order — your shipping app sees it, your warehouse picks it, your tax engine taxes it. That is the architectural reason native subscriptions feel seamless: there is no parallel ordering system. The subscription is just a contract that periodically spawns regular Shopify orders.

The app layer on top of the contract is where the differentiation lives. Two apps can read the same Subscription Contract object and present completely different portal experiences, completely different analytics, and completely different retention behavior. The contract is the standardized layer; the app is the experience and intelligence layer. When you pick a subscription app you're not picking a database — you're picking the experience and intelligence wrapper around a database Shopify already owns. See our Subscription API guide for the deeper architectural walkthrough.

Pricing models — flat-fee vs percentage of revenue vs hybrid

The single most consequential decision when picking a Shopify subscription app is understanding how cost scales with revenue. Three pricing models dominate the market and the math diverges dramatically as you grow. Flat-fee apps charge a fixed monthly amount regardless of subscription revenue (SimpleSubscription Free $0 up to 50 active subs, Growth $39, Premium $99). Percentage-of-revenue apps charge a percentage of every subscription order — sometimes with a smaller flat fee on top (Recharge 1.49% + 19¢ per transaction + $99/month; Loop ~1% + $99/month). Hybrid models combine both. The percentage model is cheaper while your MRR is tiny and brutally more expensive once you scale.

Run the math at the MRR you expect in 18 months, not the MRR you have on day one. At $5k MRR, a 1.49% percentage app costs roughly $174 per month total — already more than a flat-fee $39 plan. At $20k MRR, the same percentage app costs about $397 per month, four times the flat fee. At $50k MRR, the percentage take alone is $745, before you add the monthly subscription. The flat-fee app at $99 is the same $99. The break-even point where flat-fee becomes cheaper is around $2-4k MRR; above that, the difference compounds month over month and never reverses.

Cost comparison at different MRR levels (per month, app fee only):

  $5k MRR (~500 active subscribers):
    Flat-fee (SimpleSubscription Growth $39):    $39
    Recharge (1.49% + 19c + $99/mo):             ~$173
    Loop (1% + $99/mo):                          ~$149
    Skio ($499/mo + 1% + 20c):                   ~$549

  $20k MRR (~2,000 active subscribers):
    Flat-fee (SimpleSubscription Premium $99):   $99
    Recharge:                                    ~$397
    Loop:                                        ~$299
    Skio:                                        ~$699

  $50k MRR (~5,000 active subscribers):
    Flat-fee (SimpleSubscription Premium $99):   $99
    Recharge:                                    ~$844
    Loop:                                        ~$599
    Skio:                                        ~$999

Native Shopify checkout vs third-party checkout — why it matters

Some older subscription apps route customers through a third-party checkout page hosted on the app vendor's own domain. Modern apps built on the Subscription Contract API use Shopify's native checkout — the customer never leaves your store, the URL bar never changes domains, and the checkout has all the polish, fraud protection, and conversion optimization that Shopify continuously invests in. The conversion difference is significant: native checkout typically converts 10-30% better than a third-party redirect, and Shop Pay one-click checkout is only available on native.

Third-party checkout was the historical norm because the Subscription Contract API didn't exist before 2021. Apps built before then had to build their own checkout to handle the saved payment method and recurring billing. Many of those apps now offer a native-checkout option, but some have legacy customers still on the third-party flow, and the migration is non-trivial. When evaluating an app, confirm explicitly that subscriptions use native Shopify Checkout — not the app's hosted checkout — and that Shop Pay is supported. Anything less is leaving conversion (and money) on the table.

• Native Shopify Checkout: Customer stays on yourstore.com, full Shopify checkout UX, Shop Pay available, all Shopify apps (gift cards, tax, shipping rate calculators) work natively
• Third-party hosted checkout: Customer redirects to the app vendor's domain, custom UX (varies by app), Shop Pay typically unavailable, limited integration with other Shopify apps
• Conversion impact: Typically 10-30% better on native checkout vs third-party hosted
• Trust signal: Native checkout looks and feels like the rest of your store — third-party redirect breaks trust at the highest-friction moment

The customer portal — the most underrated feature

A self-service customer portal is the single feature that most reduces merchant support load and most affects subscriber retention. When subscribers can skip a delivery, swap a product, pause their subscription, update their address, or change their payment method without emailing support, merchants report 40-60% fewer subscription-related tickets. The quality of the portal — speed, mobile experience, branded design, language coverage, login friction — directly affects both retention and customer satisfaction.

The portal features that matter most: passwordless magic-link login (subscribers hate passwords more than anything), single-click skip with an auto-resume reminder email, product swap that doesn't require re-subscribing, in-portal address update that syncs back to Shopify, payment method update that uses Shopify's PCI-compliant card collector, and a pause option with a date the subscription will resume on its own. Pause-and-resume is particularly powerful: pause typically saves 18-25% of customers who would otherwise have cancelled, because life events (vacation, surplus inventory at home) are the actual reason — not dissatisfaction.

Beyond the actions themselves, the portal's polish matters disproportionately. A portal with the app vendor's branding instead of the merchant's, a portal that doesn't translate to the customer's language, or a portal hosted on a third-party domain (subscriptions.app-vendor.com instead of account.merchant.com) all break trust at the exact moment a subscriber is deciding whether to stay. Custom domain portal support, white-label branding, and multi-language coverage are not cosmetic features — they are retention features. See the customer portal deep-dive for the full feature matrix.

Retention tooling — cancel-save flows, win-back, smart pause

Voluntary churn (subscribers actively choosing to cancel) is the largest preventable line item in any subscription business. A serious subscription app gives you tools to intercept the cancel click before it commits — a multi-step retention flow that walks the subscriber through a reason survey, then a tailored offer (pause this month, swap to a smaller size, take 20% off next order) before any final confirmation. The reason survey alone has product value: it tells you what's actually driving churn so you can fix the underlying product or pricing issue.

Branched offers — where the offer shown depends on the reason the subscriber clicked — are noticeably more effective than a single static save offer. A subscriber who clicked cancel because they have too much product at home should be offered pause, not discount (discount makes the inventory problem worse). A subscriber who cited price should see a discount or a downgrade to a less frequent cadence. A subscriber who cited a product issue should be offered a swap to a different variant. The same generic 'here's 10% off' offer to every subscriber leaves money on the table compared to a reason-aware branched flow.

Win-back campaigns — automated emails sent 30, 60, and 90 days after a cancellation — recover 5-15% of churned subscribers. The mechanics: trigger an email at +30 days with a soft return offer (a discount or a free trial of a new product), then a stronger offer at +60, then a final win-back at +90 with a substantial incentive. After 90 days the recovery probability collapses. This is fully automatable and runs as a background process; it should not require manual operator work. See win-back campaigns and reduce subscription churn for the playbooks.

• Cancel reason survey: Capture why before showing any save offer — this data drives product decisions, not just retention
• Branched save offer: Pause for inventory-overload, discount for price, swap for product issue, address update for missed-delivery
• Smart pause: Auto-resume date with reminder email — typically saves 18-25% of cancel attempts
• Win-back automation: Email sequence at +30/+60/+90 days post-cancel with escalating offers
• AI churn prediction: Identify at-risk subscribers from behavioral signals before they click cancel — intervene with a proactive offer

Merchandising — bundles, build-a-box, gifts, memberships

Beyond plain subscribe-and-save, modern subscription stores increasingly use merchandising features to differentiate. A build-a-box lets the subscriber customize the contents of each delivery from a curated catalog (popular for snacks, supplements, coffee, pet food). A mystery box surprises the subscriber with curated picks each delivery (popular for beauty, books, hobby kits). A gift subscription lets a buyer purchase a fixed-duration subscription as a present, with the recipient receiving a magic-link to claim it. A membership plan bundles ongoing benefits (free shipping, exclusive products, members-only pricing) into a recurring fee.

These merchandising features are where pricing-tier gating gets meaningful. The base subscribe-and-save flow is supported by every app, including Shopify's free native Subscriptions app. Build-a-box, gift subscriptions, and memberships are typically paid-tier-only and are why many merchants outgrow the free tier within the first six months. If your product category fits any of these patterns, factor the feature into the app evaluation up front — switching apps to gain access to a single merchandising feature is more painful than choosing the right app initially. See the deeper guides on build-a-box, gift subscriptions, and memberships.

The economic case for merchandising features is straightforward: they raise AOV (average order value) and improve retention. A subscriber who customizes their box each month engages more with the product than one passively receiving the same items — engagement correlates strongly with retention. A gift subscription brings in a new customer at zero CAC (the gifter does the marketing for you). A membership plan creates a behavioral commitment beyond just the recurring charge. None of these are cheap to build well — the app's depth on each feature is a real differentiator.

Subscription analytics — MRR, churn, LTV, billing success

Four metrics define a subscription business's health: Monthly Recurring Revenue (MRR), churn rate, Lifetime Value (LTV), and billing success rate. An app that surfaces these in real time — with cohort breakdowns, product-level performance, and trend lines — lets operators make informed decisions about pricing, retention offers, and product mix. Without this visibility, churn is invisible until it's already expensive: by the time you notice MRR has plateaued or declined, the cohort that's leaving has already done so.

Cohort retention is the single most diagnostic chart. Plot the percentage of subscribers from each month's signup cohort still active at month 1, 2, 3, 6, 12 — and you can immediately see whether retention is improving or degrading over time. A change to the welcome email, the first-delivery experience, or the pricing should show up as a different curve in the next cohort. Without cohort analytics, you're flying blind on every retention experiment. Most basic subscription apps surface only aggregate churn (a single number for the whole base), which hides the variance between cohorts and makes experiments unmeasurable.

Billing success rate is the quietly important metric. Failed renewal payments — typically 3-8% of all renewal attempts — are the leading involuntary churn cause. Apps that retry failed payments intelligently (next day, 3 days later, 7 days later, with dunning emails between attempts) recover 50-70% of those failures. Apps that retry once and give up recover maybe 20%. The difference is a 2-5% swing in monthly revenue, every month. See the payment recovery and dunning guides for the mechanics, and the analytics dashboard guide for the full metric set.

• MRR: Real-time monthly recurring revenue with week-over-week trend
• Churn rate: Voluntary and involuntary, broken out by cohort, product, and billing interval
• LTV: Lifetime value per subscriber, segmented by acquisition channel and plan
• Billing success rate: Renewal payment success vs failure, dunning recovery rate
• Cohort retention: Percentage of each month's cohort still active at month 1, 2, 3, 6, 12 — the most diagnostic chart in any subscription business
• At-risk subscribers: Behavioral-signal-based prediction of subscribers likely to churn in the next 30 days

Dunning — how good apps recover failed renewal payments

On any given renewal day, 3-8% of payment attempts fail. The reasons are mundane: expired card, insufficient funds, bank fraud-detection false positive, declined for risk by the processor. None of these mean the subscriber wants to cancel — they're just temporary failures. Dunning is the practice of retrying the payment intelligently and notifying the subscriber by email when their action is needed (typically to update the card). A good dunning sequence recovers 50-70% of failed payments; a bad one recovers 15-25%.

The mechanics: when a payment fails, the app sends a polite email to the subscriber ('your card was declined — update it here in 30 seconds') with a deep link to update their payment method in the portal. The app retries the payment after a configurable interval (next day is typical). If the retry fails, a slightly firmer email goes out. After 3-5 retries spread over a week, the subscription is paused or cancelled with a final notification. Throughout, the tone should be human ('we noticed your card expired') not transactional ('PAYMENT FAILED'). Subscribers who churn because of a $0.99 declined payment they would have happily paid are the easiest revenue to recover — and the most embarrassing to lose.

Dunning is one of those features where the difference between a $0 app and a $39/month app is starkly visible. Free-tier apps often cancel on the first failure or after one retry; paid-tier apps run multi-retry sequences with escalating email cadence. On a $20k MRR business, even a 3% involuntary churn improvement from better dunning is $600/month recovered — fifteen times the cost of the app. See the dunning management and failed payment recovery guides for the implementation depth.

Migration — moving from Recharge, Loop, or Skio without losing subscribers

Migrating from one subscription app to another is one of the most stressful operations in a subscription business — and most merchants overestimate the technical risk. Because subscriber data lives in Shopify's Subscription Contract API (not inside the old app), migrations are largely about coordination, not data movement. The contract continues to exist regardless of which app is reading it. The mechanics: install the new app alongside the old one, configure selling plans and emails to match, switch the storefront widget to the new app's selling plans, let existing subscribers continue billing on their old plans until renewal, then disable the old app after the last subscriber has migrated.

Free migration assistance is one of the practical differentiators between subscription apps. The vendors competing for share will typically run the migration for you at no cost — exporting your selling plan configuration, recreating it in their app, verifying that test renewals work end-to-end, and standing by for the cutover. Vendors who charge $500-2000 for migration assistance are signalling that migrations aren't their priority. When evaluating an app, ask the migration question explicitly: 'do you provide free migration assistance, and how long does a typical migration take?' The answer tells you a lot about how seriously they take onboarding.

• Subscriber contracts transfer automatically — they live in Shopify, not in the app
• Payment methods transfer — saved in Shopify's PCI-compliant vault, not the app
• Billing dates and order history transfer — preserved as native Shopify objects
• Selling plans rebuild — configuration is app-specific and gets recreated in the new app
• Email templates rebuild — app-specific; rewrite once in the new app
• Portal URL changes — set up a redirect from the old portal URL to the new one to avoid breaking bookmarks and email deep links

Subscription apps and Shopify Sidekick AI

Shopify Sidekick is the in-admin AI assistant Shopify is rolling out to all merchants. It can answer merchant questions, run admin actions, and (importantly for subscription operators) take questions about subscription health and surface answers from your subscription app's data. The integration depth varies dramatically by app — apps powered by Shopify Sidekick AI via a native MCP extension can answer questions like 'which subscribers are at risk of churning this week' or 'show me MRR this month vs last month' or 'why did churn spike in week 12 of the spring cohort' directly in the Sidekick chat. Apps without a Sidekick extension force the merchant to dig through dashboards instead.

Sidekick AI integration is one of those features that's easy to dismiss until you start using it daily. The win is not the chat interface itself — it's that the operator can ask the question they actually have ('which subscribers ordered the spring blend three times then stopped — what was the reason?') instead of having to translate that into dashboard filters. The depth of the answer depends on how much subscription data the app exposes to Sidekick. Apps with a complete Sidekick MCP extension surface MRR, churn, cohort retention, at-risk predictions, billing failures, win-back candidates, and individual subscriber timelines. See the Sidekick subscriptions guide for the full feature list.

Onboarding, migration help, and ongoing support

Support quality matters more for subscription apps than for almost any other app category, because billing failures are time-sensitive and directly affect customer trust. If a renewal payment fails on a Saturday morning and the merchant has a question about the dunning sequence, a 72-hour email response is too slow — the subscriber will have already churned by the time the answer arrives. Live chat with same-day response on billing issues is the baseline expectation; phone or screen-share support is the differentiator at higher tiers.

Onboarding quality is the other invisible differentiator. A subscription app installation that takes 4 hours with documented step-by-step (selling plan setup, widget placement, email template configuration, portal customization, test renewal verification) is dramatically better than an installation that says 'we're installed!' and leaves the merchant to figure the rest out. Onboarding journey guides, in-app checklists, and a real human reaching out within 24 hours of install are signals that the vendor cares about the first-week experience. Read the App Store reviews specifically for first-week experience comments — they predict the long-term relationship more than any feature list.

• Free migration assistance: Vendor team handles the technical cutover (a fair expectation, not a luxury)
• Live chat for billing issues: Same-day response baseline; phone support for high tiers
• In-app onboarding checklist: Step-by-step guide visible inside the app, not a separate help center
• Test renewal verification: Tool to run a $0.01 test renewal end-to-end before going live
• Documented rollback: Clear procedure for backing out a change if something goes wrong post-launch
• Public changelog: Visible record of what's shipped recently — a signal the vendor is actively improving

The decision checklist — by store stage

After all the depth, here's the pragmatic decision tree. The right subscription app depends on your store stage, your product complexity, and your 18-month MRR target — not on what's cheapest on day one. Most stores follow a similar progression and the points where the right answer changes are predictable.

1. Idea stage / first 100 subscribers: Either Shopify Subscriptions (native, $0, no cap, basics only) or SimpleSubscription Free ($0 up to 100 active subscribers, includes portal, dunning, magic-link, analytics, and powered by Shopify Sidekick AI). Use it to validate that subscriptions work for your product.
2. 500 active subscribers / ~$5k MRR: Evaluate paid options seriously. You're past most free-tier caps and you need cancel-save flows, build-a-box, and retention tools. Flat-fee plans like SimpleSubscription Growth at $39/month make economic sense at this MRR; percentage-fee apps start being expensive.
3. 2,000-5,000 active subscribers / $20-50k MRR: Flat-fee is the clearly correct model. Percentage-fee apps would be charging $300-800/month in fees alone. SimpleSubscription Premium at $99/month (unlimited subscribers) covers this range cleanly.
4. Enterprise / $100k+ MRR: Flat-fee plans + custom requirements (white-label portal, custom domain, SSO, advanced webhooks). Percentage-fee apps would be costing $1,500+/month — dramatically more than any flat-fee enterprise plan.
5. Niche or hobbyist with stable subscriber count under 100: Free tier is fine indefinitely. The feature gap matters less when growth isn't happening.