What Is Loop Subscriptions? An Operator's Definition

Loop Subscriptions is a subscription-management app for Shopify stores: a customer self-serve portal, multi-stage cancellation and save flows, pause and swap tooling, and failed-payment recovery, sold as a newer, lower-cost alternative to Recharge and Skio. The distinguishing feature isn’t a single capability — most of what Loop does, Recharge and Skio also do — it’s the pricing model underneath: a flat monthly platform fee plus a percentage of subscription revenue, with no per-order transaction fee stacked on top. For a brand doing $3M–$30M, that structural difference matters more than any feature comparison.

What Does Switching to Loop Subscriptions Actually Change for an Operator?

Switching to Loop Subscriptions does not mainly change what a subscriber sees at checkout or in the self-serve portal — pause, skip, swap and cancel look broadly similar across Recharge, Skio and Loop now, because all three are built on Shopify’s own subscription contracts API and checkout extensibility. What changes is the vendor’s own incentive: Loop earns 0.75%–1.0% of subscription revenue with no flat per-order charge, a structure that pays out very differently depending on what a brand actually sells and how often it bills for it.

Loop’s revenue-share pricing has a direct operator consequence: a brand billing a high-ticket, low-frequency subscription — a $180 quarterly supplement stack, say, rather than a $30 monthly one — pays proportionally less on a revenue-share model than on a competitor charging a flat fee per order, because Loop’s fee tracks the dollar value moving through the subscription, not how often it moves. The comparison a finance team should run is not “what do we pay per order today” but “what do we pay per dollar of subscription revenue, at our actual AOV and billing cadence” — and that number changes if a brand later raises prices, moves to prepaid bundles, or shifts subscribers onto a longer billing interval.

How Does Loop’s Pricing Actually Compare to Recharge and Skio?

Checked directly against each vendor’s own pricing page in September 2026, Loop’s Pro plan costs $399 a month plus 0.75% of subscription revenue with no per-order fee; Recharge’s Plus plan costs $499 a month plus 1.34% of subscription revenue plus $0.19 per transaction; and Skio’s Scale plan costs $499 a month on annual billing or $599 on monthly billing, plus 1.0% of subscription revenue plus $0.20 per transaction.

Enterprise tiers on all three are excluded — none publish a rate, and every one quotes “custom” or “let’s talk” pricing.

The following worked example uses invented order-volume and average-order-value figures, not a real brand’s numbers, to show how those rate cards translate into an actual bill. At 1,000 subscription orders a month and a $50 average order value — $50,000 in monthly subscription GMV — Loop Pro comes to $399 plus 0.75% of $50,000 ($375), for $774. Recharge Plus comes to $499 plus 1.34% of $50,000 ($670) plus $0.19 × 1,000 orders ($190), for $1,359. Skio Scale on monthly billing comes to $599 plus 1.0% of $50,000 ($500) plus $0.20 × 1,000 orders ($200), for $1,299. At this illustrative volume, Loop Pro runs about 43% cheaper than Recharge Plus and about 40% cheaper than Skio’s monthly-billed Scale plan — a gap driven entirely by the absent per-order fee and the lower revenue percentage, not by any feature difference. The gap narrows at a lower average order value, because the per-order fees on Recharge and Skio become a smaller share of the bill relative to the revenue percentage, and widens further at a higher one — the actual crossover point for a specific brand’s own order count and AOV is arithmetic worth running before signing, not a number to borrow from this example.

One caveat that changes with time: Recharge acquired Skio for $105 million in cash on 30 April 2026, and Recharge’s own announcement states that “for merchants on both platforms, nothing is changing today,” with combined offerings described only as coming in the months ahead. The Skio pricing above is Skio’s own, still-separate published rate — not a merged Recharge-Skio price sheet, which does not yet exist.

How Long Does a Migration From Recharge or Skio to Loop Actually Take, and What Can Go Wrong?

Loop’s own migration page states that most migrations “wrap up within a few weeks” of planning and testing, run at no cost on any paid plan, and are handled by Loop’s own migration team rather than the merchant’s developer — but no specific downtime window and no data-loss-risk figure appears anywhere on that page, which is a gap worth noticing rather than assuming away.

What the page does commit to migrating, by name, is six categories: subscription plans and pricing structures, payment and billing data across the gateways Loop supports for token import — Shopify Payments, Stripe, PayPal, Authorize.net and Braintree — order counts and customer records, discounts and legacy pricing, automation and workflow rules, and the portal’s own pause-skip-swap history. Payment-token migration is the highest-consequence item on that list, because a token that fails to carry over means a subscriber has to re-enter card details manually — and a forced re-entry is exactly the moment a subscriber who was already ambivalent decides to cancel instead of retype a card number. A brand on a gateway outside that list has no stated token-migration path at all.

The actual downtime window and payment-token failure rate for a given migration are — metric to confirm. No vendor here publishes either figure, and the ones that could vary meaningfully by gateway: a Stripe-to-Stripe migration moves tokens through an API with no customer action required, while a gateway change alongside the platform switch adds a re-authentication step that a same-gateway migration does not. The way to bound the risk before committing to a cutover date is the same parallel-run discipline used for any billing migration: move a small, low-stakes cohort first — the newest 5% of subscribers, who have accrued the least loyalty to lose if something breaks — let one full billing cycle complete on the new platform, and audit that cohort’s charge-success rate against the equivalent slice of subscribers still on the old platform over the same window before migrating everyone else. Ask Loop for a written commitment on downtime and token-migration failure rate for your specific gateway before signing; a page that says “designed to reduce interruptions” is marketing language, not an SLA, and the two are not the same document.

How Much Does Churn Actually Drop After Switching to Loop Subscriptions?

No independent study measures the average churn reduction from switching a subscription programme to Loop — every published figure is Loop’s own case study of a named brand, and a single brand’s result is not evidence of what a typical switch produces.

The cases Loop itself publishes: OSEA Malibu’s monthly churn moved from roughly 10% to roughly 5% over six months after adopting Loop; Keto Chow reports a 36% cancellation save rate alongside 18% year-to-date subscription revenue growth; NutriPaw reports subscription revenue rising from 5% to 28.6% of total revenue over nine months, which measures a shift in revenue mix rather than churn directly and should not be read as a churn figure. All three are vendor-reported, self-selected success stories with no stated control group, so none of them shows what OSEA’s, Keto Chow’s or NutriPaw’s churn would have done over the same period without the switch.

Weighed against an independent baseline, the OSEA figure is a large claim to rest on one case: a DTC consumer panel puts typical monthly churn at 7.1%, split 4.1% voluntary and 3.0% involuntary (Recharge, vendor-reported — and Recharge is one of the platforms compared here, so treat it as a vendor’s own panel rather than an independent benchmark) — full figures in our own churn benchmark. A move from roughly 10% to roughly 5% monthly churn, if fully attributable to the platform switch, would take a brand from noticeably above that panel’s median to comfortably below it — plausible for a brand whose prior cancel flow was genuinely broken, but not something one vendor-published case study can generalise to every migration.

The credible way to price the lift for your own subscriber base is not to borrow OSEA’s number but to measure your own: hold cancel-flow copy, save-offer logic and pause defaults constant through the migration, move one region or product line first, and compare that cohort’s monthly churn in the 90 days before and after cutover against a control cohort left on the old platform over the same 90 days. The subscription churn calculator is built for exactly that before-and-after comparison, so the lift a brand reports is its own measured number rather than someone else’s case study.

Where Do Operators Get Loop Subscriptions Wrong?

Loop Subscriptions’ most common buying mistake is picking on price alone without checking payment-gateway compatibility first: a brand on a gateway Loop does not support for token import is not comparing like-for-like plans, it is comparing a plan it can migrate onto against one it cannot without a forced payment re-entry.

A second mistake is modelling the cost comparison against current order volume rather than the volume and average order value a brand expects to have in a year. A brand planning to raise prices, launch a higher-ticket tier, or shift subscribers onto prepaid billing should re-run the comparison at the projected AOV, not the current one — the crossover point moves with it.

A third pricing mistake is treating the Recharge-Skio acquisition as though it has already produced a combined Recharge-Skio price sheet. It has not, so a brand comparing Loop against a rumoured merged rate is comparing against a number that does not exist.

Loop’s own contracts carry no minimum term — plans run month-to-month, per its pricing and migration pages — which means a brand is never locked into a comparison it ran once at signing, but nothing prompts it to re-run that comparison either. Three of the facts a brand-vendor comparison depends on can all move after signing: which payment gateways Loop supports for token import, where the AOV crossover point sits once pricing or product mix shifts, and whether Recharge and Skio’s still-unscheduled combined product has actually shipped. The practical trigger for re-checking all three is renewal, not a calendar date: re-verify gateway support before switching payment processors of your own, re-run the AOV math after a meaningful price or mix change, and confirm Recharge and Skio have not quietly produced a combined price sheet before assuming last year’s comparison still holds.

How Is Loop Subscriptions Different From Recharge and Skio, Beyond Price?

The feature checklist is no longer where these three platforms separate, because Shopify’s own subscription contracts API and checkout extensibility now sit under all of them — cancel flows, self-serve portals and failed-payment recovery are table stakes across the category, not a Loop exclusive. What actually separates them is commercial terms and, since April 2026, vendor stability.

Recharge is the incumbent: the largest install base, a 60-day free trial on its entry plan, and years of third-party integration work with 3PLs, warehouse-management systems and marketing tools that a newer platform has not had time to accumulate. Skio, until its acquisition, competed on being built specifically around Shopify’s native checkout from the start rather than retrofitted onto it — and is now part of Recharge, with no stated timeline for what a combined product looks like. Loop’s stated differentiation is the pricing model — no per-order fee, migration bundled free on paid plans, a genuine free tier up to 50 active subscriptions — rather than a checkout architecture claim, since the checkout architecture argument that used to separate this generation of subscription apps from the previous one no longer separates Loop, Recharge or Skio from each other.

None of this is really a platform-selection problem in the end — it’s a subscription-retention problem wearing a vendor-comparison costume. Loop’s own case studies, thin as they are as evidence, still point at the same three levers that move churn on any of these three platforms: a cancellation flow that captures a reason before it captures a decision, pause and skip made genuinely obvious rather than buried behind a cancel button, and reorder timing that matches how the product is actually consumed. A platform migration can make those levers cheaper and faster to build. It does not build them automatically, which is the work subscription retention actually is, regardless of which app’s logo sits on the invoice.