For the multi-store Shopify operator

Five stores, five brands.
One inbox for support.

Email for multiple Shopify stores means giving each storefront its own professional reply-From, its own DKIM key, and its own sending reputation — while only one operator sits at the keyboard. Emcognito WebMail unifies the inbox across every bound storefront domain, with per-store colour in the margin and automatic From on every reply, instead of one Google Workspace seat per brand.

You run more than one Shopify brand. Each has its own storefront, its own brand voice, its own little-letter customer service. Each has a custom domain and a hello@ or support@ that customers expect a reply from — using that brand's name, not yours and not another store's.

Emcognito WebMail is the inbox for the operator running the whole portfolio. Per-store colour stripe, per-store DKIM, per-store reply From — so a customer of the kitchenware brand never gets a reply signed by the candle brand.

Updated 24 May 2026 (2026-05-24)

Start free — no cardSee the price

Android app live on Google Play

I · The problem with Shopify's email forwarding

Forwarded mail is not sent mail.

Shopify forwards inbound mail from your store domain to whichever address you set — usually your personal Gmail. That solves receiving. It does not solve sending. The moment you reply, you reply from your @gmail.com, and the customer sees the wizard behind the curtain.

The cottage-industry workaround is to set up Gmail's 'Send mail as' for each store domain. It works until two stores share a similar product line and you forget which one a customer wrote in about. It also leaves every store sharing one DKIM key, one reputation, one bounce pool — so a bad batch on one store's transactional mail can punish another store's deliverability.

The professional version of this is one Google Workspace per store, at $7/mo each. Five stores is $420 a year, five admin consoles, five places to manage 2FA, and you're still the only human reading the mail.

Shopify gave each of your stores a domain. The forwarder gave each of them an inbound path. Neither one gave you a way to reply as the brand the customer thinks they're talking to.

II · A morning across the storefront stack

Three brands, one support desk.

Not a screenshot — a live render in the same editorial design system the app uses. Each row's stripe is the domain the letter was sent to. Hover (or read quickly, by eye): which self is each one addressed to?

III · How a multi-store inbox should read

Each store reads like its own brand.

Bind each Shopify store's custom domain into Emcognito. Each becomes a first-class identity — coloured stripe in the margin, dedicated DKIM key, dedicated reply From. Customers of the kitchenware brand get a kitchenware reply; customers of the candle brand get a candle reply; the human typing is one person.

  • ·
    Per-store reply From, automatic. Replies pre-fill From the brand the customer wrote to. The candle customer never sees the kitchenware brand by accident.
  • ·
    Catch-all per store. hello@, support@, wholesale@, returns@ — all delivered to one inbox, filed under the store they belong to. New mailboxes cost nothing.
  • ·
    Per-store sending reputation. A bad batch on one store's order-confirmation flow cannot drag down another store's deliverability. Each Shopify-bound domain has its own DKIM key and its own SES reputation pool.
  • ·
    Flat price, every brand. Studio is $12/month annual for unlimited bound stores. Adding the next Shopify storefront's email is $0 — not $7 forever.

IV · What changes for the bookkeeping

One operator, books per store.

The point of running stores under separate brands is so each one has its own P&L. The inbox should match that — visibly, in the margin, and cryptographically, in the headers.

Per-store DKIM
Each Shopify domain you bind gets its own RSA-2048 DKIM key at provisioning. Order confirmations, wholesale invoices, and replies all sign with the store's key — never a shared aggregate signature.
One bill, every store
Stripe charges the operator one flat amount per month. Most operators expense the subscription against the holdco or the largest store; brand accounting stays clean because no per-store license exists to allocate.
Mailbox export
If you sell a store, export its mail and unbind the domain. The buyer's team can bind the same domain to their account with fresh DNS records. No data-migration negotiation; DNS is the boundary.
Calendar in the inbox
Supplier calls, wholesale onboarding, photo-shoot schedules — invites land inline with RSVP and conflict warnings. Exposed as an iCal feed any calendar app can subscribe to.

V · Common questions

Questions readers ask.

Does this replace Shopify's built-in email forwarding?

It replaces the reply side of it. Inbound mail still arrives through your store domain's MX records — once you change those MX records to point at Emcognito, mail lands in your unified inbox instead of forwarding to a personal Gmail. Outbound replies then go from the store's own DKIM-signed identity, not your @gmail.com.

What about Shopify transactional mail — order confirmations, shipping updates?

Shopify continues to send transactional mail itself; that path is unchanged. Emcognito handles the human reply mail (customer service, wholesale, supplier conversations). For higher-volume stores wanting to consolidate all sending under their own DKIM, Shopify supports custom sender configuration that can use the same domain Emcognito is bound to.

How many Shopify stores can I bind?

Studio ($12/month annual) covers unlimited bound domains. Solo ($2.99/month annual) covers up to three — fine for a two- or three-store operator just starting the portfolio. Holding Co. adds priority support and onboarding for operators with five or more stores or who want a human walking through the first cutover.

Can my VA or fulfilment partner reply on behalf of a store?

Emcognito is single-operator today — one human signs in to the inbox. If you have a VA replying to support tickets, the established pattern is to share access via your existing helpdesk (Gorgias, Front, Help Scout) by forwarding the store's support@ from Emcognito into the helpdesk and replying from the helpdesk. Multi-user is a roadmap question; ping us if it's a hard requirement.

What happens to my old Gmail aliases when I switch?

Once you change the MX records on the store's custom domain to Emcognito, mail stops landing in Gmail. Existing 'Send mail as' aliases inside Gmail still work for outbound, but you'd disable them so you stop accidentally replying from there — the whole point of the switch is reply From the store's real identity, not Gmail's.

Is the migration risky for a live store?

DNS cutover is the only real moment. Lower the MX TTL ahead of time, publish Emcognito's records, and watch inbound flow shift inside the TTL window. We run a 7-day overlap monitor so you can see when old-MX traffic has fully drained. The guided wizard at /migrate/google-workspace walks through it; an ecommerce-specific variant is on the roadmap.

VI · Adjacent readers

Other shapes of the same problem.

VII · Sources & further reading

Where the claims come from.

Open the first letter

Five stores. One support voice per brand.

Start free, no card. Bind your biggest store's custom domain first; live with the per-brand reply From for a week of real customer mail. Add the other stores when the model proves out. Twenty-five sends and the first domain are free.

Start free — no cardRead the manual

Updated 24 May 2026 (2026-05-24)