OdooBots
Loading
Integration · WhatsApp

Odoo WhatsApp integration

In India a customer will read a WhatsApp message and ignore an email, which is why every business wants this integration. What most of them do not know before starting is that WhatsApp is not an open channel: outside a 24-hour window you may only send pre-approved templates.

That one rule shapes the whole design. Done properly, Odoo sends order updates, payment reminders and follow-ups that land where customers actually look, with every conversation attached to the record it belongs to.

Suresh BabuOdoo Solution Architect, 7+ years| Reviewed by Arun Kumar| Updated 20 October 2026| Covers Odoo 16–19, Community & Enterprise
0Odoo projects delivered
0Consultants & developers
24 hoursThe window that governs everything
ChennaiAmbattur, Tamil Nadu

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What is Odoo WhatsApp integration?

Odoo WhatsApp integration sends business messages from the record they belong to and keeps the reply attached to it. Order confirmations, despatch and delivery updates, invoice and payment reminders go out as approved templates, sales follow-up and support replies run inside the 24-hour service window, and the conversation is logged on the customer, the order or the ticket rather than living on someone’s phone.

The 24-hour window is the rule everything else follows. After a customer messages you, you may reply freely for 24 hours. Outside it, only templates Meta has approved will send — and approval takes time, so templates are drafted early in the project.

Business API
The official WhatsApp channel for businesses. Not WhatsApp Business app, and not an unofficial gateway.
Template
A pre-approved message with variables. The only thing you can send outside the service window.
24-hour window
The period after a customer message during which free-form replies are allowed.
Conversation pricing
Meta charges per conversation by category, not per message. It affects what is worth automating.
What syncs

What moves between WhatsApp and Odoo

Six kinds of message move between Odoo and WhatsApp, and all of them are governed by the same window rule.

Order and delivery updates

Confirmation, despatch and delivery messages sent as approved templates from the sales order, carrying the order number and tracking detail.

TemplatesTrackingOrder

Invoice and payment reminders

Reminders triggered from the invoice and its due date, so follow-up is a rule rather than something someone remembers.

Due dateRemindersInvoice

Sales follow-up

Messages from the CRM lead, logged on the opportunity so the next person to pick it up can see what was said.

LeadsLoggedPipeline

Support conversations

Helpdesk tickets raised or continued over WhatsApp, with the thread attached to the ticket and the SLA running as normal.

TicketsSLAThread

Inbound routing

An incoming message matched to the customer by number and routed to the right team, instead of arriving on one person’s handset.

MatchingRoutingTeams

Campaign messaging

Approved marketing templates to opted-in contacts, with the opt-out honoured and recorded on the contact.

Opt-inOpt-outMarketing
How it works

How a record travels between WhatsApp and Odoo

An order is confirmed and a template goes out with the order number. The customer replies to ask about delivery, which opens a 24-hour window in which your team can answer freely from the ticket or the order itself. Everything said is logged on the record. Days later, when the invoice falls due, a reminder template goes out because the window has closed and only templates can send.

Designing around that rule from the start is the difference between an integration that works and one that silently stops sending.

  • Templates drafted and submitted early, because approval takes time
  • Free-form replies only inside the 24-hour service window
  • Every message logged on the customer, order or ticket it came from
  • Inbound messages matched by number and routed to a team, not a person
  • Opt-out honoured and recorded, which is both policy and good practice
Odoo whatsapp integration showing synchronised records between the two systems
Connected systems — how whatsapp and Odoo share one set of records.
Expertise · how we work

What we settle in week one of an Odoo WhatsApp integration

These are the decisions that are cheap to make now and painful to reverse once two systems have been exchanging records for a month.

  1. Which number and account

    The business number, its Meta Business verification and who controls the account. This blocks more projects than any technical step.

  2. Which messages are templates

    Every message sent outside a customer-initiated window needs an approved template, so the list is drafted and submitted in week one.

  3. Who answers, and where

    Whether replies are handled in Helpdesk, CRM or Discuss, and by which team. Without this, conversations land nowhere.

  4. Opt-in and opt-out handling

    How consent is recorded and how an opt-out is honoured across every message type, not just marketing.

  5. Number matching rules

    How an incoming number finds its contact, including country code variations and shared family numbers.

  6. What is worth automating

    Meta charges per conversation by category, so the message list is chosen on value rather than on what is technically possible.

  7. Escalation path

    What happens when a customer asks something the template flow does not cover, so nobody is left waiting inside the window.

Honest advice

Where an Odoo WhatsApp integration needs work

We would rather say this before you buy licences than after. Below is what the connector genuinely does not reach, where we scope development, and where we would tell you to keep the other system as it is.

  • WhatsApp Business app — The free app on a phone is a different product. The integration needs the Business API, which means verification and a provider.
  • Unofficial gateways — Unofficial automation risks the number being banned. We will not build on one, and we will say so rather than quote for it.
  • Free-form messaging outside the window — This is a Meta policy, not a configuration limit. No integration can get around it.
  • Template approval time — Templates are reviewed by Meta and can be rejected. The timeline is outside our control, which is why drafting starts early.
  • Rich interactive flows — Multi-step interactive flows and catalogue messages are possible but go beyond standard configuration into scoped development.
  • Per-conversation cost — Messaging is charged by Meta per conversation. High-volume campaigns have a real running cost that belongs in the business case.
Odoo whatsapp integration configuration showing field mapping and sync direction
Where it needs work — the parts that are development rather than configuration.
Our services

Our Odoo WhatsApp integration process

Connecting WhatsApp to Odoo is less about the connector than about agreeing what is true where, and what happens when a record will not go through.

  1. What you are connecting

    Understand which number you will use, who controls the Meta Business account, which messages you want to send and who will answer replies.

  2. Field and direction mapping

    Draft and submit the template list early, agree where replies are handled and how numbers match contacts, before anything is connected.

  3. Build and configure

    Connect WhatsApp to Odoo using the standard connector where one fits, and build only what the connector genuinely cannot reach. See Odoo customization.

  4. Test with your own data

    Your records, in a test database, including the awkward ones — the cancelled order, the partial refund, the product that exists on one side only.

  5. Error handling and alerts

    A queue for failed records with a named owner and an alert, because an integration nobody watches diverges quietly and the divergence is found at audit.

  6. Go-live and monitoring

    Cutover with a reconciliation on both sides, then hypercare, then ongoing support and AMC.

Trust · what it costs

What an Odoo WhatsApp integration costs

We do not publish one integration price, because the same connector costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.

  • Template countEach message type is its own template, drafted and submitted for approval.
  • Where replies landHelpdesk, CRM or both changes the routing configuration.
  • Account verification stateAn unverified Meta Business account delays everything and is worth starting first.
  • Automation depthTriggered reminders across orders, invoices and tickets add rules.
  • Interactive flowsMulti-step flows and catalogue messages are scoped development.
  • Message volumeMeta charges per conversation, which is a running cost rather than a project cost.
Why us

Why choose OdooBots for your Odoo WhatsApp integration

We start by drafting your templates and checking your Meta Business verification, because those two block go-live far more often than anything technical. And we will not build on an unofficial gateway, however cheap, because a banned number costs more than the saving.

Based inAmbattur, ChennaiTamil Nadu 600053, India
Phone+91 98414 81435Mon–Sat, business hours IST
Delivered630+ Odoo projects30+ consultants and developers
Versions supportedOdoo 16 – 19Community and Enterprise
FAQ

Odoo WhatsApp integration: frequently asked questions

Why should I integrate WhatsApp with Odoo ERP?
Because customers read WhatsApp and ignore email, so order updates, delivery notifications and payment reminders actually land. Sending them from Odoo means the message carries the real order or invoice detail and the conversation stays attached to the record rather than living on an employee’s phone.
Does the integration support the WhatsApp Business API?
Yes, and it requires it. The free WhatsApp Business app on a phone is a different product and cannot be integrated properly. The Business API needs Meta Business verification and a provider, which is the first thing we check in a project.
Can WhatsApp messages be sent automatically from Odoo?
Yes, as approved templates triggered by events — order confirmed, despatched, invoice due. Outside a 24-hour customer-initiated window only approved templates can send, so the template list is drafted and submitted early because Meta approval takes time.
What is the 24-hour window?
After a customer messages you, your team can reply freely for 24 hours. Once it closes, only pre-approved templates will send. This is Meta policy rather than a configuration limit, and it shapes the whole design of the integration.
Can customer conversations be synchronised with Odoo?
Yes. Incoming messages are matched to the contact by number and routed to the right team, with the thread logged on the customer, the order or the helpdesk ticket, so the next person to pick it up can see what was already said.
Can we use an unofficial WhatsApp gateway instead?
We will not build on one. Unofficial automation risks the number being banned, and losing a business number costs far more than the licence saving. We would rather lose the enquiry than set up something that fails that way.
What does WhatsApp messaging cost to run?
Meta charges per conversation by category, not per message, so it is an ongoing running cost rather than a one-off project cost. That is why we choose which messages are worth automating on value rather than on what is technically possible.
Is the Odoo WhatsApp integration customisable?
Yes. Templates, triggers and routing are configured to your process, and richer interactive flows or catalogue messages are scoped as development where they genuinely add value. See Odoo customization.
References

Sources and official documentation

Product capabilities stated on this page are documented by Odoo. The mapping advice, failure handling and limitations come from our own integrations.

Ready to connect WhatsApp to Odoo?

Tell us whether your Meta Business account is already verified and which messages you want to send. Those two answers decide the timeline, and the diagnosis call is free.