Most teams that run Odoo end up managing WhatsApp conversations in a completely separate place — a phone, a browser tab, a shared inbox no one really owns — while their customers, orders, and tickets all live in Odoo. Replies get lost, context is copy-pasted by hand, and there is no audit trail linking a message thread back to the res.partner, sale order, or helpdesk.ticket it belongs to. Odoo core gives you Discuss plus email and SMS gateways, but out of the box it has no native two-way WhatsApp channel in Community, and the Enterprise offering is coupled to specific plans and providers. When you want inbound messages, chatbot automation, and support routing all threaded into the ERP your team already lives in, native Odoo runs out of road.

The Open WhatsApp Connector is a build-to-order Odoo module that ECOSIRE scopes, builds, and installs for you. Technically it introduces a set of custom models — a WhatsApp account/channel configuration, message and template records, and a conversation link — wired into Odoo's mail framework so every inbound and outbound message lands as a threaded conversation inside Discuss. Incoming webhooks from your chosen WhatsApp Business API provider hit an authenticated controller endpoint that verifies the payload signature, deduplicates by provider message id, resolves or creates the matching res.partner, and posts the message onto the correct discuss.channel or the relevant record's chatter via message_post. Outbound sends go through a provider service layer with retries and delivery/read status callbacks, and are queued so a slow provider never blocks a user's UI.

On top of the transport we build the automation you actually need: a lightweight chatbot/flow engine driven by automated actions and server actions so keyword triggers, menu trees, and business-hours routing can be configured without redeploying code; template management that mirrors your approved WhatsApp message templates with parameter mapping; and support routing that turns an inbound conversation into (or attaches it to) a helpdesk.ticket, CRM lead, or sales follow-up. Everything respects Odoo's security model — access is governed by ir.model.access.csv and record rules so agents only see their teams' conversations, and multi-company setups keep each company's WhatsApp number and threads isolated. It ships as a proper module with a clean __manifest__.py, OWL/XML views, and QWuBE-free QWeb where reports are needed, and it is built and tested against Odoo 17.0, 18.0, and 19.0 (Community or Enterprise).

Because this is made to order, delivery follows a clear path: a scoping call to confirm your provider, numbers, volumes, and automation rules; a fixed written quote; build on an isolated branch; UAT on a staging database with your real templates and test numbers; then production install with a short hypercare window. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional numbers, multi-company routing, deeper chatbot flows, extra integrations (CRM, Helpdesk, eCommerce), and higher message volumes increase the quoted scope. You receive a fixed price after the scoping call — never a surprise.