Aug 14, 2026
How Operators Think About Dunning
Dunning is the automated or manual process of attempting to recover failed recurring payments through retries, customer communication, and payment method updates before subscription termination.

What Dunning Is (and Isn't)
Dunning sits between payment failure and churn. A customer's card declines on renewal. The payment processor rejects the charge. Dunning is the sequence of actions taken to collect that payment before the subscription ends.
This is not customer service recovery. This is not negotiation or discounting. Dunning is the mechanical process of asking the customer to fix their payment method, retrying the charge, and communicating the stakes clearly.
Dunning applies to subscriptions, recurring charges, and any business model where the customer expects to be charged on a schedule. For DTC Shopify brands, this typically means subscription boxes, membership tiers, or auto-replenishment programs.
Core Decision: Retry Count and Timing
The first operational decision is how many times to retry a failed charge and on what schedule. Industry baseline is 2 - 4 retries over 7 - 14 days. The threshold depends on payment failure rate and churn sensitivity.
A typical dunning schedule looks like this: Retry 1 on day 0 (immediate). Retry 2 on day 3. Retry 3 on day 5. Retry 4 on day 7. If all fail, send final notice and cancel on day 10.
The risk of too many retries: customer frustration, negative bank records, and involuntary churn (customer closes card or disputes charges). The risk of too few retries: leaving revenue on the table. Most operators converge on 3 retries as the operational sweet spot.
- Retry 1: Immediate (same day as initial failure)
- Retry 2: Day 3 - 4
- Retry 3: Day 5 - 7
- Final notice: Day 8 - 9
- Cancellation: Day 10 - 14
Message Framing and Escalation
Dunning emails must be clear about the problem (payment declined), the action required (update payment method), and the consequence (subscription cancels). Vague messaging increases support volume without improving recovery.
First dunning message (day 0 - 1): Neutral tone. State the fact. Provide a direct link to update payment method. Example: 'Your payment method was declined on [date]. Your subscription will pause if we can't collect payment by [date]. Update your payment method here.'
Second message (day 3 - 5): Slightly more urgent. Mention the subscription will cancel. Repeat the action link. Add a support contact option for customers with legitimate issues (card lost, account frozen).
Final message (day 8 - 10): Last chance framing. Clear cancellation date. Offer brief window to reactivate if they want to keep the subscription after cancellation.
Payment Method Update Friction
The core failure mode in dunning is friction in the update flow. A customer wants to fix their payment method but the process is unclear, requires account login, or doesn't work on mobile. They give up. Subscription cancels.
Operators should measure the conversion rate from 'dunning email sent' to 'payment method updated' for each retry. Baseline target is 15 - 25% conversion on the first dunning email. If conversion is below 10%, the update flow is broken.
Reduce friction by: (1) Using a direct update link that doesn't require login. (2) Making the link mobile-responsive. (3) Allowing saved payment methods (Apple Pay, Google Pay) as alternatives. (4) Sending a confirmation email once the method is updated.
Failure Mode: Over-Dunning and Churn Acceleration
The most common failure mode is dunning too aggressively. Sending 5 - 6 emails over 2 weeks, retrying the charge 6+ times, or using threatening language causes customers to cancel proactively rather than wait for cancellation.
Operators should track the correlation between dunning email count and voluntary churn (customer-initiated cancellations during the dunning window). If dunning emails correlate with higher churn, reduce retry count or extend the timeline.
A second failure mode is dunning customers who have legitimate reasons for the decline (card expired, new card not activated, fraud hold). These customers are trying to pay. Dunning them aggressively converts them to churn. Offer a support path in every dunning email.
Metrics and Monitoring
Track four metrics to evaluate dunning performance: (1) Recovery rate - percentage of failed charges recovered by retry. (2) Dunning-induced churn - voluntary cancellations during dunning window. (3) Payment method update rate - percentage of customers who update their method after dunning email. (4) Cost per recovery - total dunning email and support cost divided by recovered charges.
Baseline recovery rate for DTC subscriptions is 30 - 50% of failed charges. If recovery is below 20%, the dunning sequence is too short or the messaging is unclear. If recovery is above 60%, the dunning sequence may be too long and driving churn.
Dunning-induced churn should be monitored separately from natural churn. If 20%+ of customers in the dunning cohort cancel voluntarily, the dunning strategy is too aggressive.
- Recovery rate: (Recovered charges / Failed charges) × 100
- Update rate: (Customers who updated payment method / Dunning emails sent) × 100
- Dunning churn: (Voluntary cancellations during dunning / Customers in dunning) × 100
- Cost per recovery: (Total dunning costs / Recovered charges)
Operational Checklist
Implement dunning in this order: (1) Set retry schedule (3 retries, 7 - 10 day window). (2) Write dunning email templates (3 versions: neutral, urgent, final). (3) Build or configure payment method update flow. (4) Set up monitoring for recovery rate and churn. (5) Run for 30 days, measure, adjust.
- Define retry schedule: count, timing, and final cancellation date
- Write 3 dunning email templates with clear CTAs
- Ensure payment update link is mobile-responsive and doesn't require login
- Set up tracking for recovery rate, update rate, and dunning-induced churn
- Monitor for 30 days and adjust retry count or messaging based on metrics
- Document the dunning policy and share with support team
- Test the flow with a test subscription before full rollout
Questions
FAQ
How many times should we retry a failed charge?
Most operators converge on 3 retries over 7 - 10 days. This balances recovery rate (30 - 50% of failed charges) against dunning-induced churn. More than 4 retries typically increases voluntary cancellations without meaningfully improving recovery.
What's the difference between dunning and collections?
Dunning is the automated retry sequence for recurring payments before subscription cancellation. Collections is the manual outreach to customers with past-due balances after the subscription has already ended. Dunning is preventive; collections is reactive.
Should we offer discounts or incentives in dunning emails?
No. Dunning is about payment recovery, not retention. Offering a discount signals that non-payment is negotiable and trains customers to let payments fail. If a customer needs help, offer a support contact. If they want to cancel, let them cancel cleanly.
How do we know if our dunning strategy is working?
Measure recovery rate (30 - 50% baseline), payment method update rate (15 - 25% on first email), and dunning-induced churn (should be <20% of dunning cohort). If recovery is low, the sequence is too short. If churn is high, the messaging is too aggressive.
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 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
- Dunning: Definition, Thresholds, and Failure Modes
- 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