イメージプレビュー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.
Brevo (Sendinblue) Email & SMS Connectorとは？
Sends Odoo email and SMS marketing through Brevo (formerly Sendinblue), with two-way contact list sync, transactional routing and engagement tracking. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
主な機能
受注生産、すべておまかせ
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
- 1
ご注文
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
- 2
構築とインストール
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
- 3
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
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.
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 one working week 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.
得られるもの
- Complete, commented Odoo module source (models, views, controllers, security, cron, QWeb reports) delivered as a versioned Git repository or ZIP
- Installation and configuration on your Odoo 17, 18, or 19 database — Community or Enterprise — including Brevo API-key wiring, sender-identity setup, and list mappings
- Field- and list-mapping configuration tailored to your res.partner / mailing.contact structure and Brevo attributes
- Brevo webhook configuration and endpoint hardening (signature validation, HTTPS, deduplication) verified end to end
- Administrator and end-user documentation covering setup, sync behavior, template mapping, troubleshooting, and reconciliation reports
- A live training session for your marketing and admin team, with a recording and a quick-reference runbook
- A defined post-launch support and bug-fix window (two weeks, extendable) with a clear SLA
- Odoo version-compatibility notes and an upgrade path so the module moves cleanly across 17 to 18 to 19
これは誰のためのものですか
Marketing Manager on Brevo
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.
Odoo Administrator / IT Lead
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.
Revenue / Operations Lead
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.
Brevo (Sendinblue) Email & SMS Connector の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| 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 | 付属 | 付属 | 含まれていない | 付属 |
Brevo (Sendinblue) Email & SMS Connector に関するよくある質問
How long until the connector is live in our Odoo?
This is a build-to-order module, not an instant download — ECOSIRE builds it net-new for your database. Typical delivery is one working week 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.
What support and updates come with it, and after?
Every build includes a post-launch support window (two weeks) 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.
Do we need Odoo Enterprise, or does Community work?
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.
Is it two-way sync, and how are contacts kept aligned?
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.
Will campaign and delivery analytics show up inside Odoo?
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.
How are our Brevo API keys and data kept secure?
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.
関連モジュール
BPMN Workflow Designer
A build-to-order visual BPMN 2.0 workflow builder for Odoo that lets your team design multi-level approvals and conditional routing without writing XML or Python. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19 database.
Braintree (PayPal) Gateway for Odoo
A Braintree payment acquirer for Odoo that puts cards, PayPal, Venmo and Apple/Google Pay behind a single Drop-in UI, with 3DS2/SCA, vault tokenization and webhook reconciliation. ECOSIRE builds, installs and supports it for your Odoo 17, 18 or 19.
Brevo (Sendinblue) Email & SMS Connector
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.
- 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