Shopify does not host business email. A provider such as Google Workspace, Microsoft 365, or another mail service hosts the mailbox, while DNS and Shopify sender settings connect the brand identity. A sound baseline lets the team receive mail, Shopify send authenticated brand-domain messages, and customers understand where replies go.
Separate three mail systems
- Team mailboxes such as
support@brand.com, managed by the email host. - Transactional order, shipping, and account notifications triggered by Shopify.
- Marketing email, which requires consent, unsubscribe handling, list hygiene, and reputation management.
They can share a brand domain, but their access, content, and risk differ. A personal free mailbox is a poor permanent sender identity, and high-volume campaigns should not be introduced into an unplanned system that also carries critical transactional communication.
Configure DNS in a controlled order
Configure MX according to the email provider and prove inbound and outbound mail first. Then confirm sender ownership in Shopify and add the authentication records displayed for the domain. Shopify's current interface and documentation provide the required CNAME, SPF, or DKIM directions. Introduce DMARC only after inventorying every legitimate sender; copying another company's strict policy can reject valid mail.
| Record | Primary purpose | Common failure |
|---|---|---|
| MX | identifies receiving servers | deleted during storefront connection |
| SPF | authorizes sending sources | multiple conflicting SPF records |
| DKIM | signs outgoing messages | incorrect selector or host field |
| DMARC | defines alignment and handling | rejection enabled before sender discovery |
Allow DNS propagation before declaring failure; Shopify notes that authentication changes can take up to 48 hours. Test several mailbox providers and inspect From, Reply-To, Return-Path, SPF, DKIM, DMARC, and link domains. A “sent” event is not proof of inbox delivery.
Protect access and operating ownership
Give support, finance, and marketing distinct accounts or roles instead of a shared master password. Use multifactor authentication and document offboarding, domain renewal, and recovery ownership. Notification templates should contain the correct legal or brand name, order facts, policies, and contact route. Consistent facts also help search and generative systems connect communications with the correct business entity.
Accept the real customer journey
Place at least one low-value test order and validate order confirmation, fulfillment, cancellation, refund, account, and support-reply messages. Check that product, order, policy, and tracking links resolve on the intended domain and that text-only, mobile, and localized templates contain no obsolete placeholders. Inspect authentication and reply behavior from Gmail, Outlook, and a business mailbox.
Assign an owner and change date to each template. When migrating a sender domain or mailbox, update privacy and support pages, website forms, payment and delivery notifications, and external profiles so replies do not continue to an abandoned address.
For lifecycle automation, continue with the Shopify and Klaviyo implementation guide, but establish authentication and consent governance before multiplying flows.
FAQ
Does a domain purchased through Shopify include business email hosting?
No. Shopify states that it does not provide email hosting; a third-party service can be connected.
Do passing SPF, DKIM, and DMARC guarantee inbox placement?
No. Authentication is foundational, while list quality, complaints, content, sending history, and mailbox-provider decisions still influence deliverability.
Can a domain publish two SPF TXT records?
It generally should not. Authorized sources need to be consolidated into one valid SPF policy and verified by the mail administrator.
Must the Shopify sender and support reply address be identical?
Not necessarily, but the visible sender and reply route must be understandable and tested end to end.
Does changing the storefront domain migrate email automatically?
No. Website DNS and email migration are related but separate projects with separate acceptance tests.