Shopify SMS App Pricing: 13 Tools Compared

Margin math: a worked example

"Attributed revenue" is the number SMS platforms report; contribution margin is the number that pays for the app. Walk the math before committing to any plan. Take a recovered cart: $120 AOV at 55% gross margin gives $66 of gross profit. A 15% recovery discount costs $18. A three-touch flow averages 6 delivered segments at $0.03 plus a $0.08 carrier surcharge per message — call it $0.26 per recovered order in messaging. Subtract a platform allocation of $0.50 per order at mid-tier volume and the flow contributes about $47 per incremental order.

Now stress it. Move the discount to 25% and contribution drops near $33. Switch one touch to MMS at 3–5× the per-message cost and shave another $1–2. Add a 1.5-point opt-out bump from doubling frequency and you have taxed every future flow's audience. The stack that looks cheapest per message is rarely the one that leaves the most margin once discount depth and opt-out cost are priced in.

Track four numbers per flow, weekly: cost per delivered message (platform plus carrier plus MMS), discount cost per incremental order, opt-outs per 100 delivered messages, and the 90-day repeat rate of the recovered cohort. Keep a holdout group wherever the platform allows it so "attributed" never substitutes for "incremental."

Where app costs actually hide

• Overage tiers. A plan that prices "up to 5,000 messages" bills the next tier the day a strong campaign crosses the line — model 2× your expected volume.
• MMS premiums. Image and GIF messages commonly cost 3–5× per-message SMS. A "cheap" plan with MMS-heavy creative can invert the math.
• Carrier surcharges and number fees. Toll-free or short-code verification, long-code provisioning, and per-carrier pass-throughs are often quoted separately.
• Contact or profile growth. Contact-based billing charges churned and dormant profiles until segments are cleaned. Usage-based billing charges attempts, not just deliveries — ask which.
• Seats and premium integrations. Reporting access, review/loyalty data sync, and dedicated IP setup can be add-ons rather than plan features.
• Onboarding and exit terms. Enterprise contracts may include implementation minimums, data-retention fees, and cancellation notice windows. Get them in writing.

Plan names, tiers, and per-message rates change frequently, and vendors do not always surface overage or surcharge terms on public pricing pages. Treat every figure on this page — including ours — as a buying-model note, not a quote, and check each tool's official pricing page for current terms. Request a written twelve-month estimate at your real send mix before forecasting.

Decision table: which pricing model fits which store

Pricing deep-dive by model

Usage-based messaging

You pay per segment sent or delivered, usually plus a carrier pass-through and a platform floor. The model scales down gracefully and matches cost to activity, which is why most SMS-native tools use it. The risk is campaign success: a BFCM broadcast to a large list can produce a one-month bill larger than the previous quarter. Ask each vendor to quote your actual mix — average segments per message, MMS share, monthly volume, and peak-month volume — and confirm whether undelivered messages still bill.

Contact- or profile-based

You pay for stored contacts or active profiles, with messaging bundled or metered. The bill is predictable, which finance teams like, but dormant records cost the same as engaged ones until someone prunes. Profile hygiene becomes a paid discipline: dedupe identities, sunset non-engagers, and watch how the platform counts a "profile" across email and SMS. Model the bill at 2× current list size, not current size.

Custom enterprise contracts

Platform minimums, negotiated message rates, managed services, and term commitments. This model buys expertise and volume economics, and it also raises the cost of a wrong fit: onboarding fees, multi-month minimums, and notice periods make an exit expensive. Ask for carrier fees, onboarding costs, support scope, and cancellation terms in writing, and treat any case-study revenue claim as directional rather than guaranteed.

Negotiation checklist: questions that change the invoice

• Do undelivered or attempted messages bill, or only delivered ones?
• What are the per-message and MMS rates at my peak-month volume, including carrier surcharges?
• What happens when I cross a tier mid-campaign — prorated or full next tier?
• How are profiles counted across email and SMS, and what cleans a dormant profile?
• Which integrations, seats, and reporting views cost extra?
• What are onboarding, migration, and data-export fees — in and out?
• What is the cancellation notice period, and is there a term minimum?

Get every answer in writing and file it with the quote. When two finalists are close, run the same four-flow pilot in both and let the measured contribution margin — not the sales deck — settle it.

Seasonality and the twelve-month view

SMS programs are seasonal, and pricing rarely is. A store that sends 20% of its annual messages in November pays either a usage-based bill that spikes with the success it wanted, or a contact-based plan sized for a peak it reaches one month a year. Neither is wrong — but model the year, not the month. Pull your last twelve months of sends and orders, apply each vendor's model at that shape, and include the peak month explicitly rather than averaging it away.

Seasonality also changes discount pressure. Peak-season campaigns often need deeper offers to convert, which is exactly when per-message volume is highest; the combination is where margin quietly exits. A flow that earns $40 of contribution in March can earn $12 in November if the discount deepens and MMS share rises. Budget peak-season margin separately, and set a frequency ceiling for peak weeks before the calendar forces one.

Finally, revisit the pricing model annually. A store that outgrew usage-based pricing at 10,000 messages a month may find contract terms cheaper at 50,000, and a store that slimmed its list may be overpaying for profile capacity it no longer needs. The right model is a function of your current send shape, not a one-time decision.

Matchup FAQ: tools merchants price against each other

These are the pairings merchants ask about most, with the pricing lens that actually distinguishes them. The same logic applies to any pairing: identify the billing model, the channel mix, and the discount depth each requires, then let your pilot data decide.

Postscript vs. Omnisend on price

Postscript bills usage for a specialist SMS operation; Omnisend bundles email, SMS, and push into contact-plus-usage tiers. Postscript usually wins when SMS is the primary job and volume is concentrated; Omnisend usually wins when one small team wants all three channels in one builder. Compare total program cost at your volume, including the discount depth each requires to convert — not the platform fee alone.

Klaviyo vs. Sequenzy on price

Klaviyo prices by active profiles and SMS usage and rewards teams that will maintain segments and events. Sequenzy is email-first with pay-per-email positioning and no contact-based billing, designed to plan lifecycle email while a dedicated SMS provider handles consented texts. They overlap less than a feature grid suggests: if SMS depth is the requirement, shortlist a specialist; if lifecycle email planning is the requirement, price both and pilot them. Check each vendor's official pricing page for current terms before forecasting.

Attentive vs. Postscript at scale

Attentive's custom contract buys managed acquisition and service depth; Postscript's usage model stays self-serve. The crossover is program scale and internal headcount: a lean team sending high volume may find managed services cheaper than hiring, while a hands-on retention team may find a contract's minimums restrictive. Request written terms from both and compare total cost including the operator hours each model implies.