Odoo Integrations with Stores, CRM and APIs

Separate tools that do not talk to each other

When each tool works on its own and shares nothing, your team ends up typing the same data twice and nobody has one set of figures. Orders get copied from the store into the ERP, payments are matched by hand and the CRM is always a few days behind.

Odoo has built-in connectors for many services and a documented API (XML-RPC and JSON-RPC, plus REST through modules) for everything else. We use a ready-made connector where a good one exists and build the integration where it does not.

What we connect Odoo to

Online stores
Odoo eCommerce on the same database, or BigCommerce, where Kites is a partner, with products, prices, stock and orders kept in step. See e-commerce development.
Payment gateways
Online card payments recorded against the right order and invoice, so accounting sees them without manual matching. [NEEDS CLIENT INPUT: payment gateways Kites has connected to Odoo in Egypt and the Gulf]
Shipping providers
Shipping labels, tracking numbers and delivery costs pulled into Odoo from the carrier. [NEEDS CLIENT INPUT: shipping carriers Kites has connected to Odoo]
HubSpot and Salesforce
Contacts, deals and orders kept in sync between your CRM and Odoo, so sales and operations work from the same numbers.
Slack and Google
Notifications in Slack, and Google accounts, calendars and email linked to the people using Odoo.
Facebook and Instagram
Leads from your social pages and ads sent into the Odoo CRM pipeline.
Zapier
Quick links between Odoo and many other web apps, for simple flows that do not justify custom code.
Your own systems
Custom APIs to a bank, a logistics partner, a warehouse system or an app we built for you on web or mobile.

Ready-made connector or custom integration

A connector that already exists costs less than one we build, so we look for one first and build only when nothing suitable exists.

Ready-made connector

From Odoo itself or a published module.

Faster to set up
Maintained by its author across versions
Works only the way its author designed it

Custom integration

Built for your systems through their APIs.

Moves exactly the data you need, when you need it
Handles local services with no ready-made connector
Needs checking at each Odoo upgrade

Either way, we tell you before we start who will maintain the integration and what happens at the next upgrade.

How we build an integration

Map the data
Which records move between the systems, which fields match and which system is the master for each.
Agree direction and timing
One way or both ways, instantly or on a schedule, and what happens when something fails.
Build and connect
We set up the connector or write the integration against both systems’ APIs.
Test with real records
Orders, payments and customers run through end to end in a test environment before go-live.
Go live and watch
We switch it on and watch the first days of traffic, then hand over to support.

Questions about Odoo integrations

Does Odoo have an API?

Yes. Odoo exposes its data through XML-RPC and JSON-RPC, and REST APIs can be added with modules. Almost anything you can do on screen can be done through the API.

Can you connect Odoo to a system that has no connector?

Usually, yes, if the other system has an API or can export and import files. We check its documentation during the first call.

What happens to integrations when we upgrade Odoo?

Each integration is tested on the new version before the upgrade goes live. Ready-made connectors are usually updated by their authors. Custom ones are updated by us as part of the upgrade.

Can you integrate our BigCommerce store with Odoo?

Yes. Kites is a BigCommerce partner and an Odoo Partner, so we can work on both sides of the connection.

Can you connect an Odoo we did not set up?

Yes. We review the database first so we know what we are connecting to, then quote the work.