Failed payment recovery for Appstle Subscriptions merchants
Appstle Subscriptions is one of the most capable subscription apps on Shopify, and it does ship dunning basics: when a renewal fails, it can retry the charge on a schedule you configure and email the customer about the failure. If you've never opened those settings, do it today — the defaults may not match how your customers actually pay. This guide covers what the built-in tooling does, where it stops, and how to recover more without migrating anything.
What Appstle's built-in dunning handles
- Automatic retries. You set how many times a failed charge is reattempted (1–10) and how far apart (1–10 days) — treat your own admin as the source of truth for which numbers are set.
- Customer emails. Failure notifications and card-update requests can go to the subscriber automatically. The failed-payment email is opt-in — a merchant has to turn it on — with one exception: configuring a recovery discount sends it regardless, so the customer learns about the offer.
- Recovery discounts. An incentive can be attached to a specific failed attempt, optionally scoped to insufficient-funds declines only, so the customer has a reason to fix their payment method before the next retry.
- Exhaustion behavior. After the final retry, Appstle applies the exhausted-retries behaviour you selected — cancel the contract, pause it, or skip the failed order and keep the subscription active. Check which yours is on, because auto-cancel silently converts a fixable failure into churn.
Three gaps Appstle leaves to you
- You're not told, renewal by renewal. The dunning conversation happens between the app and your customer. Nothing arrives naming the subscriber who just fell out and why, so your first sign of a problem is a revenue dip weeks later — or a customer support email.
- One cadence by default. The simple recovery settings use one retry count and one fixed gap, so an expired card (which no retry can save) is treated like an insufficient-funds decline (which the right-timed retry often saves). Appstle supports phased retry campaigns for stores that need more than one cadence — set up with Appstle support rather than from the settings page. Our companion guide breaks down why the failure reason should pick the treatment.
- Reporting is aggregate, not per-renewal. Appstle's Dunning Management page has a Results tab with recovery rate, recovered revenue, subscriptions still in dunning and your most common decline reasons. What it doesn't do is tell you the moment a specific renewal fails, or route that failure by its reason.
Five settings to review this week
- Retry count and spacing — are attempts spread over enough days to catch a payday?
- Exhaustion behavior — pause is usually safer than cancel; a paused subscriber can come back.
- Customer emails — is the failed-payment email turned on at all, and does the update link work on mobile?
- Notification coverage — does anyone on your team find out when a renewal fails?
- A monthly failure review — even a manual export beats not looking.
Where Moorly fits: Moorly connects using the credential you connect — the Appstle partner connection you approve in your Appstle admin, or your own Appstle API key — so there's no migration, no checkout changes, and your Appstle setup keeps running exactly as it does now. It records each failed renewal with its decline reason, emails you a weekly recovery summary with what those failures cost, and (only when you turn actions on) works each failure by its reason while standing down whenever Appstle is already going to retry. It starts read-only. Join the early-access list →
Moorly is an independent product by Velun Labs and is not affiliated with Appstle Inc. Appstle feature details vary by plan and version — always confirm against your own admin.