Should You Build or Buy SMS Marketing on Shopify?
SMS marketing on Shopify is a buy at every revenue band: carrier registration, deliverability reputation, and consent liability that prices at $500–$1,500 per unwanted text (statutory range; verify) make in-house sending a non-starter. The real decision is narrower than build-vs-buy: the SMS module inside the email platform you already run, or a standalone platform like Attentive or Postscript once SMS gets a dedicated owner. Either way, per-message fees grow with every subscriber you add.
Your profile — see how the verdict shifts
- Confidence
- High — No native baseline, the hub's lowest buildability (carrier, deliverability, and compliance infrastructure), three mature platforms; per-message economics and lock-in are the real costs and the scorecard prices both
- Reference scenario
- $20M–$100M GMV · US-first audience · email platform already live
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $2M revenue | BUY | If Klaviyo already runs your email, its SMS module is the whole decision: consent, segments, and flows live where email already does, and you pay by message credits rather than for a second platform. A standalone vendor is a bill you don't need yet. |
| $2M – $15M | BUY | Module-first still wins: one consent store, one flow builder, shared suppression. Go standalone once SMS has its own owner and revenue target; until then the premium buys tooling nobody drives. |
| $15M – $75M | BUY | The standalone platforms earn their premium here: list-growth units, deliverability tooling, two-way conversations, and per-message rates worth negotiating. Re-run the module-vs-standalone math at every renewal, because the message line now moves real money. |
| $75M+ | CUSTOMIZE | Buy the platform and build the glue: consent captured in your own theme components, server-side event streams, opt-outs synced to customer records and your warehouse. The sending itself is never yours to build, at any scale. |
What SMS marketing Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Abandoned-checkout and back-in-stock texts land inside the buying moment, minutes after the signal, which is timing email can't match. |
| Retention & LTV | High | A consented list is a repeat-purchase channel with no algorithm between you and the buyer; replenishment reminders and drop alerts do the compounding. |
| Customer experience | Medium | Intimacy cuts both ways: a well-timed restock text feels like service, and one careless late-night campaign burns the opt-in for good. |
| Data & insight | Medium | Consent records and per-number engagement enrich customer profiles, but the history accrues inside the platform unless you pipe it to your warehouse. |
| Operational efficiency | Low | Two-way texting deflects some where-is-my-order volume, though it's a marketing channel with service side effects, not a support desk. |
Spend ceiling: Anchor spend to revenue per message, not list size: SMS is the rare channel with a hard unit cost on every send, so it either pays its way visibly or shouldn't scale. When the standalone premium stops buying measurable lift over the module, that's the ceiling.
What buying enables (top apps)
- + First compliant campaign inside a week on registered, carrier-trusted sending infrastructure
- + Consent records, quiet-hours enforcement, HELP/STOP handling, and audit trails maintained by the vendor
- + List-growth units, abandoned-checkout flows, and two-way conversations tuned across thousands of stores
- + Per-campaign revenue attribution that keeps the per-message math honest
What building additionally unlocks
- + Consent capture built into your own theme components, placed and styled by your conversion data instead of a vendor popup
- + Engagement and consent history streamed to your warehouse, so channel learning survives any future platform migration
- + Server-side events feeding segments your data model defines (margin, inventory position, predicted LTV), beyond the stock integration's events
Find Your Verdict in 3 Questions
Does the email platform you already run include an SMS module, like Klaviyo SMS?
Yes: Your verdict: BUY — turn the module on first. One consent store, one flow builder, one bill; go standalone only when SMS outgrows it.
No: Go to question 2.
Will SMS be a headline channel, with a dedicated owner, a list-growth target, and campaign cadence to match email?
Yes: Your verdict: BUY — shortlist Attentive and Postscript, and negotiate per-message rates before you sign.
No: Go to question 3.
Have you priced the program end to end, including per-message fees, carrier surcharges, and the compliance duties of consent, quiet hours, and opt-outs?
Yes: Your verdict: BUY — start on the smallest tier or module plan, single market, and let revenue per message set the growth rate.
No: Your verdict: WAIT — price it first. SMS bills by the send, so a list you can't afford to message is a liability; the math takes an afternoon.
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 | A platform sends inside a week; an in-house stack means carrier agreements, 10DLC or short-code registration, and compliance review before message one, an estimated 6–12 months out (Deploi estimate, illustrative). | ||
| Recurring fees | Nobody escapes per-message carrier fees: the platform adds subscription and markup, but an in-house stack still pays an aggregator per send, and both bills scale with list size. | ||
| Maintenance & upgrades | Vendors absorb carrier-rule churn, filtering changes, and compliance updates as their core business; a build carries all three plus ~15–20% of build cost per year in upkeep (Deploi estimate). | ||
| Switching & exit | Subscribers and consent records port between platforms; flows, engagement history, and short codes move badly, which the 2025 Yotpo SMS shutdown demonstrated at scale (July 2026 research). | ||
| Risk | |||
| Vendor risk | Yotpo shut its SMS product in 2025 and forced a migration wave (July 2026 research); the remaining platforms are category leaders, but consolidation is live. A build trades platform risk for aggregator dependence. | ||
| Security & compliance surface | The decisive risk row: consent records, quiet hours, and opt-out handling are legal duties with statutory damages of $500–$1,500 per text (verify); platforms automate the mechanics, while an in-house stack makes every mistake yours. | ||
| Platform-deprecation exposure | SMS platforms sit mostly outside Shopify's deprecation cycles; the churn that matters is carrier-side registration and filtering rules, which vendors track full-time and an in-house team tracks on the side. | ||
| Value | |||
| Fit to requirement | Attentive, Postscript, and Klaviyo SMS ship flows, campaigns, list-growth units, and two-way replies on day one; a first-party build starts years behind at delivering the same bytes. | ||
| Time to market | First campaign inside a week versus quarters of registration and warm-up; every unlaunched month is abandoned-checkout revenue the channel never recovers. | ||
| Performance & scale | Deliverability is the performance metric, and it's earned: registered senders, carrier relationships, and filtering reputation are what the subscription actually buys. New in-house senders get throttled and filtered first. | ||
| Data ownership & AI-readiness | The one row a build wins, and it's not enough: consent belongs to your brand under either path, so the ownable delta is engagement history, which the customize glue captures for a fraction of a build. | ||
| Focus & opportunity cost | Carrier plumbing is commodity infrastructure with zero brand differentiation; two quarters spent re-deriving it is storefront roadmap you never ship. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Attentive | Live — The SMS-first enterprise leader; conversational two-way tooling and aggressive list-growth units | Quote-based subscription plus per-message fees, typically a $300–$2,000+/mo band at mid-market scale (illustrative) | Brands committing to SMS as a headline channel with a dedicated owner |
| Postscript | Live — SMS-first; pairs with an email platform rather than replacing one | Message-volume-tiered | Shopify-first DTC brands that want SMS built on Shopify's data model |
| Klaviyo SMS | Live — The SMS module inside the email platform most mid-market Shopify stores already run | Message-credit bundles on top of your email plan, roughly a $15–$150/mo band at starter volumes (illustrative) | Module-first starts: one consent store, shared segments, and no second vendor until SMS earns it |
The Build Path
- In-house sending stack (priced for honesty, not recommended): An aggregator account, 10DLC or short-code registration, a consent database, quiet-hours scheduling, HELP/STOP automation, and flow tooling. It re-derives a commodity platform, still pays per-message fees, and makes carrier compliance your pager.
- Customize lane: platform plus first-party glue: Keep Attentive, Postscript, or Klaviyo SMS as the sending and compliance engine; build consent capture into your theme, stream server-side events into platform segments, and sync opt-outs to customer records and your warehouse.
- Effort band
- In-house stack: an estimated $100,000–$250,000 before the first compliant campaign (Deploi estimate, illustrative), beyond the $75K+ contact-form band. Customize glue: the $10–25K band (Deploi estimate, illustrative).
- Typical timeline
- In-house stack: an estimated 6–12 months including carrier registration and compliance review (Deploi estimate, illustrative). Customize glue: 2–4 weeks (Deploi estimate, illustrative).
- Maintenance, honestly
- An in-house stack would carry ~15–20% of build cost per year in upkeep (Deploi estimate) plus carrier-rule churn, filtering-reputation management, and compliance monitoring with legal stakes. The customize lane's upkeep is small: API version bumps roughly every 6 months (July 2026 research) and consent-flow QA at theme updates.
- What you own — and what you take on
- You own the part that matters under either lane: subscriber consent belongs to your brand, not the platform, and it exports. The glue adds owned event streams and warehouse-side engagement history. What you never want to own: carrier relationships, filtering reputation, and per-message legal exposure.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $1,000–$5,000 (onboarding, consent units, list warm-up) | $100,000–$250,000 (stack, registration, compliance tooling) |
| Years 1–3 (recurring) | $36,000–$150,000 (subscription + per-message fees) | $80,000–$180,000 (upkeep + the same per-message carrier fees) |
| 3-year total | ≈$37,000–$155,000 | ≈$180,000–$430,000 (and still behind on features) |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: mid-band standalone-platform subscription plus per-message fees at a steady send cadence, held flat (real lists grow, and the message line grows with them).
- † Build path: in-house sending stack including carrier registration and compliance tooling; the customize glue lane is additive to a platform subscription and isn't charted.
What the Sticker Price Hides
On the buy path
- — Per-message fees compound: list growth and cost growth are the same curve, so the channel's success raises its own bill every month
- — Carrier surcharges and short-code fees pass through beneath the subscription line, so invoices run above the plan-page number
- — Running a standalone SMS platform beside your email platform means two popups and two consent stores, and double-messaging unless suppression is wired both ways
- — The subscriber list exports; the engagement history and flow logic mostly don't, which is the lock-in the 2025 Yotpo SMS shutdown exposed (July 2026 research)
On the build path
- — Compliance is the product: consent capture, quiet hours by recipient time zone, and instant opt-out handling are legal duties, with statutory damages of $500–$1,500 per text (verify)
- — Carrier filtering treats new senders as suspects; deliverability reputation takes months to earn and one bad campaign to lose
- — An in-house stack still pays per-message aggregator fees, so the build never kills the recurring line it was meant to kill
- — 10DLC and short-code registration are reviewed, gatekept processes measured in weeks, not endpoints you call
What Merchants Say
The migration-wave theme after Yotpo shut its SMS product in 2025: brands discovering mid-move that the list and consent port cleanly while flows, engagement history, and the short code do not.
The recurring billing complaint shape: the plan price reads fine, then carrier surcharges and a big campaign month land on the invoice, and per-message math nobody modeled becomes a finance question.
If You Change Your Mind Later
If you bought and outgrow it
Subscriber lists and consent records export and legally belong to your brand, so a platform switch is workable; plan for the parts that don't move: flow logic rebuilds, engagement history resets, and a dedicated short code takes a carrier-mediated transfer. The 2025 Yotpo SMS shutdown turned this into a rehearsed playbook (July 2026 research); still, re-read export terms at every renewal, not at exit.
If you built and want out
Retreat is clean in data terms, because consent and subscriber records import into any major platform; what's sunk is the registration slog, the carrier setup, and a six-figure stack (Deploi estimate, illustrative) that no future buyer of your brand will value. That asymmetry is this page compressed: the exit from buying is a migration, while the exit from building is a write-off.
When This Answer Changes
We're watching for:
- ▸ Shopify shipping a native SMS marketing channel (none as of July 2026 research)
- ▸ Category consolidation continuing after Yotpo shut its SMS product in 2025; re-check vendor health and export terms at every renewal (July 2026 research)
- ▸ RCS displacing SMS for commerce messaging, which changes pricing and consent mechanics; platform support will move first
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Should you use Klaviyo SMS or a standalone SMS platform?
Start with the module if Klaviyo already runs your email: one consent store, shared segments, one flow builder, one bill. Move to Attentive or Postscript when SMS has a dedicated owner, a real list-growth target, and enough volume to negotiate per-message rates. Subscribers and consent port when you switch, so module-first isn't a trap; it's the cheap way to learn whether SMS fits your brand.
Why shouldn't we build SMS marketing in-house?
Because the hard part isn't software. Sending at commercial volume requires carrier registration, a deliverability reputation you earn over months, and compliance infrastructure for consent, quiet hours, and opt-outs, where mistakes carry statutory damages of $500–$1,500 per text (verify). And a build still pays per-message aggregator fees, so it never removes the recurring cost. Custom work belongs at the edges: consent capture, event streams, and warehouse sync.
What does SMS compliance require from a Shopify store?
Documented opt-in consent before the first message, sender identification, quiet hours respected in each recipient's local time, and instant handling of HELP and STOP keywords. Your platform automates the mechanics and keeps the audit trail, but consent-capture wording, send timing, and campaign cadence stay your calls, which is why compliance shows up in this scorecard as a risk you manage rather than one you outsource completely.
Your Next Steps
If you're going with BUY(matches your selected profile)
- Check whether your email platform already includes an SMS module; if it's Klaviyo, price that path first
- Shortlist Attentive and Postscript only once SMS gets a dedicated owner and a revenue target
- Wire suppression both ways so email and SMS never hit the same customer in the same moment
- Set consent capture, quiet hours, and cadence rules before the first campaign, not after the first complaint
- Report revenue per message monthly; it's the number that decides tiers, cadence, and renewal
If you're going with CUSTOMIZE
- Keep the platform as the sending and compliance engine; never rebuild carrier plumbing
- Move consent capture into your own theme components and A/B the placement against the vendor popup
- Stream server-side events into the platform so segments reflect your full data model, not just the stock integration
- Sync opt-outs and consent changes to customer records and your warehouse on every update
- Budget the glue in the $10–25K contact-form band (Deploi estimate, illustrative)
Official Docs & Sources
- Managing customer privacy settings — Shopify Help Center
- Shopify Flow — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Postscript vs. Attentive: Which SMS Platform Fits Shopify?
Postscript wins the mid-market SMS head-to-head with published tiers; Attentive earns its quote past roughly 100,000 engaged subscribers.
Klaviyo vs. Postscript: Email-First or SMS-First on Shopify?
Klaviyo wins while SMS supports email; Postscript wins when SMS runs as a headline channel. The hidden lane: no SMS spend at all.
Attentive vs. Postscript: Which SMS Lane Fits Your Scale?
Attentive earns its quote once SMS is a headline channel at negotiated scale; Postscript-class self-serve tiers cover most mid-market programs.
Postscript vs. No SMS at All: Does Texting Earn Its Keep?
Postscript is a buy only when your motion needs the interrupt: drops, restocks, reorders. With no native SMS, the honest alternative is email and push.
Should You Build or Buy Abandoned Checkout Recovery on Shopify?
Abandoned checkout recovery belongs in the email/SMS platform you already pay for, with an audited tracking layer underneath.
Ready to pick your SMS lane?
We'll run the module-vs-standalone math against your list, cadence, and margins, wire consent capture and cross-channel suppression correctly, and keep revenue per message on one honest dashboard. And if this verdict ever moves, 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 status and gets re-verified. 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.