How do you recover failed subscription payments on Shopify?

What problem does this play solve?

Some subscribers never decide to leave. Their card expired, their account was short that day, or their bank blocked the charge. Without a recovery process, one failed payment ends a subscription the customer wanted to keep. That’s involuntary churn. Unlike a cancellation, nobody has to be convinced: the customer only has to know and act. That makes recovery worth tuning before you spend more on winning new subscribers. Every payment you recover comes from a customer you already have, with no ad and no discount to pay for.

The metrics this play moves are the dunning recovery rate and, through it, your churn rate.

What’s the play?

Match each step to how payments actually fail:

• Retry over days, not all at once. Insufficient funds often clear once the customer gets paid. An expired card needs the customer to act. Three to five retries, two to three days apart, work for most stores.
• Tell the customer at every attempt. The first email asks them to update their payment method. The ones after each retry keep them in the loop until it’s fixed.
• Choose a final action that leaves the door open. A skip keeps the subscription and bills the next order as normal. A pause stops billing until the customer resumes. A cancellation is the clearest end, and the one that loses the subscriber.
• Step in where a person helps. Get alerted, and charge again as soon as the customer has updated their card.
• Avoid the failures you cause yourself. Charges that surprise customers turn into disputes, and a store with many disputes can see more of its normal charges declined. A reminder before every order and a cancellation that’s easy to find keep disputes rare.

Failures because stock ran out are a different problem. Reserving stock ahead of renewals prevents many of them.

How do you build it in Zubs?

• Built in: retries on your schedule, ending in a skip, a pause or a cancellation.
• Built in: an email to the customer at every failed attempt, with a link to update their payment method.
• Built in: customers change their payment method in the customer portal, without contacting you.
• Built in: alerts for your team, and a way to charge again by hand.
• With Klaviyo: an event on every failed attempt, for messages tailored to each dunning stage.
• With Shopify Flow: a trigger on every failed attempt, for a customer tag or a ticket in your helpdesk.

What each piece does is on the dunning feature page. Set it up in the help center: payment failure handling.

What should you measure?

• How often charges fail in the first place. Take it from your payment provider. A high rate can mean fraud prevention is set too strictly.
• Dunning recovery rate, in the Zubs analytics dashboard: the share of subscriptions with a failed payment that were paid again in the same period. This is the number your retries and emails move.

If recovery stays low, retry more often and make the payment update easier to find. If customers complain about too many emails, space the retries out.

Customers who cancel on purpose need a different play: an offer that fits their reason, and a win-back flow once they’ve left.