DEV Community

Swipe Again for Swipe Again

Posted on

A Shopify Renewal Has Two Checkouts, and Only One Gets Optimised

Ask a Shopify subscription merchant where conversion work happens and they will point at the first checkout: the product page, the offer, the discount code, the abandoned-cart flow. That checkout gets A/B tests, heatmaps, and opinions. The second checkout — the renewal, months later, when a stored card is charged again with nobody watching — gets none of that attention, even though it quietly decides how much of the first checkout's work survives the year. A renewal is a purchase the customer makes without being present, and it fails for reasons the storefront never sees.

The failure modes are specific to the stack. A card replaced in a bank app never reaches the subscription record. A payday miss is retried on the platform's default rhythm rather than the customer's. A customer who moved house, changed banks, or simply forgot the subscription existed gets a generic failure notice — or none at all — and discovers the lapse when the box stops arriving. None of these customers churned in any meaningful sense. They were not persuaded away; they were dropped by a process nobody was assigned to watch.

Shopify's native subscription retries are a reasonable floor: the charge is attempted again, and that alone rescues the easiest timing cases. Where the floor ends is everything around the attempt. Does anything check whether the card on file was replaced before the next try? Does the retry land near a payday, or wherever the calendar put it? When the customer is finally asked to act, is the request one clear message with one short update path — or a sequence that reads like debt collection and trains people to ignore it? And when a card is updated, does a fresh attempt follow immediately, while the customer is still holding their phone?

That last question matters more on Shopify than almost anywhere else, because the update path runs through accounts, emails, and customer portals that were designed for shopping, not for a thirty-second billing fix. Every extra sign-in wall between the request and the saved card costs recoveries that no retry schedule can win back. The stores that recover well treat the update page as part of the product: short, mobile-first, and followed instantly by a new attempt. It is worth testing that path yourself, on a phone, with a real expiring card, before assuming it works — merchants who do are routinely surprised by a password reset, a portal detour, or a confirmation step standing between their customer and a saved renewal.

None of this requires rebuilding the store. It requires assigning an owner to the second checkout and measuring it like the first: first-attempt success rate, recovery rate by failure type, and the share of updates that convert into paid renewals. recharge dunning that follows a renewal from checkout to the second attempt walks that measurement in the order a merchant would actually run it, including where Recharge's own retries should hand over to a dedicated recovery layer and where they should be left alone.

The honest framing for a Shopify merchant is unglamorous: the first checkout wins customers, the second one keeps them, and only one of the two currently gets a budget, a dashboard, and a person responsible for its number. Give the renewal the same respect for a single quarter — watch its queue weekly, fix the update path, time the retries — and the compounding shows up where it always does, in customers who never knew they almost left.

Swipe Again works as that recovery layer for Shopify subscription stores: it watches the renewal queue, times the retries, sends one clear ask when a customer needs to act, and counts recovery on the total — for a flat monthly fee, with no share of what it recovers.

Top comments (0)