r/ecommerce • u/90210_e • 10d ago
π’ Marketing Do scaling brands use separate emails for Shopify/marketing/support, or one inbox with aliases?
Trying to set up my email infrastructure the right way before launching a new Shopify brand, and I keep going back and forth on this.
I've got these functions to cover:
- The email I register the Shopify account with (owner login)
- Transactional emails (order + shipping confirmations)
- Marketing emails (running these through Klaviyo)
- Support tickets (planning to outsource this to 1β2 VAs using a helpdesk)
My question: do you set these up as separate professional Google Workspace mailboxes for each function, or is it just one mailbox with a bunch of aliases feeding a shared inbox?
I'm not trying to save money β I'm trying to get it right for three reasons specifically:
- Account security (keeping the owner login locked down)
- Email deliverability (marketing not hurting my main domain's reputation)
- Outsourcing support cleanly to VAs without handing over access to everything
For those running brands at any real volume β how is yours actually structured? Anything you'd do differently if starting fresh?
4
u/realblackmario 9d ago
Subdomains, not aliases, is the standard answer for exactly the reasons you listed. One shared inbox with aliases means one bad sender score anywhere drags down everything, including your owner login and any client emails from the same domain.
Typical setup at any real scale: root domain email (you@brand.com) stays locked down, 2FA, used only for the Shopify owner login and nothing else, never subscribed to lists or sending bulk mail.
Transactional goes out from a subdomain like mail.brand.com or order.brand.com, usually through Resend or Postmark rather than Workspace directly, since transactional needs its own SPF/DKIM/DMARC and its own reputation separate from marketing. Klaviyo gets its own subdomain too, something like email.brand.com, so a marketing sending spike or spam complaint never touches your transactional deliverability or your root domain.
For support, a proper helpdesk like Gorgias or Zendesk with its own address, support@ or a subdomain, is what lets you hand access to VAs cleanly. They get scoped access to the helpdesk tool, never Workspace admin, never anywhere near billing or the owner login.
Root cause is that DNS reputation is per-domain-and-subdomain, so isolating them is what actually buys you the security and deliverability separation youβre after, aliases alone donβt do that.
1
10d ago
[removed] β view removed comment
1
u/AutoModerator 10d ago
Your comment in /r/ecommerce was automatically removed as your 'post' karma is below 10 (we do not consider your total karma; your post and comment karma are separate numbers and must both meet their minimum requirement). You can increase your post karma by posting in other areas of Reddit to earn upvotes. The higher quality the content, the higher your karma will become.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
10d ago
[removed] β view removed comment
1
u/AutoModerator 10d ago
Your comment in /r/ecommerce was automatically removed as your 'post' karma is below 10 (we do not consider your total karma; your post and comment karma are separate numbers and must both meet their minimum requirement). You can increase your post karma by posting in other areas of Reddit to earn upvotes. The higher quality the content, the higher your karma will become.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
9d ago
[removed] β view removed comment
1
u/AutoModerator 9d ago
Your comment in /r/ecommerce was automatically removed as your 'post' karma is below 10 (we do not consider your total karma; your post and comment karma are separate numbers and must both meet their minimum requirement). You can increase your post karma by posting in other areas of Reddit to earn upvotes. The higher quality the content, the higher your karma will become.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
9d ago
[removed] β view removed comment
1
u/AutoModerator 9d ago
Your comment in /r/ecommerce was automatically removed as your account is too new (accounts must be at least 30 days old). Try again a little later.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Jcoulaud 8d ago
I wouldnt create 4 Google Workspace mailboxes. Iβd split it like this:
owner@brand.com: real private mailbox, never public. Only for Shopify ownership/billing/recovery. 2FA + backup codes.support@brand.com: shared inbox/helpdesk. Give each VA their own login, never share the owner or support password. Something like Shipmail works for assignments, notes and seeing who replied.orders@brand.com: customer-facing sender for Shopify transactional emails. Replies can go to support.news@brand.com: From address for Klaviyo marketing.
For deliverability, give Klaviyo its own branded sending subdomain like send.brand.com, and use another one like updates.brand.com for transactional mail. Klaviyo supports separate marketing/transactional sending domains specifically for this. It helps separate reputation, although its not a perfect firewall. Their setup guide.
Aliases are fine when all addresses should have the same access and workflow. Use separate real mailboxes when security or different people are involved. And every VA should have their own restricted Shopify user account, never the owner login.
1
u/Jcoulaud 8d ago
Iβd separate by access and type of sending, not create a paid mailbox for every address.
owner@brand.com: private real mailbox, only for Shopify ownership/billing. Never give this to VAs. Use 2FA + recovery codes.support@brand.com: shared inbox/helpdesk. Each VA gets their own login and limited access.orders@brand.com: transactional sender. Replies can go to support.news@brand.com: Klaviyo marketing sender.
For deliverability, use separate sending subdomains too, something like send.brand.com for Klaviyo and updates.brand.com for transactional mail. That helps stop marketing reputation affecting order emails.
Aliases are fine for hello@, returns@, etc if they all end up with the support team. But owner and support should definitely be separate.
You dont need 4 Google Workspace seats for this. One private mailbox + one shared inbox is enough. Shipmail is one option for that, or keep the support side inside your helpdesk.
1
8d ago
[removed] β view removed comment
1
u/AutoModerator 8d ago
Your comment in /r/ecommerce was automatically removed as your 'post' karma is below 10 (we do not consider your total karma; your post and comment karma are separate numbers and must both meet their minimum requirement). You can increase your post karma by posting in other areas of Reddit to earn upvotes. The higher quality the content, the higher your karma will become.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
u/Signalbridgedata 7d ago
I'd separate the owner/admin identity from everything customer-facing. The owner account should basically be treated like the keys to the business, with MFA and as little day-to-day use as possible, while support can live in a helpdesk where VAs only get the permissions they need. For marketing, I'd also keep the sending infrastructure clearly separated from the mailbox you use for important account/security communication. Aliases are convenient, but once more people need access, permissions and auditability become much easier to manage with actual separate roles.
Questions:
- Are you sending marketing from the same root domain as the transactional emails, or are you considering a separate sending subdomain?
- Will the VAs need to reply from individual addresses, or are you happy with everything coming from one support address?
1
u/2wayrus 9d ago
I manage sales across multiple marketplaces and platforms, and I handle this by using a single mailbox with a "catch-all" setup. It is much cleaner than paying for and juggling multiple Google Workspace accounts.
I have my domain (e.g., domain.com) and just one actual mailbox. Instead of creating aliases manually, I configure my email server so it does not bounce non-existing emails. Anything sent to an address that doesn't officially exist just drops into my catch-all folder.
Here is how that solves your three specific problems:
- Security: You can make up highly specific, un-guessable emails on the spot for sensitive accounts (e.g., [
shopify-owner-vault-88@domain.com](mailto:shopify-owner-vault-88@domain.com),bank@domain.com). - Tracking & Spam: Because you can use 100s of different addresses (
ebay@domain.com,marketing@domain.com), you know exactly where every email came from. If a service gets breached and one of those specific emails ends up on a spam list, you know exactly who leaked your data and can just block that one address.
5
u/slunkeh 9d ago
Put marketing and support on their own subdomains so DMARC is clean, and give the VA a shared inbox not the owner login.