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 one working week — 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 $999 (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.