Shopify Transactional Email Through Your Own SMTP

Shopify does not let you point store notifications at your own SMTP server. There is no host, port, or password field in the admin, and order confirmations, shipping updates, and refund notices all leave from Shopify's own infrastructure. What you do control is the sender address and the DNS authentication behind it, which is the difference between a customer seeing [email protected] and seeing [email protected]. Everything outside store notifications, meaning marketing, newsletters, and post-purchase flows, can move to a mailer you run.

This is the single biggest difference between Shopify and WooCommerce. On WooCommerce you install an SMTP plugin, type in credentials, and every store email routes through your server. Shopify is a hosted platform, and the mail path is part of what it hosts.

What you can and cannot move off Shopify

Shopify splits into two halves, and only one of them is yours to route.

The locked half is small in volume and large in importance. A store doing 3,000 orders a month sends maybe 9,000 notification emails, all of which have to land. The movable half is where volume and cost live: a 60,000-contact list mailed four times a month is 240,000 sends, none of which Shopify has to touch.

I would not fight the locked half. Shopify's sending reputation for order mail is good, and the failure mode people actually hit is not Shopify's IPs, it is an unauthenticated domain producing a rewritten From address.

Authenticate the domain so Shopify sends as you

The one lever you have on Shopify's own sending is domain authentication, and it is not optional any more. Since 1 February 2024, if your sender domain is not authenticated with a DMARC record present, Shopify rewrites your From address to [email protected] so the mail still passes Gmail and Yahoo bulk sender rules. Your customers get their order confirmation from a Shopify address instead of yours.

The setup, from Shopify's own sender email documentation:

1. Set your sender email in Settings, Notifications to an address on a domain you control.
2. Add every CNAME record the admin modal shows you. The count varies, so add all of them, not the first two.
3. Publish a DMARC record of at least v=DMARC1; p=none on _dmarc.yourstore.com.

_dmarc.yourstore.com.  TXT  "v=DMARC1; p=none; rua=mailto:[email protected]"

Shopify's docs state that the CNAMEs handle SPF for that sender address, so you do not add a separate SPF include for Shopify. If your domain was bought through Shopify, or is on Cloudflare, GoDaddy, or IONOS, Shopify can write the records itself.

One thing worth planning before you type anything: which domain you authenticate. Sending Shopify notifications from the root domain and your marketing from a subdomain keeps the two reputations apart, which is the same argument as root domain versus subdomain for sending.

Why alignment matters even when Shopify sends the mail

Domain alignment is worth doing precisely because you cannot control the IP. Gmail and Yahoo score the sending domain separately from the sending IP, so an authenticated yourstore.com builds a reputation that follows you to whatever you send from next, including the mailer you run yourself.

The domain reputation row is the one people undervalue. Two years of clean order mail on yourstore.com is an asset when you later warm your own IPs for marketing, because Gmail already trusts the domain even though the IP is new. Skip authentication and you spend two years building reputation for shopifyemail.com.

Gmail's bulk sender guidelines require SPF, DKIM, DMARC, one-click unsubscribe, and a spam complaint rate under 0.3% once you cross 5,000 messages a day to Gmail. Order confirmations count toward that 5,000.

Shopify Email as the bundled option

Shopify Email, now branded Shopify Messaging, is the default marketing path and it is cheap at small volume and dull at large volume. Every store on Basic, Grow, Advanced, or Plus gets 10,000 free emails a month, and abandoned checkout automations are free on top and do not count against the allowance.

Past the free block, per Shopify's email pricing page:

Unused emails do not roll over. At $1 per 1,000 it undercuts most ESPs on the raw send, and there is no contact-count charge, which is the fee that makes Klaviyo bills climb. The catch is the same as any bundled tool: no dedicated IP, no control over the sending reputation, limited automation depth, and the same shared-pool policy exposure as any relay. For a store sending 30,000 marketing emails a month, that is a $20 bill and not worth thinking about.

The app route, and what it does not give you

Klaviyo, Omnisend, Mailchimp, and the rest send through their own infrastructure. Installing one does not put your SMTP server in the path. This trips people up because the apps talk about "your sending domain" and "your dedicated IP", both of which mean something narrower than owning the server.

Klaviyo will sell you a dedicated IP and generally suggests one above roughly 100,000 sends a month, but it stays inside Klaviyo's stack. That is fine until the bill is the problem, which is the usual trigger for looking at Klaviyo alternatives when the bill gets too high. Contact-based pricing means an inactive 80,000-address list costs the same as an engaged one.

The genuinely-your-own-SMTP route

There are two ways to get Shopify data onto your own mail server, and both keep order notifications on Shopify.

Export and mail from your own stack. Pull customer and order data out of Shopify by CSV or the Admin API, load it into a mailer you run (Mautic, Mailwizz, Sendy, or your own code), and point that at your SMTP server on port 587. You own the IPs, the reputation, the logs, and the suppression list. You take on the list hygiene and the warm-up. This covers newsletters, win-back, post-purchase education, and cross-sell.

Headless. With a headless storefront you write your own checkout and post-purchase flows, so anything you generate yourself can go through your SMTP server. Shopify still sends the notifications tied to its order objects, so this narrows the locked half rather than removing it.

Neither one gets you order confirmations. Anyone telling you a plugin will reroute Shopify's order emails to your relay is describing something Shopify does not expose. The honest version is that you move the 90% of volume that is marketing and leave the 10% that is notifications where it is.

Cost at 100K and 500K a month

Marketing volume is where the decision has money in it. Two scenarios, assuming a 50,000-contact list, at 100,000 and 500,000 sends a month.

Shopify Email is genuinely hard to beat on raw send price for a store under about 300,000 a month, and I say that as someone selling the alternative. The reasons to move are control, not cents: your own IP so a bad campaign does not sit in a shared pool, full logs, no policy team, and no per-email meter as you grow. Once you are sending seven figures a year, a one-time server cost against a recurring per-1,000 charge changes the arithmetic. There is a fuller breakdown in what 100,000 emails a month actually costs.

Decision guide

That last row is the common one. A store convinced it needs custom SMTP for order confirmations almost always has an unauthenticated sender domain and a rewritten From address instead. Fix the CNAMEs and the DMARC record first, then decide about marketing.

If you also run WooCommerce or are weighing a move, the routing story there is completely different, since WooCommerce lets you swap the SMTP path outright. That is covered in SMTP for WooCommerce at high volume, and the stream separation logic that applies to any store is in SMTP for ecommerce abandoned-cart and receipts.

We keep it honest: nothing here replaces Shopify's order-notification sender, because Shopify does not offer that. What a dedicated server changes is the marketing half, where the volume, the cost, and the reputation risk actually live.

How BulkEmailSetup helps

We build the dedicated SMTP infrastructure for the half of your Shopify email you can actually move: your own server, your own IPs, SPF, DKIM, DMARC, and PTR configured correctly, plus warm-up before your peak season. Your Shopify order notifications stay on Shopify, authenticated to your domain, while campaigns and post-purchase flows run from a mailer you control with no per-email meter.

Basic is $549 one-time, covering 1 SMTP server, 3 dedicated IPs, 25,000 emails/day and unlimited contacts. Higher tiers scale to 15 IPs and 200,000 emails/day. See pricing, or read Klaviyo vs a dedicated SMTP server for the direct comparison.

Frequently asked questions