Why Your Shopify Order Emails Are Landing in Spam: DMARC and the shopifyemail.com Fallback
Shopify email deliverability: why unauthenticated stores get rewritten to a shopifyemail.com sender, and the DMARC setup that gets order emails to the inbox.
date
Your order confirmations used to arrive in seconds. Now customers are emailing support asking whether their order went through, password resets are timing out, and open rates on transactional email have slid for no obvious reason. Nothing changed in your Shopify admin. Something did change in the inbox.
Shopify email deliverability has quietly become a technical compliance job. Since February 2024, Gmail and Yahoo have required authenticated sending from any domain pushing volume at their users, and Gmail escalated to outright rejections in November 2025. If your store's sending domain is not properly set up, Shopify works around the problem by rewriting your sender address to something like [email protected]. The email still goes out. It just goes out looking a lot less like you.
What the Gmail and Yahoo bulk sender rules actually require
The rules are not complicated, but most merchants have never read them. Google's sender guidelines say that anyone sending 5,000 or more messages a day to Gmail accounts must publish SPF and DKIM, publish a DMARC record (at minimum p=none), and make sure the visible From domain aligns with at least one of those authentication results. Marketing mail also needs one-click unsubscribe, and spam complaint rates need to stay below 0.3 percent. Yahoo's requirements are essentially the same, and Microsoft applied a near identical set to Outlook.com addresses from May 2025.
Two things catch Shopify brands out. First, the threshold is counted across your whole root domain, not per sending tool. Your ESP, your helpdesk, your reviews app and Shopify's own notifications all add up. A brand doing a few hundred orders a day with an active email programme clears 5,000 messages without noticing. Second, enforcement moved from warnings to hard bounces. Vendor reporting through late 2025 shows Gmail returning permanent 550 rejections for unauthenticated or misaligned mail rather than quietly filing it in spam.
The scale of the gap is striking. Red Sift's December 2025 analysis of roughly 73 million domains found only around 15 percent had any DMARC record at all, and of those that did, more than two thirds were still sitting at p=none. A separate dmarcian review of the top 500 European retailers found a fifth had no record and a further 15 percent had a malformed one. Retail is not ahead of the curve here.
The shopifyemail.com fallback, and why it hurts order confirmations
Shopify's own help documentation is clear about what happens when your sender domain is not authenticated: your address may display with "via shopifyemail.com" appended, or the From address is replaced with a store specific address on shopifyemail.com. Shopify does this for a sensible reason. If it sent mail claiming to be from yourbrand.co.uk without authentication for that domain, Gmail would now reject it outright. Rewriting the sender keeps the email deliverable.
The cost is trust. An order confirmation from [email protected] looks like a phishing attempt to a cautious customer, and inbox providers treat it with the reputation of a shared domain rather than yours. Password reset emails are the worst case: the customer is already slightly frustrated, and now an unfamiliar sender asks them to click a link. Replies to those emails also break, because the reply address is no longer a mailbox you monitor.
Transactional email is the one message every customer opens. It is the wrong place to look like someone else.Why your root domain is fragmented across four senders
The typical plateaued Shopify brand sends email from at least four systems: Klaviyo or a similar ESP for marketing, Gorgias or Zendesk for support, a reviews app such as Judge.me or Okendo for review requests, and Shopify itself for order notifications. Each was set up by a different person at a different time, and nobody owns the result.
That produces three recurring failures. The SPF record has grown past the ten DNS lookup limit, so it silently fails for every sender. DKIM is configured for the ESP but was never completed for Shopify, so marketing mail aligns and transactional mail does not. And the DMARC record, if it exists, was published at p=none years ago by whoever set up the ESP and has never been looked at since. Meanwhile the reviews app is still sending from the root domain with no authentication at all, dragging the reputation of every other sender down with it.
This is why the fix is never "add a DMARC record". DMARC only reports and enforces. If the underlying SPF and DKIM are misaligned, turning DMARC up to quarantine simply moves more of your own legitimate mail into spam. The sequence matters.
Shopify DMARC setup: the fix sequence that holds
Here is the order we work through on client stores. DNS changes take a day or two to settle, but this is the difference between a one off fix and a durable one.
- Pick one sending identity on a domain you control. If your Shopify sender email is a Gmail or Yahoo address, change it. Those domains cannot be authenticated by you and will always be rewritten. Use something like [email protected] that domain in Shopify. In Settings, Notifications, Sender email, Shopify will show the CNAME records it needs for DKIM. Add them at your DNS provider and wait for the status to turn green. Do not add Shopify to your SPF include unless Shopify's own instructions ask for it.Audit every other sender on the root domain. List the ESP, helpdesk, reviews app, subscription app and anything else that sends as you. Confirm each has DKIM aligned with your domain. Remove any that are no longer in use from SPF.Move marketing to a subdomain. Sending Klaviyo mail from news.yourbrand.co.uk keeps promotional complaint rates from affecting transactional reputation on the root domain, and makes alignment far simpler to reason about.Publish DMARC at p=none with reporting switched on. Point rua= at a monitoring tool for 2-4 weeks and watch which sources fail. This is where you catch the forgotten app nobody mentioned.Move to p=quarantine, then p=reject. Once reports show every legitimate source aligning, step up the policy. Quarantine is the minimum worth having. At p=none you are compliant on paper but still fully spoofable, which is a brand problem of its own.
If your store runs on an ongoing support arrangement, this is exactly the kind of work that should be in scope. We cover what a sensible Shopify support and maintenance package should include, and DNS hygiene is on that list for a reason.
What authentication will not fix
Authentication is the entry ticket, not the whole journey. A few honest caveats from stores we have worked on.
Some merchants report that order emails still show a shopifyemail.com address even after their domain shows as authenticated and a DMARC record is live. In most cases this traces back to a mismatch between the sender address in Shopify and the domain that was actually authenticated, or to a DMARC record that is present but malformed. Occasionally it needs a Shopify support ticket. Either way, test with a real order to a Gmail account and read the headers rather than trusting the green tick.
Authentication also does nothing for content and list quality. If your abandoned checkout flow is firing at bot traffic, your complaint rate will rise regardless of your DNS, which is one reason we wrote about fake abandoned checkouts polluting Shopify email flows. A well authenticated domain sending dull, over frequent marketing will still end up in the promotions tab. For the retention side of the picture, our practical guide to Shopify email marketing covers what to send and how often.
Deliverability is a conversion problem in disguise
Most Shopify brands we speak to in Glasgow and across the UK do not have a traffic problem. They have a conversion problem, and email deliverability sits squarely inside it. A customer who never receives the order confirmation is more likely to open a dispute. A customer who cannot reset their password buys elsewhere. A review request that lands in spam never becomes the social proof your product page needs. None of this shows up as a line item in analytics. It shows up as a conversion rate that has stopped moving.
That is why we treat sending infrastructure as part of conversion rate optimisation rather than an IT chore. On our Conversion Growth Retainer, a domain authentication audit is one of the first things we run on a new store, because it is cheap to fix and the downstream effect on repeat purchase and support load is real. After 12 years and over 100 Shopify projects, the stores that compound growth are the ones that get the boring foundations right.
The takeaway: open a recent order confirmation from your own store in Gmail, click "show original", and read the SPF, DKIM and DMARC lines. If any of them say fail or the From address is not your domain, you have found a conversion leak that costs almost nothing to plug. If you would rather someone senior checked it for you, get in touch and we will take a look.
Related articles
view all(01) Shopify ADA and EAA Accessibility Compliance: What an Agency Fix Actually Involves
Shopify ADA compliance and EAA rules explained for store owners: why Shopify stores get sued, WCAG 2.2 AA, and what a proper theme fix involves.
read article(02) Shopify Customer Accounts and Loyalty: Why Most Stores Get It Wrong
Most Shopify stores treat customer accounts as an afterthought. Here's how to turn them into a retention tool that drives repeat purchases.
read article(03) What It Takes to Get a Theme Approved on the Shopify Theme Store
What Shopify's theme reviewers check before approving a submission: Lighthouse scores, design standards, demo stores, and ongoing support obligations.
read articleStay ahead of the Shopify curve
Uncover Insights brings the latest Shopify trends, practical tips, and a look behind the scenes straight to your inbox.
We won't send you spam. Unsubscribe at any time.