Should You Build or Buy a Points Program on Shopify?
Buying a points program wins for Shopify brands under roughly $50M in revenue: a points ledger is a balance-sheet liability with fraud and expiry rules attached, and vendors like Smile.io (Plus plans from $999/mo, per July 2026 research) amortize that machinery plus a deep integration ecosystem across thousands of stores. Building means owning liability math for one store's benefit. Go custom only when loyalty is the business model itself.
Your profile — see how the verdict shifts
- Confidence
- High — Liability accounting, fraud surface, and vendor integration ecosystems all favor renting; the build case needs loyalty to be the business model
- Reference scenario
- $20M–$50M GMV · DTC repeat-purchase brand · single storefront
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $5M revenue | BUY | Start on an entry tier and spend your energy on program design, not software; a build at this scale is out of the question, and the fee stays small against any real repeat-purchase gain. |
| $5M – $50M | BUY | The heart of the case: vendors amortize liability machinery, fraud controls, and an integration ecosystem across thousands of stores, and no plausible subscription fee beats rebuilding all of that for one storefront. |
| $50M – $150M | CUSTOMIZE | Negotiate enterprise pricing and build your own presentation layer on the vendor's APIs; you get native-feeling UX while the ledger, and the liability math behind it, stay the vendor's problem. |
| $150M+ | DEPENDS | Model both honestly: member-based pricing at this scale is real money, but a custom engine only wins when loyalty is the business model, with partner accrual, omnichannel wallets, or mechanics no vendor ships. |
What Points program Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Retention & LTV | High | Points give members a reason to consolidate purchases with you: they redeem, return, and re-earn, while tier status raises the cost of defecting to a competitor. |
| Revenue — direct | Medium | Expiry nudges and redemption deadlines pull forward orders that would otherwise drift, and dormant-balance win-back campaigns reactivate lapsed buyers with an offer already funded. |
| Revenue — indirect | Medium | Referral rewards turn members into an acquisition channel whose cost per order you denominate in points and margin instead of rising ad dollars. |
| Data & insight | Medium | Earn and redeem events reveal each member's price sensitivity and engagement cadence, sharpening LTV segments beyond what order history alone shows. |
| Customer experience | Medium | A visible balance and tier progress make repeat buying feel like accumulation rather than repetition, provided the widget behaves at checkout and theme breakpoints. |
| Operational efficiency | Low | Honest negative: a program adds liability reporting, fraud review, and missing-points support tickets, whoever runs the engine. |
Spend ceiling: Size the spend to your repeat-purchase economics, not the software: if second orders are rare in your category, no points engine, bought or built, will invent them. For most mid-market brands the right ceiling is a vendor fee that stays immaterial against the margin the program retains.
What buying enables (top apps)
- + Live in weeks: earning rules, tiers, referrals, VIP thresholds, expiry, and win-back automations that took vendors a decade to harden
- + An integration ecosystem on day one: email events, review-app points, helpdesk balance lookups, POS accrual
- + Fraud controls and liability reporting your finance team can close the books against
- + Checkout and account surfaces the vendor keeps current as Shopify's extension APIs move
What building additionally unlocks
- + Mechanics no vendor ships: partner-brand accrual, cash-back wallets, streaks tied to your replenishment cycle
- + One stored-value balance unifying points, store credit, and gift cards instead of three parallel systems
- + Flat economics at very large member counts, where per-member pricing finally hurts
- + The ledger as a first-class input to your own LTV and personalization models, with no API rate ceilings
Find Your Verdict in 3 Questions
Does your program need mechanics no vendor ships, like partner accrual, omnichannel wallets, or loyalty as the business model itself?
Yes: Your verdict: BUILD — unusual economics justify owning the engine; scope it like the financial system it is.
No: Go to question 2.
Are you under roughly $50M in revenue?
Yes: Your verdict: BUY — vendor liability machinery, fraud controls, and integrations beat any build at this scale.
No: Go to question 3.
Is the stock widget fighting your brand, theme, or checkout?
Yes: Your verdict: CUSTOMIZE — keep the vendor ledger and build your own presentation layer on its APIs.
No: Your verdict: BUY — negotiate enterprise pricing; the ledger stays the vendor's problem.
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 is live in weeks including program design; a credible custom engine needs an estimated 4–6 months before the first point is safely earned (Deploi estimate, illustrative). | ||
| Recurring fees | Loyalty pricing scales with orders or members: LoyaltyLion from ~$399/mo, Smile.io Plus plans from $999/mo (per July 2026 research); a build swaps the climbing subscription for hosting plus upkeep. | ||
| Maintenance & upgrades | Vendors absorb checkout-extension churn, integration upkeep, and API version bumps; a custom engine carries ~15–20% of build cost per year (Deploi estimate) and every platform shift lands on you. | ||
| Switching & exit | Outstanding balances are the hostage: moving points between systems is an accounting event as much as a data export, and members notice every rounding decision. | ||
| Risk | |||
| Vendor risk | The category consolidates and suites prune, as when Yotpo shut its SMS, Email, and Subscriptions products in 2025; the loyalty majors look stable, but pricing power sits with them. | ||
| Security & compliance surface | A vendor holds member PII, which is real exposure; build it and points fraud, referral abuse, and the auditable liability trail your finance team signs all become your code. Unusually for this scorecard, buying narrows the surface. | ||
| Platform-deprecation exposure | Major vendors already rebuilt on Checkout UI extensions after Scripts stopped executing in June 2026 (per July 2026 research); a custom engine tracks every such shift itself, and checkout visibility quirks are community-reported either way. | ||
| Value | |||
| Fit to requirement | Mature apps cover earning rules, tiers, referrals, VIP thresholds, and win-back out of the box; a build only pulls ahead on mechanics no vendor ships, like partner accrual or a unified stored-value wallet. | ||
| Time to market | Weeks versus an estimated 4–6 months, and a loyalty program earns nothing until members can actually redeem (Deploi estimate, illustrative). | ||
| Performance & scale | Widget scripts add page weight and can misbehave at theme breakpoints (community-reported); a build renders with the theme, though the vendor's infrastructure absorbs Black Friday redemption spikes you'd otherwise load-test yourself. | ||
| Data ownership & AI-readiness | An owned ledger feeds LTV models and personalization with no export ceiling; the majors do expose balances and events via API, which narrows, without closing, the gap. | ||
| Focus & opportunity cost | The decisive dimension: months of senior engineering plus a permanent accounting responsibility, spent rebuilding what a subscription already rents, is the classic misallocation for a sub-$50M brand. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Smile.io | Live — Category leader with the widest integration catalog | Plus plans from $999/mo (per July 2026 research; re-verify); lower tiers exist, verify current pricing | Full-ecosystem programs that want points, referrals, and VIP tiers wired into email, reviews, and support on day one |
| LoyaltyLion | Live — Established mid-market alternative with strong email coupling | From ~$399/mo (per July 2026 research; re-verify) | Tier-and-voucher programs with heavy Klaviyo flows |
| Yotpo Loyalty | Live — Yotpo shut its SMS, Email, and Subscriptions products in 2025; weigh suite-pruning risk before committing a points ledger to any suite | Quote-based; verify | Brands already deep in Yotpo Reviews who want one vendor, eyes open |
The Build Path
- Vendor engine + custom presentation layer (the CUSTOMIZE lane): Keep Smile.io or LoyaltyLion as the ledger of record and replace stock widgets with your own account-area UX and Checkout UI extensions on their APIs; the vendor carries liability math while the program looks native to your theme.
- Custom loyalty engine + customer accounts: An append-only points ledger keyed to Shopify customer IDs: earn webhooks on orders, redemption via discounts or store credit, fraud rules, expiry jobs, and an accounting export for breakage and liability reporting. Scope it like the financial system it is.
- Store-credit-based lightweight program: Skip points entirely: issue native Shopify store credit on qualifying orders via Flow or API (API issuance gated by plan tier, per July 2026 research). Not a real points program, but it tests repeat-purchase appetite before you commit to one.
- Effort band
- $75,000+ for a credible custom engine (Deploi estimate, illustrative); lands in the $75K+ contact-form band. The CUSTOMIZE glue lane typically lands in the $25–75K band (Deploi estimate, illustrative).
- Typical timeline
- 4–6 months to a safely-earned first point for a full engine; 6–10 weeks for the CUSTOMIZE presentation layer (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): fraud-rule tuning, checkout-extension API tracking, liability-report upkeep, and the integration maintenance a vendor would otherwise absorb. This line never goes away.
- What you own — and what you take on
- You own: the ledger, the member data, the program mechanics, and the accounting logic. You take on: points fraud, breakage estimation, a balance your finance team signs off every quarter, and every platform shift Shopify ships.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $2,000–$8,000 (program design + integrations) | $75,000–$150,000 |
| Years 1–3 (recurring) | $14,400–$36,000 (subscription) | $34,000–$90,000 (maintenance) |
| 3-year total | ≈$16,400–$44,000 | ≈$109,000–$240,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: mid-band between LoyaltyLion entry and Smile.io Plus pricing, held flat for three years even though most programs grow into higher tiers.
- † Build path: full custom engine at credible scope plus 15–20% annual upkeep; the CUSTOMIZE glue lane would land between the two lines.
What the Sticker Price Hides
On the buy path
- — Order-volume and member-based pricing climbs with growth; the tier you sign is not the tier you'll pay in year three
- — Outstanding points sit in the vendor's system; migrating balances later is an accounting event, not just an export
- — Widget-style loyalty UI can break at theme updates and breakpoints (community-reported pattern)
- — Checkout-extension visibility quirks can hide redemption at the exact moment it matters (community-reported); test your own checkout, don't assume
On the build path
- — The ledger is a financial system: breakage estimation, liability reporting, and audit trails are scope most builds discover late
- — Points fraud and referral abuse arrive with success, and every fraud rule is yours to write and tune
- — ~15–20% of build cost per year in upkeep (Deploi estimate), including tracking Shopify's checkout-extension APIs
- — Integration parity is a treadmill: every email event, helpdesk lookup, and review-app hook the vendors bundle, you rebuild
What Merchants Say
Loyalty-app complaint threads cluster on two things: pricing-tier jumps after growth, and redemption widgets misbehaving at checkout, exactly where member trust is on the line.
The recurring 1–2★ review shape for points apps: support can't explain a member's missing points, and the merchant eats the goodwill cost either way.
If You Change Your Mind Later
If you bought and outgrow it
Check the exit at signup, not at exit: confirm your tier exports member balances and earn history, and treat outstanding points as the migration's real risk, because moving them is an accounting event with member-visible rounding decisions. Brands migrate loyalty apps successfully all the time; the cost is a re-onboarding campaign and a support spike, not stranded data, if exports were verified up front.
If you built and want out
Retreating from a custom engine to an app means mapping your ledger into the vendor's earn model and writing off mechanics it doesn't support. Your data ports cleanly because you own it; your program design may not survive contact with the vendor's feature set. Budget a migration project plus member communications, and expect simplification, not parity.
When This Answer Changes
We're watching for:
- ▸ Shopify shipping a native points or loyalty primitive; store credit is the nearest adjacent building block (none as of July 2026 research)
- ▸ Further loyalty-vendor consolidation or suite pruning, as when Yotpo shut its SMS, Email, and Subscriptions products in 2025
- ▸ Checkout-extension API changes that alter what loyalty widgets can render at checkout (visibility quirks are community-reported; per July 2026 research)
Verdict change log:
No changes since first publication (August 2026).
Common Questions
How much does a Shopify loyalty app cost?
Verified anchors: LoyaltyLion starts around $399/mo and Smile.io Plus plans start at $999/mo (per July 2026 research; re-verify current pricing). Entry tiers below those exist across the category. Pricing typically scales with order volume or member count, so model the tier you'll be on after a year of growth, not the one you'd sign today. Against gross margin on repeat orders, most brands find the fee immaterial.
Why is building a points program harder than it looks?
Because a points ledger is a financial system, not a feature. Outstanding points are a balance-sheet liability, so you inherit breakage estimation, expiry rules, fraud review, and an auditable trail your finance team signs. Add the integration treadmill (email events, helpdesk lookups, POS accrual) and a credible engine is an estimated 4–6 months plus permanent upkeep (Deploi estimate, illustrative). Vendors amortize all of that across thousands of stores.
Can I customize a loyalty app instead of building from scratch?
Yes, and it's the best lane for brands whose objection is the widget, not the vendor. Keep Smile.io or LoyaltyLion as the ledger of record and build your own account-area UX and checkout surfaces on their APIs. You get native-feeling presentation while the vendor keeps carrying liability math, fraud controls, and integrations. Typical glue scope lands in the $25–75K contact-form band (Deploi estimate, illustrative).
Your Next Steps
If you're going with BUY(matches your selected profile)
- Model repeat-purchase economics first: program ROI lives in second-order rate and contribution margin, not in software choice
- Shortlist two vendors and price the tier you'll be on after a year of growth, not today's order volume
- Verify balance and history exports on your tier before signing; it's your future migration insurance
- Test redemption in your real checkout across devices; extension visibility quirks are community-reported
- Wire loyalty events into your email flows in week one, because unintegrated points programs stall
If you're going with CUSTOMIZE
- Confirm the vendor's API covers balance reads, adjustments, and redemption before scoping custom UX
- Rebuild the account-area loyalty page first; it's the highest-traffic surface and the stock widget's weakest
- Move checkout surfaces onto sanctioned Checkout UI extensions and test visibility across devices and payment paths
- Treat the vendor as ledger of record; never cache balances in ways that can drift
- Re-run the build-vs-buy math at each pricing renewal; the glue layer you built ports across vendors
Official Docs & Sources
- Store credit — Shopify Help Center
- About discounts — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Smile.io vs. LoyaltyLion: Which Points Program Pays?
LoyaltyLion wins the mid-market fee math at less than half Smile.io's Plus-plan anchor; Smile.io wins below Plus scale. The custom lane caps fees past ~$50M.
LoyaltyLion vs. a Custom Points Build: Which Pays Off?
Buying LoyaltyLion wins for most mid-market stores: managed loyalty from ~$399/mo (July 2026 research) beats a $40K+ build until mechanics or fees flip it.
Smile.io vs. a Custom Loyalty Build on Shopify: Which Wins?
Smile.io beats a custom loyalty build for most mid-market Shopify programs; the store-credit build lane wins on fee math at scale and owned member data.
Should You Build or Buy Store-Credit Rewards on Shopify?
Store-credit rewards belong on Shopify's native ledger: customize the earn rules instead of renting a parallel wallet.
Should You Build or Buy a Referral Program on Shopify?
A referral program on Shopify is a buy you may already own: loyalty suites bundle it, and fraud policing is most of what the subscription buys.
Ready to pick the right loyalty stack?
We'll help you shortlist the vendor whose pricing curve fits your growth, wire it into your email and support stack, and keep the widget from fighting your theme. And if the math ever flips toward building, you'll hear it from us first.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets 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.