Skip to content

Billing

Odoo integration

Orders, contacts, stock and invoices synced between Odoo and the rest of your stack, with rules shaped around how you work.

Overview

Odoo

Odoo is a modular ERP from Belgium: sales, purchasing, inventory, accounting, CRM, projects and dozens of other apps on one database. It ships localisations for many countries, Portugal included, yet every installation is configured differently and rarely talks to everything else on its own.

Tejobit connects Odoo to the pieces left outside it: a WooCommerce shop, a CRM such as HubSpot, a booking system, a third-party warehouse or a legacy ERP being phased out. The connection uses Odoo's external API (JSON-2 from version 19, XML-RPC and JSON-RPC before that) to read and write models like res.partner, sale.order, product.product, stock.picking and account.move.

In the other direction, Odoo automation rules can send webhooks when a record changes, for instance when a sales order is confirmed or an invoice is posted. That flexibility is also why this integration takes more work than most: custom fields, approval steps and multi-company setups all need handling.

Use cases

What it is for

  • WooCommerce orders entering Odoo as sales orders, reserving stock and producing the invoice in accounting.
  • A wholesaler with Odoo and a separate B2B shop, syncing customer prices and stock levels every hour.
  • Deals won in HubSpot becoming Odoo quotations without duplicate contacts.
  • A phased move from a legacy ERP to Odoo, with both kept in sync during the transition.
  • Posted Odoo invoices pushed to a customer portal or a payment system.
IN

What the connection listens to

  • Webhooks sent by Odoo automation rules when records are created or updated.
  • Paid order in the online shop or deal won in the CRM.
  • Stock movements at an external warehouse.
  • Scheduled reads by write_date for models without automation.
OUT

What the connection does

  • Creates or updates contacts (res.partner) with tax ID, address and commercial terms.
  • Creates and confirms sales orders and follows their deliveries.
  • Syncs products, variants, prices and on-hand quantities.
  • Creates or reads invoices (account.move) and payments for other systems.
  • Fills in custom fields your team has added to Odoo.

How it works

From the request to a working connection

  1. 01

    Request

    The form names the integration, the tools involved and what should happen in each case.

  2. 02

    Review and proposal

    Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.

  3. 03

    Setup and testing

    The connection is set up with the business's own accounts and tested with real cases before it goes live.

  4. 04

    Maintenance and monitoring

    Tejobit hosts the connection, follows up on errors and adapts it when the API changes.

The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.

What to prepare

  • A technical Odoo user with an API key and only the permissions it needs.
  • On Odoo Online, a plan that allows external API access (Odoo lists the Custom plan for the JSON-2 API).
  • The Odoo version plus the list of installed modules and custom fields.
  • A process map: which system owns each piece of data and what happens on conflict.

For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.

Limits

  • Every Odoo database is different; bespoke modules can add mapping work.
  • XML-RPC and JSON-RPC are flagged as legacy from version 19, so integrations on older versions are reviewed at upgrade time.
  • Whether Odoo can serve as certified invoicing software in a given country depends on version and setup; the integration does not change that.

Frequently asked questions

Before you start

Why does the Odoo integration cost more than others?

Odoo is a full ERP with many models, modules and custom fields. Respecting approval flows, multiple companies and stock rules takes more effort to build and to keep running.

Does it work with Odoo Online, Odoo.sh and self-hosted?

Yes, all three. On Odoo Online API access depends on the plan; on Odoo.sh and self-hosted it mainly depends on version and modules.

Can sync run both ways?

Yes. Tejobit agrees with your team which system owns each field, so neither side overwrites the other.

Does it work with existing customisations?

Yes. Custom fields and models are mapped during setup, and the connection is tested against a copy of the database before going live.

Set up the Odoo integration?

Describe what should pass between the tools. The reply confirms feasibility, price and timeline.