--- title: "10 Subscription Workflow Examples to Automate | Chargezen" description: "Ten subscription automations worth running, from welcome messages and starter-to-refill swaps to failed payment steps, loyalty gifts and team alerts." url: "https://chargezen.com/blog/subscription-workflow-examples" lang: "en" updated: "2026-10-18" --- Canonical URL: https://chargezen.com/blog/subscription-workflow-examples # Subscription Workflows: 10 Automations Every Subscription Brand Should Run Subscriptions · 9 min read ![Jerry Abrahamson](https://chargezen.com/assets/blogpost1.6581a30d.png) Jerry Abrahamson Founder & CEO • Oct 18, 2026 ![Subscription Workflows: 10 Automations Every Subscription Brand Should Run](https://chargezen.com/og-default.png) A subscription is a long relationship made of small moments: the first order, the reminder before each charge, a skipped box, a declined card, the sixth order in a row. Each moment is a chance to help the subscriber or to lose them. Doing all of that by hand doesn't scale past a few dozen subscribers. Workflows do it for you, on time, every time. This guide explains how a subscription workflow is put together, then walks through ten automations worth running in almost any subscription business, with the event, the conditions and the actions for each. It ends with how to test them and how to tell whether they are working. ## How a subscription workflow works Every workflow answers four questions: * **When does it start? (the event)**: Something happens to a subscription: it is created, a renewal is paid, a payment fails, an order is skipped, a product is swapped, a price change is scheduled, the subscription is paused or canceled. * **Who is it for? (the conditions)**: Narrow it to the subscribers it fits: a product or plan, a customer tag, how many orders they have paid for, how much they have spent, or who made the change. * **What happens? (the actions)**: Send an email or text, tag the customer or the order, add or swap a product, change the plan, add a discount or give a trial. * **When does it happen? (the timing)**: Right away, or after a wait. A two-hour wait after checkout feels personal; a ten-day wait lands a tip after the first box has arrived. Two habits make workflows easier to live with. Give each one a plain name that says what it does ("Starter kit to refills after order 1"), and build one workflow per job instead of one giant workflow with ten branches. Small workflows are easier to test, pause and change. ## Customer messages vs team alerts Some workflows talk to the subscriber. Others tell your team something happened. Keep them apart. Customer messages need the subscriber's language, a clear next step and a link to their portal. Team alerts need facts: who, what changed, and what to look at. A cancellation can trigger both, but the customer should never get a message written for your team, and your team shouldn't be flooded with alerts for changes they made themselves. ## 1\. A welcome that arrives a little later * **Event**: Subscription is created (at checkout). * **Action**: Send a welcome email right away, and a second, more personal message an hour or two later. The order confirmation covers the receipt. The welcome covers what the subscriber actually wants to know: what's coming, when it will ship, and how to skip, swap or change the date without contacting you. The delayed follow-up reads like a note from a person rather than a system message. Put the portal link in both. ## 2\. Starter kit to refills after the first order * **Event**: Subscription is created. * **Condition**: Subscription has the starter kit product. * **Action**: Swap the starter kit for the refill product, or change the subscription to the refill plan. If your first order includes a bottle, a device or a sample set, subscribers don't want a second one a month later. Swapping to refills after checkout means every later order is the right one, and nobody has to remember to do it. Tell the subscriber in the welcome message so the change isn't a surprise. ## 3\. Tag first orders and renewals for the warehouse * **Events**: Subscription is created; renewal payment succeeds or is recovered. * **Action**: Add tags to the order, such as "subscription first order" or "subscription recurring order", and the delivery frequency. Tags are how the rest of your stack knows what kind of order this is. Your warehouse can put a welcome card in first orders only. Your reports can split new from repeat revenue. Your email tool can filter on them. It is the least exciting workflow on this list and one of the most useful. ## 4\. A reminder before every renewal, tuned to risk * **Event**: Upcoming renewal reminder, a set number of days before the charge. * **Condition**: Churn risk is high, medium or low. * **Action**: Send a different reminder to each group. Every subscriber should hear from you before they are charged: what is coming, when, for how much, with one-tap links to skip, swap or change the date. Subscribers who look likely to leave deserve a different note: more reassurance, a reminder of what they get, maybe an offer to slow down instead of stopping. See [churn prediction](https://chargezen.com/glossary/churn-prediction). ## 5\. A failed payment sequence that ends on purpose * **Events**: Payment failed (first attempt), each retry that fails, and the last attempt. * **Conditions**: "It's the first failed payment" for the first message; "Payment retries ended by" cancel, pause, skip or keep for the last one. * **Actions**: Email and text with a link to update the card, then a final message that matches what happened to the subscription. A declined card is not a decision to leave. Tell the subscriber quickly and kindly, give them a single link to fix it, and send a different message once retries run out: "we've paused your subscription" reads very differently from "we've canceled it." Our guide to [why subscription payments fail](https://chargezen.com/blog/why-subscription-payments-fail) covers retry schedules and messages in depth. ## 6\. Warn before the card expires * **Event**: Payment method needs attention, in the days before a renewal. * **Condition**: Payment method problem is: card expiring, card expired, or can't be charged. * **Action**: Send an email and a text asking the subscriber to update it. The cheapest failed payment to recover is the one that never happens. A short note a few days before the charge ("your card on file expires this month") prevents a decline instead of chasing one. ## 7\. Confirm every skip and swap * **Events**: Upcoming order is skipped; product is swapped. * **Action**: Send a short confirmation with the new next-order date or the new product. A confirmation turns "did that work?" into trust. It also cuts support emails from people who aren't sure whether they will still be charged. Add a quiet extra line when it fits: after a swap, "here's how to use your new flavor"; after a skip, the date the next order will ship. If one subscriber skips again and again, that is a frequency problem, not a skip problem. Watch your [skip rate](https://chargezen.com/glossary/skip-rate) and offer a slower schedule. ## 8\. A thank-you gift on a loyalty milestone * **Event**: Renewal payment succeeds. * **Condition**: Consecutive paid billing cycles is at least 6 (or 3, or 12). * **Actions**: Add a free one-time product to the next order, tag the customer as a loyal subscriber, and send a thank-you message. A surprise in the box at order six costs you one product and gives the subscriber a story to tell. Tagging them also lets you treat long-time subscribers differently elsewhere: early access to launches, a different win-back offer, a personal note from the founder. Use a tag condition so each subscriber gets a given milestone gift once. ## 9\. Tell subscribers before a price goes up * **Event**: Product price change scheduled. * **Action**: Send an email and a text explaining the new price, when it starts and how to change or skip. Price increases go badly when subscribers find out from their bank statement. Give notice before the new price applies, say why in one honest sentence, and remind them of their options. Our [subscription pricing guide](https://chargezen.com/blog/subscription-pricing-strategy) covers how to raise prices for existing subscribers without losing them. ## 10\. Alert your team when a customer cancels or pauses * **Events**: Subscription is canceled, paused, resumed or restarted; a renewal is held because a product is out of stock. * **Condition**: Change was made by the customer. * **Action**: Email your store team. For a smaller brand, every cancellation is worth a look: who was it, how long had they subscribed, what did they say on the way out? An alert puts that in front of someone while a personal reply can still change their mind. Filter to customer changes so your team isn't alerted about work they did themselves. ## Trials: give the first orders free, then charge A trial is a workflow too. On "subscription is created" (or "reactivated", for a returning subscriber), add a trial period: a set number of orders that ship at no charge before regular billing begins. Trials only make sense when the subscription starts, so keep them on those two events. Be clear in the welcome message about when the first paid order will happen and how to cancel before it. See [first-order discount](https://chargezen.com/glossary/first-order-discount) for the trade-offs of starting free or cheap. ## Test before you turn it on * Save each new workflow as a draft first and read it back as a sentence: "When X happens, for subscribers who Y, do Z after W." * Run it on a test subscription with your own email and phone number. Check the timing, the links and how it reads on a phone. * Check the overlap. If two workflows fire on the same event for the same subscriber, will they send two messages? * Turn on one new workflow at a time, so you know which change moved your numbers. * Keep a short log of what you turned on and when. ## Measure what each one does | Workflow | What to watch | | --- | --- | | Welcome and onboarding | How many new subscribers pay for a second and third order | | Renewal reminders | Skips and frequency changes (good) vs cancellations (bad) in the days after | | Failed payments and card warnings | Recovery rate and how many cards are updated before a decline | | Milestone gifts | Retention of subscribers who got the gift vs those just short of it | | Price change notices | Cancellations in the month after the notice | | Team alerts | How many alerted cancellations your team saved with a reply | Compare against the same period before the workflow was on, or hold back a small group. Our [subscription metrics guide](https://chargezen.com/blog/subscription-metrics) explains how to calculate renewal, save and recovery rates. ## Run these in Chargezen Every example above can be built in Chargezen [subscription workflows](https://chargezen.com/subscriptions/workflows), part of Chargezen [Subscriptions](https://chargezen.com/subscriptions): * **18 events**: New, paused, resumed, restarted, canceled and expired subscriptions; paid, failed, retried and recovered payments; upcoming renewals; skips and swaps; price changes; renewals held for stock; bank confirmations; and payment method problems. * **Conditions**: Products, variants, plans and plan groups; customer tags; orders placed and amount spent; paid and consecutive paid billing cycles; churn risk; whether the change was made by the customer. * **Actions**: Send an email or text, tag the customer or order, add a one-time or recurring product, remove or swap a product, change the plan, add or remove a discount, and add a trial period. * **Timing**: Wait up to 30 days before the workflow runs and before each action. * **Ready on day one**: Welcome, renewal, failed payment, card expiry, skip, swap, price change, out-of-stock and store alert messages come set up as default workflows you can edit or set to Draft. For one-tap skip, swap and reactivate links inside your emails and texts, see [quick actions](https://chargezen.com/subscriptions/quick-actions). The [workflow docs](https://chargezen.com/docs/subscriptions/workflows) list every event, condition and action. Subscriptions is $199 a month or $1,990 a year for Shopify Advanced and Shopify Plus stores, with no commission. See [pricing](https://chargezen.com/pricing). ## Frequently asked questions ## What is a subscription workflow? A rule that runs on its own: when something happens to a subscription and the subscriber matches your conditions, the actions you chose happen, right away or after a wait. ## Which workflows should I set up first? The welcome, the reminder before each renewal and the failed payment messages. They touch every subscriber and protect the most revenue. Add milestone gifts and team alerts next. ## How many messages is too many? If a subscriber would get two messages about the same thing on the same day, merge them. Every message should either confirm something they did or help them avoid a problem. ## Can workflows replace my email marketing tool? They cover the messages tied to subscription events. Newsletters, launches and campaigns still belong in your marketing tool, and the two work side by side. ## Glossary * [Skip rate](https://chargezen.com/glossary/skip-rate) * [Churn prediction](https://chargezen.com/glossary/churn-prediction) * [Dunning management](https://chargezen.com/glossary/dunning-management) * [Renewal rate](https://chargezen.com/glossary/renewal-rate) ## Keep reading * [The first three orders: how to onboard new subscribers](https://chargezen.com/blog/subscriber-onboarding) * [What subscribers should be able to do in your customer portal](https://chargezen.com/blog/subscription-customer-portal-best-practices) * [Why subscription payments fail and how to recover them](https://chargezen.com/blog/why-subscription-payments-fail) ![Jerry Abrahamson](https://chargezen.com/assets/blogpost2.32f70dbd.png) Written by ### Jerry Abrahamson Jerry is the Founder and CEO of Chargezen, helping brands build sustainable omni-channel businesses. With over 10 years of experience in omni-channel commerce and SaaS, he's passionate about helping brands create recurring revenue streams. [](https://twitter.com/chargezenjerry)[](https://linkedin.com/in/jerry-a) ## Related Articles [ ![AI Receptionist for Cleaning Businesses: Quotes, Recurring Clients and Privacy](https://chargezen.com/og-default.png) Subscriptions · 8 min read ### AI Receptionist for Cleaning Businesses: Quotes, Recurring Clients and Privacy How a cleaning business can use an AI receptionist for quotes, recurring clients and reschedules while keeping access codes and schedules private. ](https://chargezen.com/blog/ai-receptionist-for-cleaning-businesses)[ ![Phone System for a Cleaning Business: Get Off Your Personal Cell Without Losing Clients](https://chargezen.com/og-default.png) Subscriptions · 9 min read ### Phone System for a Cleaning Business: Get Off Your Personal Cell Without Losing Clients How a residential or commercial cleaning business should set up its phone: a business number, crews texting clients, recurring schedules, privacy, and options. ](https://chargezen.com/blog/business-phone-system-for-cleaning-businesses)[ ![Pest Control Business Phone System: Seasons, "What Is This Bug?" Photos and Discreet Calls](https://chargezen.com/og-default.png) Subscriptions · 8 min read ### Pest Control Business Phone System: Seasons, "What Is This Bug?" Photos and Discreet Calls How to choose a phone system for a pest control company: seasonal surges, bug photos by text, discreet bed bug calls, recurring plans, and the options compared. ](https://chargezen.com/blog/business-phone-system-for-pest-control) ## Ready to Grow Your Subscription Revenue? Join leading brands using Chargezen to reduce churn, increase revenue, and automate operations. [Get Started](https://admin.chargezen.com/signup)