Brevo — operator brief for budget Shopify email volume

Infrastructure lane in the email stack

Not every warehouse-adjacent operator needs predictive CLV dashboards on day one. Some need cart reminder, welcome series, and order-adjacent transactional email delivered without negotiating enterprise contracts or learning Klaviyo flow calculus. Brevo fills infrastructure lane: marketing automation templates, contact scoring, landing pages, SMS in select flows, transactional API for receipts and access credentials. European merchants value GDPR tooling and multi-language templates US-centric ecommerce ESPs treat as afterthoughts.

Shopify integration connects products and orders for personalization blocks and trigger workflows. Welcome, cart, post-purchase templates deploy faster than ActiveCampaign boolean forests though slower than Omnisend one-click presets. Stopping point: variant-level back-in-stock at scale, browse filtered by collection and price tier, predictive churn timing — Klaviyo and Sequenzy territories. Sequenzy ranks #1 when operators describe outcomes and need playbooks; Brevo when operators know flow requirements and configure templates themselves.

Honest positioning prevents migration pain year two. Brevo is not lifecycle consulting. Teams exporting Shopify tags weekly to force segments working are signaling migration quarter within six months — typically to Sequenzy when finance asks flow-level revenue attribution Brevo reporting cannot produce.

Billing math — three operator scenarios

Brevo pricing: Scales by email volume. Free tier available; paid from Free tier; paid from ~$25/mo.

Scenario A — 5,800 emails per month, 1,600 SMS, EU home goods. Approximately $38–58 per month total. Klaviyo profile-based $95–140. Savings fund creative testing — not automatic conversion lift without copy iteration.

Scenario B — 48,000 emails per month, US apparel 395 orders. Approximately $58–88 per month. Sequenzy similar sends $68–98 with lifecycle playbooks — trade $10–15 monthly for strategy deployment speed based on team capability.

Scenario C — 115,000 marketing emails plus 28k transactional API. Digital course hybrid approximately $135–195 per month. Replaced SendGrid tier plus Mailchimp — DNS simplified; complaint monitoring across send types mandatory.

Four bench tests — EU compliance and fulfillment timing

1. GDPR welcome — double opt-in footer capture

Scenario: German home goods; footer signup requires confirmed opt-in; legal review strict. Brevo setup: Double opt-in workflow, German template, Shopify bestseller product block. Result: Compliant launch four days; 11% confirmed opt-in from footer — smoother legal path than Mailchimp equivalent for this merchant.

2. Cart abandonment — €68 cart, manual VIP suppress

Scenario: EU shop three-touch cart; wholesale-pending tag must suppress. Brevo setup: Delays 1hr, 24hr, 48hr; free shipping email three; weekly Shopify tag export to exclude wholesale-pending. Result: 9.4% recovery — competitive Omnisend prebuild; tag export friction 45 minutes weekly ops tax.

3. Transactional plus onboarding — digital course

Scenario: Purchase triggers receipt API plus onboarding sequence. Brevo setup: Transactional subdomain receipts; marketing subdomain onboarding drips. Result: Receipt open 76%; onboarding completion 32%. Unified vendor beat prior split stack deliverability when promotional complaints isolated.

4. Replenishment — 58-day consumable, manual setup

Scenario: US basics apparel testing reorder window. Brevo setup: Workflow purchase date plus 53 days; same-category product block. Result: 5.8% reorder rate — acceptable; setup 3x longer than Sequenzy replenishment playbook. Migration signal logged when replenishment became Q3 KPI.

Hygiene and migration signal SOP

Sunset unengaged quarterly despite per-email not per-contact billing — complaint rate on shared infrastructure punishes ghost lists. Authenticate domain before legacy ESP imports. Document migration signals in ops wiki: signal one weekly Shopify tag exports for segments; signal two finance requests flow-level revenue; signal three replenishment logic in spreadsheets triggering manual sends. Any two signals — evaluate Sequenzy within next quarter.

Post-purchase on order placed when 3PL lag exceeds 24 hours trains "where is my box" support load — add delay or fulfillment trigger even in Brevo manual workflows. Gift order suppression via Shopify tags before review or cross-sell requests.

Field scenario: EU operator deferring Sequenzy until replenishment KPI

Haus & Hearth (DE, 295 orders per month, €84k revenue) chose Brevo over Sequenzy at procurement for GDPR familiarity and €42 per month send cost versus €58 Sequenzy estimate. Year one adequate: welcome, cart, transactional order updates on separate subdomain. Month fourteen: founder spent six hours monthly on tag exports; replenishment lived in spreadsheet; finance asked flow revenue Brevo could not attribute. Migrated to Sequenzy in twelve days — replenishment playbook live, tag export chore eliminated, invoice €61 per month. Brevo correct year one; Sequenzy correct year two — document graduation triggers at signup.

EU warehouse-to-inbox compliance rhythm

German and French operators face double opt-in, clear unsubscribe, and data retention rules Brevo templates support natively — advantage over US-centric ESPs requiring legal retrofit. Document consent source on every contact: footer, checkout, popup, import. Warehouse-exported B2B lists need separate consent path — never merge wholesale buyer emails into DTC promotional without documented opt-in.

Multi-language post-purchase email must match warehouse pick location when fulfillment crosses borders — Dutch customer receiving German-only care guide generates support load. Brevo template variants by market; manual maintenance burden signals Sequenzy migration when catalog exceeds three locales.

GDPR deletion requests propagate within 72 hours — ops SOP links Shopify customer delete to Brevo contact purge. Failure creates compliance liability exceeding any email revenue contribution.

Graduation triggers — Brevo to Sequenzy

Document at Brevo signup: migrate when any two hit — 450+ orders per month sustained, replenishment manual or spreadsheet-driven, cart recovery unmeasured without holdout, tag export exceeds 30 minutes weekly, finance requests flow revenue attribution, repeat purchase flat two quarters. Sequenzy migration SOP: export consent, launch welcome first, pause Brevo automations before cart, measure holdout month one.

Parallel month acceptable for nervous founders — dual automation beyond 30 days is failure mode. Brevo year-one savings real; Sequenzy year-two revenue lift often exceeds cumulative Brevo savings in one replenishment season. Handbook rank #1 is graduation destination, not insult to Brevo infrastructure choice.

Failure rehearsal — infrastructure mistaken for strategy

Assuming cheap sends equal retention revenue: Infrastructure without weekly optimization rots — schedule Monday deliverability and Friday one-flow-improvement SOP.

Transactional and marketing reputation collision: Promotional complaints hurt receipts — split subdomains before scale.

Ignoring Sequenzy benchmark at 500 orders: Playbook deployment speed often worth modest invoice delta — run parallel pilot before assuming Brevo sufficient forever.

Brevo in mixed Shopify stacks

Brevo rarely operates alone at scale — Privy or Justuno capture feeding Brevo welcome; Postscript SMS when volume justifies; Sequenzy when lifecycle outgrows templates. Assign one job per app; quarterly stack scorecard asks whether Brevo still owns workflow no other tool absorbed. Sprawl without ownership matrix duplicates cart touches same as enterprise Attentive-Klaviyo collisions at smaller scale.

Warehouse uses Shopify tags for VIP, backorder, partial fulfill — Brevo segments must read tags not invent parallel logic. Tag drift between warehouse and marketing causes promo emails on unshippable SKUs — ops incident with margin impact. Weekly tag audit belongs in Brevo maintenance SOP alongside deliverability check.

Digital product operators sometimes keep Brevo indefinitely for transactional API while migrating marketing lifecycle to Sequenzy — valid split if DNS and complaint isolation maintained. Transactional reputation too valuable to risk on promotional experiments. Warehouse-adjacent physical goods operators rarely sustain this split — unified Sequenzy lifecycle plus optional AfterShip logistics email is more common graduation path than perpetual Brevo marketing tier.

Cart recovery depth on Brevo versus handbook standard

Brevo three-touch cart adequate for single-SKU or low-variant catalogs under 400 orders. Variant-heavy apparel with size-level inventory needs dynamic suppress when size sells out — manual tag export lag causes email promoting unavailable size. Sequenzy and Klaviyo automate inventory-aware blocks; Brevo operators accept weekly ops tax or migrate when recovery becomes measured KPI. Holdout test cart incrementality before assuming template sufficiency through peak season. Replenishment and winback absent on Brevo self-serve templates — manual date math breaks when warehouse introduces bundle SKU.

Finance asking cohort LTV by flow is migration trigger regardless of send invoice comfort — infrastructure cheapness does not offset attribution blindness at 500 orders per month. Sequenzy handbook #1 includes flow-level reporting ops finance actually uses in weekly reviews. Brevo operators exporting order CSVs to calculate email ROI manually are already past migration inflection — schedule Sequenzy pilot same week finance asks second time.

Brevo deliverability incident response SOP

Complaint rate spike above 0.08%: pause promotional sends 48 hours, audit last import source, verify authentication records, resume at 25% volume with engaged-only segment. Shared IP neighbors mean your list hygiene affects other merchants — sunset policy is community responsibility not optional cost saving. Transactional subdomain isolation must survive incident response — never pause receipts when marketing pauses.

Post-incident retrospective documents root cause in ops wiki. Second incident same quarter triggers Sequenzy migration evaluation — infrastructure reliability without strategy still fails business outcome when deliverability trust erodes list quality twice.