Build-to-order Odoo module putting two-way WhatsApp Cloud API into CRM, Sales, Helpdesk & Invoicing — no Enterprise needed. Built & supported by ECOSIRE. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo module putting two-way WhatsApp Cloud API into CRM, Sales, Helpdesk & Invoicing — no Enterprise needed. Built & supported by ECOSIRE.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
In WhatsApp-first markets across MENA, South Asia and LATAM, your customers already message on WhatsApp — but your Odoo doesn't. Quotations get emailed and ignored, invoices go unread, and support conversations live on someone's personal phone, disconnected from the CRM record they belong to. This module closes that gap by embedding the official Meta WhatsApp Business Cloud API directly into Odoo.\n\nThe WhatsApp Business Cloud API Connector (All-in-One) is a net-new Odoo module ECOSIRE builds to your requirements and installs on your instance. It connects to Meta's Cloud API (Graph API + a verified webhook endpoint you own) — so unlike Odoo's own WhatsApp integration, it does not require Odoo Enterprise. It runs on Community, Enterprise or Odoo.sh, on Odoo 17, 18 or 19.\n\nUnder the hood it's real Odoo engineering, not a bolt-on. New models (whatsapp.account, whatsapp.message, whatsapp.template) extend mail.thread so every inbound and outbound WhatsApp message lands in the chatter of the right crm.lead, sale.order, helpdesk.ticket or res.partner — and syncs into Discuss as a live channel your agents already know how to use. Incoming messages arrive through a /whatsapp/webhook controller (HMAC-signature verified per Meta's spec); outbound sends go through the Graph API with delivery/read receipts written back via @api.depends computed status fields. Access is governed by ir.model.access.csv and record rules so agents only see their own conversations, and QWeb-rendered message logs give managers an auditable history.\n\nBecause it's build-to-order, we scope it against your real Meta Business account, phone number and approved templates, develop and test it in a staging database, then deploy it to production with the right security groups, automated actions and scheduled (cron) jobs wired in. You get an honest lead time, a working connector on your own instance, and a named ECOSIRE team that supports and updates it — never an anonymous instant download.
Connects to the official Meta WhatsApp Business Cloud API (Graph API) with no Odoo Enterprise dependency — runs on Community, Enterprise or Odoo.sh
Two-way messaging: inbound messages arrive via a signature-verified /whatsapp/webhook controller and post into Discuss plus the record's chatter in real time
Conversations auto-link to the matching crm.lead, sale.order, helpdesk.ticket, invoice or res.partner by phone number, so history lives on the record — not a personal phone
Approved template message management: sync, categorize and send Meta-approved HSM templates with variable placeholders filled from Odoo field values
Send quotations and sales orders over WhatsApp straight from the Sales form, with the PDF (QWeb report) attached as a document message
Auto-send invoices, payment reminders and delivery/dispatch notifications via automated actions (base.automation) and scheduled cron jobs
A sales team in MENA, South Asia or LATAM whose prospects reply on WhatsApp but ignore email. They want to send and track quotations, follow up, and keep every message tied to the CRM lead — without leaving Odoo or paying for Enterprise.
A support manager who wants WhatsApp as a first-class ticket channel: inbound messages open or update helpdesk tickets, replies go out from Odoo, and conversations stay auditable instead of trapped on an agent's personal phone.
Someone responsible for getting invoices paid, who wants automated invoice delivery and polite payment reminders sent over WhatsApp — the channel customers actually read — with delivery and read status visible in Odoo.
An IT or operations owner on Odoo Community who needs official WhatsApp Cloud API messaging but can't justify an Enterprise subscription just to unlock it, and wants a supported, source-available module that stays under their control.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة WhatsApp Business Cloud API Connector (All-in-One) ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن WhatsApp Business Cloud API Connector (All-in-One)، ثم اضغط على تثبيت.
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Works on Odoo Community (no Enterprise needed) | Yes — talks to Meta Cloud API directly, runs on Community, Enterprise & Odoo.sh | Possible, but only if your developer builds the API layer correctly | Varies; many App Store modules still assume Enterprise or third-party BSPs | |
| Official Meta WhatsApp Cloud API (not an unofficial hack) | Yes — signature-verified webhook + Graph API, fully compliant | Depends entirely on the developer's diligence | Usually, but some route through resellers with markup | |
| Two-way sync into Discuss + CRM/Sales/Helpdesk/Invoicing chatter | Yes — messages auto-link to the right record via mail.thread | Only what you pay to build; deep integration is expensive | Often one or two apps, rarely all four unified | |
| Auto-send quotations, invoices & payment reminders | Yes — via automated actions, cron jobs and QWeb PDF attachments | Buildable, but each flow is billable dev time | Sometimes, usually as add-on modules | |
| Broadcast campaigns with opt-out & consent tracking | Yes — segmented lists, rate limiting, STOP-keyword opt-out on res.partner | Rarely scoped in a one-off build | Some offer it; opt-out handling quality varies | |
| Scoped, tested & installed on your instance by the vendor | Yes — staged, tested, deployed with security groups & crons wired in | You manage your own developer and QA | No — you install a generic download and self-configure | |
| Named support window + updates for new Odoo/Meta versions | Yes — defined support window and scoped major-version migrations | Only if you retain the developer separately | Ticket queue at best; abandonware at worst | |
| Full source code ownership (no lock-in) | Yes — you own and can extend the code | Yes | Often obfuscated or license-gated |
This is not an instant-download app from the Odoo App Store — it's a build-to-order module ECOSIRE builds, installs and supports for you. Typical delivery is 2–4 weeks depending on scope (how many of Sales, CRM, Helpdesk and Invoicing you connect, how many phone numbers and templates, and Meta approval timing). After a short scoping call we confirm a firm timeline, build and test in a staging database, then deploy to your production instance.
Every build includes a defined post-go-live support and bug-fix window with a named ECOSIRE contact. Because you receive the full source code, the module isn't locked to us — but we handle compatibility with Odoo point releases and Meta Cloud API changes during your window, and offer ongoing support or feature retainers afterward. Migrations to a new Odoo major version (17→18→19) are quoted as a small scoped update rather than a rebuild.
No. That's the whole point. Odoo's native WhatsApp integration is Enterprise-only, but this module talks directly to the official Meta WhatsApp Business Cloud API through its own controllers and models, so it runs on Odoo Community as well as Enterprise and Odoo.sh — across Odoo 17, 18 and 19.
It's the official Meta WhatsApp Business Cloud API. You (or we, on your behalf) set up a Meta Business account, a verified phone number and approved message templates. The module registers a signature-verified webhook and sends through Meta's Graph API — fully compliant, including the 24-hour service window and template rules. It does not use any unofficial or browser-automation hacks that risk your number being banned.
Yes. Inbound and outbound messages post to Discuss as a live channel and into the chatter of the matching record — the crm.lead, sale.order, helpdesk.ticket, invoice or res.partner — matched by phone number. Delivery, read and failed statuses are written back so your team sees the full, auditable conversation history right where they already work, not on a personal phone.
Yes. Quotations and orders can be sent from the Sales form with the QWeb PDF attached, and invoices, payment reminders and delivery notifications can be automated via Odoo automated actions and scheduled cron jobs — for example, a reminder a few days before or after an invoice due date. Broadcast campaigns to segmented lists are supported too, with opt-out handling and per-recipient rate limiting to respect Meta's messaging tiers.
Build-to-order Odoo module putting two-way WhatsApp Cloud API into CRM, Sales, Helpdesk & Invoicing — no Enterprise needed. Built & supported by ECOSIRE.