Segmented WhatsApp broadcast campaigns in Odoo with templates, scheduling, delivery analytics and opt-in compliance. Built, installed and supported by ECOSIRE. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Segmented WhatsApp broadcast campaigns in Odoo with templates, scheduling, delivery analytics and opt-in compliance. Built, installed and supported by ECOSIRE.
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Turn WhatsApp into a measurable, compliant marketing channel that lives inside your Odoo database. This is a build-to-order module — ECOSIRE designs, builds, installs and supports it against your exact WhatsApp Business Platform setup — not an instant apps.odoo.com download. Typical delivery is 2 to 4 weeks depending on scope, integrations and approval cycles.
Segment builder that resolves audiences from res.partner, crm.lead and sale.order using saved ir.filters domains, so lists stay live instead of frozen exports
Campaign object as a first-class Odoo model with draft/scheduled/running/done states, Kanban pipeline and smart-button counters
Binding to approved WhatsApp Business message templates with variable placeholders mapped to record fields and rendered per recipient at send time
Scheduling and drip release via ir.cron plus automated actions, with per-campaign send windows and timezone handling
Configurable throttling (messages per minute/hour) to respect Meta rate limits and protect your WhatsApp quality rating
Per-message status log reconciled from WhatsApp Cloud API webhooks: queued, sent, delivered, read, replied, failed — with error reason capture
Odoo core ships WhatsApp only as a transactional/conversational channel (order confirmations, one-to-one chatter replies). It has no native concept of a segmented marketing blast, per-campaign throttling, template-campaign scheduling, or attribution back to a marketing initiative. We close that gap with a purpose-built module.
Under the hood the module introduces first-class marketing objects as proper Odoo models (models.Model): a WhatsApp campaign, a recipient/queue line, and a message-event log. Audiences are resolved from your existing data — res.partner, crm.lead and sale.order — using saved filter domains and ir.filters, so a segment is a live query, not a frozen list. Templates map to your approved WhatsApp Business message templates, with variable placeholders bound to record fields and evaluated at send time. Computed fields (@api.depends) roll up delivery, read, reply, click and conversion counts onto the campaign form and Kanban cards in real time.
Sending is governed, not brute-forced. A configurable throttle (messages per minute/hour) plus scheduling via ir.cron and Odoo's automated actions spreads volume to respect Meta's rate limits and your quality rating. Every outbound message writes a status row that is reconciled from WhatsApp Cloud API delivery webhooks (queued → sent → delivered → read → replied/failed), giving you a defensible audit trail per contact.
Attribution is built in: trackable short links tag each click and tie downstream orders or leads back to the originating campaign, so you see cost-free channel ROI inside Odoo instead of guessing. Consent is treated as a compliance surface, not an afterthought — opt-in source, timestamp and opt-out (STOP) handling are stored on the contact and enforced before any send, keeping you aligned with WhatsApp Business policy and data-protection expectations.
Security is real Odoo security: access governed by ir.model.access.csv groups (Marketing User vs Marketing Manager) and record rules for multi-company / multi-team isolation. Reporting uses QWeb for campaign summary PDFs, and the whole module is reachable over XML-RPC/JSON-RPC for headless triggering from your other systems. It targets Odoo 17, 18 and 19 on both Community and Enterprise, and is delivered as clean, upgrade-safe module code you own.
Runs WhatsApp as a primary promotional channel and needs segmented blasts, scheduling and read/reply analytics in one place — without exporting contacts to a third-party blaster or losing attribution.
Wants campaign sends to draw directly from live crm.lead and sale.order filters and to see conversions attributed back to each campaign inside Odoo, feeding pipeline reporting instead of a disconnected tool.
Responsible for opt-in consent, STOP handling and audit trails; needs enforced consent checks and a per-message delivery log to stay within WhatsApp Business policy and data-protection rules.
Achetez la licence sur ecosire.com et téléchargez le module ZIP WhatsApp Marketing & Broadcast Campaigns depuis le tableau de bord de votre compte.
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez WhatsApp Marketing & Broadcast Campaigns et appuyez sur Installer.
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Segmented marketing blasts (vs one-to-one only) | Yes — campaign object with live CRM/sales segments | Possible but you design the data model yourself | Varies; many are conversational-only | |
| Audiences from live res.partner / crm.lead / sale.order filters | Yes, via saved ir.filters domains | Buildable with effort | ||
| Throttling & scheduling to respect Meta rate limits | Yes — ir.cron + configurable per-min/hour throttle | You implement and tune it | ||
| Delivery / read / reply status from Cloud API webhooks | Yes — per-message log reconciled from webhooks | You wire the webhooks yourself | ||
| Click & conversion attribution to campaign | Yes — trackable links tie orders/leads back | Significant extra build | ||
| Opt-in/opt-out consent enforcement & audit trail | Yes — enforced pre-send with STOP handling | You must design compliance logic | ||
| Fits your Odoo 17/18/19, Community or Enterprise | Yes — manifest pinned to your version/edition | Yes, if you maintain it | ||
| Built, installed & supported for you with a warranty window | Yes — full delivery + post-launch SLA | Your team owns all of it |
This is a build-to-order module, not an instant download. Typical delivery is 2 to 4 weeks from kickoff. Timing depends on scope, how many segments and templates you need, your WhatsApp Business template-approval turnaround (Meta reviews those), and whether we integrate with other systems. We confirm a firm timeline after a short scoping call and keep you updated at each milestone: build, staging demo, then production deployment.
Every engagement includes a defined post-launch support and warranty window with a bug-fix SLA and a documented change-request path. During that window we fix defects, adjust throttling or templates as your sending policy evolves, and keep the module compatible with your Odoo point releases. When you upgrade major Odoo versions (for example 18 to 19) or want new capabilities, we scope that as a follow-on. You own the source, so you are never locked in.
It runs on both Community and Enterprise across Odoo 17, 18 and 19. The module adds its own marketing objects rather than depending on Enterprise-only marketing apps, so Community users get the same segmentation, scheduling and analytics. We pin the __manifest__.py to your exact version and edition during the build.
Yes. Sending goes through the official WhatsApp Business Platform (Cloud API), so you need a Meta Business account, a verified WhatsApp Business phone number and approved message templates. You provide those credentials; we handle the integration, webhook wiring for delivery/read status, and template-variable mapping inside Odoo. Meta's own per-message and conversation pricing applies separately from our fee.
Consent is enforced at the data layer. We store opt-in source and timestamp on the contact, automatically process STOP-style opt-out replies, and hard-block any send to a non-consented or opted-out number before it reaches the queue. Suppression lists and E.164 validation run pre-send. This keeps you aligned with WhatsApp Business policy and gives you a per-contact audit trail.
That is the core design. Segments are resolved from live res.partner, crm.lead and sale.order records via saved filter domains (ir.filters), so a campaign audience is always the current matching set — for example customers who bought in the last 90 days or leads in a given stage. No CSV exports, and no stale lists.
Yes. Delivery, read, reply, click and conversion metrics are computed on the campaign record and shown on the form, Kanban and a QWeb PDF summary. Trackable links attribute clicks and downstream orders or leads back to the source campaign, so channel ROI is visible inside Odoo instead of a separate tool.
Segmented WhatsApp broadcast campaigns in Odoo with templates, scheduling, delivery analytics and opt-in compliance. Built, installed and supported by ECOSIRE.