Send WhatsApp Message

Name: Send WhatsApp Message
Brand: ECOSIRE
SKU: send-whatsapp-message

Características clave

`whatsapp.message` model storing direction, partner, template, provider message id, and a lifecycle `state` (`queued`/`sent`/`delivered`/`read`/`failed`)

`whatsapp.template` model mapping your pre-approved WhatsApp Business templates to Odoo, with per-template placeholder variables

Placeholder rendering that resolves variables from the source record at send time (customer name, order ref, amount, due date) via the ORM

"Send on WhatsApp" action buttons wired onto `sale.order`, `account.move`, `stock.picking`, and `helpdesk.ticket` (scope-dependent)

Every send posts to the record's `mail.thread` chatter, so the conversation is visible in context to the whole team

Queued outbound delivery via an `ir.cron` job and job queue, so a slow provider API never blocks the user's session

Inbound webhook controller that ingests delivery/read receipts and customer replies and updates message `state`

Provider-agnostic REST client layer so your WhatsApp Business API vendor can be swapped without rewriting business logic

Optional automated actions (`base.automation`) to fire a message on order confirmation, invoice posting, or delivery validation

`ir.model.access.csv` plus record rules restricting message visibility to partners a user is allowed to access

QWeb message preview so users see the fully-rendered text before sending

Attachment support to send PDF quotations, invoices, and QWeb reports as WhatsApp documents

Full XML-RPC/JSON-RPC API surface so external systems can queue messages programmatically

Retry-and-log handling for failed sends, with the failure reason stored on the message and surfaced in chatter

Compatible with Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise

Hecho a medida, listo para ti

Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.

Haces el pedido

Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.

Creamos e instalamos

ECOSIRE la crea, la configura y la instala en tu Odoo.

En marcha + soporte

Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.

Sobre este producto

Most teams running Odoo already talk to customers on WhatsApp, but that conversation lives entirely outside the ERP — copied by hand from a phone, untracked against the order, and invisible to the rest of the team. Odoo core can email a quotation or an invoice, and it will queue an SMS if you buy IAP credits, but there is no native way to send a WhatsApp message from a sale.order or an account.move, no delivery-status feedback, and no record of the exchange in the document's chatter. In Odoo Community there is no first-party WhatsApp channel at all, and even where a WhatsApp connector ships in Enterprise it is tied to one specific business-account setup that many teams cannot adopt as-is. The result is duplicated effort, missed follow-ups, and customer replies that never make it back into the CRM.

We build a WhatsApp messaging integration tailored to your Odoo instance and your chosen WhatsApp Business API provider. At the core is a whatsapp.message model (models.Model) that stores each outbound and inbound message, its template, recipient partner, provider message id, and a state field (queued, sent, delivered, read, failed) kept current by provider webhooks. A whatsapp.template model maps your pre-approved WhatsApp message templates into Odoo, with placeholder variables resolved from the source record at send time (for example the customer name, order reference, or total from a sale.order). Send actions are wired onto the models you actually use — a "Send on WhatsApp" button on quotations, invoices, delivery orders, and helpdesk tickets — and each send posts a message into the record's mail.thread chatter so the whole team sees the history in context.

Technically the module is a proper Odoo addon: a clean __manifest__.py declaring dependencies (mail, contacts, and sale/account/stock as your scope requires), models and OWL/XML views, QWeb-rendered message previews, and security via ir.model.access.csv plus record rules so users only see conversations for partners they are allowed to access. Outbound delivery goes through the provider's REST API from a queued ir.cron job (so a slow provider never blocks the user), inbound replies and status callbacks are handled by a controller endpoint, and everything is reachable over Odoo's own XML-RPC/JSON-RPC API for automation. Optional automated actions can trigger a WhatsApp message on an event — order confirmed, invoice posted, delivery validated — without anyone clicking a button. We support Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise.

Because this is build-to-order, nothing ships until we have agreed the exact scope on a short call: which records send messages, which templates and provider you use, and how replies should be routed. From confirmed scope, typical delivery is 2–4 weeks — we build on a staging copy of your database, run UAT with you, then install on production with a rollback plan and hand over the git repository. Pricing starts from $249 (indicative, single-company base scope); additional integrations (multiple provider accounts, extra Odoo models, two-way conversation routing, or multi-company/multi-brand number handling) increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.

lo que obtienes

Installable source code for your Odoo version (17.0, 18.0, or 19.0) as a self-contained addon

Installation and configuration on your environment, including provider credentials and webhook wiring

Technical documentation: model reference, manifest, security rules, and webhook/API contract

User guide plus a live training session for your team

Post-go-live support window for defect fixes and questions

UAT on a staging copy of your database with sign-off before production install

Rollback plan and a clean production install once UAT passes

Handover of the git repository with full commit history

¿Para quién es esto?

Sales team on Odoo

Reps who send quotations and follow-ups and want customers to reply on WhatsApp — with every message logged against the `sale.order` so nothing is lost when a rep is out.

Customer support / helpdesk lead

Runs support out of Odoo Helpdesk and needs inbound and outbound WhatsApp threaded onto the ticket, with delivery and read receipts, instead of a separate phone.

Finance / AR team

Sends invoices and payment reminders and wants a WhatsApp nudge from `account.move` with the PDF attached, tracked so they know which reminders were delivered and read.

Operations / IT manager

Owns the Odoo instance and wants one governed integration with proper access rules and a provider they control, rather than staff messaging customers from personal phones.

Cómo se compara Send WhatsApp Message

Criterio	ECOSIRE	Construcción personalizada	Competidor
Send WhatsApp from an Odoo record	Built-in button on the models you use (sales, invoices, deliveries, tickets)	Possible, but you design and build the whole flow yourself	Often only on selected models, hard to extend
Conversation logged in chatter	Every message posts to the record's `mail.thread`	Only if you build the chatter integration	Varies; sometimes a separate log, not chatter
Delivery & read receipts	Webhook-driven `state` (sent/delivered/read/failed)	You must build the webhook and state machine	Sometimes, depending on the module
Odoo Community support	Fully supported on Community and Enterprise	Whatever you build	Frequently Enterprise-only or account-locked
Fit to your provider & templates	Built around your provider and approved templates	Fully custom, but at full custom cost	Fixed to the vendor's assumptions
Access control	`ir.model.access.csv` + record rules per partner	You define and test it	Basic or none
Ownership & handover	Git repo handover, source is yours	You own it, you maintain it	Licensed module, limited source control
Time & effort to live	2–4 weeks, we build/install/support	Months of in-house dev and testing	Fast install but rework to fit your process

Preguntas frecuentes sobre Send WhatsApp Message

Is this an app I can download and install right now?

No. This is a build-to-order integration — we build it against your Odoo version and your WhatsApp Business API provider, then install and support it. There is no instant download; you request a quotation and we deliver a module made for your setup.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. Once we have agreed which records send messages, which templates and provider you use, and how replies are routed, we build on a staging copy, run UAT with you, then install on production.

Do I need my own WhatsApp Business API account?

Yes. WhatsApp Business messaging is sent through a provider (the WhatsApp Business API / Cloud API), and message templates must be pre-approved by WhatsApp. We integrate with the provider and account you use; we can advise during scoping, but the account and approved templates are yours.

Which Odoo versions and editions do you support?

Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Because Community has no native WhatsApp channel, the integration is especially useful there, but it works cleanly on Enterprise too.

How does pricing and scoping work?

Pricing starts from $249 as an indicative single-company base scope. Drivers like multiple provider accounts, extra Odoo models, two-way conversation routing, or multi-company number handling increase the scope. After a short scoping call you receive a fixed quote — no surprise charges.

What about support and updates after go-live?

Every build includes a post-go-live support window for defect fixes and questions, and we hand over the git repository. Ongoing support, enhancements, and version upgrades (for example moving from 18.0 to 19.0) can be arranged as a separate agreement.

Will the conversation be visible inside Odoo records?

Yes. Each message is posted into the record's `mail.thread` chatter and stored on a `whatsapp.message` record with its delivery state, so your team sees the full history in context on the quotation, invoice, or ticket — not on someone's personal phone.