A retail email that survives Cyber Monday traffic without throttling order confirmations.

"We are happy with Klaviyo. Why add another layer?"

Klaviyo is genuinely excellent for what it does. The flow builder, the Shopify integration, the segmentation logic are the strongest options available for ecommerce. EMP does not replace Klaviyo; it operates as the dedicated sending infrastructure beneath Klaviyo for brands that have outgrown shared-IP delivery. Three specific scenarios where the layer becomes useful. BFCM volume that exceeds Klaviyo shared-IP comfort zone: brands above 200,000 monthly typically see throttling complaints during BFCM peak that disappear with dedicated infrastructure. BIMI Verified Mark Certificate: BIMI requires DMARC enforcement which Klaviyo Standard does not natively manage; EMP delivers the BIMI VMC provisioning and the DMARC reject migration. Multi-jurisdiction compliance evidence: when the brand expands into Europe and gets DPA questionnaires from EU enterprise customers, EMP delivers the GDPR Article 32 documentation that Klaviyo Standard contract does not include. The brand marketing team continues using the Klaviyo UI; the change is invisible operationally.

"How does this affect our existing Klaviyo segments and historical data?"

Zero impact. The Klaviyo account remains the source of truth for customer data, segmentation, and campaign analytics. EMP receives outbound sends from Klaviyo via dedicated sending domain configuration; the brand marketing team continues seeing the same dashboards, the same flow builder, the same segment definitions. Historical opens, clicks, conversions remain in Klaviyo. The Klaviyo Account Manager will be familiar with dedicated sending domain configuration; the setup is documented in Klaviyo official documentation and takes 2-3 hours of coordinated technical work between EMP and the brand IT team. Existing campaigns continue running during migration; only new sends after cutover route through EMP. The brand can revert by changing the sending domain configuration back to Klaviyo defaults if they decide the dedicated infrastructure is not worth the cost.

"We sell in five countries with different compliance regimes. How do we handle this?"

Multi-region compliance is one of the operational reasons brands move to dedicated infrastructure. EMP delivers per-region compliance templates covering the active 2026 regulatory baseline: US CAN-SPAM plus state laws (CCPA/CPRA California, VCDPA Virginia, CPA Colorado, CTDPA Connecticut, UCPA Utah, others), EU GDPR with Article 6 lawful basis documentation, UK PECR plus UK GDPR, Canadian CASL with affirmative consent, Mexico LFPDPPP, Brazil LGPD, Panama Ley 81 de 2019. The DPA template between EMP and the brand covers the entire scope; the brand does not negotiate per-country bilaterally. Data residency option routes EU traffic through European mirror infrastructure when the brand has EU enterprise customers with strict residency requirements. Subprocessor list is published with 30-day change notice. For brands selling in jurisdictions outside the documented list, EMP runs a region-specific assessment within 5 business days.

"What is the realistic deliverability improvement after migration?"

Published Validity research establishes the band. Brands moving from shared-IP infrastructure to properly warmed dedicated IPs typically see inbox placement improve from 85-88 percent baseline to 92-95 percent in Gmail specifically within 60-90 days of completed warmup. The improvement comes from three sources. First, IP reputation isolation; the brand sends no longer affected by other senders sharing the same IP infrastructure. Second, DMARC enforcement plus BIMI VMC; the brand verified logo and the DMARC pass signal raise the engagement-derived reputation score that Gmail uses for spam folder vs inbox decisions. Third, subdomain segmentation; transactional pool reputation does not get dragged by marketing pool reputation. The improvement is measured against the brand baseline using Validity Sender Score, Talos reputation, and inbox seed list testing through Litmus or Email on Acid. Reports are delivered monthly with the comparison data.

"How does this work for brands selling on Shopify Plus with B2B Sales Channel?"

Shopify Plus B2B Sales Channel is a specific case worth addressing. The B2B side typically has different deliverability requirements than D2C because B2B buyer email goes to corporate mailboxes (Microsoft 365, Google Workspace) with stricter spam filtering and the average B2B buyer email engagement is structurally lower than D2C. EMP supports the B2B side with separate subdomain (typically b2b.brand.com or wholesale.brand.com) and separate IP pool dedicated to corporate-mailbox delivery. The IP warmup against B2B email follows different volume curves because corporate mailbox engagement signals take longer to accumulate than consumer mailbox engagement. Brand marketing team continues using Shopify Plus B2B Sales Channel with its native customer accounts; the email layer routes via dedicated B2B subdomain underneath. This is a smaller subset of brands but worth flagging because the technical answer is different from pure D2C.

"What happens if the brand IT team needs to migrate to a new ESP six months from now?"

Portability is explicitly contracted. The brand owns the sending domain configuration; if the brand migrates from Klaviyo to a different ESP (Iterable, Customer.io, Sendlane), the dedicated sending domain transfers with the brand. Data portability covers historical send logs (90 days online retention, 24 months archive), suppression list export in standard CSV or JSON format, list segment definitions documented in human-readable format, flow templates documented for replication in the new ESP. The exit clause in the DPA documents the 30-day migration assistance period at no additional fee; EMP supports the transition to whichever ESP the brand chooses. The contractual structure means the brand retains optionality; the lock-in risk that brands legitimately worry about with dedicated infrastructure is explicitly addressed.