Find your next app decision

Apps, topics, comparisons and practical guides.

Use ↓ to move to results, Tab to browse and Escape to close.

Common decisions

Subscription platforms

Loop Subscriptions review

Manage recurring orders and give subscribers ways to skip, swap or change their plans.

A good fit if

You already have repeat buyers and want to improve the subscription experience.

Think twice if

Customers have not shown repeat demand, or nobody has time to manage subscriptions.

Setup estimate
Heavier setup
Pricing checked
Guide researched

What you can use it for

  • Branded self-service customer portal
  • Personalised cancellation flows and analytics
  • Smart failed-payment recovery
  • Fixed and build-your-own subscription bundles
Product details, capabilities and integrations

Loop combines recurring billing with a configurable mobile-friendly customer portal, subscription bundles, cancellation flows, dunning, upsells, analytics, campaigns and migration support. Its current paid plans combine a monthly fee with a percentage transaction charge and no flat per-order fee.

Other recorded capabilities

  • Subscriber upsells and quick actions
  • Subscription, revenue and retention reporting

Connections to check: Shopify Checkout, Shopify Customer Accounts, Klaviyo, Gorgias, Subscription analytics and attribution tools, Fulfilment and shipping systems through supported integrations or APIs, Loop APIs and webhooks on qualifying plans. Confirm that your plan includes the connections you need.

How much does Loop cost?

Free

Free Forever covers up to 50 active subscriptions. Starter is $99/month plus 1% per transaction; Pro is $399/month plus 0.75% per transaction. Prices are in USD. Check current limits and terms before choosing.

Pricing checked .Check current official pricing ↗

Work out your monthly and yearly app costs, including usage fees and setup.

What should you compare it with?

See all subscriptions options →

Getting started with Loop

  1. 1

    Choose products customers already reorder. Check the discount, delivery cost and profit on a renewal.

  2. 2

    Set the delivery schedule and customer options, including skip, pause and cancellation.

  3. 3

    Test a first order, renewal, failed payment and cancellation before inviting customers.

What you need before installing

Have these ready

  • Proven repeat demand and a profitable subscription offer
  • A named subscription owner and customer-experience owner
  • Documented skip, pause, swap, cancellation and failed-payment policies
  • Reliable recurring inventory, fulfilment and shipping
  • Baseline retention, cancellation and payment-recovery data
  • A migration and cutover owner when replacing another platform

Decisions to make first

  • Plan tier, transaction-fee impact and growth forecast
  • Selling plans, discounts and product eligibility
  • Portal actions and customer-access method
  • Cancellation reasons, treatments and compliance rules
  • Dunning schedule, notifications and final action
  • Bundle, upsell and one-time product rules
  • Integration events and data ownership
  • Migration freeze, cutover and reconciliation
  • Experiment guardrails and success measures
Open the detailed setup guide (8 steps)
Build the subscription business case

Model expected active subscriptions, recurring revenue, gross margin, cancellations, payment failures and Loop's monthly plus transaction fees. Define the subscriber problem, offer, delivery cadence and the retention work the team will actually run.

Follow the official instructions ↗
Configure the core selling plan before growth features

Set products, variants, billing and delivery intervals, discounts, shipping and out-of-stock behaviour. Launch with the smallest product set that represents the real programme before adding bundles, campaigns or upsells.

Follow the official instructions ↗
Design the customer portal as a service channel

Enable only the actions customers should use, such as skip, pause, reschedule, swap, update payment and change address. Set sensible limits, plain language and a clear login route. Test the portal on mobile with active, paused and cancelled subscriptions.

Follow the official instructions ↗
Build transparent cancellation flows

Define a concise set of cancellation reasons, offer relevant alternatives such as skip, delay, swap or a limited incentive, and preserve a clear path to cancel. Configure regional automatic-renewal requirements before applying surveys or offers.

Follow the official instructions ↗
Set payment recovery and communications

Configure smart dunning, retry and failed-payment messages, payment-update access and the final outcome after recovery attempts. Keep recovery emails distinct from marketing and make the required customer action obvious.

Follow the official instructions ↗
Connect only the events needed to operate the programme

Map subscription, renewal, skip, cancellation and payment-recovery events to the approved email, support, analytics and fulfilment tools. Test for duplicate messages and make one system the source of truth for each metric.

Follow the official instructions ↗
Run a full subscriber lifecycle test

Test sign-up, renewal, bundle changes, upsells, skip, pause, reschedule, payment update, failed payment, recovery, cancellation, reactivation, inventory, shipping, tax, emails and support access. Reconcile Loop, Shopify and downstream systems.

Follow the official instructions ↗
Launch, measure and improve one retention problem at a time

Launch with a controlled cohort. Review cancellation reasons, lost recurring revenue, save actions and payment recovery, then choose one high-confidence improvement at a time. Avoid launching multiple retention changes without a baseline.

Follow the official instructions ↗
How to use and review it after launch

once

Save plan economics, portal permissions, cancellation treatments, dunning rules, integrations and baseline retention metrics.

Why: Loop's value depends on disciplined operating choices rather than feature availability.

Track: Approved configuration register and baseline churn, recovery and margin data.

Supporting guidance ↗

daily

During launch, review failed payments, portal incidents, recurring-order failures and subscriber support contacts.

Why: Subscription exceptions compound quickly when the next order or retry is already scheduled.

Track: Open recovery cases, portal errors, order failures and response times.

Supporting guidance ↗

weekly

Review cancellation reasons, save treatments, payment recovery, skips and support themes and assign one corrective action.

Why: Weekly behaviour reveals whether the issue is cadence, stock buildup, price, product or service.

Track: Subscriber churn, cancellation save rate, recovery rate, skips and top support themes.

Supporting guidance ↗

monthly

Reconcile recurring revenue, contribution margin, fees, retained subscribers and cost-to-serve with the business case.

Why: Retention activity can improve headline revenue while discounts or operational work weaken profit.

Track: Net subscriber growth, retained MRR, contribution margin and platform cost per active subscriber.

Supporting guidance ↗

event driven

Repeat lifecycle tests after portal, selling-plan, theme, payment, shipping, cancellation or integration changes.

Why: A subscriber's next action may happen weeks after a configuration change.

Track: Completed regression test and zero unresolved high-risk exceptions.

Supporting guidance ↗
How to decide whether it is working

Check that the app still works after changes to your theme, checkout or connected tools. Review the result you installed it for, alongside its cost.

  • Subscription conversion and net subscriber growth
  • Subscriber churn and cancellation save rate
  • Failed-payment recovery rate and recovered revenue
  • Skip, pause, swap and reactivation behaviour
  • Recurring contribution margin after platform fees
  • Portal completion and subscriber support volume

Keep it if it solves a real problem. Simplify or remove it if the extra cost and work are not worthwhile.

Things to check before installing

  • Customers have not shown repeat demand, or nobody has time to manage subscriptions.
  • Paid plans combine a monthly fee with a percentage transaction charge
  • Migration and workflow design still require careful implementation
More limitations and common mistakes
  • Advanced portal and retention controls create ongoing operating work
  • Regional cancellation rules can bypass parts of a configured flow
  • The platform is disproportionate for a small validation-stage programme
  • Buying Loop for retention features without assigning a retention owner
  • Using blanket discounts instead of reason-specific cancellation treatments
  • Blocking or obscuring cancellation in ways that create customer and legal risk
  • Launching bundles and upsells before the core renewal path is stable
  • Comparing monthly fees without modelling percentage transaction charges
  • Running several experiments at once without a baseline

Common questions

How much does Loop cost?

Loop currently publishes a free plan for up to 50 active subscriptions, Starter at $99 per month plus 1% per transaction and Pro at $399 per month plus 0.75%, with no flat per-order fee. Check current pricing before buying.

What makes Loop different?

Loop puts unusual emphasis on the subscriber portal, cancellation journeys, payment recovery and retention analytics. That is valuable only when a team will operate and improve those areas.

Can customers manage their subscriptions themselves?

Yes. Loop documents controls for actions including skip, pause, reschedule, product changes, payment updates, address changes and cancellation, subject to the permissions you configure.

Does Loop help prevent cancellations?

Loop supports cancellation reasons, benefits pages, targeted alternatives and analytics. Keep the journey transparent and comply with regional rules that may require direct cancellation.

Will Loop migrate existing subscriptions?

Loop documents white-glove and self-service migration paths. Paid plans currently include white-glove migration, but the merchant still needs a freeze, reconciliation and cutover owner.

Sources and how we put this guide together

This is a research-based guide, not a claim that we have personally tested every feature. Prices and product availability can change.

How our recommendations work