Recharge + Shopify integration

What Recharge is

Recharge is a subscription app for Shopify. It runs subscribe-and-save offers, recurring orders, the customer portal and failed-payment recovery.

How we would approach Recharge with Shopify

Recharge now runs on Shopify Checkout. Stores that still have subscribers on a legacy payment gateway must migrate them, and Recharge says unmigrated recurring orders stop processing after 14 October 2026. We check where your subscribers are, plan the migration, and test renewals, card updates and the customer portal, then look at the subscription offer itself on the product page.

What the work involves

• A check of which subscribers are still on a legacy gateway
• Existing-subscriber migration planned and tested
• Subscription options on product pages that are clear on mobile
• Renewals, card updates, skips and cancellations tested in the portal

Ways to connect Recharge and Shopify

• Existing app

  Recharge Subscriptions

  Recharge's Shopify app, integrated with Shopify Checkout. Subscribers on legacy gateways need the existing-subscriber migration.

• Built in

  Shopify Subscriptions

  Shopify's own subscriptions app, for simpler subscribe-and-save setups.

Where these projects go wrong

• Subscribers on a legacy gateway aren't migrated before the deadline, so their renewals stop.
• The subscribe option is hidden below the fold on mobile, or worded so the discount isn't clear.
• Customer portal actions such as skip, swap or cancel aren't tested after theme changes.
• Failed payments go unrecovered because nobody owns the recovery emails.

Questions

What happens to Recharge subscribers on a legacy gateway after 14 October 2026?

Recharge says recurring orders that haven't been migrated will no longer be processed. Check your Recharge Merchant Portal for subscribers that still need migrating.

Recharge or Shopify Subscriptions?

Shopify Subscriptions covers simple subscribe-and-save. Recharge adds a richer customer portal, bundles, retention tools and analytics, for a fee.

Before we scope the work

• Which data or customer journey needs to connect, and which system owns it?
• What access, plan features or API permissions are available?
• Does an existing connector cover the requirement, including failures and updates?
• Who will maintain the connection, and how will you know it is working?

Send your current setup and one real example of the flow you need. We'll tell you whether it can be done and what it would take.