ReCharge vs Skio After the Acquisition: An Honest 2026 Comparison
On 30 April 2026 Recharge announced it had acquired Skio for $105 million in cash. Reported as the largest private acquisition subscription commerce has seen, it was also the quietest possible end to the argument this page used to referee. The two platforms every Shopify subscription brand was told to compare are now owned by the same company.
Which means the question people still type into Google — Recharge vs Skio — no longer has the answer it used to have. It is not a competitive bake-off any more. It is a question about a vendor's product portfolio, and about what happens to you if the portfolio gets rationalised.
We build on both. This post is the advice we have actually been giving clients since the announcement, including the answer we give most often, which is to change nothing yet and spend the saved effort somewhere it compounds.
$20B+
Annual GMV processed across the combined business, spanning more than 20,000 merchants. Whatever else the deal changes, it makes one vendor the default subscription infrastructure for a very large share of Shopify's recurring revenue — and gives that vendor considerably more room to set prices.
What actually happened, and what has not
Skio was a Y Combinator alumnus that had raised roughly $8 million in total. It sold for $105 million, in cash, to the incumbent it had spent its whole existence positioning against. For a company built on the pitch that the older architecture was the problem, that is a striking outcome, and it tells you something about how hard it is to displace a platform once thousands of merchants have their payment tokens sitting inside it.
Recharge's public line was short: for merchants on both platforms, nothing is changing today, with details of a combined offering to follow. Both products continue to operate separately. That is the whole of the official position, and it has not been meaningfully expanded since.
From challenger to portfolio product
The dashed section is the honest part of this diagram. Nobody outside the company knows how long the two-product period lasts, and nobody has committed either way.
That last point deserves emphasis, because it is the thing most commentary has quietly papered over. Whether these two products eventually merge into one, or stay permanently distinct as a good-better-best portfolio, has not been publicly committed either way. There is no announced sunset. There is also no announced guarantee of permanence.
Anyone telling you confidently which way it goes is guessing. We are not going to guess on this page. What we can do is tell you which decisions are sensitive to that uncertainty and which are not, because most of them are not.
The engineering difference is still real
Common ownership does not merge two codebases. The architectural gap that made this comparison interesting in the first place is exactly as wide today as it was in March, and it is still the thing that determines what your storefront can do.
The distinction is checkout ownership. Recharge grew up running its own checkout on a separate domain, outside Shopify's. It has supported Shopify Checkout Integration since 2023, which routes subscription purchases through the native checkout, but a meaningful number of stores are still sitting on the legacy path and the move across is not a settings toggle. Skio never had a legacy checkout to leave: every purchase has always gone through Shopify's own checkout on selling plans.
Three checkout paths, one owner
Two of these three rows now belong to the same company. Only one of them was ever architecturally free.
Underneath that, the developer experience still diverges sharply. Recharge exposes a broad, mature REST API — subscriptions, charges, orders, customers, payment methods, addresses — with a webhook model we have built migration tooling, warehouse pipelines and bespoke portals against. It is dependable, if occasionally inconsistent in how it shapes responses across API versions.
Skio's GraphQL API is narrower. For the operations most brands need — skip, swap, pause, reschedule, change quantity — it is perfectly adequate. For multi-system orchestration or anything unusual, you reach the edges sooner. What partially compensates is that because Skio's subscriptions live on Shopify selling plans, a good deal of what you would otherwise do through a vendor API you can do through Shopify's own.
On the customer-facing side the split is equally clear. Recharge gives you its hosted portal or a fully custom build against the API; we have written up what that second route actually costs in our guide to building a custom member portal. Skio embeds into Shopify customer accounts with passwordless magic-link login, which is a genuinely better default and removes an entire category of password-reset support tickets. Skio also ships native A/B testing on cancelation offers, which on Recharge is a custom build — and which most brands get wrong in the same handful of ways we catalogued in cancelation flow mistakes.
Head to head, corrected for 2026
The rows below include two that would have been meaningless a year ago — roadmap certainty and exit cost — and which are now among the most important things on the table.
Snapshot taken in September 2026. Both products iterate, and post-acquisition pricing is precisely the sort of thing that moves — check the current rate cards before you build a business case on these rows.
The cost model, and where it turns
Treat everything in this section as a dated snapshot rather than a permanent truth. As published at the time of writing, Recharge runs an entry plan at around $25 a month capped at 50 subscribers and open only to net-new merchants, a Starter plan at about $99 a month plus 1.49% and $0.19 an order, and a Plus plan at about $499 a month plus 1.34% and $0.19 an order on a twelve-month commitment. Skio publishes three tiers — Starter at $0, Growth at $399 and Scale at $599 — all charging 1.0% plus $0.20 an order, with roughly 17% off for annual prepay.
The single cent between $0.19 and $0.20 per order is close to noise; at 100,000 orders a year it is a thousand dollars. The percentage does nearly all the work, and once you are past roughly 50,000 to 100,000 subscription orders a year the swing between the two structures runs into five figures annually. The chart below models it at a $60 average order value.
Annual platform cost by subscription order volume — $60 AOV
Modelled from published list rates in September 2026 at a $60 AOV. It ignores negotiated pricing, which is exactly where Recharge closes most of this gap for larger merchants — and which nobody publishes.
Two things fall out of that model that are worth saying plainly. The first is that Recharge's own tiers cross each other at around 53,000 orders a year; below that the Starter plan is cheaper despite the higher percentage, above it the Plus platform fee pays for itself. If you are on Plus and doing 20,000 orders a year, you are paying for the tier rather than saving with it.
The second is that on published list rates Skio's variable rate is lower at essentially every volume, and it is the same 1.0% on the $0 Starter tier as on Scale — the tiers buy features and support, not a better rate. That is unusually clean pricing, and it is the thing we would most expect to change once a combined commercial offering appears.
None of which is an argument for switching platforms to save 0.3%. The money that goes missing in most subscription programs is not on the rate card; it is sitting in failed payments, badly built skip flows and prepaid maths that quietly loses margin. We have written about both the common revenue leaks and the trade-offs in prepaid plans, and in the audits we have run this year those two areas have moved more money than any platform fee ever has.
If you were about to migrate between them, stop
This is the sharpest question the acquisition creates, and the one clients have asked us most since April. Plenty of brands had a Recharge-to-Skio migration on the roadmap for this year. Several were mid-scoping when the news landed.
A migration between two products owned by the same vendor is a fundamentally different bet from a migration to a competitor. When you moved from Recharge to Skio in 2025, you were buying architecture and buying leverage: a second vendor with an incentive to keep you, and a credible threat to wave at the first one. Today you are buying only the architecture, and you are paying full migration price for it.
Worse, you are paying it into a roadmap nobody has committed to. If the products converge, you will have spent a quarter's engineering to arrive somewhere you might have been carried for free. If they stay distinct, you have done a real migration for real reasons — but you have not reduced your vendor concentration by a single percentage point. Our detailed Recharge-to-Skio migration guide still describes the mechanics accurately; what has changed is the reason for doing it.
-
You are stuck on the legacy Recharge checkout and cannot use Shop Pay, checkout blocks or Functions
-
Your support load is dominated by password resets and portal confusion
-
You have already committed the budget, scoped the work and the business case survives without the leverage argument
-
“We want to reduce our dependence on Recharge” — this migration no longer does that
-
“The challenger will out-innovate the incumbent” — the challenger is now a line item in the incumbent's plan
-
“It gives us negotiating leverage at renewal” — both quotes now come from the same finance team
Half the standard business case for this migration survived the acquisition. The half that survived is the technical half.
What we would actually advise, by where you sit
Three starting positions, three different postures. Note that two of the three end in doing very little, which is the correct answer more often than consultants like to admit.
Posture by starting position
Doing nothing is a decision, and here it is usually the correct one. It is just not a decision you should make by accident.
If you are on Recharge
You are on the acquiring platform. Your contract does not change, your support does not change, and your roadmap risk went down rather than up. The one piece of work we would push hard is getting off the legacy checkout and onto SCI if you have not already. That has been the right call since 2023 and the acquisition does not alter it; what it does alter is that you now have a slightly better story to tell your account manager about why they should help you do it.
If you are on Skio
Nothing is changing today, and we have no reason to disbelieve that. Your subscriptions live on Shopify selling plans, which is a genuinely better place for them to live than inside a vendor's private data model, and that remains true whoever owns the app. What we would change is contract shape rather than platform: if you are being offered the 17% annual prepay discount on a long term right now, weigh that discount against the value of being able to leave on ninety days' notice in a year when the product's direction is unstated. For some brands the discount still wins. For most of the ones we have advised, it has not.
If you are on neither
Then your shortlist has quietly shrunk and you should notice. Putting Recharge and Skio side by side in a procurement spreadsheet in 2026 gives you the illusion of two options and the reality of one vendor relationship. Add at least one genuinely independent platform to that comparison, even if you do not pick it, so that your pricing conversation has somewhere else to go.
Who is still independent
These are the platforms we see on real shortlists, all still separately owned at the time of writing. We are not ranking them here — fit depends far more on your subscription mechanics than on any feature grid — but you should know the names.
The loudest migration story
Loop publicly claims 400-plus brands migrated to it from Recharge. That is their number, not ours, but the direction of travel is real and they will happily give you references.
Portal-led
Built around the subscriber account experience and loyalty mechanics. Strong fit if your retention plan is mostly about what happens after the first order.
Churn-prediction first
Positions around predicting and intervening before cancelation. Judge it on whether the interventions are things you would otherwise have built yourself.
Enterprise and multi-channel
The option that turns up when subscriptions have to work beyond Shopify — retail, marketplaces, several storefronts under one program.
The long-standing option
Been in this market a long time and tends to suit merchants who already run other Bold products. Check how much of the estate you would be committing to.
The budget floor
Cheap, capable enough for straightforward recurring orders, and the sensible answer for a brand testing whether subscriptions work at all before committing budget.
Independent as at September 2026. Consolidation of this kind rarely happens once, so verify before you sign anything long.
What leaving actually costs
Any de-risking conversation is worthless until somebody prices the exit. The number that matters is not the platform fee you would save; it is the elapsed time and the churn you take while doing it.
realistic end-to-end migration
Payment-method portability is the whole problem. Moving stored card tokens between vaults means coordinating with processors, and that coordination alone routinely eats four to eight weeks before anybody writes a line of code. Budget a full quarter including a parallel-run period, and expect a measurable churn bump in the fortnight around the cutover regardless of how well you communicate it.
Direction matters too. Leaving Skio is comparatively clean because the subscriptions themselves are Shopify selling plans; a good deal of your state is already in Shopify rather than in the app. Leaving Recharge's legacy checkout is the hardest version of this job, because you are unpicking a checkout, a customer portal and a payment vault at the same time. Recharge on SCI sits between the two.
If any of that sounds familiar it is because it is the same shape of project as a full platform move; our Shopify migration guide covers the sequencing and the communications plan, and most of it transfers directly.
What is genuinely not knowable yet
We would rather be explicit about the gaps than fill them with plausible-sounding speculation. These four are open, and anything you read that closes them is somebody's guess wearing a confident tone.
Convergence or coexistence
One product or two, permanently. Not committed either way, and the two outcomes imply completely different plans for a Skio merchant.
Whether pricing harmonises
Skio's flat 1.0% and Recharge's tiered 1.34–1.49% are hard to run side by side forever. Which way they converge is unannounced.
Long-term API support
Two APIs in two paradigms is expensive to maintain. If you are building deep integrations against either, ask for written deprecation notice periods.
Support and pace
Integrations of this size usually slow shipping somewhere for a couple of quarters. Watch your own ticket response times rather than the press release.
Four open questions. Only the first two would change our advice, and neither has an answer yet.
The honest recommendation
Almost nobody should change platform because of this acquisition. That is a dull conclusion and it is the right one. Platform migrations cost a quarter, carry churn risk, and consume the engineering time that would otherwise go into the flows that actually retain subscribers.
What you should change is your contract posture. Shorter terms while the direction is unstated. Written deprecation notice on any API you build against. A rough exit plan documented before you need it rather than during a crisis. Those cost you an afternoon and a conversation with an account manager, not a quarter of engineering.
And if the acquisition prompted you to go looking at your subscription program for the first time in a while, that instinct is worth following — just point it somewhere else. Look at your failed-payment recovery rate, your cancel-flow save rate, and how many subscribers are quietly skipping their way to a cancelation nobody logged. In our experience those three numbers move revenue considerably more than any choice you make between two apps that now share a parent company.
We work on both platforms and have migrated brands in both directions, which is exactly why we are not selling you a migration here. If you want a straight read on your own situation, that is what our subscription work is for — or just get in touch and describe your setup. We will tell you if the answer is to do nothing, because most of the time it is.