# WhatsApp Odoo integration. Keep the document in view.

Canonical source: [WhatsApp Odoo integration. Keep the document in view.](https://multiconversion.com/en/services/whatsapp-api/odoo/)
Language: en

> WhatsApp Odoo integration for quote and order enquiries. We check your edition, document access and message templates before launch.

Available versions: [es](https://multiconversion.com/servicios/whatsapp-api/odoo/index.md) · [en](https://multiconversion.com/en/services/whatsapp-api/odoo/index.md) · [pt](https://multiconversion.com/pt/servicos/whatsapp-api/odoo/index.md)

WhatsApp Business API · CRM & ERP

A **WhatsApp Odoo integration** needs a clear link between the customer’s question and the document your team is discussing. We select one document workflow first, define who may send or consult it and test what happens when the customer asks for a change.

[Discuss my integration](https://multiconversion.com/en/services/whatsapp-api/odoo/#contacto) [Explore all integrations](https://multiconversion.com/en/services/whatsapp-api/integrations/)

what we connect

## How we _connect WhatsApp to Odoo_

![WhatsApp Odoo integration workflow: WhatsApp enquiry → Odoo quotation → Document review.](https://multiconversion.com/img/integraciones/en-odoo.svg "WhatsApp Odoo integration")

Example workflow to configure

01

### Quotes with follow-up

Consider a customer who replies to an earlier quotation after its quantities have changed. We agree which reference identifies the document, who may inspect its terms and how the adviser finds the valid revision. The design should help an employee resolve that ambiguity before making a promise based on an outdated attachment.

02

### Process-based notifications

Each proposed notification starts with a specific event and a check. Commercial acceptance and warehouse dispatch are different milestones, even when they concern the same order. We identify the state to inspect and the employee responsible for its accuracy. Configuration follows the functions verified in the installed edition, modules and channel.

03

### Replies that lead to a reviewed change

A reply may request another delivery address, extra units or a different date. We define where that request is recorded and who must approve it before the underlying document changes. Receiving a message does not itself settle the commercial consequences. Where a decision changes agreed terms, the proposed route includes an explicit review.

Example workflow to configure · WhatsApp + Odoo

1.  ### The requested quantity changes
    
    In this example, a customer replies to an installation quotation and asks for two additional units. The adviser needs to find the correct proposal and establish whether it is still open before discussing a revised price.
    
2.  ### The request reaches a reviewer
    
    The proposed journey relates the supplied reference to a document the employee may access. The extra quantity is recorded for commercial review; the incoming message is not treated as confirmation of an amended total.
    
3.  ### The revision has a clear next step
    
    The responsible employee prepares the appropriate revision and records what remains to be confirmed. We repeat the example with a reply to the superseded quotation and with a shared number, so the procedure covers both ambiguities.
    

before we start

## A connection that fits _your system._

We review these points before defining the scope, budget and launch.

01

### Odoo WhatsApp Business: installed edition and customisations

The official WhatsApp application is an Odoo Enterprise feature. A Community installation needs a separately assessed alternative. We record the version, hosting arrangement and relevant modules before confirming a route. Custom fields or altered document states are reviewed with the administrator, since a standard demonstration cannot establish how a customised installation behaves.

02

### Company boundaries and document access

We identify the company issuing the quotation and the employees permitted to read or amend it. In a multi-company setup, a shared telephone number must not become a shortcut to another entity’s records. Acceptance examples include an unknown reference and a document that the receiving employee is not authorised to open.

03

### Activation and failed deliveries

We review the Meta business account, existing number arrangement and templates required for the selected journey. Before activation, we agree who will inspect the first exchanges and how a failed delivery is handled. Historical messages and a provider change are separate assessment items, included only once the available route has been checked.

our approach

## From your process to a _useful integration._

We start with one workflow, validate it with your team and document how to maintain it. The scope follows your configuration.

[Discuss my integration](https://multiconversion.com/en/services/whatsapp-api/odoo/#contacto)

01

### Understand the process

We review how enquiries arrive, who handles them and what information they need. Together, we choose a first use case and how to measure it.

02

### Prepare the connection

We check licences, the number, permissions and fields. We define templates, assignment rules and how to handle failed operations.

03

### Test with your team

We validate messages, records and follow-up with test cases. We refine the workflow before using it with customers.

04

### Launch and support

We document the configuration and train the people responsible. We agree on support and how to review results.

questions

## Before you _connect._

### What changes when several companies share an Odoo installation?

The assessment identifies which entity owns each journey and which employee acts at each point. A valid reference may still belong to the wrong company. We review access restrictions and use examples from different entities during acceptance. If the selected connection cannot maintain the required separation reliably, that limitation is documented before the scope is agreed.

### Should a message amend an order automatically?

We first establish which changes need commercial approval and who may make them. A quantity or address request can affect pricing, transport or a document already confirmed. The design records the request and its review. Any automatic amendment is assessed as a specific operation with stated permissions, conditions and acceptance examples.

### How do you handle a reply to an old quotation?

A test example includes a proposal that has been replaced. We agree what the employee should see when locating it and how the current document can be found. The reply should follow that check instead of assuming the latest message refers to the latest revision. The procedure names the person who resolves the discrepancy and where their decision is recorded.

### What should an employee do after a notification fails?

We specify who needs to know, where they can inspect the outcome and how they decide whether another attempt is appropriate. Tests distinguish an unavailable document from an operation that succeeded but returned a late confirmation. The aim is to avoid both repeated messages and forgotten requests. Recovery options are verified for the chosen connection.

### What does the administrator receive at handover?

The handover records the agreed journey, fields and document states, access checks and validation examples. It identifies the installed modules or customisations on which the connection depends. That gives the administrator a reference when assessing a future upgrade. Ongoing support and additional invoice, warehouse or other journeys are scoped separately.

other tools

## More ways to _connect WhatsApp._

[01 CRM · marketing and sales

### WhatsApp HubSpot

Connect each conversation with the contact, the team and sales follow-up.

Explore integration](https://multiconversion.com/en/services/whatsapp-api/hubspot/) [02 CRM · sales and service

### WhatsApp Salesforce

Connect WhatsApp customer service with your Salesforce teams and processes.

Explore integration](https://multiconversion.com/en/services/whatsapp-api/salesforce/) [03 CRM · sales team

### WhatsApp Zoho CRM

Organise enquiries, contacts and sales team tasks in Zoho CRM.

Explore integration](https://multiconversion.com/en/services/whatsapp-api/zoho/)

[Explore all integrations](https://multiconversion.com/en/services/whatsapp-api/integrations/)

## Using a different CRM or ERP?

Tell us which software and version you use and which task you want to solve. We will assess available connectors and the feasibility of a custom integration.

[Discuss my integration](https://multiconversion.com/en/services/whatsapp-api/odoo/#contacto)

[Explore our WhatsApp API service](https://multiconversion.com/en/services/whatsapp-api/)

let’s start

## Let’s talk about your _integration._

Tell us your CRM or ERP, its plan or version and the process you want to connect with WhatsApp. We will review your setup and the next steps.

📍 Valencia · Madrid · Dublin · Berlin☎ 686 568 904✉ hola@multiconversion.com
