[Skip to content](#main)

[→](/)

[![Avunu](/brand/avunu-logo.svg)![Avunu](/brand/avunu-logo-light.svg)](/)[Services](/services/)[Consulting](/services/consulting/)[ERP](/services/erp/)[Odoo](/services/erp/odoo/)[ERPNext](/services/erp/erpnext/)[Custom software](/services/custom-software/)[Devices & IoT](/services/devices-iot/)[Websites](/services/websites/)[Infrastructure](/services/infrastructure/)[Partners](/partners/)

[Work](/work/)[Open source](/open-source/)[Knowledge base](/kb/)[About](/about/)

[About Avunu](/about/)[Team](/about/team/)[Insights](/insights/)[Contact](/contact/)

[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

- [Services](/services/)[Consulting](/services/consulting/)
- [ERP](/services/erp/)
- [Odoo](/services/erp/odoo/)
- [ERPNext](/services/erp/erpnext/)
- [Custom software](/services/custom-software/)
- [Devices & IoT](/services/devices-iot/)
- [Websites](/services/websites/)
- [Infrastructure](/services/infrastructure/)
- [Partners](/partners/)

[Work](/work/)[Open source](/open-source/)[Knowledge base](/kb/)[About](/about/)

- [About Avunu](/about/)
- [Team](/about/team/)
- [Insights](/insights/)
- [Contact](/contact/)

[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

[Knowledge base](/kb/)[Odoo](/kb/odoo/)Odoo Community and OCA overview

Search the knowledge basePress/

ESC

Jump to

[Browse the knowledge base](/kb/)[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

↵select↑↓navigateescclose

Search the knowledge base

[Skip to the article](#kb-article)[Odoo](/kb/odoo/)7 articles

- [Overview](/kb/odoo/)
- [A repair shop workflow on Odoo 18, from inspection to invoice](/kb/odoo/repair-shop-workflow-on-odoo/)
- [Importing documents from email into Odoo](/kb/odoo/importing-documents-from-email-into-odoo/)
- [Migrating from QuickBooks to Odoo with a clean cutover](/kb/odoo/migrating-from-quickbooks-to-odoo/)
- [Odoo Community and OCA overview](/kb/odoo/odoo-community-and-oca-overview/)
- [Set up and work in an Odoo 18 development environment with odoo-nix](/kb/odoo/odoo-development-environment/)
- [Set up two-way SMS in Odoo with Twilio](/kb/odoo/two-way-sms-in-odoo-with-twilio/)
- [Test custom Odoo modules from the command line](/kb/odoo/testing-custom-odoo-modules/)

Other sections[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

In Odoo: 7 articles

[Overview](/kb/odoo/)[A repair shop workflow on Odoo 18, from inspection to invoice](/kb/odoo/repair-shop-workflow-on-odoo/)[Importing documents from email into Odoo](/kb/odoo/importing-documents-from-email-into-odoo/)[Migrating from QuickBooks to Odoo with a clean cutover](/kb/odoo/migrating-from-quickbooks-to-odoo/)[Odoo Community and OCA overview](/kb/odoo/odoo-community-and-oca-overview/)[Set up and work in an Odoo 18 development environment with odoo-nix](/kb/odoo/odoo-development-environment/)[Set up two-way SMS in Odoo with Twilio](/kb/odoo/two-way-sms-in-odoo-with-twilio/)[Test custom Odoo modules from the command line](/kb/odoo/testing-custom-odoo-modules/)

Other sections[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

OdooOdoo Community and OCA overview

What Odoo Community, OCB and the OCA are, how they differ from Enterprise, and how Avunu chooses modules for Odoo builds.

UpdatedOct 5, 2026

Applies toOdoo 18.0 CommunityOCB 18.0odoo-nix

Tagsodooocaerpopen-source

Reading time7 min

On this page[The pieces](#the-pieces)[How Community differs from Enterprise](#how-community-differs-from-enterprise)[Why we build on Community plus OCA](#why-we-build-on-community-plus-oca)[Which Odoo version we use](#which-odoo-version-we-use)[How we choose modules](#how-we-choose-modules)[Bundles](#bundles)[Adding modules to a project](#adding-modules-to-a-project)[Why every project is pinned](#why-every-project-is-pinned)[What is in this section](#what-is-in-this-section)

This document explains the pieces Avunu builds Odoo systems from (Odoo Community, OCB and the Odoo Community Association), how that differs from Odoo Enterprise, and how we decide which modules go into a build. Read it first if you are new to the Odoo section of this knowledge base.

## The pieces

Four names come up constantly, and they are easy to mix up.

| Name            | What it is                                                                                                                                                                                           |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Odoo Community  | The open-source edition of Odoo: invoicing and core accounting, sales, inventory, purchasing, repairs, fleet, a customer portal and more.                                                            |
| OCB             | Odoo Community Backports, the [OCA's maintained distribution](https://github.com/OCA/OCB) of Odoo Community. It is published as one branch per Odoo release series, such as `18.0`.                  |
| OCA             | The [Odoo Community Association](https://odoo-community.org/), a nonprofit community of Odoo companies and developers. It maintains a large library of open modules, organized as many repositories. |
| Odoo Enterprise | The commercial edition, sold as a per-user subscription, with some features reserved for subscribers.                                                                                                |

An Avunu Odoo project is OCB plus a chosen set of OCA modules plus, where your business is genuinely different, a few small custom modules of our own.

## How Community differs from Enterprise

Enterprise is a polished product with a subscription attached. Some of its features are not in Community. That is a fair business model, but it is not the only way to run Odoo.

Two practical consequences are worth knowing before you choose:

**Some Enterprise features have no Community equivalent.** One we have run into: Community has no Gantt view, so a shop schedule board is the calendar view colored by technician instead.

**Odoo's own hosting is built around Enterprise.** Because of that, you host Community yourself or with a provider. Avunu runs it on our managed platform, on your hardware, or with another host you trust.

If a specific Enterprise feature matters to your business, we say so plainly and help you weigh the options. Checking whether an OCA module covers a gap is where most of our selection work happens.

## Why we build on Community plus OCA

We build on Community and OCA for four reasons:

**No license fees.** Adding a technician, a counter clerk or a seasonal hire does not add a subscription line.

**No lock-in.** The code is open, your data sits in a standard PostgreSQL database, and any qualified Odoo developer can support the system. You can bring it in-house whenever you like.

**Proven building blocks.** OCA modules are reviewed and used by businesses around the world, so most requirements start from existing code instead of a blank page. We write custom code only where we have to.

**A path forward.** The OCA ports its modules to each new Odoo release, so the system has an upgrade route.

OCA modules are published under open licenses. In the module catalog bundled with [odoo-nix](https://github.com/Avunu/odoo-nix), nearly all of the 18.0 modules are AGPL-3 or LGPL-3. Our own open-source Odoo modules are released under AGPL-3, with one LGPL-3 exception (`shopfloor_mobile_camera_scan`). Check a module's manifest for its license before you adopt it.

## Which Odoo version we use

New projects start on Odoo 18.0. It is the default series in odoo-nix, and the series where the OCA catalog is richest. Odoo 19.0 is supported by the tooling, but the OCA's port to it is still in progress, so fewer modules exist there.

At the time of writing, the odoo-nix catalog lists 2,923 module records across 149 OCA repositories for 18.0, and 1,259 across 121 repositories for 19.0. These numbers come from a catalog snapshot and change whenever the catalog is refreshed.

Note

Before you plan around a module, check that it exists for your series. A module that is fine on 18.0 may not be ported to 19.0 yet.

## How we choose modules

We work down a short ladder and stop at the first rung that meets the need.

**Core Odoo.** Configure what Community already does.

**An OCA module.** Look for a maintained module that covers the requirement, and read its manifest and source before adopting it.

**A small custom module.** Write focused glue that connects existing pieces. We prefer several small modules over one large one, and we ship automated tests with them. See [Testing Custom Odoo Modules](/kb/odoo/testing-custom-odoo-modules/).

When we evaluate an OCA module, we check these things:

**It is ported and installable for your series.** The `version` in the manifest starts with the series (for example `18.0.`), and the module is marked installable.

**Its dependencies are acceptable.** A module's `depends` can pull in further OCA repositories. Every extra repository is something to keep updated, so we look at the whole set, not just the module.

**Its maturity matches the risk.** OCA modules carry a development status. In our repair-shop build, `repair_type` is Alpha, and a few repair modules are young Betas. They are small and readable, but we pin exact versions and smoke-test after every update.

**It does not fight the workflow.** One timesheet module we first installed forced a task on every timesheet line, which broke technician time on repair orders, so we removed it. Reading how a module behaves before you commit saves a rework later.

Sometimes two modules collide, or an upstream module has a bug we need to work around. We override it in our own module, and the fix is worth offering upstream to the OCA so the override can be dropped once it is merged.

### Bundles

Common starting points are collected in curated bundles. odoo-nix ships these (defined in its `data/oca-bundles.json`):

| Bundle           | Purpose                          |
| ---------------- | -------------------------------- |
| `base`           | OCA must-have foundation modules |
| `oca-accounting` | OCA accounting suite             |
| `project`        | OCA project management           |
| `purchase`       | OCA purchase workflow            |
| `sales`          | OCA sales workflow               |

OCA software is entirely opt-in. A new project can start as plain Odoo core, with no bundles and no modules, and you add what you need later.

### Adding modules to a project

In an odoo-nix project, run these from the project root inside the dev shell:

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">odoo</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">module</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">add</span>
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">odoo</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">module</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">add-bundle</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">base</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">sales</span>
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">direnv</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">reload</span>
```

`odoo module add` opens a picker over every installable OCA module for the series. Choosing a module resolves the OCA repositories it needs, adds only the new ones as git submodules, records the module in `modules.txt` and re-locks the Python dependencies. `odoo module add-bundle` does the same for a named bundle. Run `direnv reload` afterwards so the environment picks up the new paths.

You can also add a repository from outside the OCA by passing a git URL or `owner/repo` shorthand to `odoo module add`.

Two conventions keep a project readable:

`modules.txt` is the install set, and `odoo db provision` installs everything in it on a new database.

Your own modules live in `custom/`, and OCA repositories live in `modules/`. Many projects keep `modules.txt` to OCA modules only and install their own modules explicitly, for example from the Apps menu. Nothing in odoo-nix forces that, so follow what your project already does.

The full workflow is in [Odoo Development Environment](/kb/odoo/odoo-development-environment/).

## Why every project is pinned

Every OCA repository is a git submodule, and every Python dependency is locked. What we test is exactly what runs in production, and an update is a deliberate step, never a surprise. After pulling new module versions, we run the project's tests and smoke-test the workflows that matter before anything reaches a live system.

## What is in this section

The Odoo section covers the system from the workstation to the finished workflow:

[Odoo Development Environment](/kb/odoo/odoo-development-environment/): set up a reproducible local Odoo with OCB, OCA modules, a database and a mail catcher.

[Testing Custom Odoo Modules](/kb/odoo/testing-custom-odoo-modules/): run automated tests against custom modules.

[Repair Shop Workflow on Odoo](/kb/odoo/repair-shop-workflow-on-odoo/): how an auto and heavy-truck repair shop runs from repair order to paid invoice on Community and OCA.

[Migrating from QuickBooks to Odoo](/kb/odoo/migrating-from-quickbooks-to-odoo/): move a business off QuickBooks with a clean cutover.

[Importing Documents from Email into Odoo](/kb/odoo/importing-documents-from-email-into-odoo/): turn emailed documents into Odoo records.

[Two-Way SMS in Odoo with Twilio](/kb/odoo/two-way-sms-in-odoo-with-twilio/): send and receive text messages inside Odoo.

Tip

If you are starting from nothing, read the development environment document next, then the workflow document closest to your business.

Sources

- [github.com/OCA/OCB](https://github.com/OCA/OCB)
- [odoo-community.org](https://odoo-community.org/)
- [github.com/Avunu/odoo-nix](https://github.com/Avunu/odoo-nix)

Need help with Odoo?

Our notes can take you a long way, but sometimes you'd rather have someone who's done it before.

[Odoo implementation](/services/erp/odoo/)

[← PreviousMigrating from QuickBooks to Odoo with a clean cutover](/kb/odoo/migrating-from-quickbooks-to-odoo/)[Next →Set up and work in an Odoo 18 development environment with odoo-nix](/kb/odoo/odoo-development-environment/)

CC0This article is in the public domain ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)), code samples included. Use it however helps you.

On this page

- [The pieces](#the-pieces)
- [How Community differs from Enterprise](#how-community-differs-from-enterprise)
- [Why we build on Community plus OCA](#why-we-build-on-community-plus-oca)
- [Which Odoo version we use](#which-odoo-version-we-use)
- [How we choose modules](#how-we-choose-modules)
- [Bundles](#bundles)
- [Adding modules to a project](#adding-modules-to-a-project)
- [Why every project is pinned](#why-every-project-is-pinned)
- [What is in this section](#what-is-in-this-section)

[Back to top↑](#top)

Services

- [ERP implementation](/services/erp/)
- [Odoo](/services/erp/odoo/)
- [ERPNext](/services/erp/erpnext/)
- [Custom software](/services/custom-software/)
- [Devices & IoT](/services/devices-iot/)
- [Websites](/services/websites/)
- [Infrastructure](/services/infrastructure/)

Resources

- [Our work](/work/)
- [Open source](/open-source/)
- [Knowledge base](/kb/)
- [Insights](/insights/)

Company

- [About](/about/)
- [Team](/about/team/)
- [Partners](/partners/)
- [Contact](/contact/)

Clients

- [Project portal](https://erp.avunu.net/projects)
- [Invoices](https://erp.avunu.net/)
- [Support](https://erp.avunu.net/)

[![Avunu](/brand/avunu-logo-light.svg)](/)[\<av-icon data-jx-static>\<svg viewBox="0 0 24 24" width="20" height="20" fill="currentColor" stroke="none" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false">\<path d="M20.400 20.500h-3.600v-5.600c0-1.300 0-3-1.800-3s-2.100 1.400-2.100 2.900v5.700H9.400V9h3.400v1.600c.5-.9 1.600-1.900 3.400-1.900 3.600 0 4.300 2.400 4.300 5.500v6.300zM5.300 7.400a2.100 2.100 0 1 1 0-4.100 2.100 2.100 0 0 1 0 4.100zm1.800 13.100H3.600V9h3.500v11.500zM22.200 0H1.800C.8 0 0 .8 0 1.700v20.600c0 .9.800 1.700 1.800 1.700h20.400c1 0 1.800-.8 1.800-1.700V1.700C24 .8 23.200 0 22.200 0z">\</path>\</svg>\</av-icon>](https://www.linkedin.com/company/avunu)[\<av-icon data-jx-static>\<svg viewBox="0 0 24 24" width="20" height="20" fill="currentColor" stroke="none" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false">\<path d="M12 .3a12 12 0 0 0-3.8 23.4c.6.1.8-.3.8-.6v-2c-3.3.7-4-1.6-4-1.6-.6-1.4-1.4-1.8-1.4-1.8-1-.7.1-.7.1-.7 1.2.1 1.8 1.2 1.8 1.2 1 1.8 2.8 1.3 3.5 1 .1-.8.4-1.3.7-1.6-2.7-.3-5.5-1.3-5.5-5.9 0-1.3.5-2.4 1.2-3.2-.1-.3-.5-1.5.1-3.2 0 0 1-.3 3.3 1.2a11.500 11.500 0 0 1 6 0c2.300-1.500 3.300-1.200 3.300-1.200.6 1.700.2 2.900.1 3.200.8.8 1.200 1.900 1.200 3.200 0 4.600-2.800 5.600-5.500 5.900.4.400.8 1.100.8 2.200v3.300c0 .3.2.7.8.6A12 12 0 0 0 12 .3">\</path>\</svg>\</av-icon>](https://github.com/Avunu)[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

Avunu LLC · 948 East Philadelphia Street, York, PA 17403 · (717) 814-8540Knowledge base articles are in the public domain[Privacy](/privacy/)[Terms](/terms/)
