SUBSCRIPTIONS · INTEGRATIONS · RETENTION · 5 AUGUST 2025 · 8 MIN READ
Subscriptions natively, or with a platform
Every subscription on Shopify runs on the same platform primitives, including the ones a third-party platform sells you. What you are really choosing is the tooling on top.
Start with Shopify’s own Subscriptions app unless you can name the capability it is missing. Shopify provides the subscription machinery at platform level — selling plans, subscription contracts, stored customer payment methods and contract calculation APIs — and every subscription app on the market, first-party or not, is built on those same objects. A third-party platform is not selling you the ability to bill someone monthly. It is selling you the retention tooling, the customer portal and the operational reporting that sit above it. Decide whether you need those, because that is the actual question.
IN SHORT
- Shopify’s subscription primitives are platform features: selling plans, subscription contracts, customer payment methods and subscription contract calculation APIs.
- An app is still required — Shopify’s documentation states that apps must implement selling plans and contracts, admin extensions to surface purchase options, and an app proxy for the customer portal.
- Shopify’s first-party Subscriptions app handles auto-billed weekly, monthly and yearly renewals, multiple plans per product, and skip, pause, resume and cancel from the customer’s account.
- The first-party app has documented boundaries: it is incompatible with bundles, cannot be used with draft orders, and gift cards and Shopify Scripts apply only to the first payment.
- Subscription gateway support is narrower than checkout gateway support, so confirm your payment provider before you design anything.
- Migrating between subscription platforms means moving live payment agreements, which is the expensive part and the reason to choose deliberately the first time.
“Native” means two different things, and the confusion costs money
When someone asks whether to run subscriptions natively, they usually mean “can I avoid paying a subscription platform”. But there are two separate layers underneath that question, and mixing them up is how a store ends up buying a platform it did not need, or building a portal it should have bought.
The lower layer is Shopify itself. Subscriptions are a platform capability: Shopify documents selling plan APIs for delivery, pricing and billing policies, subscription contract APIs for “the agreement between a customer and a merchant over a specific term for recurring purchases”, customer payment method APIs to “store payment methods that can be used to pay for future orders”, and a set of contract calculation APIs that work on a calculate, poll and commit flow. Those objects belong to Shopify. A subscription order is a real Shopify order, against a real contract, charged against a vaulted payment method.
The upper layer is an app, and here is the part that surprises people: you cannot skip it. Shopify’s own documentation is explicit that apps must implement selling plans and subscription contracts to model the functionality, add extensions to surface purchase options in the admin, and use an app proxy to give customers a portal for managing “existing agreements under the shop’s domain”. There is no subscription toggle in settings.
So the choice is never platform versus no platform. It is which app sits on Shopify’s primitives — the first-party one, a third-party one, or something built for you.
What the first-party app gives you
Shopify’s Subscriptions app is free, and it covers the shape of subscription most stores actually sell. Per Shopify’s documentation it creates auto-billed subscriptions that renew weekly, monthly or yearly, supports multiple plans on one product at different frequencies, and handles dollar amount, percentage, buy X get Y and fixed-amount discounts.
On the customer side it gives subscribers the ability to skip, pause, resume and cancel, change their payment method and shipping address, and it sends email notifications about upcoming subscription orders. Merchants get an analytics view of active, paused and cancelled subscriptions.
That list is worth reading slowly, because it is most of what a mid-market replenishment programme needs. Coffee, supplements, pet food, consumables of every kind — a product, a frequency, a discount, and a way for the customer to skip next month. If your requirements fit inside that paragraph, a paid platform is buying you reporting and marketing tooling, not capability.
Where it stops — the documented constraints
These are the limits Shopify publishes for the first-party app, and they are the ones worth checking against your plan before anyone designs a page.
- Gateways are narrower than checkout. Shopify lists Shopify Payments, PayPal Express, Authorize.net, Adyen and Stripe for selected merchants. Not every Adyen payment method supports recurring billing, and with Authorize.net, Shopify notes PayPal is the only wallet option available. Subscriptions on POS require Shopify Payments outright.
- Bundles are incompatible, which rules out the build-a-box pattern in the first-party app.
- Subscriptions cannot be used with draft orders, so a sales-assisted or wholesale-style subscription sign-up is out.
- Gift cards and Shopify Scripts apply only to the first payment, not to subsequent renewals.
- The order editing API is unsupported for subscriptions, which matters if your ops team routinely amends orders after the fact.
- Billing runs the day after the subscription is due, at 10:00 am in the store’s local time. If you have expectations about charge timing across time zones, that is the number to design around.
- The theme must support sections and blocks. On a legacy vintage theme this is a theme project before it is a subscription project.
What a platform is actually selling you
Third-party platforms have had a decade of building on top of subscription primitives, and the good ones are genuinely further along in three areas. None of the three is billing.
Retention mechanics. Cancellation flows with save offers, swap-this-for-that before the next charge, gift a box, one-click reactivation, upsells into the next shipment. This is the strongest honest reason to pay for a platform: it is a lot of interface, it is tuned by people who watch thousands of subscription programmes, and it is the difference between a subscriber who pauses and one who leaves.
Failed payment handling. Cards expire, and every recurring business loses revenue to declines that have nothing to do with intent. Shopify documents automatic card updates with Shopify Payments, particularly in the US, and that covers a real share of the problem. If a configurable retry ladder with its own messaging is something you need, check the current capability of whatever you are considering rather than assuming — this is the feature that moves fastest and the one most often described vaguely in a sales call.
Reporting. Cohort retention, revenue by cohort month, churn reasons captured at cancellation. A subscription business is run on these numbers, and if nobody on your team can produce them, you are running the programme blind regardless of which app bills the card.
And the unglamorous fourth: complex plan logic. Prepaid terms, tiered commitments, delivery calendars that do not fit a weekly or monthly cadence, subscribe-and-save that interacts with your promotions. If your merchandising team already talks in those terms, the first-party app is not where you land.
The switching cost nobody prices at the start
Moving a subscription programme from one app to another is not a data migration. It is moving live payment agreements between systems, and that is the reason to make this choice deliberately rather than starting somewhere cheap and revisiting it later.
The technical side is tractable: Shopify owns the contract and payment method objects, which is exactly why they were built at platform level, and a move between apps that use them properly is a far smaller job than it would have been on a platform that vaulted cards itself. The awkward side is everything around it — the customer portal URL changes, the emails change sender and format, any custom logic somebody wrote against one platform’s API has to be rewritten, and every subscriber is a person who might read a change of billing arrangement as a good moment to cancel.
We would rather see a store start on the first-party app, prove the programme works, and move when it has a named reason, than buy the most featured platform on day one for a subscription range of four SKUs. The features you are paying for are retention tools, and you cannot retain customers you do not have yet.
How we would decide it
Five questions, in this order. The first “no” usually settles it.
- Does your payment provider support recurring billing through the app you are considering? If not, nothing else matters.
- Can you describe every plan you sell as a frequency plus a discount? If yes, the first-party app probably covers it.
- Does anything you sell need bundles, build-a-box, prepaid terms or a delivery calendar? Each one of those is a documented boundary of the free option.
- Who owns retention, and what will they do on a Tuesday? If the answer is “nobody yet”, buying cancellation-flow tooling is buying a tool with no operator.
- What are you going to measure, and can the candidate produce it without an export and a spreadsheet?
The honest position
We build and maintain subscription integrations, including migrations onto Recharge and off it, and the advice we give most often is to spend less than the client expected. A subscription programme fails on merchandising and retention, not on billing infrastructure — the billing has been a solved problem since Shopify moved contracts and payment methods into the platform.
Where the money is genuinely well spent is the bit neither the free app nor the paid one gives you: the customer experience around the subscription. A portal that looks like your store rather than an embedded iframe, a skip flow that does not read as a cancellation prompt, honest emails before a charge lands, and a product page that makes the commitment legible. That work is the same regardless of which app is billing the card, and it is the work that decides whether the programme is worth running.
Questions this raises
Does Shopify support subscriptions natively?
The machinery is native — selling plans, subscription contracts, stored customer payment methods and contract calculation APIs are all Shopify platform features. An app is still required on top: Shopify’s documentation states that apps must implement selling plans and contracts, add admin extensions to surface purchase options, and use an app proxy for the customer portal. Shopify publishes its own free Subscriptions app for this.
Is Shopify’s free Subscriptions app good enough?
For a straightforward replenishment programme, usually yes. It handles weekly, monthly and yearly auto-billed renewals, multiple plans per product, the common discount types, and skip, pause, resume and cancel from the customer’s account. It stops at bundles, draft orders, and renewals that need gift cards or Shopify Scripts applied beyond the first payment.
Which payment gateways work with Shopify subscriptions?
For the first-party app Shopify lists Shopify Payments, PayPal Express, Authorize.net, Adyen and Stripe for selected merchants, and notes that not all Adyen methods support recurring billing. Subscriptions sold through POS require Shopify Payments. Confirm your gateway before designing the programme — subscription support is narrower than checkout support.
What does a subscription platform give you that the free app does not?
Retention tooling — cancellation flows with save offers, product swaps before the next charge, reactivation journeys — plus cohort-level reporting and more elaborate plan logic such as prepaid terms and delivery calendars. It is not billing capability, since both sit on the same Shopify contracts.
How hard is it to move between subscription apps later?
Harder than a normal data migration, because you are moving live payment agreements and everything the subscriber recognises about them. It is much easier than it used to be — Shopify owns the contract and payment method objects — but the portal, the emails and any custom API work all change. Choose deliberately rather than planning to switch.
Can you run a build-a-box subscription on Shopify?
Not through the first-party Subscriptions app, which Shopify documents as incompatible with bundles. Build-a-box needs either a third-party subscription platform that supports it or a custom implementation against Shopify’s selling plan and contract APIs. Price that properly before committing to the merchandising idea.
NEXT STEP
Free store audit
A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritised list of fixes.
