Brevo (Sendinblue) Email & SMS Connector

This is a build-to-order module, not an instant download — ECOSIRE builds it net-new for your database. Typical delivery is 2 to 4 weeks from the time we confirm scope and receive Brevo API access. Simple single-company setups land nearer 2 weeks; multi-company, custom template mapping, or heavy field-mapping work pushes toward 4. We share a milestone plan up front and give you a staging build to review before go-live.

Every build includes a post-launch support window (typically 30 days) covering bug fixes and configuration help under a defined SLA. You also receive the full source, so nothing is locked in. After the window, we offer optional support-and-maintenance retainers that keep the module current with Brevo API changes and with new Odoo releases — we support 17, 18, and 19 and will port your build forward when you upgrade.

Both work. The connector builds on Odoo's Email Marketing (mass_mailing) and SMS (sms) modules, which exist in Community and Enterprise alike. We tailor the build to your edition — where an API or view differs between Community and Enterprise or across versions 17/18/19, we branch the code accordingly so you get a clean, upgrade-safe result on your exact stack.

Yes. Contacts sync in both directions between Odoo (res.partner / mailing.contact) and Brevo contacts and lists. A scheduled ir.cron job runs incremental sync — pushing only changed records — while Brevo webhooks feed unsubscribes, bounces, and list changes back into Odoo in near real time. You configure exactly which fields and lists map, and each record shows a computed sync-state badge and last-synced timestamp.

Yes. Brevo webhooks push delivered, opened, clicked, bounced, and unsubscribed events into Odoo, updating mailing.trace records and the native campaign statistics so your Odoo dashboards reflect Brevo's real outcomes. We also ship a QWeb reconciliation report comparing Brevo-reported delivery against Odoo's expected sends, so you can audit any gap between the two systems.

The Brevo API key is stored in a company-scoped settings model, encrypted at rest, and never committed to source control. Webhook endpoints validate signatures and deduplicate events. Access to the connector's models and settings is governed by ir.model.access.csv and record rules, including per-company isolation so a multi-company database keeps each company's keys, senders, and lists separate. All Brevo traffic uses HTTPS.