Email MarketingJanuary 15, 2026

Managing Multiple Shopify Stores in Klaviyo

Running multiple Shopify stores? Here's how to manage them in Klaviyo — shared account vs. separate accounts, unified profiles, and cross-store marketing strategies.

Mark Cijo

Mark Cijo

Founder, GOSH Digital

Managing Multiple Shopify Stores in Klaviyo

You started with one Shopify store. Then you launched a second brand. Or opened an international store. Or split your B2B and DTC operations. Or acquired another brand.

Now you have multiple Shopify stores and a critical question: how do you handle email marketing across all of them?

This is not a trivial decision. The wrong setup creates data silos, duplicated work, confused customers, and billing headaches. The right setup gives you unified customer data, efficient operations, and the ability to cross-sell between brands.

Here is how to structure Klaviyo for multiple Shopify stores — including when to use one account vs. multiple accounts, how to handle shared customers, and how to market across stores without annoying people.

The Core Decision: One Account or Multiple Accounts?

Klaviyo gives you two options for managing multiple stores.

Option 1: Multiple Stores in One Klaviyo Account

Connect all your Shopify stores to a single Klaviyo account. All customer data, events, and campaigns live in one place.

When this makes sense:

  • Your stores share a customer base (same person might buy from both)
  • Your stores are sub-brands under one parent company
  • You want unified reporting across all stores
  • You want to cross-sell between stores
  • Your team manages all stores (one team, one tool)

Advantages:

  • Single customer profile with data from all stores
  • Cross-store segmentation ("bought from Store A but not Store B")
  • One bill, one login, one team workflow
  • Easier to maintain consistency across brands
  • Customer gets one unified communication preference

Disadvantages:

  • Flows and campaigns get complex (must always filter by store)
  • Easy to accidentally send Store A content to Store B customers
  • Billing is based on total unique profiles across all stores
  • Harder to give separate teams access to only their store's data

Option 2: Separate Klaviyo Accounts Per Store

Each Shopify store connects to its own dedicated Klaviyo account.

When this makes sense:

  • Your stores are completely separate brands with no overlap
  • Different teams manage different stores
  • You want complete separation of data, billing, and access
  • The brands target different customer segments with zero crossover
  • You acquired a brand and want to keep it operationally independent

Advantages:

  • Complete data isolation (no risk of cross-contamination)
  • Clean, simple setup per account
  • Separate billing (easier for cost allocation between brands)
  • Independent team access and permissions
  • Each brand has its own deliverability reputation

Disadvantages:

  • No cross-store customer data (if someone buys from both, you have two separate profiles)
  • Cannot cross-sell between brands via email
  • Duplicated work for shared templates, flows, or strategies
  • Multiple logins and workflows to manage

Setting Up Multi-Store in a Single Account

If you chose the single-account approach, here is how to set it up properly.

Connecting Multiple Stores

In Klaviyo, go to Settings then Integrations. You can add multiple Shopify integrations — one per store. Each connection syncs its own orders, products, and events.

Critical: When you connect multiple stores, Klaviyo merges profiles by email address. If the same email exists on both stores, it becomes one profile with events from both stores. This is usually what you want (unified customer view) but requires careful flow and campaign design.

Organizing with Custom Properties

For every profile, track which store(s) they interact with:

  • Add a profile property: Source Store (set on first interaction)
  • Track events with a Store property (so each order, browse, and cart event carries the store context)
  • Create segments per store: "Customers of Store A," "Customers of Store B," "Customers of Both"

Building Flows That Respect Store Context

Every flow needs conditional logic to route customers to the correct store experience.

Welcome flow example:

  • Trigger: Someone subscribes to a list
  • Conditional split: Did they subscribe from Store A or Store B?
    • Store A path: Welcome emails with Store A branding, products, and links
    • Store B path: Welcome emails with Store B branding, products, and links

Abandoned cart flow example:

  • Trigger: Checkout Started event
  • Conditional split: Which store was the checkout on? (Check event property Store)
    • Store A path: Cart recovery emails with Store A branding
    • Store B path: Cart recovery emails with Store B branding

Post-purchase flow example:

  • Trigger: Placed Order event
  • Conditional split: Which store was the order on?
    • Store A path: Store A post-purchase sequence
    • Store B path: Store B post-purchase sequence

Campaign Segmentation

For every campaign, always include a store-specific segment filter. Never send a Store A promotion to Store B customers unless you are intentionally cross-selling.

Create base segments:

  • "Store A Engaged Subscribers" (subscribed to Store A list AND opened/clicked in last 90 days)
  • "Store B Engaged Subscribers" (same for Store B)
  • "Cross-Store Customers" (has purchased from both)

Cross-Store Marketing Strategies

If your stores share a customer base, cross-selling between stores is a significant revenue opportunity.

Cross-Sell Flows

Trigger cross-store recommendations based on purchase behavior:

  • Bought from Store A (skincare) but not Store B (supplements)? Send a "Complete your wellness routine" email introducing Store B.
  • Bought from both stores? Send a VIP bundle offer spanning both stores.
  • High LTV on Store A? They are a strong prospect for Store B.

Timing: Do not cross-sell immediately after a first purchase. Wait until the customer has bought 2-3 times from one store and is clearly satisfied before introducing the other brand.

Unified Loyalty Programs

If your stores share a loyalty program (or should), Klaviyo can track points and status across both:

  • Points earned at either store count toward the same balance
  • Tier status reflects total spending across both brands
  • Redemption works at either store

This incentivizes shopping at both stores and increases total customer lifetime value.

Shared Content Marketing

A newsletter can feature content from both brands without feeling disjointed if the brands are related:

  • Parent brand sends a monthly "what's new across our brands" digest
  • Content organized by interest category rather than by store
  • Subscribers choose which brands' content they want to receive (preference center)

The Billing Question

Klaviyo bills based on total active profiles in your account. With multiple stores in one account, profiles are deduplicated by email. If the same customer shops at both stores, they count as one profile.

Separate accounts: You pay for every profile in each account separately. If 10,000 customers overlap between Store A (30K profiles) and Store B (25K profiles), you pay for 55K total profiles instead of 45K.

Single account: You pay for 45K unique profiles. The billing savings can be significant if you have substantial customer overlap.

Calculate your overlap before deciding. If overlap is under 5%, the billing difference is negligible. If overlap is 30%+, a single account saves real money.

Deliverability Considerations

Each brand should have its own sending domain and authentication (DKIM, SPF). In a single account, you can configure multiple sending domains and assign each brand's emails to its domain.

Why separate domains matter:

  • If Store A has deliverability problems, it does not affect Store B
  • Each brand builds its own sender reputation
  • Subscribers who mark Store A as spam do not impact Store B's reputation

Setup: In Klaviyo, add multiple sending domains under Settings then Domains. When creating campaigns and flows, select the appropriate sending domain for each brand.

Common Multi-Store Mistakes

Not filtering campaigns by store. Sending a Store A Black Friday email to your entire list (including Store B-only subscribers) creates confusion and spam complaints.

Shared unsubscribes. If someone unsubscribes from Store A emails, should they still receive Store B emails? This depends on your relationship between brands. If they are clearly separate brands, yes. If they are closely related (same parent brand), respect the unsubscribe across both.

Inconsistent data tagging. If you do not tag every event and every profile with its store source from day one, you cannot reliably segment later. Set up the tagging before connecting your stores.

Over-communicating. If a customer is subscribed to both stores and both send 3 times per week, that person gets 6 emails per week from related brands. Use frequency caps (Klaviyo's Smart Sending) to prevent email fatigue.

Not planning the migration. If you are moving from separate accounts to a combined account (or vice versa), plan the data migration carefully. Export lists, profiles, and historical events. Map custom properties. Test flows thoroughly before switching.

The Decision Framework

Answer these questions to determine your setup:

  1. Do your stores share customers (same person buys from both)? If yes, lean toward single account.
  2. Do you want to cross-sell between stores? If yes, single account.
  3. Are the brands operated by separate teams with separate budgets? If yes, lean toward separate accounts.
  4. Is brand separation critical (different industries, different audiences)? If yes, separate accounts.
  5. Do you want unified reporting? If yes, single account.
  6. Is deliverability isolation important (one brand is riskier)? If yes, separate accounts.

Most multi-brand eCommerce companies we work with end up with a single account because the cross-selling and unified data benefits outweigh the added complexity.

The Bottom Line

Multi-store Klaviyo management is an operational decision that impacts revenue, team efficiency, and customer experience. There is no universally right answer — it depends on your specific brand structure, team, and goals.

What matters is choosing deliberately and setting up the structure correctly from the start. Migrating from one setup to another mid-flight is painful and risks data loss.

Make the decision once. Set it up right. Then use the structure to do things your single-store competitors cannot — like cross-store personalization, unified loyalty, and efficient multi-brand operations.


Managing multiple stores and need help structuring your Klaviyo setup? Book a free strategy call and we will recommend the right architecture for your brand portfolio.

Mark Cijo

Written by Mark Cijo

Founder of GOSH Digital. Klaviyo Gold Partner. Helping eCommerce brands grow revenue through data-driven marketing.

Book a free strategy call →

Want results like these for your brand?

Book a free call. We'll look at your data and show you what's possible.

Pick a Time

15 minutes. No pitch deck. Just your data and our honest take.