A build-to-order Odoo integration for two-way WhatsApp messaging over Meta's official Cloud API — with a chat inbox, send-from-any-record, template sync, and event-driven automation. ECOSIRE scopes, builds, installs, and supports it for your database. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo integration for two-way WhatsApp messaging over Meta's official Cloud API — with a chat inbox, send-from-any-record, template sync, and event-driven automation. ECOSIRE scopes, builds, installs, and supports it for your database.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
Most teams that run Odoo already live inside it for sales, invoicing, and support — but the conversations that actually close deals and resolve tickets happen on WhatsApp, in someone's phone, invisible to the system of record. Reps copy-paste order numbers into a personal handset, customers reply to a number nobody else can see, and when that person is on leave the thread is simply lost. Odoo's native Discuss and email chatter cover internal notes and SMTP, but there is no first-class, auditable two-way WhatsApp channel bound to the customer, the sales order, or the helpdesk ticket. Off-the-shelf marketplace modules exist, but they are generic, rarely fit your object model, and leave you owning nothing you can extend.
Built on Meta's official WhatsApp Business Cloud API (Graph API) — no unofficial browser automation, no number-ban risk
Signed inbound webhook controller verifying Meta's X-Hub-Signature-256 HMAC before any payload is trusted
Dedicated models (`whatsapp.message`, `whatsapp.template`, `whatsapp.account`) inheriting `mail.thread` so messages post to the record chatter
Unified chat inbox view (list + OWL conversation panel) for reading and replying to threads inside Odoo
'Send on WhatsApp' action injectable on any nominated model — `sale.order`, `account.move`, `crm.lead`, `helpdesk.ticket`, `res.partner`
Automatic inbound routing to the matching `res.partner` by phone number with configurable country-code normalization
We build a made-to-order integration on Meta's official WhatsApp Business Cloud API — never an unofficial browser-automation hack that risks a number ban. At its core is a new set of models (whatsapp.account, whatsapp.message, whatsapp.template) with proper models.Model inheritance of mail.thread, so inbound and outbound messages post directly onto the chatter of the linked record. A controller exposes a signed webhook endpoint that verifies Meta's X-Hub-Signature-256 HMAC, then routes each inbound payload to the matching res.partner by phone (with configurable country-code normalization) and threads it under the right conversation. Outbound sends go through the Graph API with delivery/read receipts written back via @api.depends compute fields and status enums. A "Send on WhatsApp" action appears on any model you nominate — sale.order, account.move, helpdesk.ticket, crm.lead — rendering a QWeb-style body with record placeholders. Approved message templates are synced from your Business Account so agents pick from the live, Meta-approved list, and automated actions (server actions / base automation) can fire a template when an invoice is posted or a delivery is validated. Everything is scoped with ir.model.access.csv plus record rules so agents see only their teams' threads, and the whole thing ships as a clean, upgrade-safe module with its own __manifest__.py targeting Odoo 17.0, 18.0, or 19.0 on Community or Enterprise.
Because this is build-to-order, you are not downloading a frozen package. We start with a scoping call to pin down which models get the send action, how partners are matched, which templates and automations you need, and whether media (images, PDFs, documents) and multi-number routing are in play. We then build against a staging copy of your database, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. You receive the full source and the git repository, so your team — or ours on retainer — can extend it later.
Pricing starts from $249 (indicative, single-company base scope); multi-company routing, several linked models, multiple WhatsApp numbers, media handling, deeper localization of phone/number formats, and migrating historical conversation data increase the quoted scope. We confirm a firm fixed quote after the scoping call — never a surprise on the invoice.
Wants reps to send quotes and follow up on `crm.lead` and `sale.order` records over WhatsApp without leaving Odoo, and needs every thread visible to the whole team and preserved when a rep leaves.
Runs helpdesk on Odoo and needs a shared, auditable WhatsApp channel bound to tickets — with the 24-hour service window respected and template replies for out-of-window contacts.
Wants posted invoices and payment reminders pushed automatically as approved WhatsApp templates from `account.move`, with delivery and read receipts logged against the record.
Needs an official-API, upgrade-safe module they own the source to, with proper access rules, signed webhooks, and support across their Odoo 17/18/19 upgrade path.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة WhatsApp Business Two-Way Messaging for Odoo ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن WhatsApp Business Two-Way Messaging for Odoo، ثم اضغط على تثبيت.
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Official Cloud API | Built on Meta's official Graph API, no ban risk | Depends on your developer's choices | Usually official, but varies by vendor | |
| Two-way inbox in Odoo | Chat inbox with threads on record chatter | Only if you build it | Often outbound-focused, thin inbox | |
| Send from any record | Injectable on models you nominate | Bespoke per model, your effort | Fixed to the models the vendor chose | |
| Fit to your data model | Scoped to your objects and partner matching | Fully bespoke but you own the build | Generic, may not match your model | |
| Template sync & automation | Live template sync plus event-driven actions | Build it yourself | Basic template send, limited automation | |
| Security & access rules | ir.model.access.csv + record rules per team | As good as your spec | Generic, often no per-team rules | |
| Source & ownership | Full source + git repo handover | You own it, but you built it | Often licensed/obfuscated binary | |
| Support & upgrades | Support window + retainer across 17/18/19 | You maintain it | Vendor tickets, version lag common |
This is a build-to-order integration, not an instant download. Typical delivery is 2-4 weeks from confirmed scope, depending on how many models get the send action, whether media and multi-number routing are involved, and any historical data migration. The scoping call sets the exact timeline.
Pricing starts from an indicative $249 for a single-company base scope. After a short scoping call we issue a firm fixed quote — no hourly surprises. Drivers that raise the quote include multi-company routing, several linked models, multiple WhatsApp numbers, media handling, deeper localization, and migrating historical conversations.
Every build includes a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full source and git repository, your team can extend it, or we can maintain and upgrade it across your Odoo 17/18/19 path under a retainer.
It is built exclusively on Meta's official WhatsApp Business Cloud API via the Graph API. We do not use unofficial browser automation or QR-linking hacks, which violate WhatsApp's terms and risk your number being banned. You will need an approved WhatsApp Business Account and phone number, which we help you onboard.
We target Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise. The module ships with its own `__manifest__.py` and is built upgrade-safe. We confirm your exact version and edition during scoping so the delivered code matches your environment.
Yes. We wire server actions / base automation so an approved template fires on events you choose — an invoice being posted, a delivery validated, or a lead reaching a stage — respecting WhatsApp's rule that messages outside the 24-hour customer window must use an approved template.
Yes. You receive installable source for your version plus the full git repository at handover. There is no obfuscation and no vendor lock-in — your team or any Odoo partner can maintain and extend it.
A build-to-order Odoo integration for two-way WhatsApp messaging over Meta's official Cloud API — with a chat inbox, send-from-any-record, template sync, and event-driven automation. ECOSIRE scopes, builds, installs, and supports it for your database.