Aug 14, 2026
Dunning: Definition, Thresholds, and Failure Modes
Dunning is the automated and manual process of attempting to collect failed recurring payments by retrying charges, notifying customers, and updating payment methods before marking a subscription as churned.

What Dunning Actually Is
Dunning starts the moment a recurring charge fails. A payment processor (Stripe, PayPal, etc.) declines the transaction. The subscription does not automatically cancel. Instead, a dunning workflow begins: retry the charge on a schedule, notify the customer, collect a new payment method, and eventually churn the subscription if recovery fails.
The goal is simple: recover the failed payment before the customer notices or leaves. Recovery rates vary by failure reason. Expired cards recover at 40-60%. Insufficient funds recover at 20-40%. Fraud blocks recover at 5-15%. Each reason demands a different retry cadence and messaging strategy.
Dunning is not a single action. It is a sequence of retries, notifications, and decision points spanning 7-30 days. Operators who treat it as a one-time retry lose 50%+ of recoverable revenue.
Retry Logic and Timing Thresholds
Retry timing determines recovery rate. Retrying too soon (within 24 hours) increases decline rates because the underlying issue (insufficient funds, card block) often persists. Retrying too late (after 14 days) means the customer has already mentally churned.
Industry benchmarks suggest a 3-retry schedule over 10-14 days. Retry 1 occurs 3-5 days after the initial failure. Retry 2 occurs 7-10 days after failure. Retry 3 occurs 12-15 days after failure. Each retry should be preceded by a customer notification (email or SMS) asking them to update their payment method.
- Retry 1: Day 3-5 post-failure. Soft notification: 'Your payment didn't go through. Update here.' Recovery rate: 30-40%.
- Retry 2: Day 7-10 post-failure. Escalated notification: 'Your subscription is at risk. Update now to avoid cancellation.' Recovery rate: 15-25%.
- Retry 3: Day 12-15 post-failure. Final notice: 'Your subscription will cancel in 2 days unless you update payment.' Recovery rate: 5-10%.
- Post-retry 3 failure: Cancel subscription and trigger win-back campaign (separate from dunning).
Failure Mode: Retry Fatigue
Retry fatigue occurs when a brand retries the same failed card too many times without asking the customer to update their payment method. Each failed retry signals to the processor that the merchant is not managing risk. The processor may flag the merchant account as high-risk, increasing decline rates across all transactions.
Threshold: If a card fails twice in a row, stop retrying that card. Require the customer to provide a new payment method before retry 3. This protects the merchant account and signals to the customer that action is required.
Failure mode indicator: Retry decline rate exceeds 80% on retry 2 and 3. This means the underlying payment method is bad and retrying is pointless.
Failure Mode: Silent Churn
Silent churn happens when a subscription fails to charge but the customer is never notified. The customer discovers the lapse weeks later, assumes they canceled, and never returns. The brand loses the customer and the recovery opportunity.
Prevention: Send the first notification within 24 hours of the failed charge. Use email + SMS if SMS is available. Include a direct link to update payment. Do not bury the call-to-action in footer text.
Threshold: First notification should reach 95%+ of customers within 24 hours. If delivery rate is below 90%, audit email deliverability and SMS opt-in rates.
Failure Mode: One-Size-Fits-All Messaging
Generic dunning emails ('Your payment failed') have 15-25% click-through rates. Segmented messaging based on failure reason and customer lifetime value (LTV) can reach 35-50%.
High-LTV customers (12+ months tenure, $500+ lifetime spend) warrant a personal outreach call or concierge payment update. Mid-LTV customers (3-12 months, $100-500 spend) warrant SMS + email with a discount incentive. Low-LTV customers (under 3 months, under $100 spend) warrant automated email only.
Threshold: Segment dunning campaigns by LTV. Allocate manual outreach (calls, concierge) to top 10% of customers by LTV. Measure recovery rate by segment. If high-LTV recovery rate is not 20%+ higher than low-LTV, increase manual outreach investment.
Failure Mode: No Churn Reason Tracking
Operators often do not track why a payment failed. Was it an expired card? Insufficient funds? Fraud block? Processor timeout? Each reason has a different recovery probability and requires different messaging.
Stripe and other processors provide decline codes (card_declined, insufficient_funds, lost_card, etc.). Capture these codes in your subscription database. Use them to segment retry logic and messaging.
Threshold: Categorize 100% of failed charges by decline code. If more than 20% of failures are labeled 'generic decline' or 'unknown,' audit your processor integration. Track recovery rate by decline code. If any single code has a recovery rate below 10%, consider skipping retries for that code and moving straight to customer outreach.
Building a Dunning Checklist
Dunning success requires a repeatable process. Use this checklist to audit your current dunning workflow.
- Retry schedule defined: 3 retries over 10-14 days with specific day thresholds documented.
- Notifications sent: Email + SMS (if available) within 24 hours of failure, before each retry.
- Decline codes captured: Payment processor decline codes logged and categorized in subscription database.
- LTV segmentation: High-LTV customers receive manual outreach; mid-LTV receive SMS + email; low-LTV receive email only.
- Recovery rate tracked: Weekly dashboard showing recovery rate by retry, by decline code, by LTV segment.
- Churn threshold set: Subscriptions marked as churned after retry 3 failure + 3-day grace period.
- Win-back campaign triggered: Churned customers receive a separate re-engagement campaign within 7 days of churn.
Questions
FAQ
What is a good dunning recovery rate?
Industry average is 30-40% of failed charges recovered through dunning. High-performing brands (strong LTV, low churn) recover 45-60%. Low-performing brands (weak retention, high churn) recover 15-25%. Recovery rate varies significantly by decline code: expired cards recover at 50-60%, insufficient funds at 25-35%, fraud blocks at 5-10%.
Should we retry immediately after a failed charge?
No. Retrying within 24 hours increases decline rates because the underlying issue (insufficient funds, card block, processor timeout) often persists. Wait 3-5 days for the first retry. This gives the customer time to notice the failure and update their payment method, and gives the processor time to resolve temporary issues.
How many retries are too many?
Three retries over 10-14 days is the industry standard. A fourth retry adds minimal recovery (under 2%) and increases the risk of processor penalties. After three failed retries, move to manual outreach (call, concierge) for high-LTV customers, or churn the subscription for low-LTV customers.
What happens if we don't segment dunning by LTV?
You will waste resources on low-value customers and under-invest in high-value customers. High-LTV customers warrant personal outreach and concierge payment updates. Low-LTV customers warrant automated email only. Without segmentation, recovery rates flatten and customer satisfaction declines because high-value customers receive generic treatment.
More from the blog
- Did the action actually work?
- One number a day
- Sunday night reporting is a product bug
- Never let AI change ad spend without a yes
- Stop optimizing platform ROAS alone
- Write-Access Matrix for AI on Meta and Google
- Reverse Platform ROAS Dependency Before It Reverses You
- AI Agents for Ecommerce: Scheduled Loops, Tools, and Approval Gates
- Data Requirements for AI in Ecommerce
- The AI Ecommerce Stack for DTC Brands
- AI for Ecommerce Agencies: Automate Execution, Keep Craft
- Reconciling Attribution Conflict with AI
- AI for Ecommerce During BFCM: What to Freeze, Monitor, and Automate
- AI for Ecommerce Creative Testing Workflows
- AI for Ecommerce Customer Support That Protects Brand
- AI for Email and SMS Operations: Detection, Fatigue, and Segmentation
- Recovering Revenue from Failed Payments: AI Retry Logic for DTC
- What Ecommerce Founders Should Never Automate
- AI for Ecommerce Fraud and Chargeback Signals
- AI for Ecommerce Growth Teams: Roles and Rituals
- AI for Ecommerce Inventory: Demand Signals from Ads and Cohorts
- AI for Ecommerce Pricing and Promo Calendars
- AI for Ecommerce Reporting: Kill the Sunday Deck
- Security and Access Control for Ecommerce AI
- AI for Ecommerce Unit Economics Decisions
- Winback Campaigns: Prioritize High-Value Lapsed Customers and Ladder Offers
- Prevent PMax Cannibalization and Reclaim Brand Search ROI
- AI for Meta Ads in Ecommerce: Operator Checklist
- AI for Multichannel Ecommerce: Connecting Inventory, Pricing, and Ads Across Channels
- AI for Shopify Merchandising and Margin
- AI for Subscription Ecommerce: Dunning, Churn Prevention, and Revenue Stacking
- AI for TikTok Ads: Solving Creative Volume Without Losing Control
- AI Operator vs Growth Agency: What Each Covers and Costs
- AI Operator vs In-House Analyst: Cost and Task Split
- AI Operator vs Klaviyo AI: When to Choose Each
- AI Operator vs Meta Advantage+ - Where Each Solves
- AI Operator vs Northbeam: Measurement vs Execution
- AI Operator vs Shopify Sidekick: Scope and Operational Fit
- AI Operator vs Triple Whale: Measurement Layer vs Execution Layer
- AI Will Not Fix Bad Creative
- AI Will Not Negotiate Your Suppliers
- Analyst vs Operator: Split the Job Before You Hire
- AOV Checklist for Growth Leads
- AOV for Multi-Channel DTC
- AOV Thresholds Worth Writing Down
- Approval-Gated AI Is a Feature, Not a Missing Feature
- ASC Campaigns and Contribution Margin
- Attribution Checklist for Growth Leads
- Attribution for Multi-Channel DTC
- Attribution Thresholds Worth Writing Down
- Best AI Tools for Ecommerce in 2026 (By Job, Not Hype)
- Black Friday Automation Freeze: What Stays Manual
- Never Mix Brand Search and Prospecting Efficiency
- Building an AI-First Ecommerce Ops Team
- CAC Checklist for Growth Leads
- CAC for Multi-Channel DTC: Definitions, Thresholds, and Failure Modes
- CAC Thresholds Worth Writing Down
- Cancel Flow Metrics That Matter
- ChatGPT Cannot See Your Ad Account
- Churn Checklist for Growth Leads
- Churn for Multi-Channel DTC
- Churn Thresholds Worth Writing Down
- Cohort Analysis: The Gate Before Scaling Spend
- Cohorts Checklist for Growth Leads
- Cohorts for Multi-Channel DTC
- Cohorts Thresholds Worth Writing Down
- Common AI Ecommerce Mistakes Brands Make
- Common AOV Mistakes on Shopify
- Common Attribution Mistakes on Shopify
- Common CAC Mistakes on Shopify
- Common Churn Mistakes on Shopify
- Common Cohorts Mistakes on Shopify
- Common Creative Mistakes on Shopify
- Dunning Failures on Shopify: Definitions, Thresholds, and Recovery
- Common LTV Mistakes on Shopify
- Margin Mistakes That Kill Shopify Unit Economics
- Common MER Mistakes on Shopify
- Common Retention Mistakes on Shopify
- ROAS Mistakes That Kill Shopify Profitability
- Contribution Margin: The One Finance Number Paid Social Needs
- Copilot vs Autopilot: Approval Gates for Ecommerce AI
- Creative Checklist for Growth Leads
- Detecting Creative Fatigue: Operational Signals That Matter
- Creative for Multi-Channel DTC
- Creative Kill Criteria You Can Write Down
- Creative Thresholds Worth Writing Down
- Credits and Honest Metering: How Usage-Based Pricing Should Work
- Dashboards Do Not Pause Ads
- Dayparting Is Usually Wrong for Ecommerce
- Demo Theater vs Production AI: Why Read-Only Proofs Matter
- Dunning Checklist for Growth Leads
- Dunning for Multi-Channel DTC
- Dunning Thresholds Worth Writing Down
- Email Fatigue from Growth Teams: When Send Volume Kills LTV
- Email Revenue Collapsed Overnight: Flow Break Detection
- Evidence Packet for Every Budget Move
- Failed Payment Alert Design for Operators
- Failed Payments Are Not Churn
- Finance Rejects Marketing Numbers
- First Week With an AI Operator: Read-Only, Briefings, Then Gated Writes
- Why Your CAC Just Moved: A Diagnostic Framework
- Frequency Cap as Brand Protection
- GA4 Is Not Your P&L
- Google Ads Brand vs Nonbrand Split: Reporting Rule
- Brand Cannibalization: Measuring When Paid Brand Search Destroys ROI
- Health Score Inputs for DTC: RFM + Support + Payments
- Why Horizontal AI Employees Don't Move Shopify Store Metrics
- How Operators Think About AOV
- Attribution as a Measurement System
- How Operators Think About CAC
- How Operators Think About Churn
- Cohort Analysis for DTC Operators
- How Operators Think About Creative
- How Operators Think About Dunning
- How Operators Think About LTV
- How Operators Think About Margin
- How Operators Think About MER
- How Operators Think About Retention
- How Operators Think About ROAS
- How Operators Think About Subscription
- MER as a Daily Operating Metric
- Run a Two-Week Read-Only AI Pilot
- How to Use AI for Ecommerce Ads Without Blowing the Budget
- How to Use AI for Ecommerce Retention and Lifecycle
- Human SLA for AI Proposals: Same-Day Approvals or the Queue Is Theater
- Implementing AI in Ecommerce in 30 Days
- Who Owns Involuntary Churn
- Connect Shopify, Meta, and Klaviyo Without a Data Team
- Klaviyo Flows the Operator Watches Weekly
- Learning Phase Budget Mistakes: Why Ad Restarts Waste Spend
- LTV Checklist for Growth Leads
- LTV for Multi-Channel DTC: Calculation, Thresholds, and Failure Modes
- LTV Thresholds Worth Writing Down
- Margin Checklist for Growth Leads
- Margin Floor by Collection: Gate Media Spend on Unit Economics
- Margin for Multi-Channel DTC
- Margin Thresholds Worth Writing Down
- Measuring AI ROI in Ecommerce: Hours, Revenue, and Avoided Spend
- MER Checklist for Growth Leads
- MER Down After a Creative Win
- MER for Multi-Channel DTC: Thresholds and Failure Modes
- MER Thresholds Worth Writing Down
- Meta Ads Manager Is Not Enough
- What to do when Meta Pixel stops firing
- Ecommerce AI Operator vs Generic AI Employee: Vertical Depth and Operational Ownership
- The Eight Fields Every Monday Brief Needs
- Multi-Channel Complexity Is the Prerequisite
- New CMO Wants Another Dashboard: What to Buy Instead
- Connected Operator vs Chat With a CSV
- Pause Rules That Fire on Noise
- Pixel Broke on Friday Night: Incident Response Playbook
- Freeze AI Automation During Promo Weeks
- Prompting vs Connecting: Two Modes of Ecommerce AI
- Reading Failed Billing Signals in Your Morning Brief
- Refund Rate as Acquisition Quality Signal
- Fix Retention Before Buying More CAC
- Retention Checklist for Growth Leads
- Retention for Multi-Channel DTC
- Retention Thresholds Worth Writing Down
- ROAS Checklist for Growth Leads
- ROAS for Multi-Channel DTC: Channel Benchmarks and Reallocation Rules
- ROAS Thresholds Worth Writing Down
- ROAS Up, Cash Down: The Pattern
- Rules Engine vs Approval-Gated AI: When If-Then Logic Fails
- Scale Signals That Are Fake
- Second Purchase Campaign Timing by Category
- Shopify Plus Operator Checklist: Connection Sequence
- Skio, Loop, Bold: Subscription Stack Comparison for Operators
- Slack Approval Button Design
- Slack as the Ecommerce Ops Console
- Software Does Not Replace Brand Taste
- Stop Guessing on AOV
- Stop Guessing on Attribution
- Stop Guessing on CAC
- Stop Guessing on Churn
- Cohort Analysis for DTC: Definitions, Thresholds, and Failure Modes
- Stop Guessing on Creative
- Stop Guessing on LTV
- Stop Guessing on Margin
- Stop Guessing on MER
- Stop Guessing on Retention
- Stop Guessing on ROAS
- Subscription Billing Decline Codes Operators Must Know
- Why Subscription Churn Spikes on Monday
- Surface MRR Risk and Dunning Status Daily
- Subscription Pause as Retention
- Support Tickets as a Churn Signal
- The 11pm Slack Question That Should Be a Scheduled Job
- TikTok Creative Volume Problem: Ops Capacity Limits
- TikTok Testing Budget Rules for DTC
- Using AI to Increase Ecommerce LTV
- Reduce Ecommerce CAC by Automating Waste Detection and Creative Cycles
- UTM Hygiene as Ops Debt
- Vanity Automation Scoreboards: Actions Taken vs Revenue Moved
- Voluntary Churn Reasons Taxonomy
- Weekly AOV Review Template
- Weekly Attribution Review Template
- Weekly CAC Review Template
- Weekly Churn Review Template
- Weekly Cohorts Review Template
- Weekly Creative Review Template
- Weekly Dunning Review Template
- Weekly LTV Review Template
- Weekly Margin Review Template
- Weekly MER Review: Thresholds and Failure Modes
- Weekly Retention Review Template
- Weekly ROAS Review: Thresholds, Diagnostics, and Decision Rules
- What Is a Scheduled Growth Brief?
- What Is an Ad Audit Agent?
- What Is an Ecommerce AI Operator?
- Approval-Gated Automation: Definition and Implementation
- Blended CAC for Operators
- Churn Risk Ranking: Prioritized Customer Intervention Lists
- Contribution Margin ROAS: The Profitability-First Ad Metric
- Cross-Tool Reconciliation: Matching Data Across Shopify, Meta, and Klaviyo
- Operator Memory Across Tools: Why Chat Tabs Fail
- Read-Only Pilot Mode: Definition and Implementation
- What We Will Not Automate in Ecommerce Ops
- Adjudicating Meta ROAS vs Shopify MER Without Politics
- When AOV Is the Wrong Metric
- When Attribution Is the Wrong Metric
- When CAC Is the Wrong Metric
- When Churn Is the Wrong Metric
- When Cohort Analysis Hides What You Need to Fix
- Creative Is Not a Metric
- When Dunning Is the Wrong Metric
- When LTV Is the Wrong Metric
- When Margin Is the Wrong Metric
- When MER Is the Wrong Metric
- When Not to Buy an AI Operator
- When Retention Is the Wrong Metric
- When ROAS Is the Wrong Metric
- When to Kill the Weekly Deck
- When to Pause vs Cut Budget
- Why Every Write Action Is Gated
- Build an Offer Ladder for Lapsed Customers
- You Still Need a Human Who Owns the P&L
- All guides