WhatsApp is where Indian customers actually reply. Odoo is where the order, the invoice and the support ticket already live. Odoo and whatsapp integration joins the two, so a confirmed order, a posted invoice or a dispatched delivery fires a message on the channel people open within minutes. This guide covers how the connection works, what the official Business API permits, what it costs in India, and the consent rules that keep your business number alive.
📋 Key Takeaways
- The connection runs on the official WhatsApp Business API through Meta or a provider such as Gupshup, Wati or Twilio. Recent Odoo Enterprise releases include a native module.
- Allowed traffic is approved templates for order updates, invoices, receipts and delivery alerts, plus free text replies inside the 24 hour window a customer opens.
- Blocked traffic is promotional blasts, messages to contacts who never agreed, and any unofficial automation tool. All three risk a permanent ban.
- Budget roughly ₹2,000 to ₹5,000 a month for 500 to 2,000 notifications, plus a one time setup for template design and Odoo automation rules.
- Start transactional. Add consented sales follow up later. Marketing templates belong at the end of the rollout, never the beginning.
📑 Table of Contents
- What Odoo and WhatsApp Integration Actually Does
- Official API Versus Unofficial Tools
- Order and Invoice Notifications
- Sales Follow Up From CRM
- Support Conversations Inside Odoo
- Template Approval and Messaging Rules
- Consent and Compliance
- What Odoo and WhatsApp Integration Costs in India
- Misuse That Gets Numbers Banned
- Rollout Checklist
- Frequently Asked Questions
What Odoo and WhatsApp Integration Actually Does
Without it, a sales executive copies order details out of Odoo, pastes them into a phone and forgets to log anything. The customer replies on WhatsApp and the Odoo record stays blank.
The gap it closes
- Reach. WhatsApp open rates in India sit around 85 to 95 percent, against 15 to 25 percent for email.
- Automation. Confirming a sales order, posting an invoice or validating a delivery can each trigger a message without anyone touching a phone.
- Visibility. The conversation attaches to the customer record, so the next person to open that order sees the full history.
- Context. It behaves like any other connector in the stack, and the same scoping questions apply as in a wider Odoo integration project.
Official API Versus Unofficial Tools
The official WhatsApp Business API
- Supplied by Meta, usually through a Business Solution Provider such as Gupshup, Wati, Twilio or 360dialog.
- Requires a verified business account inside Meta Business Manager.
- Supports approved templates, media attachments such as invoice PDFs and interactive buttons.
- Recent Odoo Enterprise releases connect natively, so credentials and templates are managed from inside the system.
Tools worth avoiding
- Browser automation that drives WhatsApp Web through scripts or extensions, and unofficial libraries that reverse engineer the protocol.
- App store modules that never name their API method. If the listing does not say official Business API through an approved provider, assume it is not.
- Why it matters. Meta detects this traffic and disables numbers without warning. There is no dependable appeal.
A banned number is not only a technical problem. Customers, vendors and staff all reach you on it, and the saving from an unofficial tool never covers losing it.
Order and Invoice Notifications
Transactional alerts are the safest place to begin because customers want them and block rates stay near zero.
Messages worth automating first
- Order confirmation. A confirmed sales order sends the order number, total and expected delivery date.
- Invoice delivery. A posted invoice sends the PDF straight to the phone instead of burying it in a mailbox nobody opens, which shortens the whole Odoo invoicing cycle.
- Payment receipt. Recording a payment sends confirmation immediately, which matters for business customers who need proof before the next order.
- Delivery alert. Validating a delivery order sends the carrier name and tracking number as a tappable link.
- Online store updates. Teams running Odoo eCommerce can replace or supplement email across the whole order lifecycle.
Sales Follow Up From CRM
How the pipeline changes
- Quotation delivery. Rather than emailing a PDF, the salesperson sends a link to the online quotation, which the customer can accept from the browser.
- Reminders. A quotation left unopened for two days can trigger an approved reminder template automatically instead of relying on memory.
- Nurture messages. Catalogues and event invitations count as marketing, so they need recorded consent first.
- One timeline. Inside Odoo CRM, the WhatsApp thread sits alongside emails, calls and internal notes on the same opportunity.
Sales templates need approval too. You cannot send free text outside the 24 hour customer window. Even a line saying a quotation is ready must be cleared before Odoo can fire it.
Support Conversations Inside Odoo
What agents actually see
- Inbound messages. A customer question lands in Discuss or opens a Helpdesk ticket carrying the name, number and message body.
- The 24 hour window. Once a customer writes to you, free text replies are allowed for 24 hours. Ask questions, send screenshots and close the issue conversationally. After that, only templates.
- Routing. Messages can be split by topic, segment or agent availability.
- Continuity. Because the thread lives on the record rather than a personal handset, Odoo support and maintenance stays measurable.
Template Approval and Messaging Rules
How templates work
- When they are required. Any message your business starts, rather than one you send in reply, must use an approved template.
- Submission. Write the message with numbered placeholders, submit through Business Manager or your provider dashboard, and expect a decision within two days.
- Approval criteria. Templates must identify the business clearly and placeholders cannot smuggle promotional wording into a transactional template.
- Categories. Utility covers order updates and receipts, authentication covers verification codes, marketing covers offers. Pricing and scrutiny differ by category.
Rules to design around
- Business initiated. Approved templates only, charged per conversation window.
- Customer initiated. Free text for 24 hours, then templates again. The first 1,000 of these conversations each month carry no charge.
- No cold messaging. Contacting a number that never agreed is a policy breach enforced through account action, not an error message.
Consent and Compliance
What you need before the first send
- Explicit agreement. A ticked box on your form, a message from the customer, or a documented verbal yes. A purchased list is never consent.
- A way out. Marketing templates need an unsubscribe instruction, honoured the same day.
- Matching scope. Agreement to receive order updates does not extend to promotional offers. Keep the two consents separate in your contact data.
- Records. Store when and how each contact agreed. Meta asks for this during quality reviews.
- Where it lives. Consent flags usually need a field and a rule of their own, which is standard work under Odoo customization services.
What Odoo and WhatsApp Integration Costs in India
Meta charges per conversation window
- Marketing. Roughly ₹0.65 to ₹0.80 per conversation.
- Utility. Roughly ₹0.30 to ₹0.40 per conversation.
- Authentication. Roughly ₹0.25 to ₹0.35 per conversation.
- Service. First 1,000 customer started conversations each month are free, then roughly ₹0.25 to ₹0.35.
- A conversation is a 24 hour window, so several messages inside it still count once.
Provider and setup costs on top
- Platform fee of ₹1,000 to ₹10,000 a month depending on the provider and plan.
- Markup of ₹0.10 to ₹0.30 per message above the Meta charge.
- One time configuration, template writing and Odoo automation rules, commonly ₹20,000 to ₹80,000.
Realistic monthly spend
- Small volume. 200 to 500 notifications lands near ₹500 to ₹2,000.
- Mid volume. 500 to 2,000 notifications lands near ₹2,000 to ₹5,000.
- High volume. 2,000 to 10,000 notifications lands near ₹5,000 to ₹15,000.
- Against faster payments and fewer status calls, this is a cheap line in an ERP budget.
Misuse That Gets Numbers Banned
The common triggers
- Bulk sends without consent. Importing a list and blasting offers is the single most frequent cause of restricted numbers in India.
- Unofficial automation. Extensions, bots and reverse engineered libraries are detected and acted on quickly.
- Blocks and reports. When recipients block you, your quality rating falls and sending limits drop.
- Category abuse. Pushing offers through a template approved as utility invites revocation and account review.
Recovery is not something you can plan around. Appeals are slow and rarely succeed. Consent, official access and weekly quality monitoring are the only dependable protection.
Rollout Checklist
Confirm before going live
- Business account verified in Meta Business Manager.
- Provider chosen and connected, or the native Enterprise module configured with valid credentials.
- Templates written, submitted and approved for every use case you plan to send.
- Consent capture built into your web form or sales process, stored on the contact.
- Test messages sent internally to check formatting, placeholders and PDF attachments.
- Support routing decided, so inbound messages create tickets and reach a named owner.
Sequence matters more than scope. Ship order confirmations, invoices and delivery alerts first. Once block rates hold near zero for a month, add consented sales follow up. Marketing templates come last.
WhatsApp and Odoo
Want WhatsApp Messages Firing Straight From Odoo?
Tatvamasi Labs sets up the official Business API, writes and submits your templates, wires the automation rules and builds consent handling in from day one.
Talk to Our TeamFrequently Asked Questions
Yes. Odoo and WhatsApp integration runs on the official WhatsApp Business API from Meta, either directly or through a provider such as Gupshup, Wati or Twilio. Recent Odoo Enterprise releases ship a native module. Community edition needs a verified third party module or a custom connector.
Meta bills per conversation window rather than per message. Utility conversations sit near ₹0.30 to ₹0.40 and marketing near ₹0.65 to ₹0.80. Providers add ₹1,000 to ₹10,000 a month plus a small markup, so 500 to 2,000 notifications usually lands between ₹2,000 and ₹5,000.
Approved templates only, covering order confirmations, invoice PDFs, delivery updates, payment receipts and quotation links. Free text replies are allowed only inside the 24 hour window that opens when a customer messages you first.
Only with recorded consent and a marketing template approved by Meta. Blasting a purchased list breaches WhatsApp Business Policy and is the fastest route to a restricted number. Keep transactional and promotional consent separate.
Messaging capability is restricted or switched off and message history goes with it. Appeals are slow and rarely successful. Usual triggers are high block rates and unofficial automation tools. Prevention is far cheaper than recovery.
Enterprise is easier because the module is built in and maintained by Odoo. Community works too, but someone has to own updates when the API changes. Budget for that maintenance either way.
Yes. Incoming messages can land in Discuss or open a Helpdesk ticket carrying the sender name and message body. Agents reply from inside Odoo and the thread stays on the customer record.
Two to four weeks for a standard rollout. Business verification with Meta is the slow part. Template writing, approval, automation rules and testing normally take a week once the account is live.
Prefer a quick chat? Message our Odoo team on WhatsApp.
CHAT ON WHATSAPP
