If your buyers live inside WhatsApp — in the Gulf, South Asia, or LATAM the chat thread is the storefront, the checkout, and the support desk all at once — then your Odoo catalog and your real sales channel are two disconnected worlds. Someone browses the WhatsApp Business catalog, taps items into a cart, and sends it as a message; your team then re-keys that into an Odoo sale.order by hand, checks stock in a second screen, and copy-pastes a tracking link back into the chat. Odoo Community and Enterprise ship no native WhatsApp catalog sync at all, and even Enterprise's whatsapp messaging integration is template-and-conversation oriented — it does not push product.template records into a Meta catalog, it does not parse the structured order payload WhatsApp sends when a cart is submitted, and it has no concept of an abandoned WhatsApp cart. That gap is where orders get lost, prices drift, and out-of-stock items keep selling.

We build a dedicated connector that treats the WhatsApp Business catalog as a managed downstream of Odoo. A new model (for example whatsapp.catalog.sync) maps each published product.template/product.product to its Meta catalog retailer_id, and a scheduled ir.cron plus on-write automation pushes name, description, price, currency, images, and availability through the WhatsApp Cloud API — so a price change or a stock move in Odoo propagates to the catalog instead of being maintained twice. Inbound is the harder half: a webhook controller (http.Controller with a JSON route) receives Meta's messages payloads, validates the X-Hub-Signature-256 HMAC, and when the message type is order it resolves each product_retailer_id back to the Odoo product, creates or matches the res.partner from the sender's phone number, and drafts a sale.order with correct pricelist and taxes for a human to confirm — or auto-confirms within rules you set. Outbound notifications (order confirmed, picking validated, delivery shipped, return authorized) fire from Odoo automated actions and stock.picking/sale.order state changes using approved WhatsApp message templates, and an abandoned-cart job re-engages carts that never became orders.

Everything is real Odoo engineering, not a black box. The module ships as a standard addon with a versioned __manifest__.py, models built on models.Model with @api.depends computes for sync state, access control via ir.model.access.csv and record rules scoped to your sales teams, OWL/XML views for the catalog-mapping and message-log screens, and QWeb for any printable order/return artifacts. Credentials (phone-number ID, WABA ID, permanent token) live in encrypted ir.config_parameter settings, and all external calls are queued and retried so a WhatsApp API hiccup never blocks a picking. It reads and writes through Odoo's own ORM, so it composes cleanly with your existing Inventory, Sales, and eCommerce apps and with the XML-RPC/JSON-RPC API if you drive orders from elsewhere.

Because this is build-to-order, we start from your actual scope, not a generic template. After a short scoping call we confirm your Odoo version (17.0, 18.0, or 19.0), Community vs Enterprise, your catalog structure and pricelists, the exact notification moments you want, and your WhatsApp Business Account setup. You get a fixed scope and quote, we build and test on a staging copy of your database, run UAT with your team, and deploy behind a rollback plan. Typical delivery is one working week from confirmed scope depending on catalog complexity and how many notification templates need Meta approval — there is no instant download, because there is nothing generic to download.