Most solo operators start with one email service provider and route everything through it: welcome emails, password resets, weekly newsletters, product updates, receipts. It’s simple, it works, and for a while there’s no reason to change.
Then something breaks. A welcome email arrives four hours late. A password reset never shows up. Or worse: your newsletter gets a spam complaint, and suddenly all your emails—including order confirmations—land in the promotions tab or get delayed.
The root issue is conflating two fundamentally different types of email: transactional and marketing. They serve different purposes, have different legal rules, and need different infrastructure. Mixing them creates risk you don’t see until it costs you money.
What makes an email transactional
Transactional emails are triggered by a user action and contain information the recipient explicitly requested or needs to complete that action. Examples:
- Password resets and login links
- Order confirmations and receipts
- Account notifications (payment failed, subscription renewed)
- Download links after a purchase
- Two-factor authentication codes
These emails are expected. The user did something, and your system is responding. CAN-SPAM and GDPR treat them differently because they’re not commercial messages—they’re functional infrastructure.
Marketing emails are everything else: newsletters, product announcements, promotional offers, content roundups. They require explicit consent in most jurisdictions, must include an unsubscribe link, and are subject to stricter anti-spam rules.
The line blurs with hybrid emails—like a receipt that also suggests related products—but if the primary purpose is commercial, it’s marketing.
Why reputation matters more than you think
Email service providers (Gmail, Outlook, Yahoo) track sender reputation at the domain and IP level. If you send both transactional and marketing email from the same domain, a single spam complaint on your newsletter can damage deliverability for your password resets.
This is why companies like Stripe and Shopify send transactional email from dedicated domains (receipts come from @stripe.com, but newsletters come from subdomains or separate services). They’re isolating reputation risk.
For solo operators, the practical version of this is: use a dedicated transactional ESP for critical emails. Route your password resets, purchase confirmations, and login links through a service built for speed and reliability. Send your newsletter through a platform optimized for bulk sends, engagement tracking, and unsubscribe management.
Postmark is the gold standard here—transactional-only, no marketing allowed, designed for sub-second delivery. Pricing starts at $15/month for 10,000 emails, and because these are triggered sends (not bulk), most operators stay under 1,000/month. If you’re on WordPress and using a membership plugin or WooCommerce, you’re already generating transactional email. Route it through the right pipe.
When to split your setup
You don’t need two ESPs on day one. If you’re pre-revenue or sending fewer than 100 emails a month total, the complexity isn’t worth it. But you do need to split when:
- You’re processing payments or running a membership site (receipts and login emails must arrive instantly)
- Your newsletter list is growing past 500 subscribers (spam complaints become statistically inevitable)
- You’ve had a deliverability issue with transactional email (password resets delayed, order confirmations in spam)
- You’re sending time-sensitive notifications (webinar reminders, expiring cart links)
The cost of a delayed or missing transactional email—lost sale, frustrated customer, support ticket—is higher than the $10–15/month for a dedicated service.
How to route it correctly
If you’re on WordPress, install a transactional plugin (WP Mail SMTP, Postmark’s official plugin, or Brevo‘s SMTP add-on) and configure it to handle system emails. Your membership plugin, WooCommerce, and form notifications should route through this.
Your newsletter platform (Beehiiv, MailerLite, ConvertKit) handles everything else: weekly sends, product launches, content updates. These platforms are built for engagement tracking, A/B testing, and list segmentation—features you don’t need (and don’t want) in a password reset.
If you’re not on WordPress, check your app’s email settings. Most SaaS tools let you configure SMTP credentials. Point transactional sends to your transactional ESP, and keep marketing sends in your newsletter tool.
One non-obvious tip: set up separate subdomains. Send transactional email from mail.yourdomain.com and newsletters from news.yourdomain.com. This isolates reputation at the DNS level and makes it easier to debug deliverability issues later.
If you’re routing everything through one service today and haven’t had a problem yet, you’re not wrong—you’re just early. But when you hit the threshold where mixing email types starts costing you conversions, you’ll know exactly what to fix.
Got a question about your email setup? Reply to this email—I read every message and often turn answers into future pieces.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.