StackLift
Integration · CRM & ERP

Odoo integration: cost, timeline and how it works.

An Odoo integration reads and writes Odoo models, such as sale orders, partners, and products, from outside systems through its external API, authenticated with a per-user API key. How hard it is depends on which apps you installed, how much custom code the instance carries, which edition you run, and where it is hosted.

From the estimate

What an Odoo integration adds to a project

StackLift's free estimate prices every integration by the engineering it takes. These are its numbers for a typical setup; your data, volumes and edge cases move them.

Typical effort

82 hours

About 10 working days of engineering

Catalog group

Commerce + ERP Platform

Odoo Website/eCommerce with sales, inventory, accounting, CRM, POS, and operations in one suite.

The complete guide

Odoo integration: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

An Odoo integration reads and writes Odoo models, such as sale orders, partners, and products, from outside systems through its external API, authenticated with a per-user API key. How hard it is depends on which apps you installed, how much custom code the instance carries, which edition you run, and where it is hosted.

What do teams connect Odoo to?

Odoo is a suite of apps that share one database: CRM, Sales, Inventory, Accounting, Purchase, Website, and more. A company may adopt only a few and keep other tools for the rest. Integration keeps those tools and Odoo agreeing with each other.

  • Create sale orders and contacts from an outside storefront.
  • Keep product catalogs and on-hand quantities aligned with a marketplace.
  • Open CRM leads from a marketing form.
  • Reflect Odoo invoice and delivery status inside a customer account area.
  • Push posted accounting data to a reporting database.

Which Odoo API should you call?

Odoo exposes its models to external callers. The long-standing routes are XML-RPC and JSON-RPC, where you name a model and a method and pass arguments. Recent releases introduce a JSON-2 style endpoint that uses ordinary HTTP conventions, and Odoo's documentation points toward it for new work, with the older routes slated for retirement. Dates have shifted, so read the notes for your exact version.

Users create API keys in their account security settings. A key stands in for the user's password and carries that user's access rights, which makes a dedicated integration user the safe pattern. Access to the external API on Odoo Online is tied to the plan you hold, so verify it before designing around it. See the API glossary entry for the basics.

How do hosting and edition change things?

Odoo can run as Odoo Online, on Odoo.sh, or on servers you manage, and it comes in Community and Enterprise editions. Each combination decides whether you can install your own modules, how you get a test copy, and who handles upgrades.

What to confirm for each way of running Odoo
SetupCustom modulesWhere to test
Odoo OnlineGenerally not installable, so work stays outsideA duplicate database, if your plan allows
Odoo.shYes, from your repositoryStaging branches built from production data
Self-hostedYes, you control the add-ons pathA separate server or container you create

Treat the table as a checklist for your first call with the Odoo administrator, not as a promise about every plan.

Which Odoo records move, and which way?

Typical Odoo exchanges
Model areaDirectionTrigger
Sale orders and linesInto OdooCheckout or quote acceptance
Partners (customers, vendors)Into Odoo, matched by email or referenceFirst contact
Products and variantsMostly out of OdooOn catalog change
Stock quantitiesOut of OdooScheduled poll
Customer invoicesOut of OdooOnce posted
CRM leadsInto OdooForm submission

What pushes an Odoo project up in effort?

The typical effort shown above describes a lightly customized database. Plan for more when you see:

  • Third-party or in-house modules that add required fields or change validation.
  • Studio changes and automated actions that fire on write.
  • Product variants built from attributes, plus several units of measure.
  • Multi-company setups with separate chart of accounts and fiscal rules.
  • Several warehouses and routes, or a manufacturing app.
  • An upgrade to a new major version in the middle of the project.

The CRM and ERP cost guide shows how these factors move budgets.

What commonly fails in Odoo integrations?

  • Building on the old RPC routes without checking when your version retires them.
  • Using an administrator's key, so a bug in the integration can touch everything.
  • Writing a sale order with a product that has variants and picking the template instead of the variant.
  • Ignoring computed and onchange behavior, so totals differ from what the Odoo screen would produce.
  • Looping over records one call at a time, which crawls on large imports.
  • Testing only on a fresh database that lacks the production customizations.

Connector, community module, or custom code?

Zapier and Make offer ways to reach Odoo, and the Odoo app store lists connectors for popular platforms. Check that any option supports your version and edition.

Options compared
OptionGood forWatch for
iPaaS scenarioAlerts and single-record creationPer-task fees and thin error handling
Packaged connector for a platformA common store-to-Odoo patternVersion support and how it treats your custom fields
Custom service calling the APIOrders, stock, accounting with retriesYou own the upkeep
Custom Odoo moduleLogic that must live inside OdooNot possible on every hosting option

The iPaaS glossary entry explains the category.

How should you go live?

  1. Get a staging database that matches production, including modules.
  2. Create an integration user and give it only the access groups it needs.
  3. Agree how products, variants, taxes, and units match between systems.
  4. Test a refused write, a revoked key, and a repeated request.
  5. Backfill a copy and have the people who use Odoo check the numbers.
  6. Rerun the flows after any planned version upgrade.
  7. Release one flow first, with alerts on, and keep a rollback ready.

How does StackLift scope an Odoo job?

StackLift integrates with Odoo as an independent team. Discovery records your version, edition, hosting, installed apps, and custom code, and a senior architect reviews the scope before it becomes a commitment. Build it up feature by feature in the free estimate.

Work stays on feature branches, agents never handle production secrets, and the plan includes CI/CD, observability, and rollback from the first sprint.

Questions people ask

How do I get an Odoo API key?

A user creates one in their account security settings. Odoo shows it once, so store it in a secret manager. Use a dedicated integration user.

Is XML-RPC still the way to integrate with Odoo?

It still works on many versions, but Odoo steers new work toward its JSON-2 interface. Confirm what your version supports before you choose.

Can I install my own module on Odoo Online?

Typically not. That is one reason hosting matters, so confirm with Odoo for your plan.

Is Odoo or ERPNext easier to integrate?

Neither wins in general. Customization and hosting dominate, so compare using the ERPNext page and your own setup.

How long does an Odoo integration take?

Most first versions take 6 to 16 weeks depending on scope. A 3-day Scope Sprint gives you a detailed plan first.

Sources

Official Odoo documentation

The vendor's own reference for the APIs, limits and authentication this guide describes. Check it for the current version before you build.