Shopify merchants shopping for dunning help face a shelf problem. Every app on the shelf promises to recover failed payments, the screenshots all show the same rising graph, and the differences that decide whether the app earns its fee are invisible until the first renewal cycle runs through it. Five checks separate the tools that work the queue from the tools that merely watch it.
Check one: does it retry with judgment, or on a fixed timer? A fixed-interval retry sequence treats an expired card and a short-on-cash Friday identically. Ask how the sequence changes by decline type. If the answer is a screenshot of one ladder, the app is a metronome, not a recovery system.
Check two: does it check for updated cards before it retries? Network account updater services refresh replaced cards automatically for a large share of failures. An app that retries the old credentials first, and asks the customer second, has the order backwards. The silent fix should always be attempted before the noisy one.
Check three: who sends the customer messages, and in whose voice? The recovery email arrives at a delicate moment. It should carry the store's name and tone, state plainly what happened and what to do, and link to a card update page that works on a phone in under a minute. Ask to see the actual email and the actual update page, not a description of them.
Check four: what does it cost when it works a little? Percentage-of-recovery pricing sounds aligned until a good month makes the fee the largest line in the stack. A flat fee is duller and easier to judge. Either way, do the arithmetic on your own failure volume before installing — and if your subscriptions run through Recharge, as a large share of Shopify stores' do, use recharge dunning and what it does to the queue as the template for the questions.
Check five: how does it count a save? A recovery the platform's native retry landed, a recovery from a card the network updated, and a recovery your email produced are three different events with three different lessons. An app that blends them into one heroic rate is grading its own homework. The honest report separates the mechanisms, counts each recovered dollar once, and reconciles to money that actually settled.
Check six, the one merchants skip: what happens when a subscriber cancels mid-sequence? A failed payment and a cancellation are different events, and an app that keeps emailing, or worse, keeps retrying, after a customer has cancelled is not being persistent. It is manufacturing chargebacks and complaints out of people who left politely. The recovery sequence must stop the moment the subscription does, automatically, and the app should be able to show you that stop happening in its own logs. Ask about it directly. The pause family deserves the same clarity: a subscriber who skips a month or pauses a box is not a failure to be chased, and any tool that counts a resumed pause as a recovery is inflating the very rate you are using to judge it.
Run those five checks and the shelf gets much smaller. What remains is the short list worth trialling, and the trial itself should be judged on one renewal cycle of your own data, not on the graph in the listing. The tool that reads failures before it retries them, fixes silently what can be fixed silently, and reports its saves in a way your bank statement can confirm is the tool that belongs in the stack. That is the standard Swipe Again publishes for itself, and it is a fair standard to hold every app on the shelf to, including this one.
Top comments (0)