Odoo WhatsApp Integration India 2026: Setup & Cost
You connect WhatsApp to Odoo by attaching a WhatsApp Business API (Cloud API) account from Meta to your Odoo database, either through Odoo's own WhatsApp module or through a Business Solution Provider that sits between Odoo and Meta. On the software side the integration can start at zero in India: RichAutomate charges Rs 0 setup and Rs 0 monthly platform floor, and you pay only per message, while Meta bills its own conversation charges by category.
That is the short answer. The longer answer matters because Odoo teams usually discover the real work is not the connector at all, it is the Meta side: a WhatsApp Business API account, a verified business, and an approved message template for every business-initiated message. This guide covers what you need, the two ways to wire it up, an honest comparison of the native module against a BSP-backed setup, and what the whole thing actually costs in 2026.
What you need before Odoo can send a single WhatsApp message
WhatsApp is not an SMTP server. You cannot point Odoo at a phone number and start sending order confirmations. Officially, an Odoo WhatsApp integration requires four things in place:
- A WhatsApp Business API (Cloud API) account created under a Meta App and a WhatsApp Business Account (WABA). The consumer WhatsApp app and the free WhatsApp Business app cannot be integrated with Odoo.
- A dedicated phone number that is not currently active on any WhatsApp app. Once it joins the API it leaves the mobile app permanently.
- Meta business verification for your legal entity, which in India means matching company documents, GST details and a public business presence. Our walkthrough of Meta business verification for WhatsApp in India covers the document list and the usual rejection reasons.
- Approved message templates for anything you initiate: invoices, delivery updates, payment reminders, quotations. Meta reviews each template, approval is never guaranteed, so keep a fallback for rejected copy.
Only replies inside an open 24-hour customer service window can be free-form. Everything Odoo pushes out on its own schedule is a template message.
Two ways to connect Odoo to WhatsApp
The first route is Odoo's native WhatsApp module, shipped with recent Odoo versions on the paid Online and Enterprise editions. You create your own Meta App, paste the App ID, App Secret, phone number ID and access token into Odoo, register a webhook URL, and Odoo talks to Meta directly. Templates are drafted in Odoo and submitted to Meta for approval. Odoo Community, the free open-source edition, does not ship this module, so most Community users take the second route.
The second route is Odoo plus a Business Solution Provider such as RichAutomate. The BSP holds the Meta integration and handles WABA onboarding, template submission, webhook plumbing and delivery retries, then exposes a REST API plus a shared inbox. Odoo calls the BSP through an automated action, a scheduled action, or a small custom module on the record events you care about: sale order confirmed, invoice posted, delivery validated, payment received.
Neither route is wrong. The native module is tidy if all you want is a WhatsApp send button on an Odoo record. The BSP route wins the moment marketing, support agents, chatbots or non-Odoo channels enter the picture.
Odoo native WhatsApp module vs Odoo + RichAutomate
| Capability | Odoo native WhatsApp module | Odoo + RichAutomate |
|---|---|---|
| Template management | Drafted inside Odoo and submitted to Meta from Odoo, with limited component support | Template builder with buttons, media headers and variables, plus status tracking and re-submission |
| Campaigns and broadcasts | Not a campaign tool; sends are record-driven, one document at a time | Segmented broadcast campaigns with scheduling, throttling, opt-out handling and per-campaign reporting |
| Chatbot and flows | None; inbound messages land in chatter and wait for a human | Visual flow builder plus Meta Native Flows for in-chat forms, qualification and routing |
| Multi-agent inbox | Chatter tied to the Odoo record; no queue, assignment or SLA view | Shared team inbox with assignment, tags, notes, canned replies and 24-hour window tracking |
| Per-message cost | No platform fee from Odoo; Meta bills you directly | Client Pay: Rs 0.10 per message plus Meta billed to your own Meta account. SaaS Pay: Rs 1.20 per marketing message, Rs 0.30 per utility or authentication message, all-inclusive |
| Setup cost | No connector fee, but it requires a paid Odoo Online or Enterprise subscription | Rs 0 setup, Rs 0 monthly platform floor, 14-day free trial with 100 free credits |
| Meta approval handling | Self-serve: you create the App and the WABA and chase verification yourself | Guided onboarding, template review support and rejection diagnostics, though Meta always makes the final call |
Want to model your own volumes before committing? Run your monthly send mix through the WhatsApp API cost calculator and compare both billing modes side by side.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Setting up the integration, step by step
The sequence is the same for either route. Only the destination of the credentials changes.
- Create the Meta assets. A Meta Business account, a Meta App with the WhatsApp product added, and a WhatsApp Business Account. Start business verification early, because it is the slowest step.
- Attach and verify the phone number. Use a number with no active WhatsApp account. Complete OTP verification and set the display name, which Meta also reviews.
- Wire the credentials. For the native module, paste the App ID, App Secret, phone number ID and a permanent access token into Odoo's WhatsApp Business Account form, then copy Odoo's callback URL and verify token into Meta's webhook configuration. For the BSP route, connect the WABA once inside RichAutomate and use an API key from Odoo instead.
- Build and submit templates. Map each Odoo document to a template: order confirmation, proforma invoice, dispatch note, payment reminder, feedback request. Keep variables minimal and the copy transactional, since promotional wording inside a utility template is the most common rejection cause.
- Trigger from Odoo. Native: the WhatsApp send button on the model. BSP: an Odoo automated action or server action fires an HTTP request on state change, so Sales, Accounting, Inventory and Helpdesk each get their own trigger.
- Test on a real handset with a live template before switching anything on for customers, and confirm delivery statuses flow back into your records.
If you also run Tally alongside Odoo for statutory books, the same template and trigger logic applies there; the Tally WhatsApp integration guide covers that side of the stack.
Common mistakes to avoid
- Using a number already on WhatsApp. Migrating it removes the app from that phone, so plan a cutover instead of surprising your sales team.
- Marketing copy inside utility templates. It gets rejected or recategorised, and a recategorised message costs more.
- Skipping opt-in. Meta requires it, and unsolicited bulk sends drive blocks and quality-rating drops. No provider can promise immunity from restrictions, and anyone who does is selling you a story.
- No delivery-status handling. Without webhooks flowing back, Odoo will happily show "sent" for messages that never arrived.
- Ignoring the display name and verification path. How your business appears on the customer's screen affects reply rates more than most teams expect.
What Odoo WhatsApp integration costs in India in 2026
There are three separate cost lines, and mixing them up is why quotes look wildly different.
Odoo itself. Odoo Community is free and open source. Odoo Online and Enterprise are paid per-user subscriptions, and the native WhatsApp module belongs to those paid editions. Price your Odoo plan with Odoo directly.
The platform layer. RichAutomate is usage-only: Rs 0 setup and no monthly platform floor. In Client Pay, you pay Rs 0.10 per message as the platform fee and Meta's conversation charges go straight to your own Meta account. In SaaS Pay, everything is bundled: Rs 1.20 per marketing message and Rs 0.30 per utility or authentication message. A 14-day free trial with 100 free credits lets you validate the Odoo triggers before spending anything.
Meta's conversation charges. Meta bills per 24-hour conversation by category: marketing, utility, authentication and service. Rates change and vary by country, so treat them as a live input rather than a fixed line item. The breakdown in our WhatsApp Business API cost guide for India explains how the categories behave and which one your Odoo messages will fall into.
For a typical Indian SME sending order and dispatch updates from Odoo, almost every message is utility, which is the cheapest category on both sides of the bill. Marketing volume is what actually moves the number.
Where Odoo plus WhatsApp actually pays off
The integrations that survive past month three are the boring, high-frequency ones. Sales quotations delivered as a PDF on WhatsApp instead of an ignored email. Invoice and payment reminders fired from Accounting on the due date with a payment link button. Dispatch and delivery updates from Inventory. Service appointment reminders from Field Service or Helpdesk. Post-delivery feedback requests that feed straight back into the CRM.
Two things separate the winners. Replies land somewhere a human can see them, and every send respects the 24-hour window rules. A one-way integration that pushes notifications into a void frustrates customers who reply and hear nothing back, which is exactly the gap a shared agent inbox closes.
Getting started
If your Odoo instance is Enterprise and you only need a send button on a handful of records, the native module is the shortest path. If you need campaigns, chatbots, a real agent inbox, or you are on Odoo Community, put a BSP in front of Meta and let Odoo call it. Start on the 14-day free trial with 100 free credits, wire one trigger such as invoice posted, and watch the replies land before you scale it up. Full per-message rates for both billing modes are on the RichAutomate WhatsApp API pricing page.