A full subscription platform,
not just another Shopify app

The subscription lifecycle: where each component fits

A subscription business has four distinct phases in the subscriber lifecycle, and a real platform needs to address all of them. Acquisition is the storefront widget — the subscribe-and-save offer that converts a one-time buyer into a recurring customer. Activation is the onboarding experience after the first order. Retention is everything that keeps the subscriber active: the customer portal, skip/pause/swap functionality, dunning for failed payments, and proactive win-back. Analytics closes the loop — MRR trends, churn rate, cohort survival, and LTV give the merchant the data to make decisions at each of the three prior stages.

• Acquisition — subscribe-and-save widget on product pages
• Activation — first-order confirmation, portal access, onboarding emails
• Retention — portal, flexible actions, dunning, win-back sequences
• Analytics — MRR, churn, cohort LTV, cancellation reason data

Why native Shopify subscription contracts matter

Some subscription platforms store subscription data in their own databases, parallel to Shopify's. This approach creates two sources of truth and makes migration painful — your subscription data is in the app's database, not Shopify's. Platforms built on Shopify's native subscription contract API store all contract data in Shopify directly. When you run reports in Shopify, your subscription data is there. When you want to migrate to a different app, the contracts move with you. When Shopify releases new subscription features, they're immediately available. The architecture decision of where data lives has long-term consequences that compound over time.

Billing automation and dunning

Subscription billing isn't just charging a card on a schedule. Failed payments are a constant reality — cards expire, limits are hit, banks flag unusual charges. Dunning is the automated process of retrying failed payments on an intelligent schedule and communicating with the subscriber about the failure. A platform's dunning system should support configurable retry intervals, email notifications at each stage, and a final status update when a subscription is suspended due to non-payment. Without good dunning, involuntary churn (subscribers who wanted to stay but whose card failed) can represent 5–15% of overall churn.

• Configurable retry schedule — 3 days, 5 days, 7 days post-failure
• Email notifications to subscriber at each retry attempt
• Merchant dashboard visibility into dunning status per contract
• Automatic suspension after retry limit reached
• Win-back flow triggered on suspension

Analytics: what subscription metrics actually matter

Monthly Recurring Revenue (MRR) is the foundation — the total expected recurring revenue from active subscriptions in the current month. Churn rate is MRR lost to cancellation and suspension divided by beginning MRR. Cohort survival rate shows what percentage of subscribers who started in a given month are still active after 1, 3, 6, and 12 months. Average Order Value (AOV) for subscription orders tracks whether subscribers are upgrading or downgrading over time. LTV (Lifetime Value) combines survival rate with AOV to give the real value of a subscriber cohort. Platforms that only show you total subscribers and a revenue number are hiding information you need.

• MRR and MRR growth trend
• Churn rate — voluntary and involuntary broken out
• Cohort survival curves — 1/3/6/12 month retention
• Cancellation reason distribution
• Dunning success rate — recovered payments / total failures

REST API and webhooks: when the platform needs to fit into a larger stack

Growing subscription businesses don't run on a single tool. They have ERPs, loyalty programmes, fulfilment systems, and customer data platforms that need subscription data. A platform with a public REST API and webhooks allows subscription data to flow into the broader stack without manual exports or custom integrations built on fragile screen-scraping. Key events — new subscription, renewal, cancellation, suspension, address change — should all be available as webhooks so downstream systems can react in real time.

Pricing model: why flat fee beats per-transaction for growing merchants

Transaction-fee pricing (0.5%–1% of subscription revenue) sounds small and feels manageable when you're starting out with $10k in MRR. At $100k MRR it's $500–$1,000/mo in additional fees on top of the base subscription. At $500k MRR it's $2,500–$5,000/mo. A flat-fee platform removes this growth penalty entirely. The cost of the platform does not scale with your success. For merchants at any meaningful subscription revenue level, the arithmetic on flat-fee vs per-transaction platforms becomes obvious quickly.

• $10k MRR → 1% fee = $100/mo. Flat fee = $79/mo. Difference: $21
• $100k MRR → 1% fee = $1,000/mo. Flat fee = $79/mo. Difference: $921
• $500k MRR → 1% fee = $5,000/mo. Flat fee = $79/mo. Difference: $4,921