What a Shopify subscription app does (and what it doesn't)

What a subscription app actually does

Shopify ships the underlying subscription primitives — the contracts API, selling plans, vaulted payment methods, native checkout. What Shopify does NOT ship: a product-page widget that converts shoppers into subscribers, a cron job that runs renewals on the right dates, a customer portal where subscribers can self-manage, a dunning flow when cards fail, and a dashboard that shows you MRR and churn. The subscription app fills exactly that gap. It's an orchestration layer that takes Shopify's primitives and turns them into a working subscription business.

Put differently: Shopify owns the data (contracts, payment tokens, orders, customers). The app owns the workflow (creating selling plans, running the renewal cron, rendering the widget, managing the portal, sending dunning emails, surfacing analytics). The data persists even if you uninstall the app — your contracts stay in Shopify. The workflow only exists while the app is installed. That separation is what makes switching apps possible without losing subscribers.

The five components every subscription app provides

Almost every subscription app is some combination of the same five things. When you're comparing apps, you're really comparing how well each one executes on each of these — not whether they have the feature at all.

1. Selling plan management — the admin UI for creating, editing, and assigning selling plans to product variants. Includes discount structure, cadence options, and product eligibility rules.
2. Billing engine — the cron job that runs renewals on the right dates, handles retries on failure, and manages state changes (skip, pause, swap). The least visible piece, the most critical.
3. Customer portal — the self-service interface where subscribers manage their own subscriptions. Skip, pause, swap, update card, update address, cancel.
4. Webhooks and integrations — events fire when subscriptions change state (created, renewed, paused, cancelled). Powers email automations, dashboards, and external systems.
5. Merchant dashboard — MRR, churn, active subscriber count, cohort retention, failed payment recovery rates. Your view into the subscription business.

Apps differentiate by which components they invest in. Loop and Recharge spend heavily on the dashboard and analytics. Skio invests in the widget conversion rate. Appstle adds breadth at the expense of depth in any single area. SimpleSubscription bets on portal quality and pricing transparency. There's no single 'best' app — there's a best fit for what your store needs.

Why you can't just use Shopify native

Shopify's Subscription Contracts API is powerful but incomplete on its own. It lets you create, update, and bill contracts via GraphQL — but it doesn't ship the orchestration. Concretely, here's what's missing from native Shopify and why the app exists:

• No product-page widget — Shopify ships the contract API, but the storefront UI to offer subscriptions is the merchant's responsibility (or the app's).
• No renewal cron — Shopify doesn't automatically charge on renewal dates. The app must call subscriptionContractAtomicCreate on the right day for each contract.
• No customer portal — Shopify's customer account area doesn't include subscription management. Subscribers can see their orders, not manage their subscriptions.
• No dunning logic — Shopify will attempt the charge; if it fails, the app decides what to do (retry tomorrow, retry in 3 days, send an email, pause the contract).
• No subscription analytics — Shopify analytics shows orders, not subscription health. MRR, churn, cohort retention need a separate layer.
• No widget UI for cancel-save flows — the cancel page, the pause offer, the discount intercept all need to be built somewhere.

An app fills every one of those gaps. Building them yourself is what the 'buy vs build' section below addresses. Go deeper: how the native API works and what it does ship.

The install decision — when to install an app at all

If you're selling consumables on Shopify and any meaningful portion of your customers repurchase, you should install a subscription app. The economics are straightforward: a free-tier app costs $0 until you have meaningful MRR, the install is under 10 minutes, and even a 5% subscribe rate at the product page meaningfully changes your business.

The decision is less obvious in three cases: very low repurchase products (where almost no one would subscribe), very high AOV products (where the recurring charge is too large for most customers to commit to), and products where the customer experience is choosing each time (artisan goods, novelty). In those cases, run the math: at what subscribe rate and retention curve does the app pay for itself? Most apps have free tiers up to 100 subscribers, so the question is really 'do I think I'll exceed 100 subscribers within a year?' If yes, install now and build the funnel. If you're genuinely unsure, install free anyway — the only cost is a day of evaluation.

How to compare apps before committing

The Shopify App Store sorts by review count and rating, which mostly reflects how long an app has been around and how hard it pushes for reviews — not how well it would fit your store. The better evaluation method is to identify the 2-3 components from the five above that matter most to your business, then evaluate each shortlisted app specifically on those.

• If retention is the priority — portal quality and cancel-save flow are what matter. Install the app's free tier, create a test subscription, log in as a subscriber, see how many taps to skip, swap, pause, cancel.
• If pricing matters — model the cost at your year-2 projected MRR, not month-1. Transaction fees compound. Flat-fee apps win past about $8k MRR. Go deeper: no-transaction-fee comparison.
• If conversion is the priority — widget quality matters. Look at how the widget renders on mobile (where 70%+ of traffic is) and how prominently the savings number is displayed.
• If you're migrating from another app — confirm the new app handles payment method migration, not just contract migration. Migrations that force subscribers to re-enter cards cause significant churn.

Go deeper: the head-to-head comparison framework.

The questions to ask in a pre-install demo

Most subscription app demos are scripted around the marketing message. To get useful signal you have to redirect to operational questions — the answers tell you whether you'll regret the install in month 6.

Go deeper: how to evaluate Shopify subscription apps in the App Store.

The cost dimension — monthly fee vs transaction fee

Subscription app pricing comes in three structures: flat monthly fee, transaction fee (% of subscription revenue), and tiered subscriber pricing (per-subscriber fee above a threshold). Each rewards different growth curves and each app picks the one that maximizes their revenue against their customer base.

• Flat monthly fee — predictable cost regardless of MRR. Examples: SimpleSubscription (free up to 50 active subs, then $39/mo Growth flat), Yotpo Subscriptions (tiered flat).
• Transaction fee — base monthly fee + 0.5-2% of subscription revenue. Examples: Recharge ($99 + 1.49% + 19¢), Loop ($99 + 1%), Skio ($499 + 1% + 20¢).
• Per-subscriber — base + per-active-subscriber charge. Examples: Appstle (cheap up to a subscriber threshold, then per-subscriber pricing).

The math: at $20k MRR, a 1% transaction fee app costs $200/mo on top of the base fee, totaling $250-300/mo. A flat-fee app at $79-149/mo costs less than half. At $50k MRR, the transaction fee app is $500-745/mo. The flat-fee app is still $79-299/mo. Transaction-fee apps optimize for low entry; flat-fee apps optimize for scale. Pick the structure that matches your projected trajectory, not your install-day number. Go deeper: no-transaction-fee comparison.

Migration cost — switching apps later

Migrations between subscription apps used to be brutal because every app ran its own subscription database. Today, with most apps on Shopify's native Subscription Contracts API, the contracts themselves are portable — they live in Shopify, not in the app. Migration mostly involves the destination app picking up the existing contracts and applying its own metadata (cancel-save offers, dunning policy, portal branding).

Two things still cause friction. First, payment method migration: if the source app used a different vaulting mechanism, subscribers may have to re-enter cards (and you'll lose some). Most modern apps use Shopify Payments vaulting and don't have this problem. Second, parallel-database apps (a shrinking minority) require export/import and bespoke migration tooling. Before installing any app, ask explicitly: 'If I want to leave in two years, what does my migration look like?' The honest answer separates apps that are easy to leave from apps that aren't.

Go deeper: subscription migration guide.

The Shopify Sidekick AI angle — ask + act inside the admin

Shopify Sidekick is the AI assistant inside the Shopify admin that answers natural-language questions about your store. For subscription merchants, the question is whether a subscription app extends Sidekick so you can both ask about your subscriptions ('what's my MRR trend?', 'which products have the worst churn?') AND let Sidekick open the right editor in one click when you want to act on the answer.

SimpleSubscription's Sidekick extension does both. Sidekick never mutates data directly — instead it deep-links you to the plan editor, the subscriber detail, the win-back editor, loyalty config, email/SMS settings or analytics, with the right action modal pre-opened so you click confirm once. Every mutation still goes through an admin editor with explicit confirmation, audit trail, and undo path. The apps without a Sidekick extension leave you context-switching for every question or change. It's becoming a meaningful differentiator. Go deeper: how Sidekick integrates with subscription data.

Buy vs build — the question for $100k+ MRR stores

At some scale, the transaction-fee or flat-fee app cost crosses the threshold where in-house engineering starts to look cheaper. For most stores that's never — you're better off paying $200-500/mo for software that solves a hard problem reliably. But past about $100k MRR with a transaction-fee app, the math shifts.

Concretely: at $200k MRR with a 1.49% + 19¢ transaction-fee app, the app cost is $3,000+/mo, or $36k+/year. A single backend engineer half-time on subscription infrastructure costs $50-75k/year fully loaded. The build-vs-buy calculation is much closer than at $20k MRR, and at $500k+ MRR the in-house build is unambiguously cheaper on raw cost.

But cost is one variable. The harder ones: the build is 4-6 months of engineering before you have parity with a $99/mo app, dunning logic has edge cases that take years to harden in production (every payment processor has different retry semantics), and you have to maintain it forever including when Shopify changes their API. Most stores past $100k MRR pick a flat-fee app (no transaction-fee tax on scale) rather than building, because the build cost is more than the flat-fee app for years to come and the engineering team has higher-leverage things to work on.

If two or fewer of those apply, stay on an app and pick the right cost structure. If four or five apply, the build conversation is worth having seriously.