Email Deliverability for E-commerce Platforms: Shopify, WooCommerce, and Klaviyo

E-commerce platforms — Shopify, WooCommerce, Magento, BigCommerce — and the marketing tools built around them (Klaviyo, Mailchimp for WooCommerce, Omnisend) handle enormous email volume with varying degrees of native deliverability control. A Shopify store sending order confirmations through Shopify's default email infrastructure and weekly promotions through Klaviyo is operating across two separate sending configurations that require independent setup, monitoring, and optimisation. Understanding the deliverability characteristics of each platform and tool — and where the configuration levers actually exist — is the foundation of e-commerce email deliverability management.

The E-commerce Platform Deliverability Challenge

E-commerce platforms and their associated marketing tools present a specific deliverability challenge: they are designed to make email sending easy rather than to make it optimally deliverable. Default platform email configurations — Shopify sending from shopify-hosted infrastructure, WooCommerce sending via PHP's mail() function — work well enough to deliver most messages most of the time, but they do not provide the authentication completeness, reputation visibility, or sending infrastructure quality that commercial email deliverability requires.

The specific gaps in default e-commerce platform email configurations: (1) Shared sending infrastructure where the platform's reputation is shared across all stores using the default configuration — a badly behaved store on the same shared IP pool affects all stores using that pool. (2) Limited authentication configuration — some platforms do not enable custom domain DKIM signing on entry-level plans, meaning emails are signed with the platform's domain rather than the store's domain. (3) No direct access to delivery event data — the accounting log equivalent that a self-managed MTA provides is not available through platform dashboards, making deliverability diagnosis more difficult. (4) Limited control over sending IP selection — campaigns and transactional emails may share IP pools with no separation available.

Shopify Email: Configuration and Deliverability

Shopify sends transactional email (order confirmations, shipping notifications, abandoned checkout reminders) from its own email infrastructure. Shopify Email (the native marketing email tool) sends promotional campaigns from the same infrastructure. The deliverability configuration available to Shopify stores:

Custom domain email authentication (all Shopify plans): Shopify allows configuring a custom sending domain — store@yourdomain.com instead of store@shopify-email.myshopify.com. Setting this up requires publishing DKIM and SPF records in the store's domain DNS zone via records provided in the Shopify admin panel (Settings → Notifications → Sender email). This is the highest-priority Shopify deliverability configuration — custom domain authentication moves the store's reputation to its own domain and enables Postmaster Tools tracking.

The Shopify DNS records to publish:

# SPF record for yourdomain.com
yourdomain.com TXT "v=spf1 include:shops.shopify.com ~all"

# DKIM records (Shopify provides specific values in admin)
# Typically: shopify._domainkey.yourdomain.com TXT "v=DKIM1; k=rsa; p=PUBLIC_KEY"

After publishing these records, verify authentication in Shopify admin (the panel shows authentication status) and send a test order to a seed email address — confirm the Authentication-Results header shows spf=pass and dkim=pass with d=yourdomain.com.

Shopify Email limitations: Shopify Email does not provide per-campaign delivery reports comparable to dedicated ESP reporting — open rates and click rates are available but per-ISP delivery breakdown and hard bounce detail are limited. For advanced deliverability monitoring on Shopify, supplement the native tools with Gmail Postmaster Tools (which will start showing data once the custom domain authentication is configured and sufficient volume is sending) and an external blacklist monitoring tool for the Shopify shared IPs (which cannot be changed but can be monitored).

WooCommerce Email: SMTP Plugin Configuration

WooCommerce's default email sending uses PHP's mail() function, which routes email through the WordPress hosting server's mail daemon. This default configuration produces poor deliverability: the hosting server's IP is typically not configured for email sending (no PTR record, no dedicated MTA), authentication is often incomplete, and the sending IP shares reputation with every other WordPress site on the hosting server.

The mandatory first step for any WooCommerce store's email deliverability: install an SMTP plugin that routes WooCommerce's transactional email through a proper SMTP relay rather than PHP mail(). The most commonly used SMTP plugins for WooCommerce:

WP Mail SMTP (wpforms.com): The most widely used SMTP plugin for WordPress/WooCommerce. Supports Postmark, Mailgun, SendGrid, SparkPost, and generic SMTP. The Postmark integration is recommended for highest transactional deliverability — Postmark is optimised specifically for transactional email reliability. The Pro version (approximately €50/year) adds email logging and resend capabilities.

FluentSMTP: A free WordPress SMTP plugin with multiple provider integrations including Amazon SES, Postmark, Mailgun, and Outlook 365 SMTP. Provides email logging and a delivery test feature. Recommended for stores that need SMTP routing without a premium plugin budget.

The SMTP relay configuration for WooCommerce: (1) Create an account with the chosen SMTP provider (Postmark recommended for transactional; Mailgun as an alternative). (2) Configure custom domain authentication in the SMTP provider's dashboard — publish the required DKIM and SPF records in the store's DNS. (3) Install and configure the SMTP plugin with the API key or credentials from the provider. (4) Send a WooCommerce test order and verify the order confirmation delivers within 60 seconds with correct authentication headers.

Klaviyo Deliverability: Best Practices

Klaviyo is the dominant e-commerce marketing email platform and provides the most sophisticated deliverability features of any e-commerce marketing tool. Klaviyo's deliverability configuration options and best practices:

Custom domain authentication (essential): Klaviyo supports custom DKIM signing from the store's own domain. Configure via Klaviyo → Settings → Email → Sending Domains. Publish the DKIM and Return-Path DNS records Klaviyo provides. After verification, all Klaviyo sends from the store will be signed with d=yourdomain.com and will contribute to the store's own Gmail Postmaster Tools domain reputation rather than the Klaviyo shared domain reputation.

Dedicated sending IPs (Klaviyo Dedicated IP plan): Klaviyo offers dedicated sending IPs (separate from the shared Klaviyo IP pool) on higher-tier plans. For stores sending above 100,000-250,000 emails per month, dedicated IPs provide isolation from other Klaviyo customers' sending behaviour. The dedicated IP plan requires an IP warming period — Klaviyo's platform handles warmup scheduling automatically, but the store must supply high-quality engaged contacts for the warmup sends.

Klaviyo deliverability monitoring: Klaviyo provides per-campaign delivery, open, and bounce rate data in its analytics dashboard. The hard bounce data is particularly useful — Klaviyo's bounce classification distinguishes hard bounces (automatically suppressed) from soft bounces (retried). Monitor the per-campaign hard bounce rate in Klaviyo dashboard; rates above 0.5% indicate list quality issues in the specific segment used for that campaign.

List quality management in Klaviyo: Use Klaviyo's built-in engagement suppression (Klaviyo's "Never Opened" and "Never Clicked" segments) to identify and suppress contacts who have not engaged in 6-12 months. The Klaviyo Smart Send Time and Smart Sending features (preventing multiple sends to the same contact within a configurable window) help manage frequency-related complaint risk automatically.

Separating Transactional from Marketing Email

One of the most common e-commerce email deliverability problems is commingling transactional email (order confirmations, shipping notifications) with marketing email (promotional campaigns, newsletters) on the same sending infrastructure. A promotional campaign complaint spike affects the shared IP pool's reputation and can delay or degrade delivery of the transactional emails that customers need immediately after purchase.

The separation architecture for a Shopify/Klaviyo e-commerce store: (1) Shopify transactional email (order confirmations, shipping notifications, abandoned checkout first email) — send through a dedicated transactional ESP (Postmark or similar) configured as the Shopify SMTP relay. This is separate from Klaviyo. (2) Klaviyo flows (welcome series, post-purchase follow-up, review request, win-back) and campaigns (newsletters, promotions) — send through Klaviyo's infrastructure. (3) Use separate sending subdomains: transactional.yourdomain.com for the Postmark/transactional sends; marketing.yourdomain.com for Klaviyo sends. This ensures Postmaster Tools tracks transactional and marketing reputation independently.

The separation requires the Shopify SMTP relay setting (Settings → Notifications → Configure a custom SMTP server) to point to the transactional ESP rather than using Shopify's default email infrastructure. This configuration change routes Shopify's transactional emails through the chosen dedicated transactional ESP while Klaviyo handles all marketing flows independently.

Authentication Setup Per Platform

Each platform and tool in the e-commerce email stack requires its own authentication configuration. The DNS records typically required per platform for a store at yourdomain.com:

When multiple platforms send from the same sending domain (yourdomain.com), all of their SPF includes must be in a single SPF record. Multiple SPF records for the same domain are invalid — the SPF standard specifies that a domain MUST NOT have more than one SPF record. Combine all SPF includes into one record: v=spf1 include:shops.shopify.com include:klaviyomail.com include:spf.mtasv.net ~all. Verify the combined SPF record does not exceed 10 DNS lookups using MXToolbox's SPF analyzer.

Monitoring E-commerce Email Deliverability

E-commerce email deliverability monitoring requires checking data from each platform and tool in the sending stack independently, since each may have different deliverability performance:

Gmail Postmaster Tools: Register yourdomain.com and each sending subdomain (transactional.yourdomain.com, marketing.yourdomain.com) in Postmaster Tools. After custom domain authentication is configured for each platform, Postmaster Tools will show domain reputation and spam rate per registered domain. Check weekly for each registered domain — separate reputation tracking is the primary benefit of using separate subdomains per sending type.

Klaviyo deliverability dashboard: Review per-campaign bounce rate and unsubscribe rate monthly. Sort campaigns by hard bounce rate — any campaign above 0.5% indicates the specific list segment used warrants list quality investigation. Use Klaviyo's suppression management to review and clean suppression lists quarterly.

Postmark activity log (transactional): Postmark provides per-message delivery logs for all transactional sends. Check the activity log weekly for any "soft bounced" or "bounced" messages — identify the destination domains generating bounce responses and investigate whether specific ISP or corporate gateway configurations are causing transactional email delivery failures.

Order confirmation delivery time monitoring: For the highest-priority transactional flow, monitor delivery time end-to-end. A simple test: place a test order on the store periodically and record the time from order placement to order confirmation email arrival. Target: under 2 minutes. Alert: over 5 minutes. Delivery time degradation for order confirmations is the earliest indicator of transactional email infrastructure problems.

When to Migrate Beyond Platform Email

Platform email tools — Shopify Email, Klaviyo — work well for most e-commerce stores up to moderately high volume. The signals that indicate migration to more sophisticated infrastructure is needed:

Inbox placement problems that are not addressable through platform configuration — some Klaviyo deliverability issues stem from shared IP pool quality that cannot be improved without upgrading to Klaviyo's dedicated IP plan or migrating to a dedicated ESP entirely. If dedicated IP plans are available and the volume justifies them, try the dedicated IP option before migrating platforms.

Volume above 2-5M monthly messages — at this volume, dedicated email infrastructure provides per-message economics that are significantly better than Klaviyo's pricing, and the accounting log access provides deliverability visibility that platform tools cannot match. Evaluate total cost of ownership (Klaviyo plan cost vs dedicated infrastructure cost + engineering time) at 2M+ monthly messages.

Complex multi-brand or multi-region operations — stores operating multiple brands, multiple locales, or multiple Shopify stores sharing a customer base benefit from infrastructure that allows consolidating sending management rather than managing separate Klaviyo accounts per brand with no cross-brand suppression or reputation visibility.

E-commerce email deliverability is achievable within platform tools when configured correctly — custom domain authentication, transactional separation, list quality management, and weekly monitoring provide the foundation for reliable inbox delivery from Shopify, WooCommerce, and Klaviyo. The platform configuration is not the constraint for most stores; the constraint is the consistency of these practices. Configure them completely, monitor them consistently, and platform-based e-commerce email delivers reliably at the commercial volumes most stores require.

The e-commerce store that invests 4-6 hours in correct platform email configuration — custom domain authentication, SMTP relay for WooCommerce, transactional separation, Postmaster Tools registration — builds the deliverability foundation that all subsequent email programme growth depends on. That foundation is not complex to build; it is simply not built by default. Build it deliberately, verify it end-to-end, and platform-based e-commerce email will deliver reliably at the scale the store's growth requires.