Odoo Development 21 October 2026

How to Integrate WhatsApp with Odoo: A Complete Guide for Businesses

Key takeaways:

  • Odoo’s native WhatsApp app runs only on Odoo Enterprise and needs a WhatsApp Business Platform account, not the regular WhatsApp Business App.
  • The setup connects a Meta developer app to Odoo through four values (phone number ID, access token, app ID, and account ID) plus a webhook.
  • Since July 1, 2025, Meta charges per delivered template message, and free-form replies inside the 24-hour customer service window cost nothing.
  • Templates with dynamic fields let Odoo send quotes, receipts, and event tickets straight from Sales, Point of Sale, and Events.
  • An AI chatbot can answer routine questions, but a clear handoff to a human agent still matters to most customers.

Most sales and support teams already run half their customer conversations on WhatsApp.

The trouble is that those chats live on a few phones, while quotes, invoices, and order history live in Odoo. So a rep copies a price from the ERP, pastes it into a chat, and nobody else on the team can see what was promised.

Odoo WhatsApp integration closes that gap. It connects the official WhatsApp Business Platform to your Odoo database, so messages, templates, and replies live on the same record as the lead, sales order, or invoice.

This guide explains how the connection works, how to set it up, what it costs per message, and when a custom build makes more sense than the standard app.

What Odoo WhatsApp integration actually connects

WhatsApp integration with Odoo links a WhatsApp Business Account (WABA) to your database through the Odoo WhatsApp Business API connection that Meta provides.

According to Odoo’s documentation, this lets users send and receive messages inside Odoo. It also lets them send pre-approved templates with dynamic placeholders, such as quotations from Sales, receipts from Point of Sale, and tickets from Events.

The connection supports two flows. In the first, the company starts the chat by sending a template to one or more customers. In the second, a customer messages the public business number, and Odoo opens a group chat in Discuss with every operator assigned to that WhatsApp channel.

One detail trips up many teams early. Odoo’s documentation states that the integration works only with WhatsApp Business Platform accounts. Personal WhatsApp accounts and WhatsApp Business App accounts are not compatible. In practice, this means:

  • The free Business App is out: The green app on a sales manager’s phone cannot plug into Odoo’s native module.
  • The Platform is API-first: Messages flow through Meta’s Cloud API, so several agents can work on one number from inside Odoo.
  • Existing numbers can move: Meta lets businesses migrate a current WhatsApp number to a Platform account, though the number then stops working in the phone app.

Also worth knowing before you plan the budget: Odoo’s documentation is clear that the WhatsApp app is Enterprise only and does not run on Community edition. Community users need a third-party module or a custom connector, which a later section covers.

Why the business case holds up

The reach argument is simple. WhatsApp crossed 3 billion monthly users, Meta CEO Mark Zuckerberg said on the company’s Q1 2025 earnings call. For businesses in the Middle East, India, and much of Europe, that number is less a statistic and more a description of where customers already are.

Reach alone does not justify an ERP project, though. The real Odoo WhatsApp integration benefits show up when chats stop living outside the system of record:

  • One shared history: Every message lands on the contact, lead, or order, so a new agent sees the full thread before replying.
  • Faster document delivery: Quotes, invoices, and delivery updates go out as templates pulled from live Odoo data, with no copy-paste step.
  • Cleaner handovers: Group chats in Discuss and let a manager join or reassign a conversation without asking for screenshots.
  • Better reporting: Message volume and response activity sit beside pipeline and sales data, which makes channel performance measurable.

Automation is where the next gain sits.

Gartner predicts that by 2029, agentic AI will resolve 80% of common customer service issues without human help, cutting operational costs by 30%. That figure is a forecast with conditions attached.

It describes common issues, and it assumes the AI can access accurate order and account data. Odoo is where that data lives, which is why the integration matters more than the chat window itself.

Odoo WhatsApp setup: Detailed step-by-step instructions

Odoo Whatsapp Setup
This Odoo WhatsApp integration guide follows the flow in Odoo’s official documentation. Most of the work happens in Meta’s dashboards, and Odoo only needs the right values pasted in.

  1. Create a Meta Business account: Sign up in Meta Business Suite. Odoo notes that the personal Facebook account behind it must be at least one hour old, or the setup returns an error.
  2. Create a developer app: In the Meta Developer dashboard, create an app of the Business type and name it Odoo. Meta rejects app names that include the word WhatsApp.
  3. Add the WhatsApp product: Meta then issues a test number that can message up to five verified recipients, so you can confirm the API works before going live.
  4. Connect the account in Odoo: Go to WhatsApp, then Configuration, then WhatsApp Business Accounts. Copy the phone number ID, access token, app ID, account ID, and app secret from Meta, then click Test Connection.
  5. Configure the webhook: Paste Odoo’s callback URL and verify the token in Meta’s webhook settings. Subscribe to the messages, account update, and template status fields, so replies reach Odoo.
  6. Add your real business number: Verify it by SMS or call. Meta requires a payment method at this stage as part of its fraud checks.
  7. Create a permanent token: Replace the temporary token with a system user token, since the temporary one expires and silently breaks messaging.
  8. Build and submit templates: Write templates in Odoo, map placeholders to fields such as customer name or order total, and submit them for Meta’s approval.

So how long does it take? With admin access to Meta and Odoo, the technical steps fit into a working day. Business verification and template approval run on Meta’s timeline, so plan a buffer of a few days before the first campaign.

Blog Talk to an Odoo expert Blog

Where WhatsApp earns its place inside Odoo

A connected number is only the start. The value of Odoo ERP WhatsApp integration comes from tying messages to the modules your teams already use every day.

Odoo CRM WhatsApp integration

For sales teams, Odoo CRM WhatsApp integration means a lead’s chat sits on the lead itself. Reps can send a follow-up template from the opportunity, and the reply arrives in Discuss with the context attached. As a result, pipeline reviews stop depending on what someone remembers from their phone.

  • Lead follow-ups: Send a template after a demo or a web form submission.
  • Quotation sharing: Push a quote from Sales with the total and validity date filled in.
  • Payment reminders: Nudge customers on overdue invoices from Accounting.

Odoo WhatsApp automation and automated messaging

Odoo WhatsApp automation uses automation rules to trigger templates when a record changes. For example, a delivery order that moves to Done can send a shipping update, and a confirmed booking can send a reminder the day before. This kind of Odoo automated messaging removes the manual “just checking in” work that eats an agent’s afternoon.

However, every proactive message outside a customer’s reply window must be an approved template. Meta categorizes templates as marketing, utility, or authentication, and the category decides the price, so write utility messages that stay strictly transactional.

WhatsApp chatbot for Odoo

A WhatsApp chatbot for Odoo answers routine questions, such as order status, store hours, or invoice copies, by reading live ERP data. Built with AI chatbot development expertise, it can also qualify a lead and book it into CRM before a rep picks it up.

Still, design the exit first. A Gartner survey of 5,728 customers found that 64% would prefer companies didn’t use AI in customer service, and difficulty reaching a person was the top concern. A bot that hands off cleanly keeps customers. A bot that traps them loses them.

What it costs and which route fits

Per-message pricing

Meta’s pricing documentation confirms that since July 1, 2025, the platform charges per delivered message instead of per conversation. Charges apply only to template messages. Free-form replies sent inside the 24-hour customer service window carry no fee, and utility templates sent inside that window are free as well.

Rates vary by country and template category, and Meta may revise them only on the first day of each quarter. Teams selling into Saudi Arabia or the UAE should check the current rate card, because Meta has listed higher marketing rates for both markets.

Community, enterprise, or custom

The right Odoo WhatsApp API integration route depends on your edition and on how far the workflow goes beyond sending templates.

RouteEditionBest forMain trade-off
Native WhatsApp appEnterpriseTemplates and two-way chat from standard modulesLimited to what Odoo ships
Marketplace moduleCommunity or EnterpriseBasic sending on a tight budgetQuality and API approach vary by vendor
Custom connectorCommunity or EnterpriseChatbots, multi-number routing, custom triggersHigher upfront effort

Treat marketplace modules with care. Some connect by scanning a QR code with WhatsApp Web instead of using the official Business Platform API. This approach risks number bans and breaks when WhatsApp changes its web client.

A custom build makes sense when the workflow spans several modules, needs AI on top, or must route chats by region or department.

Experienced Odoo integration services teams build on the official API, follow Odoo’s module structure, and keep the connector upgrade-ready for future Odoo versions.

That is the practical case for custom Odoo integration services over a self-built script.

Making the integration pay off

Odoo WhatsApp integration works best when teams plan it as part of the ERP itself.

Start with two or three high-volume messages, such as quotes, delivery updates, and payment reminders, and measure response times before adding a chatbot. Then extend into automation once the templates and handoff rules are stable.

Blog Book a free consultation Blog

FAQs

Odoo's native WhatsApp app runs only on the Enterprise edition. Community users can still connect WhatsApp through a custom connector or a third-party module built on the official WhatsApp Business Platform API.
The technical setup usually fits into one working day with the right Meta and Odoo access. Business verification and template approval depend on Meta, so plan a few extra days.
Yes. Templates can pull live data from CRM and Sales, so teams send quotes and follow-ups from the record itself, and customer replies stay attached to that lead or order.
The Business App is a phone app for small teams on one device. The Business Platform is API-based, supports multiple agents and automation, and is the only option compatible with Odoo.
A chatbot can resolve routine questions like order status or invoice copies using live Odoo data. Complex or sensitive issues still need a clear, quick handoff to a human agent.
A tested module already handles webhooks, token renewal, template sync, and Odoo upgrades. Building it yourself means owning those failure points, which costs more time than most teams expect.
Yes, Meta charges per delivered template message, with rates set by country and category. Free-form replies within the 24-hour customer service window carry no charge.
Author
Author

Hardik Soni

Hardik Sonii is the CEO and Sales Director at CodeTrade's official Odoo Partner operation in Dubai. He works across Odoo, AI/ML, Python, Django, and e-commerce, and has spent years helping businesses in the Middle East adopt technology that fits their scale and industry requirements.