Custom email and SMS providers for subscription notifications

When defaults are fine and when they aren't

Every subscription app ships with default email handling — pre-built templates for magic-link, renewal-reminder, dunning, cancellation, skip confirmations. By default these are sent from the vendor's email infrastructure (often AWS SES or SendGrid under the hood) via vendor-owned sender addresses like [email protected].

This is fine for most stores in the first year. Deliverability is decent because the vendor's infrastructure has good sender reputation. Templates are professional even if generic. SMS support, if included, is usually basic but functional. The defaults break down in three specific situations, each of which is a signal to consider a custom provider.

1. Spam folder rate climbs — subscribers report magic-link emails not arriving, or your dunning sequence stops recovering failed payments at the same rate. This typically happens when a vendor's shared IP reputation degrades because of another merchant's behavior on the same infra.
2. Branding outgrows the default templates — you've polished the portal UI, the storefront, the order confirmations, and the subscription-app email templates are now the visibly weakest brand surface. Default WYSIWYG editors only go so far.
3. Operational visibility is too limited — you can't see open rates, click rates, bounce rates per email type without a dedicated email-analytics layer. Default reporting from subscription apps is usually rough.

The major transactional email providers, compared

Three providers dominate transactional email for Shopify stores: Postmark, SendGrid, and Resend. Each has a different center of gravity. Picking the right one depends on what matters most for your subscription flow.

• Postmark — purist's choice for transactional only. Best-in-class deliverability, separate transactional and broadcast streams (so a marketing IP reputation problem can't hurt transactional). Slightly more expensive per email but the deliverability is consistently rated highest. Best for stores where magic-link and dunning emails MUST arrive.
• SendGrid — the industry default, Twilio-owned. Cheapest at scale, broadest feature set (templates, analytics, A/B testing), but mixes transactional and marketing on shared IPs unless you pay for dedicated. Deliverability is good but not best-in-class. Best for stores already using SendGrid for marketing.
• Resend — the developer-friendly newcomer. Clean API, React Email integration for templates, decent deliverability, simple pricing. Newer so less long-term track record on edge cases. Best for stores with engineering teams who want to build custom email flows.
• AWS SES — cheapest by far but raw — no UI, no templates, no built-in analytics. Most subscription apps that use SES under the hood do so because of the price. Don't try to plug SES in directly unless you have engineering bandwidth.
• Mailgun — long-established alternative to SendGrid. Solid deliverability, especially in EU. Worth considering if you're EU-headquartered or selling primarily into EU markets.

If your subscription app supports plugging in a provider, the integration is usually via API key plus a few configuration steps in the admin. Postmark and SendGrid are supported by every major subscription app; Resend is supported by most modern apps and growing.

How deliverability actually works: SPF, DKIM, DMARC

Once you switch to a custom email provider, the most important setup work is sender-domain authentication. Without it, your custom provider may produce worse deliverability than the defaults — because you'll be sending from a domain with no established email reputation.

Three DNS records make a domain trustworthy to email providers: SPF (which servers are allowed to send for your domain), DKIM (cryptographic signature proving the sender), and DMARC (policy for what to do when SPF/DKIM fail). All three are required for good deliverability with Gmail and Outlook in 2026 — neither will reliably accept bulk transactional mail without them.

# DNS records for sender-domain authentication
# (Postmark example; exact values come from your provider)

# 1. SPF — TXT record at root domain
Type:  TXT
Name:  @                    # yourstore.com itself
Value: v=spf1 include:spf.mtasv.net include:spf.shopify.com ~all
TTL:   3600

# 2. DKIM — TXT records; provider gives you specific selector
Type:  TXT
Name:  20231120pm._domainkey
Value: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4...   (long public key)
TTL:   3600

# 3. DMARC — TXT record at _dmarc subdomain
Type:  TXT
Name:  _dmarc
Value: v=DMARC1; p=quarantine; rua=mailto:[email protected]
TTL:   3600

• SPF lists every server allowed to send mail for your domain. Combine includes for each provider (Postmark + Shopify + Klaviyo, etc.) — don't have separate SPF records.
• DKIM proves messages weren't tampered with by signing them with a private key your provider holds. The public key lives in DNS so receivers can verify.
• DMARC tells receivers what to do if SPF and DKIM both fail: reject, quarantine, or just monitor (p=none). Start with p=quarantine after verifying SPF/DKIM are passing.
• BIMI (optional) lets your logo show in Gmail's inbox next to your sender name. Requires a verified VMC certificate ($1500+/year). Nice-to-have, not required.

Sender-domain alignment: matching email to portal URL

Beyond technical authentication, modern email providers increasingly weight the alignment between the From domain and the URLs inside the email. A magic-link email sent from [email protected] containing a link to portal.yourstore.com is fully aligned. The same email sent from [email protected] containing a link to yourstore.subscriptionapp.com is misaligned and ranks worse.

This is one of the strongest arguments for setting up a custom domain on the portal alongside switching email providers. The two work together — aligning both the sender and the portal URL under your root domain produces deliverability gains larger than either change in isolation. Same root, same trust signal, no structural ambiguity.

• From address: [email protected] (or orders@, notifications@, hi@ — match your brand voice)
• Reply-To: a real address you actually monitor (subscribers will reply to magic-link emails sometimes)
• Links in email body: portal.yourstore.com (custom domain), yourstore.com (storefront), and any docs/help links on yourstore.com
• Unsubscribe link: required by CAN-SPAM and increasingly enforced by Gmail; for transactional mail this is optional but a good signal
• Physical address: required in marketing emails (CAN-SPAM); not required in pure transactional but doesn't hurt

When the default email templates aren't enough

Default email templates from subscription apps tend to be functional but generic — variable name in the greeting, product details in the body, action button styled with your brand color, footer with company name. They cover the basics. For some stores, that's all the email needs to do. For others, the email is a brand surface that needs more.

The signals that you've outgrown defaults: you want a transactional email that doesn't look like a transactional email (richer typography, photography, multi-column layout), you want conditional content (different copy for first-time vs returning subscribers), or you want to A/B test subject lines and content systematically. Default editors handle the first; conditional content and A/B testing typically require switching to a dedicated provider's template editor.

• Postmark templates — MJML-based, version-controlled, includes a designer-friendly editor and a code-first option for engineers. Strong for stores with engineering bandwidth.
• SendGrid Dynamic Templates — handlebars-based, WYSIWYG editor, supports conditional content and A/B testing in the same template. Best feature set if you want to iterate visually.
• Resend + React Email — JSX templates, version-controlled in your repo, designer-friendly preview. Best if your team already builds with React.
• Klaviyo — not a transactional provider per se, but some subscription apps integrate with Klaviyo for transactional+marketing in one place. Watch deliverability — mixing transactional with broadcast on shared IPs is risky.

If you go custom-template, keep two principles in mind. First, the magic-link email is structurally a transactional email — keep it short, single-action, no marketing content. Subscribers tab into the magic-link, click through, done. Adding marketing content lowers click-through and raises spam complaints. Second, the dunning sequence is the highest-leverage email in subscription commerce — invest design and copy effort there before anywhere else.

SMS providers: Twilio, Vonage, and when SMS matters

SMS is a smaller part of subscription notifications but a higher-leverage one where it applies. Renewal reminders via SMS see significantly higher open rates than email (95%+ vs 25–40%). Dunning via SMS recovers failed payments faster because the response window is hours instead of days. The tradeoff is cost per message (5–10 cents vs <1 cent for email) and stricter consent requirements.

Two providers dominate: Twilio (US-strong, broad global) and Vonage (formerly Nexmo, EU-strong, sometimes cheaper internationally). Most subscription apps include basic SMS via one of these as their default provider. Switching to a direct Twilio or Vonage account makes sense when you want SMS for additional flows (renewal-reminder, post-skip confirmation, win-back) beyond what the default supports, or when your shipping markets have weak coverage on the vendor's default carrier.

• Twilio — broadest US carrier coverage, strong everywhere, well-documented API. Most subscription apps default to Twilio under the hood. Per-message pricing is mid-pack globally.
• Vonage / Nexmo — strong EU coverage, sometimes cheaper for international SMS, similar feature set to Twilio. Good alternative if you're EU-headquartered.
• MessageBird — EU-based, strong on global messaging, also supports WhatsApp Business API for stores that want subscription notifications via WhatsApp.
• Plivo — cheaper than Twilio for high-volume US SMS, smaller global footprint. Worth considering at scale.

How custom providers integrate with subscription apps

Most subscription apps support plugging in a custom email or SMS provider via two patterns: configuration (paste an API key, the app sends through the provider) or webhook (the app fires a webhook, you handle the actual sending in your own code or a Zapier/Make workflow).

• Direct API integration — paste your provider's API key in the subscription app admin. The app sends through your provider, you get the deliverability benefits and the analytics in your provider's dashboard. Easiest path. Available on most modern subscription apps.
• Webhook-based — the subscription app fires a webhook (subscription.renewed, subscription.payment_failed) and you handle the email/SMS sending in your own code. Most flexibility, more engineering work, only worth it if you have unusual flows.
• Klaviyo integration — some apps offer one-click Klaviyo integration where subscription events become Klaviyo metrics and you build the email/SMS flows in Klaviyo. Powerful if you already use Klaviyo for marketing, but mixes transactional with marketing in ways that can hurt deliverability.

Monitoring deliverability after the switch

After switching to a custom provider, watch deliverability closely for the first few weeks. Sender reputation is built over time — your domain may have decent reputation already from past Shopify-managed emails, but the new provider's IPs need to build reputation with your specific sender pattern. Volume ramps gradually for new senders.

• Inbox placement — your provider's dashboard shows what percentage of emails landed in inbox vs spam vs missing. Target 95%+ inbox for transactional.
• Bounce rate — hard bounces should be <2%. Above that, your subscriber list has bad data or your provider has IP-reputation issues.
• Spam complaints — should be <0.1%. Above that, content or sender pattern is triggering complaints.
• DMARC reports — set the rua= address on your DMARC record to receive aggregate reports. Tools like dmarcian or postmark.com/dmarc parse these into readable dashboards.
• Gmail Postmaster Tools — register your domain to see Gmail-specific reputation, spam rate, and authentication status. Free and well worth doing.

If deliverability degrades after a switch, the fix order is: verify SPF/DKIM/DMARC are all passing (check via mail-tester.com), confirm the sender domain hasn't been blocklisted (mxtoolbox.com blacklist check), reduce send volume for 48 hours and watch if it recovers (sender reputation issue), then contact your provider's support if it persists.