How to Integrate Odoo 20 with Other Business Systems Using APIs and Connectors

Modern businesses don’t usually function on just one software. The company can use Odoo for ERP and accounting, but at the same time, it uses other software to handle the processes of payment, delivery, eCommerce marketplaces, communications, analysis, HR, and even artificial intelligence.

But the issue is not only about connecting two software. Business executives have to figure out how to integrate them, how much it is going to cost, how safe the integration is going to be and whether it is scalable further.

There are several methods to integrate different software offered by Odoo 20 - starting from connectors to APIs and modern integration of artificial intelligence via MCP protocol.

1. What Are Odoo Integrations?

Integration makes it possible for Odoo to communicate with another application.

Examples include:

• The payment gateway can transmit payment status to Odoo.
• The logistics company can receive delivery data and transmit tracking information.
• The e-commerce platform can communicate products and orders with Odoo.
• Google Calendar can synchronize meeting schedules with Odoo.
• Microsoft Outlook can connect email and Odoo.
• External applications can leverage the Odoo API to create/modify records.

The AI assistant can use the Odoo MCP Server to get information and carry out actions supported by it.

The type of integration depends on what you need to integrate and the level of control the business requires.

2. Built-in Odoo Connectors: Start With What Already Exists

The first integration opportunity should be considered as a connector that Odoo already has out of the box.

An inbuilt integration is always simpler to configure and maintain than a custom integration since the required workflows and configuration screens are already in place in Odoo.

Payment providers

Odoo allows integrations with several online payment providers as well as payment terminals.

Depending on the payment provider, the payment services can be integrated into either eCommerce, Sales, or Point of Sale workflow.

Odoo 20 has integrations with providers such as Adyen, Authorize.net, Stripe, Razorpay, Mollie, and others. Odoo also supports payment terminal integrations for providers such as Adyen, Stripe, Razorpay, and Worldline.

Instead of developing a custom payment integration, the business can configure one of the available providers and let Odoo take care of the payment workflow.

Shipping carriers

In addition to payment services, Odoo offers ready-to-use shipping carrier integrations.

Odoo 20 has shipping integration with:

• DHL Express
• FedEx
• UPS
• USPS
• Sendcloud
• EasyPost
• Shiprocket
• Starshipit
• Region-specific carriers

Depending on the shipping carrier and configuration, Odoo can calculate shipping costs and generate shipping labels.

This eliminates manual work when thousands of orders are shipped.

Marketplaces and eCommerce Platforms

Odoo can also connect its eCommerce and sales processes to third-party platforms.

For example, Odoo's documentation includes integrations that allow product catalogs and sales orders to be synchronized with external applications. Odoo's eCommerce platform can also integrate its product information with other third-party applications like Google Merchant Center, TikTok, Facebook, and Instagram.

Other integrations include the Gelato integration that allows product information, sales orders, fulfilment information, and shipment synchronization.

Google and Microsoft

Odoo also offers productivity platform integrations.

For instance, Google Calendar allows synchronizations between Google Calendar and Odoo in both directions.

Users can integrate Microsoft Outlook with Odoo using the Odoo Outlook plug-in that enables them to manage Odoo records straight from their Outlook inbox.

This could be extremely useful for sales, CRM, services, and management teams that use Google or Microsoft applications most of the time during their workdays.

WhatsApp

It is also possible to integrate WhatsApp into Odoo. For example, Odoo eCommerce allows using WhatsApp templates for order communications if the WhatsApp application is installed.

This helps businesses connect customer communications to their sales and service processes, so they don't have to manage customer communications outside the ERP system.

3. When a Built-in Connector Is Not Enough

The pre-built connector is the best place to start, but it will not address all the needs of every business.

Think about a business that has:

• Proprietary Warehouse Management System
• Legacy Accounting software
• Custom B2B portal
• Proprietary Manufacturing software
• Third-party Data warehouse
• Custom Logistics software

There may be no pre-built Odoo connector for these applications.

That is when the Odoo External API comes into play.

4. Odoo 20 External API

Odoo offers an external API for communication between external software programs and Odoo.

The more recent JSON-2 API gives access to Odoo models and methods via the URL "/json/2" using HTTP. It requires bearer authentication with an API key.

It can be visualized as follows:

External System > (HTTPS + API Key) > Odoo /json/2  > Odoo Model / Method >  Odoo Database

Through this API, an external system can perform actions like:

• Read customers
• Create sales orders
• Update products
• Read invoices
• Update inventory information
• Query business data

The actual models, fields, and methods vary based on the Odoo database in use.

5. Odoo's Live API Documentation

One helpful thing is the API documentation provided by the Odoo database.

API documentation is accessible at:

https://your-odoo-domain.com/doc

The documentation is created for the particular database, meaning that developers will be able to see exactly what models, fields, and methods are available in their particular Odoo installation.

It is especially important since Odoo databases may include:

• Standard Odoo models
• Custom modules
• Custom fields
• Custom methods
• Special industry modules

Consequently, developers should be aware of the fact that the API is different in each case.

6. API Keys and Security

API integration from outside should never employ a user password when API keys are available.

The API key serves as a method of authentication for any external software.

In terms of business operations, accessing APIs is comparable to possessing the digital key to your ERP.

Best practices would be:

• Create unique integration users when needed.
• Provide necessary permissions.
• Keep your API keys safe.
• Never use your keys in your source code.
• Rotate keys periodically.
• Employ HTTPS.
• Keep track of failed integration attempts and other suspicious behaviour.
• Turn off API keys that are no longer needed.

The aim of the process is not just to integrate; the aim is to integrate without compromising your security.

7. Odoo 20 and MCP: Connecting AI to Odoo

The traditional API is used mainly for application purposes.

The Model Context Protocol (MCP) offers one more alternative, where compatible AI agents can interface with the Odoo system.

Odoo 20 includes a MCP server, which can be used by the external AI agent to connect to the Odoo database and manipulate data using available tools.

This can be seen as follows:

User > AI Agent > (MCP) > Odoo MCP Server > Odoo Database
There will be no need for the developer to integrate separately for each AI purpose; instead, the AI client will find out the available tools provided by Odoo and use them based on the user requirements.

8. Odoo MCP Endpoint

The Odoo MCP server can be accessed from the URL of the database plus:

/mcp

For example:

https://your-odoo-domain.com/mcp

According to Odoo documentation, clients that support MCP, such as Claude, Antigravity, and Codex, can be used to connect to this API.

This provides some interesting possibilities for business users.

For example, instead of going through various screens of Odoo manually, an AI assistant could fulfill requests like:

"Show me the sales for this month, per salesperson."

or:

"Get all open opportunities that haven't been contacted lately."

or:

"Make contact records for these five leads."

It all depends upon the tools provided through the Odoo MCP settings and the user's permissions.

9. MCP Uses a Dedicated API Key Scope

Security plays a crucial role while connecting AI systems to corporate data.

The Odoo MCP integration employs an API key with MCP scope.

The procedure is as follows:

• Open the user preferences.
• Access the Security tab.
• Generate the API key.
• Set the scope to MCP.
• Set up the expiration period.
• Connect the AI client to the Odoo / MCP endpoint.

According to Odoo, the MCP key is utilized in order to authenticate the user’s identity and permissions for the requests made from the AI client. The generated API key is shown only once and should be saved safely.

One important point: MCP is not supposed to circumvent the Odoo security model. The AI client accesses the data with the help of the Odoo user’s permissions.

10. API vs MCP: What Is the Difference?

It is useful to think about the two technologies differently.

Integration with a CRM, a warehouse management system, or a data warehouse will likely work better with an API or a connector.

An AI assistant requiring access to Odoo can be a good candidate for MCP.

11. Integration Costs and Odoo Plan Implications

Integration considerations should encompass licensing and infrastructure fees and not just development fees.

Currently, in the pricing data offered by Odoo, Custom plan includes the feature of External API, while Standard Plan does not have this feature. Currently, the pricing page of Odoo mentions Custom plan costs US$49/user/month on annual pricing, compared with US$24.90/user/month for Standard, although pricing can change and regional or promotional pricing may differ.

The Custom plan includes access to the following features:

• Odoo Studio
• External API
• Custom Developments
• Odoo Online
• Odoo.sh
• On-Premise
• Multi-Company
• Agentic AI

Odoo claims that the installation of Studio in a Standard database results in an upgrade to the Custom plan.

An important distinction

However, not all integrations will require payments to an external API. For instance, if Odoo itself communicates with an external application, like a payment gateway, a shipping carrier, a VoIP service, or a bank synchronization service, then Odoo considers this functionality as part of its standard operations and not an External API call from an external system to Odoo.

As a result, companies should make a difference between:

Odoo > External Application and External system > Odoo

This second case will be typical for Odoo's definition of an External API.

There might also be some additional expenses aside from Odoo subscriptions, like:

• Payment gateway fees
• Shipping carrier fees
• Marketplace fees
• Google / Microsoft API fees
• WhatsApp fees
• iPaaS subscription fee
• AI provider fee
• Development and maintenance fees
• Hosting and infrastructure fees

12. iPaaS vs Custom Integration

In situations where an appropriate existing connector does not exist, there are essentially two major options available to firms: an iPaaS offering or custom integration.

What is iPaaS?

iPaaS is an acronym for Integration Platform as a Service.

The iPaaS solution offers pre-packaged connectors and workflow features to integrate various applications.

The core concept is:

Odoo > iPaaS Platform > CRM > Marketplace > Marketing Platform > Data Warehouse

This is a good option when there is a need to integrate many mainstream applications quickly.

Strengths:

• Faster implementation
• Less custom coding
• Workflow design through visuals
• Built-in connectors
• Easier to maintain common use cases
• Good for integrating many SaaS applications

Weaknesses:

• Subscription-based costs recurring
• Limited capability of the connector
• Vendor dependence
• Complex business logic can get difficult
• Transaction volumes can add costs
• Some workflows require custom coding

13. When Custom Development Makes More Sense

A custom integration is usually recommended when the business has very specific requirements.

Such as:

A company requires Odoo to integrate production orders, stock availability, quality, and shipping status information with a proprietary manufacturing software solution.

When the business process has intricate business logic, using iPaaS may be hard to manage.

Custom development allows the business to have more control over:

• Data mappings
• Business logic
• Error handling
• Security
• Performance
• Retries
• Logging
• Webhooks
• Transactions

However, the problem is that it will fall on the business to develop, test, maintain, upgrade, and support the solution.

14. Is it iPaaS or Custom? A Practical Decision Framework

A basic framework for making decisions could be used by business owners.

Opt for an in-built Odoo connector in case:

• Odoo has native support for the service.
• The default process satisfies your needs.
• There is a desire for minimum development.
• Easier upgrades are needed.

Pick an iPaaS in case:

• There are several SaaS applications that need to exchange information.
• The processes are fairly simple.
• Speed is a priority compared to customization.
• There is no interest in maintaining integration code.

Go for the Odoo API in case:

• Another application requires access to Odoo.
• Structured data exchange is required.
• There is custom business logic within the integration.
• Synchronization is either real-time or scheduled.

Select MCP in case:

• An AI agent requires controlled access to Odoo.
• Users want to use Odoo via natural language.
• AI needs to extract/execute any business-related data.
• Exposing certain capabilities of Odoo as AI tools is desired.

15. The Future of Odoo Integrations

Integration in Odoo 20 becomes even more relevant beyond just data synchronization.

Classic connectors still cope with typical needs in terms of:

• Payments
• Shipping
• Marketplaces
• Email
• Calendars
• Communication

For customized system integration, the APIs allow the necessary flexibility.

The MCP adds one more dimension to that. The AI becomes an interface to business applications.

Rather than having to design a unique screen for each management issue, it will become possible to let AI agents authorized to do so fetch data, analyze it, and take certain actions.

The technology itself is extremely capable, but governance is crucial. The business should define what information is accessible to the AI, what changes it is allowed to make, and what actions should be approved by a person.

Odoo 20 comes with a variety of integration options, and there is no magic wand that can work in all cases.

A reasonable way would be to choose the following order of tools:

Start with the built-in connector > apply API integration for custom solutions > go for iPaaS for quick workflow integration between several SaaS systems > utilize MCP for AI interactions with Odoo.

The main point is not to pick the latest technology; it is about picking the right integration method.

To read more about Overview of API Integration in Odoo 19, refer to our blog Overview of API Integration in Odoo 19.