What happened between Recharge and Skio
Recharge announced it was acquiring Skio on 30 April 2026. TechCrunch reported the price as $105M in cash, a figure Skio's founder shared on social media and that was not in the press release. TechCrunch also reported that Skio had raised about $8M and had around $32M in annual recurring revenue. Coverage put the combined business at more than 20,000 merchants.
Both are established subscription apps, and an acquisition does not mean Skio stops working. It does mean pricing, product plans and support can change over time, which is reason enough to look at your options before your next contract renewal.
Questions to ask before you decide
Get answers in writing from your Skio account manager first. The answers decide whether a move is worth the work.
- Will my pricing change, and from what date?
- Is Skio staying a separate product, and for how long?
- Who will my support contact be, and will response times change?
- What is the notice period in my contract?
- Can I export subscribers, selling plans and order history in full, and in what format?
- Will the Klaviyo integration and its events stay the same?
Staying on Skio is a reasonable choice if the answers are clear, the terms suit you and your cancel flow and payment recovery are performing. Moving is worth looking at if your terms are changing, you want features Skio does not have, or you were already unhappy with retention results.
How a move from Skio to Loop works
The move itself is mostly a data transfer that Loop's team supports. Loop says it has handled 1,065+ Skio-to-Loop moves and that one typically takes about 2 weeks. Those are Loop's own figures, so ask them for a timeline based on your store.
This is the checklist we work through with a brand before, during and after the move:
| Area | What to check | What often gets missed |
|---|---|---|
| Subscribers | Every active, paused and scheduled subscription moves with the right product, quantity and status | Paused subscriptions and their restart dates |
| Payment methods | Whether stored cards move without subscribers re-entering them, which depends on your payment gateway | Subscribers on a non-standard gateway who will need to update their card |
| Selling plans | Every frequency and discount is rebuilt so subscribers keep the price they signed up at | Legacy prices and old discounts still running for early subscribers |
| Next billing dates | Each subscriber's next charge date stays the same | Double charges or skipped renewals around the cutover date |
| Customer portal | Portal actions (skip, swap, pause, change frequency) and branding are set up before launch | Links in old emails and on the site still pointing to the Skio portal |
| Cancel flow | Cancel reasons and offers are rebuilt in Loop, ideally improved | Starting from Loop's defaults and losing the offers that worked |
| Payment recovery | Retry ladder, failure-reason strategies and card-update messages are set in Loop | Default retry settings running for weeks before anyone checks |
| Notification emails | Loop notifications are styled and worded for your brand | Duplicate emails from Loop and Klaviyo |
| Add-ons | Upsells, prepaid plans, gifts and loyalty rules are rebuilt | Prepaid subscriptions with the wrong remaining order count |
What to rebuild in Klaviyo after the move
Every Klaviyo flow, segment and email that relies on Skio data stops working once Skio stops sending events, so this part needs as much planning as the move itself.
Before the move, list everything in Klaviyo that uses Skio:
- Flows triggered by Skio events, such as payment failed, subscription canceled, upcoming order and subscription started.
- Segments and flow filters that use Skio profile properties, such as "is an active subscriber". A broken subscriber segment means subscribers start getting one-time reorder reminders and offers meant for buyers.
- Links to the Skio portal inside templates, flows and SMS.
- Campaign exclusions that rely on Skio data.
Then rebuild each one on Loop's events in Klaviyo, for example "Loop Billing Attempt Failed and will be Retried", "Loop Subscription Cancelled" and "Loop Order Processed". Keep the new flows in draft until Loop events are arriving with real volume, switch them on, and only then turn off the Skio versions. Keep the old flows as drafts for a while so you can compare.
A safe order for the move
Run the 2 setups side by side for a short period and never leave subscribers without payment recovery or a cancel flow. The order we use:
- Build the Loop portal, selling plans, cancel flow, payment recovery and notifications while Skio is still live.
- Build the Klaviyo flows on Loop events, in draft.
- Test with internal subscriptions: a renewal, a skip, a swap, a cancel and a failed card.
- Pick a cutover date away from your busiest billing days.
- Move subscribers, then check the first renewal run line by line.
- Switch the Klaviyo flows live and turn off the Skio flows.
- Tell subscribers about the new portal login if the way they sign in changes.
- Review cancel saves and payment recovery 30 days later against your Skio numbers.
EK proof
Email Kong is an official Loop partner and a Klaviyo Platinum Partner. 6 brands currently run subscriptions on Loop with us, including:
- Kaori (women's health): Klaviyo went from 3.3% to 19% of store revenue. Flow revenue grew 17.7x.
- Penrose Skin (skincare): Klaviyo's share of store revenue went from 15.2% to 23.2%. Flow revenue grew 10.5x.
- KittySpout (pet): 46% of store revenue comes from Klaviyo.
