Brevo WooCommerce integration: connect, test, and automate the store

Short answer. A reliable Brevo WooCommerce integration follows seven stages: verify the store and REST API, connect the official plugin, reconcile the WooCommerce-to-Brevo sync, configure consent, authenticate the sending domain and SMTP, test identity and cart events, then launch automations with monitoring and an offboarding process. Installing the plugin is only the connection step. Business value comes from trustworthy data, clear permission, and real journey QA.

The Brevo plugin for WooCommerce can synchronize contacts, products, categories, and orders, install the Brevo tracker, support behavioral segments, and route selected WooCommerce transactional emails through Brevo SMTP.

It also has important limitations:

• the primary sync direction is WooCommerce to Brevo;
• deletions and updates do not always move back to the other system;
• arbitrary custom WordPress attributes are not supported by the standard sync;
• a visitor must be identifiable before a useful cart-recovery journey can reach that person;
• consent configuration remains the merchant's responsibility.

This guide was reviewed on July 16, 2026 using Brevo's official WooCommerce plugin documentation. Check current plugin, WordPress, WooCommerce, and plan compatibility before production.

What the integration can do

The integration does not replace an ecommerce CRM strategy. It transports data. Strategy decides which system owns each field and which customer action should follow.

Understand the architecture before installation

The operating path is straightforward:

WooCommerce
  -> contacts, products, categories, and orders
  -> Brevo plugin
  -> Brevo contacts, ecommerce dashboard, tracker, and events
  -> segments, campaigns, automations, and reporting

The main arrow points toward Brevo. That matters for governance:

• correcting a record in Brevo does not automatically correct WooCommerce;
• deleting a WordPress user does not guarantee deletion in Brevo;
• a Brevo unsubscribe does not necessarily rewrite the WooCommerce profile;
• a custom WordPress attribute may not become usable in Brevo.

Do not describe the integration as complete real-time two-way synchronization unless your own tested configuration proves that behavior for a specific field.

Pre-installation checklist

Store and infrastructure

• WooCommerce is installed and active.
• The store is publicly reachable.
• The REST API responds at /wp-json.
• WordPress, WooCommerce, PHP, and plugin versions are compatible.
• A recent backup is available.
• WordPress and browser caches can be cleared.
• The firewall allows the domains and network ranges documented by Brevo.
• A staging environment or controlled testing window is available.

Account and governance

• The target Brevo account is confirmed.
• Marketing, technical, and compliance owners are named.
• The source of truth for customer data is documented.
• Customer identity rules are defined.
• Email and SMS permission are stored separately.
• Deletion and data-rights requests have an operating process.
• Sending domains and sender addresses are controlled by the company.

For account-wide configuration, use the Brevo email, automation, SMS, and CRM tutorial.

Install and connect the plugin

Brevo's documented connection path is:

1. Install and activate the Brevo for WooCommerce plugin in WordPress.
2. Open WooCommerce, then Brevo.
3. Request the account connection.
4. Sign in to Brevo.
5. Allow access.
6. Activate the integration.
7. Open its settings under Integrations > My integrations.

Do not enable every feature immediately. Connect the accounts, let the initial synchronization run, and reconcile volumes before activation.

Validate the data synchronization

Brevo documents an initial synchronization for existing data followed by synchronization of new or updated data. Validate each object type separately.

Use the integration's sync details and download the error report when records fail.

What does not automatically synchronize

The official plugin documentation states that:

• data primarily moves from WooCommerce to Brevo;
• changes made in Brevo do not generally sync back to WooCommerce;
• selected WordPress updates, deletions, or blocklists are not reflected in Brevo;
• only a fixed set of WordPress attributes is supported;
• custom attributes are not freely synchronized.

Create a mapping document with four columns: source field, destination field, owner, and correction rule.

Consent: do not mark every customer as subscribed

The plugin can import WooCommerce contacts as marketing subscribers. That option is risky when the historical database does not contain clear, verifiable marketing consent.

Brevo recommends leaving it disabled when evidence is uncertain. New customers can then become marketing subscribers only when they actively opt in at checkout.

Recommended permission configuration

1. Display an unambiguous checkout checkbox.
2. Separate account creation from marketing subscription.
3. Store source and timestamp.
4. Use the confirmation method appropriate to the market.
5. Use double opt-in when stronger proof and list validation are required.
6. Exclude pending confirmation states from campaigns.
7. Test unsubscribe behavior.

The plugin uses dedicated WooCommerce attributes to represent subscription and confirmation states. A contact waiting for double-opt-in confirmation must not receive marketing, even if that person appears in a technical list.

Consent test matrix

Compliance does not come from installing a plugin. It comes from configuration, evidence, and repeatable processes.

Identity and tracking: test guest shoppers

When ecommerce synchronization is active, the plugin installs the Brevo tracker. The documentation lists events such as:

• Page for a page view;
• Identify for contact identification;
• cart_updated when a cart changes;
• order_completed when a purchase completes.

Event logs are available in Brevo's Automations area.

One documentation nuance requires real testing. Brevo lists identification during signup or checkout as an example, while its troubleshooting section says that entering an email during checkout may not be enough for the visitor to be tracked as a contact. It also refers to account login, a Brevo form, or engagement with a Brevo transactional email as identification paths.

The implication is important: do not promise recovery of every abandoned cart before testing the store's real guest checkout.

Minimum identity test

• Browse while logged out.
• Add a product to the cart.
• Enter an email at checkout and leave.
• Inspect the Brevo profile and event log.
• Repeat while logged in.
• Repeat after opening or clicking a Brevo email.
• Check the applicable tracking and cookie permission state.

Document the exact moment when the visitor becomes identifiable. That point determines the coverage of browse and cart journeys.

Authenticate the sending domain before SMTP

Before routing transactional or automated emails, authenticate the domain used by the sender. Brevo documents its required records, DKIM, and DMARC in the official domain authentication guide.

Checklist:

• company-owned domain;
• professional sender address;
• valid DKIM;
• governed DMARC record;
• alignment checked;
• monitored Reply-To;
• tests at major mailbox providers;
• gradual sending plan for a new domain.

SMTP infrastructure cannot compensate for weak permission, broken authentication, or a sudden send to a dormant database.

Configure Brevo SMTP for WooCommerce

The plugin lets an administrator select which WooCommerce email events should be handled by Brevo SMTP.

For every selected event:

1. Enable Brevo sending.
2. Choose a Brevo or WooCommerce template.
3. Confirm From, Reply-To, and language.
4. Use the plugin-specific personalization variables.
5. Trigger a real test.
6. Inspect delivery, rendering, links, and customer data.
7. Review transactional statistics.

Variables used by Brevo templates sent through the WooCommerce plugin are not necessarily the same as variables in a standard Brevo template. Copying an existing template without updating variables can produce empty order fields.

Messages to test

• order created or processing;
• order completed;
• shipping notification if supported by the store setup;
• password reset;
• account creation;
• customer-facing refund;
• any custom email added by another WooCommerce plugin.

Some WooCommerce statuses create messages for the store owner rather than the customer. Test recipients, not only design.

Avoid the statement that Brevo guarantees inbox delivery. A more accurate claim is that Brevo SMTP provides sending infrastructure and exposes available delivery, click, bounce, and message statistics.

Build a reliable abandoned-cart journey

Brevo provides a preconfigured cart recovery automation. Its official abandoned-cart documentation requires the Brevo tracker and the relevant purchase events.

A reliable journey follows this logic:

cart_updated
  -> wait
  -> confirm that an order was not completed
  -> check consent and pressure rules
  -> send the reminder
  -> exit after purchase or cart deletion

Add rules for:

• contact identification;
• marketing permission when the message contains promotion;
• cart value and products;
• purchases after the trigger;
• unavailable products;
• re-entry frequency;
• promotions already received;
• relevant open support issues.

Test a customer who completes the purchase during the wait. That customer must exit before the reminder sends.

WooCommerce automation roadmap

Do not launch ten journeys at once.

Back-in-stock alerts and selected advanced ecommerce features depend on the Brevo plan. Verify current availability before promising them in the implementation scope.

The Brevo automation workflow guide explains how to structure triggers, waits, branches, and exits.

Useful segments after synchronization

Create segments only when they change an action:

• subscribers without an order;
• first-time buyers;
• repeat buyers;
• customers by purchased category;
• customers with a recent cart and no order;
• refunded customers excluded from a sensitive promotion;
• inactive customers;
• high-value customers when net value is reliable;
• contacts without marketing permission;
• contacts waiting for confirmation.

Use the CRM segmentation framework to define conditions, exclusions, ownership, and validation.

Prelaunch QA plan

Data

• WooCommerce and Brevo counts are reconciled.
• Orders have unique identifiers.
• Currency and amount are correct.
• Line items contain the expected SKU.
• Canceled, refunded, and failed states are understood.
• Guest and logged-in customers are distinguishable.

Consent

• The checkbox works on mobile and desktop.
• A customer without consent does not receive campaigns.
• Unconfirmed double opt-in remains excluded.
• Unsubscribe prevents future marketing.
• Deletion requests have a manual operating path.

Tracking and automation

• Events appear in logs.
• Identity behavior is understood for every scenario.
• The cart contains the correct products.
• Purchase stops recovery.
• Re-entry follows the intended rule.
• Every branch has a tested profile.

Transactional email

• Every template renders the correct variables.
• From and Reply-To are correct.
• Links work.
• Mobile and dark-mode rendering remains readable.
• No message sends twice.
• Bounces and available statistics appear.

Monitoring after launch

Monitor these signals daily during the first stage:

• synchronization failures;
• sudden event-volume drops;
• missing orders;
• growth in unidentified profiles;
• empty template variables;
• bounces and complaints;
• duplicate emails;
• contacts remaining in a journey after purchase.

Then establish a cadence:

Brevo's ecommerce dashboard and message reporting help observe the system. They do not replace reconciliation with WooCommerce and finance.

Offboarding: design the exit before launch

Removing the plugin does not delete data already synchronized to Brevo. New synchronization and plugin-dependent sending stop, but historical data remains.

An offboarding runbook should cover:

1. stop campaigns and automations;
2. disable Brevo SMTP for WooCommerce events;
3. restore the selected sending path under change control;
4. export contacts, consent, and suppressions;
5. export useful templates and reports;
6. archive mappings and journey rules;
7. revoke access and credentials;
8. delete or retain data according to policy;
9. verify that no customer receives duplicate messages;
10. document the cutover date and owner.

Planning the exit reduces lock-in and makes a future migration safer.

When is Brevo a good fit for WooCommerce?

Brevo deserves a proof-of-concept when:

• marketing and transactional email should share a platform;
• the team wants ecommerce automation without a heavily fragmented stack;
• SMS or chat may complement email;
• the send-based cost model fits the program;
• the integration limitations still cover required data;
• the team can govern identity, consent, and monitoring.

If the decision also includes a more automation-centered platform, read Brevo vs ActiveCampaign.

Brevo WooCommerce FAQ

Is the Brevo WooCommerce plugin free?

The plugin can be installed without a separate plugin purchase, but Brevo usage depends on the plan, contacts, sends, channels, and activated features. Model the full configuration on the official plan page.

Is the synchronization bidirectional?

Not completely. The primary path is WooCommerce to Brevo. Changes, deletions, and blocklists are not all reproduced in the other system.

Can Brevo send WooCommerce transactional emails?

Yes. The plugin can route selected events through Brevo SMTP using either a Brevo or WooCommerce template. Test every event, recipient, and variable before launch.

Why does an abandoned-cart automation fail to start?

Common causes include missing identity, missing tracker or event data, an incorrect entry rule, ineligible consent, or a purchase that correctly removed the contact. Inspect event and workflow logs with a real scenario.

What happens after the plugin is removed?

New synchronization and plugin-dependent messages stop. Data already stored in Brevo is not automatically deleted. Run the offboarding process and validate the replacement sending path.

Turn the plugin into an operating system

Our CRM agency and email marketing agency can audit synchronization, consent, SMTP, lifecycle journeys, and reporting before launch. Book a Brevo WooCommerce implementation diagnostic.