Brevo Shopify integration: setup and essential automations

Short answer. Connect Shopify through Brevo's current supported ecommerce integration, sync contacts and catalog data, validate cart_updated, order_created or the integration's actual purchase event, preserve Shopify consent, and test event payloads before launching automation. Start with welcome, abandoned cart, post-purchase, and back-in-stock. Add winback only after purchase-cycle data is reliable.

The integration is not complete when the app says connected. A production setup must prove that the right customer, event, consent state, product, price, currency, and order identifier arrive in Brevo at the expected time.

Brevo's current event documentation distinguishes contact attributes from behavioral events and lists ecommerce events such as cart_updated, cart_deleted, and order_created. Exact events can vary by plugin and ecommerce-dashboard configuration, so inspect the live account rather than copying an old workflow.

What the integration should synchronize

Not every setup exposes every row. Document what the official integration sends and where custom API or webhook work is required.

Step 1: prepare Shopify and Brevo

Before connecting:

1. List every active Shopify marketing app and automation.
2. Export the current email and SMS consent records.
3. Document transactional messages sent by Shopify or another app.
4. Decide which system owns campaigns, marketing automation, and transactional email.
5. Create a test plan for new subscriber, cart, order, cancellation, fulfillment, and unsubscribe.

This prevents duplicate cart reminders, welcome emails, and order messages after the integration goes live.

Step 2: install the supported integration

Use the current Brevo and Shopify installation path linked from Brevo's App Store or Help Center. Product naming and packaging can change, so follow the in-account instructions rather than a third-party screenshot.

Grant only the permissions required for the documented sync. Record:

• Shopify store and market connected.
• Brevo account and workspace.
• App owner.
• Install date.
• Permission scope.
• Sync direction for profiles and consent.
• Catalog scope.
• Transactional sender ownership.

If several storefronts share one Brevo account, define how store, market, language, and currency are represented on the profile and events.

Step 3: validate contacts and consent

Shopify customer records can include purchasers who never opted into marketing. They may need transactional communication, but they should not automatically become campaign subscribers.

Test four profiles:

• Newsletter subscriber with no order.
• Customer who accepted email marketing at checkout.
• Customer who declined marketing.
• Customer who later unsubscribed.

Confirm the Brevo contact's email subscription state, source, timestamp, list membership, and attributes. Keep email, SMS, WhatsApp, and push permission separate.

Do not infer consent from an order. Preserve the exact evidence available from Shopify and connected forms.

Step 4: validate ecommerce events

Brevo event names depend on whether the store is connected to the ecommerce dashboard and which plugin version is in use. Current documentation describes standard cart_updated, cart_deleted, and order_created events, while some configurations also expose non-standard events such as order_completed.

Run a controlled test:

1. Identify a test contact.
2. Add a known product and variant to cart.
3. Open Brevo's event logs.
4. Confirm the cart event and payload.
5. Complete the order with a documented payment method.
6. Confirm the order event, value, currency, tax treatment, product IDs, and unique order ID.
7. Cancel or refund the test order and record whether that event syncs.

Brevo notes that an event must occur at least once before it may appear in automation and segmentation controls. Generate real test events before building the workflow.

Step 5: decide the five essential automations

1. Welcome automation

Trigger: valid subscription form or list entry.

Job: deliver the signup promise, explain product selection, add proof, and create a first step.

Exclude profiles without marketing consent. Split existing Shopify customers from prospects so buyers are not treated as if the brand is new to them.

2. Abandoned cart automation

Trigger: the integration's cart event, commonly cart_updated.

Exit or stop rule: order created or completed after entry.

Use the cart's product data and a working return path. Check whether the link rebuilds the cart across devices. Do not rely on an event property until a live payload confirms its name.

3. Post-purchase automation

Trigger: the validated order event.

Separate marketing education from required transactional status messages. Useful messages include product setup, care, support, cross-sell after product success, and review timing after fulfillment.

Add cancellation and refund protections where the data exists. A canceled order should not receive a usage guide or review request.

4. Back-in-stock automation

Brevo's current back-in-stock documentation lists Shopify through the supported PushOwl/Brevo setup among eligible integrations.

Validate product ID, variant, stock event, signup consent, and duplicate alert behavior. A restock alert should point to the exact available variant.

5. Winback automation

Use customer order-gap data rather than a generic 90-day delay. Trigger or segment customers who moved beyond the expected next purchase window, then stop after a new order.

Winback should not be the first automation built. Without clean order history, it targets the wrong customers.

Dynamic product content

Brevo can personalize automated emails with event data. Use the actual event variables from the event log and current template language.

For every dynamic block, test:

• Product title and variant.
• Image URL and missing-image fallback.
• Product and cart URL.
• Price, currency, and tax display.
• Quantity and multiple products.
• Escaping for apostrophes and non-English characters.
• Empty or deleted product behavior.

Keep critical legal, shipping, and offer conditions as live text rather than text inside product images.

Consent and tracking for European stores

Shopify privacy settings, the Brevo tracker, and applicable consent rules can change which onsite events are available. Do not assume every EU visitor can be behaviorally tracked or entered into marketing automation.

Record:

• Cookie and tracking consent behavior by market.
• Marketing opt-in wording and channel.
• Legal basis for transactional messages.
• Data retention and deletion workflow.
• Process for access and erasure requests across Shopify and Brevo.

This is an implementation checklist, not legal advice. Have the final setup reviewed for the markets where the store operates.

Deliverability setup

Before expanding sends:

1. Authenticate the sending domain with Brevo.
2. Verify DKIM and DMARC.
3. Use a recognizable From name and reply-capable address.
4. Import historical unsubscribes and blocklisted contacts correctly.
5. Start with opted-in, recently engaged contacts.
6. Keep volume changes gradual and explainable.
7. Monitor bounces, complaints, unsubscribes, and provider-level behavior.

The Brevo deliverability guide contains the complete pre-send audit.

End-to-end QA matrix

Attach event IDs, screenshots, and profile links to the QA log. Retest after an app update, checkout change, consent change, or theme migration.

Reporting

Track each automation on delivered rate, click rate, order rate, revenue per recipient, unsubscribe, complaint, and overlap. Add store-level net revenue and refunds.

Brevo attribution can support message optimization, but a credited order is not automatically incremental. For high-volume flows, withhold a randomized eligible group and compare store outcomes over a predefined window.

Common integration mistakes

• Assuming app installation proves event quality.
• Marking every Shopify customer as a marketing subscriber.
• Building automations before event names appear in logs.
• Sending duplicate Shopify and Brevo cart messages.
• Failing to stop abandonment after purchase.
• Ignoring refunds and cancellations in post-purchase.
• Using one currency or language across several markets.
• Launching high volume before domain and list QA.

FAQ

Does Brevo integrate with Shopify?

Yes. Brevo documents Shopify among its supported ecommerce integrations. Use the current official installation path because app packaging and feature availability can change.

Which Shopify events can Brevo use?

Current Brevo documentation includes cart and order events, but exact names and payloads depend on integration and ecommerce-dashboard configuration. Verify them in Event logs.

Can I email every Shopify customer through Brevo?

No. A purchase record does not automatically grant marketing consent. Preserve Shopify subscription status and send promotional messages only to eligible contacts.

Should Shopify or Brevo send order confirmations?

Choose one transactional owner per message type. If Brevo takes ownership, validate reliability, event timing, templates, and fallback before disabling Shopify's message.

How often should the integration be retested?

Run a small smoke test monthly and a full event matrix after app, theme, checkout, consent, or catalog changes.

Connect the store, then prove the lifecycle

A Shopify integration becomes valuable only when data, permission, automation, and reporting survive a real customer journey. Deliver helps ecommerce teams implement and audit that complete setup. Book a Brevo and CRM diagnostic.