Should You Build or Buy Prepaid & Gift Subscriptions on Shopify?
Buying prepaid and gift subscriptions wins for mid-market Shopify stores: Recharge or Loop Subscriptions ships prepaid billing, gift redemption and dunning in weeks, while a billing-engine build starts at $75K+ (Deploi estimate, illustrative). Shopify's free Subscriptions app covers simple replenishment only. Build solely when a custom subscriber portal already runs your billing. Budget the exit: migrations run $10K–$30K with 2–5% subscriber loss (July 2026 research).
Your profile — see how the verdict shifts
- Confidence
- High — Deep billing-engine scope, no native prepaid or gift coverage, mature app shortlist
- Reference scenario
- $20M–$100M GMV · subscription-led DTC · no existing custom portal
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $2M revenue | BUY | A starter-tier app covers prepaid and gifting for less than any dev retainer; a billing engine is the last thing to build first. |
| $2M – $15M | BUY | Prepaid cash-flow and Q4 gifting revenue arrive this season via an app; a custom build costs more than the capability returns at this scale. |
| $15M – $75M | BUY | SaaS tiers and per-charge fees sting, but dunning, proration and redemption edge cases are still cheaper rented. Negotiate the tier; get export terms in writing. |
| $75M+ | DEPENDS | Transaction-fee math plus an in-house bench can justify a custom stack, and an existing custom portal flips this to BUILD. Re-run the TCC on your own subscriber numbers. |
What Prepaid & gift subscriptions Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Prepaid plans collect 3–12 cycles of revenue at checkout, and gift subscriptions open a Q4 acquisition channel that one-off products never reach. |
| Retention & LTV | High | A prepaid term is commitment by design: a subscriber who paid for six cycles upfront can't churn passively at month two. |
| Revenue — indirect | Medium | Gift recipients are new households acquired at zero ad spend; every smooth redemption seeds a future full-price subscriber. |
| Operational efficiency | Medium | Prepaid cycles cut failed-payment volume: one successful charge replaces months of retries, dunning emails and involuntary-churn recovery work. |
| Data & insight | Medium | Cohort, churn and dunning analytics live inside the subscription platform's dashboard; owning the stack turns billing events into a queryable stream for finance and CRM. |
Spend ceiling: The offer is cheap; the billing engine is expensive. Size spend to offer design and portal UX, and rent the charge-scheduling, dunning and redemption plumbing until fee math forces the question.
What buying enables (top apps)
- + Prepaid discounting, gift purchase and recipient redemption flows live in weeks, in time for Q4
- + Dunning, card-updater and failed-payment recovery run by the vendor from day one
- + A subscriber portal with pause, skip, swap and address-change self-service out of the box
- + An integration ecosystem into email, loyalty and analytics tools without custom glue
What building additionally unlocks
- + Zero per-charge transaction fees: unit economics that improve rather than degrade with subscriber growth
- + Billing logic no app tier gates: hybrid prepaid-plus-usage terms, custom proration, loyalty-linked gifting
- + The full billing event stream as owned data for finance, CRM and churn models
- + A portal indistinguishable from your brand, with no vendor script weight in the storefront
Find Your Verdict in 3 Questions
Is a custom subscription portal already running your billing on Shopify's subscription APIs?
Yes: Your verdict: BUILD — extend the portal with prepaid terms and gift redemption; the scope is bounded.
No: Go to question 2.
Do you need prepaid or gift offers live for the next gifting season?
Yes: Your verdict: BUY — Recharge or Loop Subscriptions ships in weeks; a billing engine takes months.
No: Go to question 3.
Will subscriptions carry a meaningful share of revenue, say 20%+, at your scale?
Yes: Your verdict: BUY — start on an app, negotiate fees, and re-run the build math at each subscriber doubling.
No: Your verdict: BUY — a starter tier covers the offer without touching dev budget; revisit if subscriptions take off.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | An app configures in one to three weeks including selling-plan setup; a custom billing engine runs an estimated 3–6 months (Deploi estimate, illustrative). | ||
| Recurring fees | Subscription platforms charge SaaS tiers plus per-charge transaction fees that scale with subscriber count; the build's recurring cost is upkeep, not a revenue share. | ||
| Maintenance & upgrades | The vendor absorbs dunning tuning, payment-provider changes and Shopify's ~6-month API version cycles (July 2026 research); a custom engine puts that treadmill on your bench. | ||
| Switching & exit | The lock-in row: contracts and payment methods accumulate in-app, and migrations run 60–90 days, $10K–$30K and 2–5% subscriber loss (July 2026 research). A build keeps contracts on Shopify's own objects. | ||
| Risk | |||
| Vendor risk | The category is consolidating: Recharge acquired Skio in April 2026 with consolidation unresolved, and Yotpo shut its subscriptions product in 2025 (July 2026 research). A build has no vendor to lose. | ||
| Security & compliance surface | Payment methods stay vaulted with Shopify either way; an app adds a third party holding subscriber PII, while a build concentrates billing-failure edge cases in your own code. | ||
| Platform-deprecation exposure | Selling plans and subscription contracts are first-class Shopify APIs under both lanes; on the buy side the vendor rides each version bump for you. | ||
| Value | |||
| Fit to requirement | Recharge and Loop Subscriptions cover mainstream prepaid and gifting patterns well; only a build matches genuinely odd terms like hybrid prepaid-plus-usage billing. | ||
| Time to market | Weeks versus months, and gifting revenue is seasonal: miss the Q4 window and the capability waits a year. | ||
| Performance & scale | Mature platforms bill large subscriber bases daily without drama; portal widgets add some script weight, and a custom stack scales exactly as well as your engineering does. | ||
| Data ownership & AI-readiness | Orders and customers sync to Shopify either way, but cohort, churn and dunning analytics live in the vendor's dashboard; a build owns the full billing event stream. | ||
| Focus & opportunity cost | The decisive row: rebuilding a solved billing engine burns quarters of dev capacity that storefront differentiation would repay better. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Recharge | Live — Category leader. Acquired Skio ($105M, closed 2026-04-30, per July 2026 research); consolidation of the two platforms remains unresolved | Plan tiers + per-order fees | Deepest prepaid, gifting and integration ecosystem for subscription-led stores |
| Loop Subscriptions | Live — The strongest independent alternative now that Skio sits inside Recharge | Tiered | Cost-conscious stores wanting portal customization without custom code |
The Build Path
- Full custom: selling plans + subscription contracts: Model prepaid terms as selling plans; your service creates subscription contracts, schedules billing attempts through Shopify's Subscription APIs, and owns dunning, proration and notifications.
- Gift extension on an existing custom portal: The verdict's 'unless': add gift purchase, recipient claim and contract handoff to a portal that already bills correctly. Bounded scope, real payoff.
- Customize the glue (buy + build): Keep the app as the billing engine and build custom portal UI and gift UX on its APIs; most 'we need custom' asks end here, not at a from-scratch engine.
- Effort band
- Full custom engine: $75K+ band; gift or prepaid extension to an existing portal: $25–75K band (Deploi estimate, illustrative)
- Typical timeline
- 3–6 months for a full custom engine; 4–8 weeks for a gift extension to an existing portal (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): dunning tuning, API version bumps about every 6 months, and payment-edge-case fixes. A billing engine is never finished, only current.
- What you own — and what you take on
- You own: the offer design, the portal UX, and on a full build the complete billing event stream. You take on: dunning, proration, gift-redemption edge cases, and a finance-audited system your team can never hand back.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,000–$5,000 (setup + theme integration) | $75,000–$150,000 |
| Years 1–3 (recurring) | $15,000–$45,000 (SaaS + transaction fees) | $34,000–$90,000 (maintenance) |
| 3-year total | ≈$16,000–$50,000 | ≈$109,000–$240,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: mid-tier SaaS plus per-charge transaction fees at a flat subscriber count (real fees scale with growth — conservative for the build case).
- † Build path: full custom selling-plan engine including gift redemption; upkeep at 15–20% of build cost per year; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Per-charge transaction fees scale with subscriber count: the line item grows even in months the SaaS tier doesn't
- — Contracts accumulate in-app from day one; migrating out runs 60–90 days, $10K–$30K in agency cost and 2–5% subscriber loss (July 2026 research — re-verify)
- — Prepaid and gifting features often sit above the entry tier
- — Vendor consolidation is live: Recharge acquired Skio in April 2026 (July 2026 research), so pin your plan terms in writing
On the build path
- — Dunning is the hidden half: failed-payment retries, card-updater flows and pause/skip logic outgrow the first estimate (Deploi estimate: most of the engine)
- — Prepaid accounting means revenue recognition across future cycles plus refund proration; that's finance-team scope, not just code
- — ~15–20% of build cost per year in upkeep (Deploi estimate); a billing engine never goes maintenance-free
- — API versions cycle about every 6 months (July 2026 research), and billing-attempt code sits on that treadmill permanently
What Merchants Say
Migration pain is the loudest subscription-app theme: merchants describe 60–90 day moves, surprise data gaps and subscriber loss when they outgrow a platform.
The recurring 1–2★ shape: gift recipients hitting redemption friction, December support spikes, and per-charge fees that grew faster than the plan tier suggested.
If You Change Your Mind Later
If you bought and outgrow it
Price the exit at signup: subscription migrations run 60–90 days, $10K–$30K in agency cost and 2–5% subscriber loss (July 2026 research — re-verify). Confirm contract-export completeness and payment-method portability on your tier in writing, and keep selling-plan definitions documented outside the vendor's dashboard.
If you built and want out
Retreat stays open: contracts created through Shopify's Subscription APIs live on the platform, so moving to an app later is an import of your own structured data, not a vendor-mercy export. The sunk cost is the engine itself; the subscribers come with you.
When This Answer Changes
We're watching for:
- ▸ Shopify's free Subscriptions app expanding into prepaid terms or gifting (simple replenishment only per July 2026 research)
- ▸ Recharge–Skio consolidation resolving into forced plan or pricing changes (acquisition closed 2026-04-30, July 2026 research)
- ▸ Per-charge fees crossing your build-amortization math: re-run the TCC at each subscriber-count doubling
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Does Shopify support prepaid and gift subscriptions natively?
No. Shopify's free Subscriptions app covers simple replenishment only, per July 2026 research; prepaid multi-cycle terms and gift redemption flows sit outside it. Prepaid and gift selling still runs on Shopify's selling-plan and subscription APIs, so apps like Recharge and Loop Subscriptions supply the billing engine, portal and redemption UX on top of native primitives. Re-verify the native roadmap.
How hard is it to switch subscription apps later?
Switching subscription apps is the category's real cost: community-reported migrations run 60–90 days, $10K–$30K in agency fees and 2–5% subscriber loss (July 2026 research — re-verify). Subscriber contracts and payment methods accumulate inside the vendor's system from day one. Treat the choice as a 5-year decision: confirm contract-export completeness and payment-method portability in writing before signup, not at exit.
When does building a custom subscription stack make sense?
Building makes sense in one case: a custom portal already runs your billing on Shopify's subscription APIs, so prepaid or gift flows arrive as a bounded $25–75K extension (Deploi estimate, illustrative). A from-scratch billing engine lands at $75K+ and 3–6 months (Deploi estimate, illustrative), then carries ~15–20% of build cost per year in upkeep. Buy first; build once subscription economics are proven.
Your Next Steps
If you're going with BUY(matches your selected profile)
- Shortlist Recharge and Loop Subscriptions; demo the gift flow end to end as a recipient, not a buyer
- Verify tier gating: confirm prepaid and gifting sit on the tier you're actually quoted
- Negotiate per-charge fees against your subscriber forecast before signing
- Get contract-export and payment-method portability terms in writing at signup
- Instrument prepaid-to-recurring conversion and gift-redemption rate from day one
If you're going with BUILD
- Audit the existing portal: confirm it creates subscription contracts through Shopify's APIs, not a bolt-on database
- Scope prepaid as selling-plan variants first; add gift purchase and recipient redemption second
- Design the gift handoff explicitly: purchase, recipient claim, address capture, contract start
- Budget dunning and proration as first-class scope; they're the hidden half of a billing engine
- Set a kill criterion: if scope crosses the $75K+ band (Deploi estimate, illustrative), re-price the app path
Official Docs & Sources
- Shopify Subscriptions — Shopify Help Center
- About subscriptions — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy a Build-a-Box Program on Shopify?
Build-a-box pays to build once boxes are a core revenue line at $15M+ revenue; below that, buy a picker and prove the concept.
Should You Build or Buy Product Subscriptions on Shopify?
Product subscriptions are a genuine three-way call: native for simple replenishment, buy for retention depth, build the portal at scale.
Should You Build or Buy a Membership Program on Shopify?
A membership program on Shopify is a customize call: bill the fee on native Subscription APIs and build the entitlement layer that makes the program yours.
Should You Build or Buy Digital Subscriptions on Shopify?
Building digital subscriptions wins for mid-market Shopify stores selling gated content: entitlement is the product, and no delivery app ships yours.
Should You Build or Buy a Points Program on Shopify?
Buying a points program wins for Shopify brands under roughly $50M in revenue; the liability math and vendor ecosystems beat building.
Ready to pick the right subscription platform?
We'll pressure-test Recharge and Loop Subscriptions against your subscriber math, verify tier gating and fee structure, confirm export terms before you sign, and wire the integration. Prefer to watch? Ask for the verdict-change alert.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing is re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.