Send Odoo email & SMS marketing through Brevo with two-way contact list sync, transactional routing, and engagement tracking. Build-to-order for Odoo 17/18/19. One-time license from $199.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Send Odoo email & SMS marketing through Brevo with two-way contact list sync, transactional routing, and engagement tracking. Build-to-order for Odoo 17/18/19.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Your team already trusts Brevo (formerly Sendinblue) for high-deliverability email and SMS — but Odoo's Email Marketing, SMS Marketing, and transactional mail still leave through Odoo's own outgoing servers, so your sender reputation, warmed-up IPs, and Brevo analytics never come into play. This build-to-order connector closes that gap. ECOSIRE designs, builds, installs, and supports a custom Odoo module that makes Brevo the delivery engine for your outbound email and SMS while keeping Odoo the system of record.
Brevo REST v3 API integration with an encrypted, company-scoped API key stored in a dedicated settings model (never hardcoded, never in source control)
Outbound email routing so Odoo Email Marketing mailings dispatch through Brevo's transactional and campaign endpoints instead of Odoo's own SMTP
SMS marketing sending through the Brevo SMS API, mapped to Odoo's native SMS Marketing and sms.sms records
Two-way contact list synchronization between res.partner / mailing.contact and Brevo contacts and lists, with configurable attribute and field mapping
Incremental sync via a scheduled ir.cron job that pushes only changed records and reconciles deletions and unsubscribes
Transactional email routing for order confirmations, invoices, portal and password-reset mails through Brevo for consistent deliverability
This is NOT an instant apps.odoo.com download. ECOSIRE builds this module net-new for your database, tuned to your Brevo account, sender domains, list structure, and Odoo edition. Typical delivery is 2 to 4 weeks depending on scope.
Under the hood, the module adds an authenticated integration layer against the Brevo REST v3 API using a stored API key (encrypted at rest, never committed to source). A res.company-scoped settings model holds the API key, default sender identities, and list mappings; email and SMS are dispatched over Brevo's transactional and campaign endpoints. Contact synchronization is two-way: an Odoo model derived from res.partner and mailing.contact maps to Brevo contacts and lists, with @api.depends computed fields tracking sync state and last-synced timestamps. Engagement events (delivered, opened, clicked, hard/soft bounce, unsubscribe, SMS delivery status) flow back into Odoo through Brevo webhooks handled by a controller route, updating your mailing.trace records and Odoo's native campaign statistics so your marketing dashboards reflect reality.
Everything is delivered as clean, upgrade-safe Odoo code: a proper __manifest__.py declaring dependencies (mass_mailing, sms, contacts), models under models/, access control via ir.model.access.csv plus record rules for multi-company isolation, XML/OWL views for the configuration screens and sync dashboards, automated actions and scheduled ir.cron jobs for incremental sync and retry queues, and QWeb reporting for a Brevo-vs-Odoo delivery reconciliation summary. The same codebase supports Odoo 17, 18, and 19 on both Community and Enterprise, with version-specific branches where the API surface differs.
You get the source, the configuration, documentation, a training session, and a post-launch support window — plus ECOSIRE on call to extend it as your Brevo usage grows.
Runs email and SMS campaigns and already relies on Brevo's warmed IPs, deliverability, and analytics. Wants to launch mailings from Odoo where the CRM and segments live, but keep Brevo as the delivery engine and single source of engagement truth.
Owns the Odoo instance and its integrations. Needs a clean, upgrade-safe module with proper access control, multi-company isolation, encrypted credentials, and reliable cron-based sync — not a brittle script that breaks on the next Odoo upgrade.
Cares that transactional emails (invoices, confirmations, portal notices) actually land and that campaign performance is measurable. Wants unified reporting where Odoo campaign stats reflect Brevo's real delivery, open, click, and bounce data.
Buy the license on ecosire.com and download the Brevo (Sendinblue) Email & SMS Connector module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Brevo (Sendinblue) Email & SMS Connector, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Sends Odoo email & SMS through Brevo's deliverability engine | ||||
| Two-way contact & list sync (res.partner / mailing.contact ↔ Brevo) | ||||
| Engagement events fed back into Odoo mailing.trace & campaign stats | ||||
| Built for your exact Brevo account, senders, lists & Odoo edition | ||||
| Upgrade-safe across Odoo 17, 18 & 19 with a maintained port path | ||||
| Multi-company isolation via record rules (per-company keys & lists) | ||||
| Documentation, team training & post-launch support window | ||||
| Full source ownership, no vendor lock-in |
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.
Send Odoo email & SMS marketing through Brevo with two-way contact list sync, transactional routing, and engagement tracking. Build-to-order for Odoo 17/18/19.