BigCommerce email: test both streams before the next send

BigCommerce merchants operating at any real volume run two parallel email streams: transactional (order, shipment, account) directly from BigCommerce's built-in mailer, and marketing (newsletter, abandoned cart, winback) through Klaviyo, Omnisend, or MailerLite. Each stream has its own sender domain, its own authentication posture, and its own way of failing silently.

The classic merchant mistake is to test only the marketing campaign. Klaviyo's own dashboards say "97% Inbox placement", you ship the campaign, and the sales conversion looks fine — but returns spike two weeks later because a cohort of customers never got their shipment emails and assumed the store was a scam.

The two BigCommerce email streams

Transactional — built-in BigCommerce mailer

BigCommerce sends order confirmations, shipment notifications, account creation and password reset through its own relay. The default sender domain is a BigCommerce-owned envelope unless you configure a custom one in Advanced Settings → Store Profile.

• Default envelope is shared — reputation averaged across all BigCommerce stores.
• Custom sender requires TXT records BigCommerce provides (SPF include + DKIM key).
• DMARC alignment is relaxed by default. If you tighten it to strict via your own DMARC record, confirmations will start failing alignment if any sub-flow is misconfigured.

Marketing — Klaviyo (or similar)

Most serious BigCommerce stores push marketing through Klaviyo. Klaviyo has its own dedicated IP or shared pool, its own DKIM key, and its own DMARC alignment.

• Klaviyo provides a CNAME-based authentication flow with em._domainkey and a tracking subdomain.
• The sending subdomain is usually send.yourstore.com, which needs SPF + DKIM records of its own.
• DMARC at _dmarc.yourstore.com applies to both streams — a policy that is too strict will break whichever stream has weak alignment.

Sender domain alignment across streams

The lowest-friction setup is to put both streams on the same root domain, but with different subdomains:

Transactional (BigCommerce):   orders@yourstore.com
Marketing (Klaviyo):           send.yourstore.com (em._domainkey)
DMARC record:                  _dmarc.yourstore.com  p=quarantine
SPF on yourstore.com:          v=spf1 include:_bigcommerce-spf +
                               include:_spf.klaviyo.com ~all

Both streams inherit the same DMARC policy, but each signs with a distinct DKIM selector. That way a mistake on one side does not collapse the other. When BigCommerce rotates its DKIM key (rare but it happens), Klaviyo keeps sending fine. When Klaviyo changes its tracking subdomain (more common), transactional mail keeps flowing.

Placement test the full campaign lifecycle

Before any large send, run a three-part seed test across a single real order from end to end:

1. Send the marketing campaign to the seed addresses — this tests the Klaviyo stream with the actual subject, preview text, and template of the planned campaign.
2. Click a product and check out with a seed buyer — this fires the BigCommerce order confirmation. Record the placement per provider.
3. Manually mark the order as shipped with a fake tracking number — this fires the shipment notification, which often uses a slightly different template chain than the order email.

Running all three gives you a complete picture. You see whether a DMARC tightening broke one stream, whether Klaviyo's reputation is dragging marketing into Promotions, or whether BigCommerce's template is the source of a Gmail Promotions drift.

Ongoing monitoring after the campaign

The single biggest reason BigCommerce deliverability silently degrades is that nobody tests after the initial setup. The typical pattern:

• Merchant configures custom sender, green DKIM, DMARC quarantine. Placement is 95%+ across Gmail, Outlook, Yahoo.
• Three months later marketing team adds a new Klaviyo template with different From display name. Gmail treats the new display name as a new sender and reputation-resets it.
• Marketing placement drops into Promotions. Nobody notices because Klaviyo's dashboard shows "delivered", which only means accepted-by-mailbox-provider, not landed-in-Inbox.

Scheduled placement tests — weekly on marketing, daily on transactional — catch drift before it becomes a revenue problem.

FAQ