What Is Dunning Management? A Guide for Shopify Subscription Merchants

Every subscription business loses money to failed payments. Most merchants accept it as an unavoidable cost of doing business. The ones who've built real recurring revenue treat it differently — they've built a dunning management system that catches failed payments automatically and recovers the majority of them before the subscriber is ever lost.

This guide covers what dunning management is, how a well-built sequence works, what it costs to get it wrong, and what Shopify merchants need to look for when choosing a subscription app.

What Is Dunning Management?

Dunning management is the automated process of recovering failed subscription payments through a structured sequence of retries, notifications, and subscriber outreach.

The term "dunning" comes from the 17th century — "to dun" meant to persistently demand payment from a debtor. The modern version is less aggressive and far more automated, but the goal is the same: get the payment collected without losing the customer.

In the context of subscription businesses, dunning management typically refers to everything that happens after a payment fails: the retry attempts, the emails to the subscriber, the window of time before the subscription is cancelled, and the analytics that tell you how well the system is working.

It's worth being clear about what dunning management is not. A single failed payment email is not dunning management. A one-time retry is not dunning management. Dunning management is a coordinated, multi-step system designed to maximize recovery across the full window of opportunity — usually 7 to 14 days after the initial failure.

The Real Reasons Subscription Payments Get Declined

Before building a recovery system, it helps to understand why payments fail. Most failures are not the customer's fault and have nothing to do with their intent to stay subscribed.

Expired cards are the most common cause. A subscriber's card expires, the new one arrives in the mail, and they forget to update their billing details. They still want the product — they just haven't gotten around to updating a number.

Bank blocks on recurring charges happen when a bank flags an automatic charge as suspicious or requires additional verification. This is increasingly common as banks add fraud prevention layers. The subscriber never sees this happen until the subscription stops.

Temporary insufficient funds occur around the end of a pay period. A charge attempted on the 28th of the month might fail, but the same charge on the 3rd would go through without issue. The customer isn't broke — the timing was wrong.

Card replacement after loss or theft is self-explanatory. A subscriber's wallet gets stolen, they get a new card with a new number, and the old subscription billing details become invalid.

None of these scenarios represent a subscriber who wants to cancel. That's what makes involuntary churn so costly and so preventable — the relationship isn't broken, just the billing.

The Anatomy of a Dunning Sequence

A well-built dunning sequence has three phases: prevention, recovery, and resolution.

Prevention: Before the Payment Fails

The best dunning management starts before a payment even fails. Expiring card alerts — emails sent to subscribers 7 to 14 days before their card on file expires — give customers the chance to update their billing details before the next charge attempts. Catching the problem before it becomes a failure is always cheaper than recovering after.

Ongoing Subscriptions sends proactive expiring card notifications automatically. No merchant configuration required — the system monitors card expiry dates and notifies subscribers before billing, preventing a significant portion of failures before they occur.

Recovery: After the Payment Fails

When a payment does fail, the recovery phase begins. A strong dunning sequence typically looks like this:

Day 0: Payment fails. First retry attempted automatically. First notification sent to the subscriber explaining what happened and providing a direct link to update their payment method.

Day 1–2: Second retry. Second notification sent if the first retry failed. The tone is helpful and matter-of-fact — not alarming, not demanding. The subscriber needs to know the payment didn't go through and exactly what to do about it.

Day 3–5: Third retry. Follow-up notification. At this point, the communication shifts slightly — the subscriber is reminded that their subscription may be paused or cancelled if the payment isn't resolved.

Day 7–8: Final retry. Final notification before the subscription is flagged as lapsed.

Each notification should include a frictionless link for the subscriber to update their payment method directly — no login required, no navigation required, just click and update. Every step added to that process reduces completion rates.

Resolution: After the Window Closes

Subscribers who don't recover within the dunning window fall into one of two categories: recovered (payment eventually went through) or lapsed. Lapsed subscribers are different from cancellations — they didn't choose to leave, they just didn't respond in time. Many can be reactivated through a well-timed win-back email.

What Good Dunning Management Looks Like

The difference between a basic dunning setup and a well-optimized one isn't the number of emails — it's the quality of every touchpoint in the sequence.

Proactive prevention: Sending expiring card alerts before billing dates eliminates a category of failures entirely. Most subscription apps skip this step.

Multiple intelligent retries: Not just two or three attempts, but a full 7-8 day retry cadence with attempts spaced at optimal intervals. The research on retry timing shows that spreading attempts across multiple days significantly increases recovery rates compared to batching retries on day one.

Decline reason context: When a payment fails, the reason matters. A card expiry requires a different action than a bank block. The best dunning systems surface the specific decline reason in the subscriber notification, making it easier for the customer to take the right action quickly.

Frictionless payment update: A subscriber who wants to fix their billing situation should be able to do it in one click. If the update flow requires logging in, navigating to account settings, and re-entering a card number, completion rates drop significantly.

Analytics and visibility: Recovery rate by decline reason, retry success rates by day, subscriber-level visibility into where each customer is in the dunning sequence — these numbers tell you whether your system is working and where it's losing money.

Ongoing Subscriptions includes all of these built in — the 8-day retry sequence, expiring card alerts, decline reason surfacing, and a self-serve subscriber portal that lets customers update their payment method without any friction.

What Bad Dunning Management Costs

The cost of a weak dunning system is easy to calculate and almost always surprises merchants when they see the math.

A typical subscription business sees payment failure rates between 5% and 10% of billing attempts. At a 5% failure rate with 1,000 active subscribers paying $40/month, that's 50 failed payments worth $2,000 in a single billing cycle.

A weak dunning system — one with a single retry and a single email — might recover 20% of those failures. That's $400 recovered, $1,600 lost. Every month.

A strong dunning system typically recovers 60–70% of failed payments. That's $1,200–$1,400 recovered, and only $600–$800 lost.

The gap between those two numbers — $800 to $1,000 per month at this scale — is entirely a function of the dunning system. It's not about acquiring new customers or improving the product. It's about recapturing revenue that was already earned, from customers who already wanted to stay.

Annualized, that gap is $9,600–$12,000. From a business with just 1,000 subscribers. At scale, the number grows proportionally.

Dunning Management for Shopify Merchants Specifically

Shopify's subscription infrastructure handles the payment processing side, but the dunning logic — the retry cadence, the notifications, the subscriber outreach — lives in the subscription app you install.

This means the quality of your dunning management is entirely dependent on which app you use. Some apps offer minimal dunning: one or two retries, a generic failed payment email. Others, like Ongoing Subscriptions, treat dunning as a core feature rather than an afterthought.

When evaluating a Shopify subscription app specifically for dunning capabilities, look for:

• Retry depth: How many days does the sequence run? A 2-day window is not enough.
• Expiring card alerts: Does the app proactively notify subscribers before their card expires?
• Decline reason surfacing: Can you see, at the subscriber level, why a specific payment failed?
• Notification quality: Are the emails clear, helpful, and frictionless? Do they include a one-click update link?
• Recovery analytics: Does the app show you your actual recovery rate, not just failure count?

Ready to Stop Losing Revenue to Failed Payments?

Dunning management is one of the highest-ROI improvements a subscription business can make — and it's entirely automatic once it's set up. The revenue doesn't require new marketing, new products, or new customers. It requires a system that catches failed payments and recovers them before subscribers are lost.

Ongoing Subscriptions+ Bundles is built around keeping the revenue you've already earned. The full 8-day dunning sequence, proactive card expiry alerts, decline reason visibility, and a self-serve subscriber portal are all included — free to install, zero transaction fees.

Published by Ongoing Apps