Odoo and the WhatsApp Business API

Enterprise only

Verified against the Odoo 19 source: the whatsapp module is in the Enterprise addons and absent from Community.

So a Community deployment cannot enable this natively. The options become a third-party app from the Apps Store or a custom build against the WhatsApp Business API, and both carry the maintenance question that a first-party module does not.

For a business where WhatsApp is a primary customer channel, this is worth weighing as an edition decision rather than as an integration decision.

It is not SMS with better formatting

The platform rules are the substance of this integration, and they have no equivalent in email or SMS.

Templates. A business-initiated message, outside an open conversation, must use a template approved by Meta in advance. You submit the wording with placeholders, it is reviewed, and only then can you send it. Templates can be rejected, and changing one means resubmitting.

The practical consequence: outbound messaging has to be planned. You cannot decide on Tuesday to send a message with new wording on Wednesday. Campaign and transactional flows both need their templates in place before the flow goes live.

The service window. When a customer messages you, a window opens during which you can reply freely, without a template. Once it closes, reaching them again needs an approved template.

This reshapes support design. A conversation that pauses overnight may need a template to resume, so a workflow assuming a support agent can simply pick a thread back up the next morning will not behave as expected.

Opt-in. Customers must have agreed to be contacted, and the standard is stricter than for email. Model consent explicitly and check it at send time.

Sender identity and setup

A WhatsApp Business account needs a verified business and a phone number dedicated to it. The number cannot also be used in the normal WhatsApp app, which surprises businesses intending to use the number staff already answer.

Business verification takes time and requires documentation. Start it early, because it frequently becomes the critical path on a launch date set from the technical work alone.

Costs work differently

WhatsApp is priced by conversation rather than by message, in categories that differ in rate, and the rules change periodically.

Two things follow. Cost estimates built on message counts will be wrong, because a conversation covers multiple messages within a period. And an automation that opens conversations frequently is more expensive than one that batches, which is the opposite of the intuition carried over from SMS.

Designing flows that fit the rules

Transactional notifications are the natural fit: order confirmed, shipped, out for delivery. Templated, expected, and genuinely more useful on WhatsApp than in email for many audiences.

Support conversations work well inside the service window and need care at its edges. Design for the window closing rather than treating it as an edge case.

Marketing is where businesses get into trouble. Templates limit what you can say, the opt-in standard is high, and users report unwanted messages readily, which affects your account quality rating and eventually your ability to send at all.

That rating is the thing to protect. Unlike email, where a poor sender reputation degrades deliverability gradually, WhatsApp account quality can result in restrictions on messaging volume.

If you build it yourself

The same discipline as any other channel, plus the platform rules.

Send asynchronously, never inside a user's save. Consume delivery and read webhooks, because handing a message to the API is not evidence it arrived. Store the message id for idempotency and investigation. Normalise phone numbers to a consistent international format.

And model templates as data in Odoo, matching what is approved on the Meta side, so a template that was rejected or edited upstream is visible rather than failing at send time. The general patterns are in integration architecture, and the same asynchronous send rules apply as for Twilio.