The Odoo WhatsApp connector that runs commerce, not just notifications.
Audience selection from Odoo customer data. Different catalogues per customer segment. Credit-line aware ordering. Meta orders synced into Odoo Sales with the full fulfilment workflow. All from inside Odoo — no exports, no middleware.
"WhatsApp connected to Odoo business logic — not just Odoo notifications."
Positioning · Odoo × Go4whatsup commerce connectorTypical Odoo WhatsApp connector vs. this one
Most Odoo WhatsApp modules stop at notifications and template management. This connector extends WhatsApp into audience selection, catalogue presentation, ordering logic, and end-to-end commerce workflow.
| Capability | Typical connector | Go4whatsup for Odoo |
|---|---|---|
| WhatsApp notifications | Common | Core capability |
| Template management | Common | Full lifecycle · variable mapping · testing |
| Trigger-based automation | Basic | Module-wise · conditional · scheduled |
| Chatter integration | Common | Integrated communication timeline |
| Broadcasting from Odoo | Limited / varies | Audience from Odoo + Excel upload |
| Customer segmentation | Basic / varies | Customer type, category, rule-based |
| Multi-catalog management | Often limited | Customer-based catalogue presentation |
| Customer-specific ordering | Often limited | Flow changes by customer configuration |
| Credit-line aware ordering | Rare / varies | Credit-line + direct-ordering logic |
| WhatsApp commerce | Notification-focused | Catalogue + ordering + Odoo fulfilment |
| Meta catalog sync | Available in some | Integrated with product + order sync |
| Meta order sync | Available in some | Meta orders → Odoo Sales with full workflow |
| AI auto-reply (context-aware) | Rare | LLM-powered · reads Odoo customer + order data |
| Cross-module Odoo coverage | Varies | CRM · Sales · Purchase · Accounting · Inventory · Manufacturing · POS · Helpdesk · HR · Projects · custom |
Five things this connector does that others don't
Each of these ties WhatsApp to real Odoo business logic — the kind procurement teams evaluate on, and the kind that makes WhatsApp work as a sales channel instead of a notification pipe.
Audience straight from Odoo customer data
Build a WhatsApp campaign by selecting customers from Odoo — filter by category, tag, region, salesperson, or CRM stage. No CSV exports before every send. Excel upload stays available for one-off lists.
Different catalogue per customer segment
Map catalogues to customer types or categories. A wholesale customer sees the trade catalogue; a retail customer sees consumer SKUs. The WhatsApp catalogue adapts to the customer's Odoo profile automatically.
Credit-line aware ordering
Customers with an approved credit line follow a credit-based ordering journey. Cash customers get the payment flow. Direct-ordering customers get their own path. The WhatsApp experience reflects the commercial rules already in Odoo.
Meta orders → Odoo Sales, end-to-end
Every WhatsApp order becomes an Odoo Sales Order automatically. Standard workflow takes over: inventory reserved, delivery generated, invoice raised, accounting posted. Complete traceability from WhatsApp click to books.
Context-aware AI, reading Odoo data
Nova AI answers "where's my order?", "what's my balance?", "is this in stock?" by pulling the answer from Odoo — customer, sales, invoice, delivery, inventory. Handovers to a human agent preserve the full chat history.
Eleven Odoo modules, one connector
CRM, Sales, Purchase, Accounting, Inventory, Manufacturing, POS, Helpdesk, HR, Projects, and custom modules — each with its own triggers and templates. WhatsApp becomes an event channel across every operational area.
Nineteen modules, organised as four pillars
Everything in the connector fits into one of four things you can do with WhatsApp inside Odoo. Pick the pillar that maps to your bottleneck.
1. Communication
Every WhatsApp interaction, inside Odoo.
- Central dashboard (API health, WABA status, message analytics)
- Template management (create, sync, test, version)
- Chatter timeline integration
- Multi-company support
- Complete message logging
2. Automation
Right message, right time, no manual send.
- Trigger-based sends across every module
- Conditional automation (amount · country · tag · status)
- Scheduled + recurring campaigns
- Dynamic variable mapping from Odoo fields
- AI auto-reply (planned enterprise)
3. Commerce
WhatsApp as a real sales channel.
- Meta catalog + product sync
- Multi-catalog per customer segment
- Credit-line + direct-ordering logic
- Meta orders → Odoo Sales Orders
- Standard fulfilment (inventory · delivery · invoice)
4. Support
Post-sale interactions handled in-thread.
- Helpdesk integration (reply from ticket)
- SLA + escalation notifications
- Appointment booking (Odoo Calendar)
- Customer enquiry → CRM lead auto-create
- Helpdesk service requests via Meta Flows
Real B2B flow — customer profile drives everything
A single WhatsApp interaction, controlled by the customer's Odoo record. This is the flow that "notification only" connectors can't run.
Customer identified in Odoo. WhatsApp number matches an Odoo customer record — category, credit-line, tags, and price list all load automatically.
Relevant catalogue presented. Customer category → catalogue map is applied. Wholesale sees trade SKUs, retail sees consumer SKUs — no manual filtering.
Customer selects products. Meta Catalog surfaces the right items. Stock is validated against Odoo Inventory in real time.
Credit-line + direct-ordering status checked. Credit customer → credit ordering flow. Cash customer → payment link. Direct-ordering account → its configured process.
Order created in Odoo Sales. Sales Order lands in the standard queue with all customer, product, quantity, and pricing data mapped.
Standard Odoo fulfilment continues. Inventory reserves, Delivery Order generates, Invoice posts, Accounting reconciles. Every step visible in the Chatter and traceable back to the WhatsApp thread.
Every module you already use in Odoo
Each of these can trigger a WhatsApp send, feed the AI auto-reply with context, or receive an inbound message logged against the right record.
Common questions from Odoo teams
Straight answers from real evaluations — pricing, versions, catalogues, and what the AI can and can't do today.
How is this different from the Odoo WhatsApp integration I already have?
Most connectors send notifications when an Odoo event fires — order confirmed, invoice created, delivery done. This connector adds four things: (1) audience selection for broadcasts straight from Odoo customer records, (2) multi-catalog presentation based on customer segment, (3) credit-line aware ordering journeys, and (4) Meta order sync back into Odoo Sales with the full fulfilment workflow. It's WhatsApp commerce, not just WhatsApp messaging.
Can I run broadcasts to specific customer segments without exporting?
Yes. Build a WhatsApp broadcast by filtering Odoo customers — by category, tag, salesperson, CRM stage, country, or any Odoo field. No CSV exports before every campaign. Excel upload is still available for one-off lists you don't want to add to Odoo.
How does multi-catalog work — do I need separate Odoo databases?
No. You maintain multiple catalogues inside one Odoo. Then map each catalogue to a customer type or category. When a customer starts a WhatsApp order, the system reads their Odoo profile and shows the mapped catalogue automatically. One database, multiple customer experiences.
What happens when a customer with a credit line places an order?
The connector reads the customer's Odoo credit-line status. Approved credit → order follows the credit-based journey (billed against credit, no payment link needed). No credit line → payment link generated. Direct-ordering account → its own configured flow. Every path lands as a proper Odoo Sales Order.
Does the AI auto-reply need OpenAI, or can I use my own LLM?
Both are supported. The AI Auto Reply module works with OpenAI GPT, Anthropic Claude, Google Gemini, or other enterprise LLM providers. You configure the provider that fits your compliance and cost profile. The AI reads relevant Odoo data (customer, orders, invoices, inventory) before generating any response, so answers are grounded in your actual business data.
Which Odoo versions does the connector support?
Built for Odoo 19 (latest). Backward-compatible with Odoo 12, 13, 14, 15, 16, 17, and 18 — both Community and Enterprise editions.
How does pricing work for this connector?
Standard plan is $39/month globally (₹1,499 India, AED 149 GCC, €39 Europe) with the Odoo connector included. Free forever tier is available with no credit card. Enterprise plans (custom-quoted) for teams over 50 agents or regulated industries. Meta's per-conversation charges pass through at cost as a separate line item — never marked up.
How long does setup take?
Typical go-live is 24 hours once your Meta Business Manager is verified. End-to-end range is 24–72 hours including Meta verification for new businesses. Enterprise setups with SAP or Salesforce wiring run 3–7 business days with a dedicated integration engineer. Free assisted onboarding is included on every paid plan.
Can support agents reply to WhatsApp directly from an Odoo Helpdesk ticket?
Yes. The Helpdesk integration lets agents send and receive WhatsApp messages inside the ticket record. Templates, media, status updates, SLA reminders, and closure notifications all fire from the ticket. Full conversation logs stay in the ticket history.
Is customer data staying inside my Odoo, or does it leave?
Customer records stay in your Odoo. The connector reads Odoo data to send WhatsApp messages and writes back inbound messages plus order data. Meta's WhatsApp Business API is the message transport layer — same as any other WhatsApp Business integration. Signed DPA available on request; GDPR, DPDP Act 2023, and GCC PDPL compliant.
See the Odoo commerce connector in a 20-minute demo
We'll walk your Odoo setup, wire one live automation, and show you the credit-line and multi-catalog flow with a real product.