Every Recharge store produces the same handful of moments each month. A charge is coming. A card gets declined. Someone skips. Someone cancels. Recharge email marketing done well means each of those moments has a Klaviyo flow waiting for it, written for that exact situation, instead of one generic newsletter that treats a loyal subscriber and a churned one the same way.
This guide covers the events the Recharge integration sends to Klaviyo, the flow we build on each one, and how to split the work between Recharge's own notifications and Klaviyo so nobody gets the same email twice. For the wider strategy behind subscription emails, read our guide to subscription email marketing.
What Recharge sends to Klaviyo
Once you connect Recharge to Klaviyo, subscription activity starts showing up in Klaviyo as metrics, and subscriber data lands on the profile as properties. Think of next charge date, subscription status or the products on the subscription.
We describe the events in plain terms here on purpose. The exact names in your account depend on your Recharge plan, the integration version and the settings you picked, and Recharge updates them from time to time. In general you will see events for these moments:
- A subscription is created
- A charge is coming up
- A charge fails
- A charge is skipped
- A subscription is cancelled
- A subscription is reactivated or changed
So before you build, open Klaviyo, go to the metrics list and write down exactly what arrives from Recharge. Then open a test profile with an active subscription and note which properties sit on it. That list decides which flows you can build and how far you can personalize them. If something you need is missing, Recharge support or their developer docs are the place to ask.
The Recharge email marketing flows we build
Here is the map we start from with a Recharge brand. Timing is our default, and we adjust it to the product and the charge interval.
| Event | Flow | Goal | Timing |
|---|---|---|---|
| Subscription created | Subscription welcome | Confirm the order, explain how to skip, swap or pause | Right away, then a second email a few days later |
| Upcoming charge | Charge reminder | No surprise charges, make skip and swap easy | 3 to 5 days before the charge |
| Charge failed | Failed payment | Get the card updated before the order is lost | Within hours, then 2 or 3 follow-ups over a week |
| Charge skipped | Skip follow-up | Offer a swap or a different interval | 1 day after the skip, one email |
| Subscription cancelled | Cancellation save | Catch people who left for a fixable reason | Within 24 hours |
| Subscription cancelled | Win-back | Bring churned subscribers back | Starts 3 to 6 weeks after the cancel |
Subscription welcome
The first subscription email has one job. Make the subscriber feel in control. Say what ships, when the next charge happens, and where to manage it. A subscriber who knows they can skip in two clicks is far less likely to cancel the first time life gets busy.
The second email can be about the product itself: how to use it, what to expect in week two, the mistakes new customers make. If you sell consumables, this is also where you set expectations on results.
Upcoming charge reminder
This email prevents more refund requests than anything else in the account. Put the date, the amount and the products near the top. Then a skip link and a swap link, clearly visible.
Yes, some people will skip. That's fine. A skip keeps the subscription alive, while a surprise charge often ends it, plus a chargeback.
The timing depends on when Recharge fires the upcoming charge event. That lead time is a setting in Recharge, so check it first. If the event fires seven days out and you want the email three days before, add a delay in the flow.
Failed payment
Recharge retries failed charges on its own schedule. Your Klaviyo flow should run alongside those retries, not against them. Send the first email within a few hours with a direct link to update the payment method. Keep it short and neutral. Most failed payments are expired cards, and nobody likes being told they did something wrong.
Follow up two or three times over the next week. Before each email, add a flow filter or conditional split that checks whether the payment was fixed, so people who already updated their card stop getting reminders.
Skip follow-up
A skip tells you something. Maybe they still have product at home, maybe they got bored of the flavor. One email a day later, suggesting a longer interval or a different product, does the job. If Recharge passes the product on the event, name it. Don't build a long sequence around a single skip.
Cancellation save and win-back
Recharge has its own cancellation flow in the customer portal, where subscribers can be offered a pause, a skip or a discount before they confirm. Look at what your portal currently shows, because the email should not repeat the same offer the subscriber just declined.
The save email goes out within a day. Plain text, from a real person at the brand, asking what went wrong. If the cancellation reason reaches Klaviyo as a property, split on it. "Too much product" gets a frequency change, "too expensive" might get a smaller size or a one-time discount.
The win-back starts weeks later and runs over a month or two. Lead with something new or a reminder of why they subscribed, and link straight to reactivation where your setup allows it. Our win-back flow guide covers timing and offers.
Recharge notifications vs Klaviyo: who sends what
Recharge comes with its own customer notifications. Order confirmations, upcoming charge reminders, payment failure emails, cancellation confirmations. Turn on Klaviyo flows without touching those, and your subscribers get two emails for the same event, in two different designs.
Our rule is simple. Anything that sells or retains moves to Klaviyo, because that's where the brand design, segmentation and testing live. Pure transactional messages can stay in Recharge if Klaviyo does not replace them. Then go through the Recharge notification settings line by line and switch off each email that a Klaviyo flow now covers.
| Message | Usually sent by | Note |
|---|---|---|
| Upcoming charge reminder | Klaviyo | Turn off the Recharge version |
| Failed payment | Klaviyo | Check the retry schedule in Recharge first |
| Cancellation follow-up | Klaviyo | Coordinate with the portal cancel flow |
| Account and login emails | Recharge or Shopify | Leave these where they are |
Test it with a real test subscription. Trigger each event and check your inbox. If two emails arrive, one of the systems still has a notification switched on.
Segments that keep campaigns clean
The flows are half of Recharge email marketing. The other half is making sure campaigns respect subscription status. Build segments for active subscribers, cancelled subscribers and one-time buyers using the Recharge properties or events. Then exclude active subscribers from first-order discounts, because nothing annoys a loyal subscriber faster than seeing a newcomer get a better price. Our segmentation guide shows how to set these up.
Also check your regular post-purchase flow. A recurring Recharge order can trigger a "thanks for your first order" email if the flow filters don't exclude subscription orders.
If you'd rather have this built and run for you, that's what our subscription marketing service does for Recharge brands.
Questions we get a lot
Does Recharge send data to Klaviyo?
Yes. Recharge has a Klaviyo integration that sends subscription events and subscriber properties into your Klaviyo account. The exact metric names and properties depend on your Recharge setup and integration version, so check the metrics list in Klaviyo before you build any flow.
Which Recharge events should trigger Klaviyo flows?
Start with the upcoming charge, a failed charge, a cancelled subscription, a skipped charge and a newly created subscription. Those cover the moments where an email changes whether the subscriber stays.
Should I turn off Recharge notifications if I use Klaviyo?
Only for the messages Klaviyo takes over. If both systems send an upcoming charge reminder, subscribers get two. Go through the Recharge notification settings one by one and switch off each email that a Klaviyo flow now covers. Keep the transactional ones Klaviyo does not replace.
How far before the charge should the reminder go out?
We usually aim for three to five days before the charge. The real limit is when Recharge sends the upcoming charge event, which is a setting on the Recharge side, so check it before you set flow delays.