Resources

Loop Subscriptions Dunning: Recovery Guide

Subscription boxes live and die on the renewal. Your customer signed up months ago, the box ships on a rhythm, and the only moment that can break the relationship without anyone choosing to break it is the moment the renewal charge fails. Loop Subscriptions handles that moment with native dunning — retries and notifications built into the billing platform. It is a reasonable baseline. It is not a recovery system. This guide explains how dunning works on Loop at capability level, the gaps that quietly cost box brands their renewals, and how a decline-aware recovery layer closes them cleanly, step by step.

Why failed renewals hit subscription boxes harder

Box businesses have three properties that make failed payments unusually expensive:

• The renewal is the business. Acquisition is expensive and the first box is often discounted. Profit lives in renewals three, four, and five. Losing a subscriber at a renewal to a card problem burns the acquisition cost and the future margin at the same time.
• The cadence creates pay-cycle collisions. Monthly boxes renew on the same date every month for every subscriber in a cohort. If that date lands just before a common payday, a wave of insufficient-funds declines arrives together — a billing problem, not a demand problem.
• Fulfilment has a clock. A streaming service can restore access the day a card is fixed. A box has a ship window. A renewal recovered after the cut-off means a late box, a support ticket, or a skipped month the customer blames on you.

None of this means your subscribers want to leave. According to Recurly research, 20–40% of subscriber churn is involuntary — churn caused by payment failure rather than a decision. On a box, that involuntary share is where the recoverable money sits.

What Loop's native dunning does

At capability level, native dunning in a Shopify subscription platform like Loop generally includes:

• Automatic retries when a renewal charge fails, so one bad attempt does not immediately cancel the subscription.
• Failed-payment notifications to the customer, typically by email, telling them the charge did not go through.
• Customer self-service through the subscription portal, where subscribers can update their payment method, skip or pause a delivery, and manage their plan — tools that resolve some failures when customers use them.
• A sequence end, after which the failed subscription is cancelled or moved to its end state.

Loop's real strength is the subscription experience itself: the customer portal, retention touches inside that experience, and the merchandising of the subscription. That is what the platform is built for. Dunning inside a billing platform is a supporting feature, and it behaves like one. For how box-specific dunning stacks up across tooling, see our guide to the best dunning tools for subscription boxes.

The gaps that cost renewals

Fixed retry behavior, blind to decline type

Native retries generally follow a fixed pattern regardless of the decline reason. But a box renewal that failed for insufficient funds needs an attempt timed after payday. A renewal that failed because the card expired needs the customer to act — retries against the old details will fail identically every time. A renewal that failed with a hard decline — card closed or reported lost — should never be retried at all. One fixed pattern gives each of those failures the wrong sequence, and the fulfilment clock means the wasted days actually cost shipments.

Email-centric outreach

Native notifications are usually email-only and template-driven. Two problems follow. First, attention: a failed-payment email for a box the customer loves still competes with a full inbox, and a customer who misses it discovers the failure when the box does not arrive — the worst possible moment. Second, clarity: generic notifications rarely say exactly what happened, what the customer needs to do, and by when, in the brand's own voice. A dedicated layer adds branded email, a branded card-update page, and SMS in the sequence. Outreach volume matters as well as voice: according to Churnkey's published analysis of Stripe data, each additional dunning email touch adds roughly 1–2 points of recovery.

No pre-failure prevention

Some failures are knowable in advance. Cards expire on printed dates. Billing platforms can warn you, but a prevention sequence — contacting the customer before the renewal with an expiring card, not after the failure — is a recovery discipline, covered in our explainer on pre-dunning. Native dunning starts at the failure. A recovery system starts before it where it can.

No backfill of the existing backlog

Every box brand of any age has a backlog: past failed renewals that lapsed after the native sequence gave up on them. Some are long gone. The recent ones — especially the insufficient-funds failures from a bad-luck renewal date — are subscribers who never decided anything. Native dunning never revisits them.

No deflection at the cancel step

When recovery ends, or when a subscriber moves to cancel, the billing layer generally just processes the cancellation. There is no structured save moment — no Discount for the price-sensitive, no Pause for the subscriber with a full shelf of product, no Service offer for the one whose box arrived damaged twice. For boxes, Pause in particular is a natural save: the customer's problem is often timing or stock, not desire. A billing layer that only cancels leaves that save unplayed.

The layered recovery model for Loop stores

The model below keeps Loop as your billing platform and adds a recovery layer for the failure window. It is the same architecture used across platforms — the category is mapped in our guide to subscription dunning software — tuned here to box economics.

Step 1: Prevent the failures you can see coming

Run pre-expiry outreach before renewals hit cards near their expiry date, pointing customers to a branded card-update page. Templates for the payment side of that sequence live in our dunning email templates — the pre-failure versions are calmer: a heads-up, not a warning.

Step 2: Route each failure by decline code

When a renewal fails anyway, the decline code assigns the playbook: soft declines to timed retries, expired and replaced cards to the update flow, hard declines to a card-update request with zero retries. Across 5.4M failed payments, insufficient funds is the largest decline category at 40.6%, according to Churnkey's published analysis of Stripe data — for a box cohort renewing on one date, that category deserves a schedule built around paydays, not around the platform's default intervals.

Step 3: Retry on a decline-aware schedule

Up to 6 attempts over roughly 16 days, spaced in days and aligned to when the account behind the card is likely funded. Sixteen days is long enough to cross a pay cycle and short enough to resolve before the next renewal compounds the problem — and, for boxes, to recover inside or near the ship window rather than a month later.

Step 4: Backfill the backlog on connect

The layer works your failed payments from the previous 90 days, not just new failures. Be honest about the gradient: a soft decline from three weeks ago is a live opportunity; a hard decline from eighty days ago is mostly a card-update request to a cold address. Worked in order, the backlog tells you exactly how much of your "churn" was never churn.

Step 5: Deflect at cancellation

At the cancel step — including cancellations that arrive via failed dunning — present one offer matched to the reason: Discount, Pause, or Service. Keep the exit easy to find and the offer honest. Deflection that traps customers backfires; deflection that solves the actual problem retains them.

Coordination: one sequence, not two

• Retries: one owner per failed charge. If the recovery layer runs the decline-aware schedule, native retries should be coordinated so the same renewal is not attempted twice in a window.
• Messages: one branded stream. Avoid the customer receiving a platform notification and a recovery email about the same failure on the same morning.
• End state: both layers agree — success returns the subscription to normal billing, failure ends in cancellation, pause, or a save offer, never in limbo.

What the recovery layer costs

Swipe Again supports Loop Subscriptions as one of nine public platforms: Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle. It is $179/mo flat ($1,799/yr), with no percentage of recovered revenue and no MRR tiers. Included: decline-code-aware retries (up to 6 attempts over ~16 days, hard declines never retried), branded dunning emails and card-update pages, SMS in the sequence, cancel deflection with Discount / Pause / Service offers, and a 90-day backfill on connect. Connect takes about 2 minutes; the 14-day trial is self-serve with a card upfront. The guarantee, in its only form: "Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days".

The bottom line

Loop's native dunning retries and notifies, and for a young box with few failures that may be enough. The renewals it loses disappear through structural gaps: decline-blind retry timing, email-only outreach, no prevention, no backfill, and no save offer at the cancel step. Layer decline-aware recovery on top, keep the systems coordinated, and watch the number that matters — renewals recovered that your native sequence would have cancelled.

Frequently asked questions

Does Loop Subscriptions retry failed payments automatically?

Yes, Loop's native dunning retries a failed renewal charge and notifies the customer. The limits are structural: retries generally follow a fixed pattern rather than timing to the decline type, outreach is typically email-based, and the native sequence does not revisit older failures or add a save offer at cancellation.

Why do subscription boxes lose so much to failed payments?

Three reasons compound. The renewal carries the profit after an expensive first-box acquisition. Whole cohorts renew on the same date, so a payday collision produces a wave of insufficient-funds declines at once. And fulfilment has a ship window, so a slowly recovered renewal can still mean a late or skipped box and a support problem.

What should happen when a renewal fails with a hard decline?

It should never be retried. A hard decline means the card cannot be charged again — it is closed, blocked, or reported lost or stolen. The only productive step is a clear, branded request for the customer to update their payment details, sent promptly while the subscription and the ship window can still be saved.

What is the 90-day backfill?

When you connect a recovery layer, the backfill works the failed payments already in your account from the previous 90 days instead of only handling new failures. Native dunning cannot do this. Recent soft declines in the backlog are often still recoverable; older and hard declines are colder, and a good layer sequences the backlog accordingly.

How much does Swipe Again cost for a Loop store?

Swipe Again is $179 per month flat, or $1,799 per year. There is no percentage of recovered revenue and there are no MRR tiers. The price includes smart retries, branded dunning emails and card-update pages, SMS in the sequence, cancel deflection, and the 90-day backfill. There is a 14-day trial and connecting takes about 2 minutes.