Self-hosted vs SaaS: who controls your email?

Every e-commerce platform choice is also an email architecture choice. Shopify, BigCommerce, Ecwid, Wix, Squarespace, Tilda — these own your sending stack. WooCommerce, Magento 2, OpenCart, PrestaShop, 1C-Bitrix — these let you own it. The difference shows up three months in, the first time you hit a deliverability problem you cannot diagnose from the admin panel.

The SaaS model

On Shopify, BigCommerce, Ecwid and their peers, the platform operates its own sending infrastructure. You get:

• Zero operational burden — no SMTP server, no bounce handling, no retry logic, no queue worker.
• Pooled IP reputation — established, warmed, and managed by the platform.
• Template engine integrated with the platform's data model.
• DKIM signing as a checkbox feature (with DNS on your side).

You give up:

• Per-message logs and bounce detail.
• Ability to choose the sending IP, relay, or MTA.
• Ability to run a separate transactional IP pool.
• Feedback loop data beyond what the platform chooses to expose.
• The freedom to move the sending stack without migrating the whole store.

The self-hosted model

On WooCommerce, Magento 2, OpenCart, PrestaShop, 1C-Bitrix, you own the mail stack end-to-end. You can:

• Pick any SMTP relay — Postmark, SendGrid, SES, Mailgun, Unisender, SendPulse.
• Split streams by purpose: transactional on one relay, marketing on another, account on a third.
• Use dedicated IPs, warm them how you want, monitor at the level you choose.
• Extract every piece of metadata: bounce reason, engagement, complaint, per-recipient log.

You take on:

• Relay account management, credential rotation, SMTP module upgrades.
• DKIM rotation logistics.
• IP warm-up if you go dedicated.
• Bounce and complaint processing — you need to remove bad addresses yourself.
• DMARC aggregate report ingestion.

Where each path breaks first

SaaS breaks at the ceiling

Shared envelope reputation means individual stores inherit the average of all other stores on the platform. For a boutique brand with high-engagement customers, that is often a downgrade. The only way out is to leave the platform or to send transactional mail via your own ESP in parallel — which is possible (Flow + webhook on Shopify, similar on BigCommerce) but defeats the point of SaaS simplicity.

Self-hosted breaks at the floor

Default PHP mail() is terrible. Shared hosting IPs are worse. A new store on default WooCommerce has 10-20% inbox placement. Without someone on the team who knows what SPF and DKIM are, you never climb out of that hole.

The hybrid pattern

A growing pattern: SaaS platform for checkout, your own ESP for post-purchase flows. Example:

SHOPIFY CHECKOUT
  │
  ├── Order confirmation: Shopify native (kept simple)
  │
  └── FLOW WEBHOOK → your backend → Postmark
       │
       ├── Branded receipt
       ├── Shipping updates
       ├── Delivery confirmation
       └── Review request (after 14 days)

This lets you keep Shopify's checkout simplicity while controlling the customer-facing transactional stream that matters most for brand. It is more operational load than pure SaaS but less than pure self-hosted, and it scales with your team.

Authentication is required either way

SaaS does not mean "skip DNS". Every SaaS platform that offers custom sender (Shopify, BigCommerce, InSales, Ecwid on paid plans) still requires you to publish SPF include, DKIM CNAMEs and ideally DMARC at your domain. The checkbox in the admin does not publish DNS for you.

Monitoring: different dashboards, same questions

• SaaS: Shopify Email dashboard, BigCommerce abandoned cart reports, or third-party monitoring via seed testing.
• Self-hosted: your ESP's dashboard (Postmark activity, SendGrid stats, SES reputation), plus DMARC reports, plus Postmaster Tools, plus seed testing.

Seed testing is the one constant. ESP dashboards tell you the message was accepted for delivery. Seed tests tell you where it actually landed.

FAQ