[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/)[NixOS](/kb/nixos/)Add OCA modules to an odoo-nix project

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)[NixOS](/kb/nixos/)13 articles

- [Overview](/kb/nixos/)
- [A NixOS micro desktop for family and friends](/kb/nixos/nixos-micro-desktop-for-family-and-friends/)
- [Add OCA modules to an odoo-nix project](/kb/nixos/adding-oca-modules-with-odoo-nix/)
- [Build a Firefox web kiosk USB drive with web_kiosk](/kb/nixos/building-a-web-kiosk-usb-with-web-kiosk/)
- [Build production images with frappe-nix](/kb/nixos/building-production-images-with-frappe-nix/)
- [Mount and sync cloud storage on NixOS with nixos-rclone](/kb/nixos/mounting-cloud-storage-with-nixos-rclone/)
- [Reference architecture for self-hosting business systems on NixOS](/kb/nixos/reference-architecture-for-self-hosting-business-systems/)
- [Run Frappe as a NixOS service](/kb/nixos/running-frappe-as-a-nixos-service/)
- [Run Odoo as a NixOS service](/kb/nixos/running-odoo-as-a-nixos-service/)
- [Run WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/)
- [Set up a reproducible Frappe development environment with frappe-nix](/kb/nixos/frappe-dev-environment-with-frappe-nix/)
- [Set up an Odoo and OCA development environment with odoo-nix](/kb/nixos/odoo-dev-environment-with-odoo-nix/)
- [Why Nix for business systems](/kb/nixos/why-nix-for-business-systems/)
- [WordPress performance and hardening on Nix](/kb/nixos/wordpress-performance-and-hardening-on-nix/)

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

In NixOS: 13 articles

[Overview](/kb/nixos/)[A NixOS micro desktop for family and friends](/kb/nixos/nixos-micro-desktop-for-family-and-friends/)[Add OCA modules to an odoo-nix project](/kb/nixos/adding-oca-modules-with-odoo-nix/)[Build a Firefox web kiosk USB drive with web_kiosk](/kb/nixos/building-a-web-kiosk-usb-with-web-kiosk/)[Build production images with frappe-nix](/kb/nixos/building-production-images-with-frappe-nix/)[Mount and sync cloud storage on NixOS with nixos-rclone](/kb/nixos/mounting-cloud-storage-with-nixos-rclone/)[Reference architecture for self-hosting business systems on NixOS](/kb/nixos/reference-architecture-for-self-hosting-business-systems/)[Run Frappe as a NixOS service](/kb/nixos/running-frappe-as-a-nixos-service/)[Run Odoo as a NixOS service](/kb/nixos/running-odoo-as-a-nixos-service/)[Run WordPress on FrankenPHP with wordpress-nix](/kb/nixos/wordpress-on-frankenphp-with-wordpress-nix/)[Set up a reproducible Frappe development environment with frappe-nix](/kb/nixos/frappe-dev-environment-with-frappe-nix/)[Set up an Odoo and OCA development environment with odoo-nix](/kb/nixos/odoo-dev-environment-with-odoo-nix/)[Why Nix for business systems](/kb/nixos/why-nix-for-business-systems/)[WordPress performance and hardening on Nix](/kb/nixos/wordpress-performance-and-hardening-on-nix/)

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

NixOSAdd OCA modules to an odoo-nix project

Pick OCA modules or bundles from the odoo-nix catalog, let it add the dependency repos as submodules, and keep modules.txt and the uv lock in sync.

UpdatedOct 5, 2026

Applies toodoo-nixOdoo 18.0Odoo 19.0

Tagsnixosodooocamodules

Reading time11 min

On this page[How the pieces fit](#how-the-pieces-fit)[Add modules from the catalog](#add-modules-from-the-catalog)[What happens after you choose](#what-happens-after-you-choose)[Add a curated bundle](#add-a-curated-bundle)[Add a repo that is not in the catalog](#add-a-repo-that-is-not-in-the-catalog)[What goes into pyproject.toml](#what-goes-into-pyprojecttoml)[Update modules and re-lock](#update-modules-and-re-lock)[Pins, branches and submodules](#pins-branches-and-submodules)[How submodules are cloned](#how-submodules-are-cloned)[Where OCB comes from](#where-ocb-comes-from)[Checklist](#checklist)[Related documents](#related-documents)

This document explains how `odoo module add` and `odoo module add-bundle` work in an [odoo-nix](https://github.com/Avunu/odoo-nix) project: where the module list comes from, which repos get cloned, what gets written to `modules.txt` and `pyproject.toml`, and how to hold a repo at a version you control. Use it when you want to install an OCA module, or when an add did something you did not expect.

## How the pieces fit

An odoo-nix project keeps its Odoo code in three places, all relative to the project root:

| Path       | Contents                                                                    |
| ---------- | --------------------------------------------------------------------------- |
| `odoo/`    | The OCB source, a git submodule on the branch that matches your Odoo series |
| `modules/` | One git submodule per OCA (or third-party) repo                             |
| `custom/`  | Your own modules                                                            |

Two files describe what you want installed:

`modules.txt` lists the modules you chose, one name per line. `odoo db provision` installs these into a new database.

`pyproject.toml` holds the Python dependencies. odoo-nix writes two managed blocks into it, and `uv.lock` is the lock file built from it.

The module catalog is a JSON file shipped inside odoo-nix (`data/oca-modules.json`). It has one record per module and series, taken from each module's manifest: name, repo, version, whether it is installable, and its `depends` list. The picker and the dependency resolver both read this file, so they never need the network to answer "which repo has this module?".

Note

`odoo module add`, `odoo module add-bundle` and `odoo project update` only work in the dev shell of a project checkout. The production `odoo` binary has no git checkout and no `modules.txt`, so these commands fail there with a message saying so.

## Add modules from the catalog

Run these from the project root, inside the dev shell.

Run `odoo module add` with no arguments to pick interactively:

```
<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>
```

On a terminal it first asks whether to browse the OCA catalog or add from a git URL. The catalog picker lists every installable module for your project's series, with its repo and a short summary. Modules marked with a star are flagged as applications in their manifest and sort first, but you can select any of them. Type part of a module or repo name to filter, press Tab to mark modules, and press Enter to confirm. Nothing is pre-selected.

If you already know the names, pass them as arguments:

```
<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:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">account_financial_report</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">repair_order_group</span>
```

### What happens after you choose

**Resolve the repos.** odoo-nix walks the `depends` of every module you chose, within your series only. Each module found in the catalog contributes its repo. A dependency that is not in the catalog for your series is assumed to be Odoo core, which OCB already provides, and is skipped. The result is the full set of OCA repos your selection needs.

**Add only the missing repos.** A repo counts as present if a folder with its name already exists under `modules/`. For each new repo, odoo-nix checks that the repo has a branch named after your series. If it does, the repo is cloned there and registered as a submodule tracking that branch. If it does not, you get a warning and that repo is skipped.

**Record your choices.** The modules you named, not their dependencies, are appended to `modules.txt`. The file is then sorted and de-duplicated, so diffs stay small.

**Regenerate `pyproject.toml`.** See the next section.

**Re-lock.** odoo-nix runs `uv lock`, then updates the sdist build-dependency block from the lock file and locks again.

When it finishes, reload the environment so Nix re-derives `addons_path` and rebuilds the Python environment, then install:

```
<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>
<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">db</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">provision</span>
```

Warning

Module names you pass as arguments are not checked against the catalog. A typo, or a module that does not exist for your series, still lands in `modules.txt`. No repo is added for it, and the Python step prints a note that the module was not found on disk and skipped. Check the output of the add before you move on.

Note

`odoo db provision` installs `modules.txt` into a database that does not exist yet. On a database that already exists, it migrates instead and does not install anything new. For a database that is already in use, install the new module from the Apps menu after updating the apps list. You can also use odoo-bin's own `-i` flag, because `odoo` passes unknown subcommands and flags through to `odoo-bin`.

## Add a curated bundle

A bundle is a named list of modules defined in `data/oca-bundles.json` inside odoo-nix. The bundles in this version of the file are `base`, `oca-accounting`, `project`, `purchase` and `sales`.

```
<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:#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>
```

With no arguments on a terminal you get a picker showing each bundle's name, label and module count. In a script you must pass the names. odoo-nix expands the bundles into one list of modules, drops any that have no catalog record for your series (it prints which ones), and then runs the same flow as `odoo module add`.

Bundles are plain JSON, so changing one is an edit to the file. If you want a set of your own, that is a change to odoo-nix itself, not to your project.

## Add a repo that is not in the catalog

Give `odoo module add` a git URL or `owner/repo` GitHub shorthand and it adds that repo as a submodule instead:

```
<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:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">https://example.com/owner/repo.git</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</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">owner/repo</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</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">owner/repo</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">17.0</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">my-repo</span>
```

The optional second and third arguments are the branch and the submodule folder name under `modules/`. The rules are:

A string with `://` or a `git@` prefix is used as given, on any host. A scheme-less `owner/repo` becomes `https://github.com/owner/repo.git`. Anything else is rejected.

The folder name defaults to the last part of the URL, and the command refuses a folder that already exists or is already registered.

The branch defaults to your Odoo series. If the repo has no such branch, odoo-nix finds the remote's default branch. On a terminal it asks you to confirm that branch. In a script it uses it and says so. A branch you name explicitly must exist on the remote.

odoo-nix scans the clone for `__manifest__.py`, either at the repo root or one folder down. If it finds one module it records it. If it finds several, it asks which to record, and in a script it records all of them. If it finds none, the submodule is still added and nothing goes into `modules.txt`.

Warning

The git URL path does not resolve dependencies. If a third-party module depends on an OCA module whose repo you do not have yet, add that module with `odoo module add <MODULE_NAME>` as well.

## What goes into pyproject.toml

OCA modules are packaged with [whool](https://github.com/sbidoul/whool). Each module's metadata names its dependencies, and `uv` can read it. So odoo-nix does not translate manifests into requirements itself. It only tells uv where every module lives, and uv resolves the rest.

`lib/oca_sources.py` rewrites two blocks, each between marker comments that start with `# >>> odoo-nix:`:

**`[project].dependencies`** gets `odoo` plus one `odoo-addon-<module>` entry for each module in `modules.txt` that exists on disk. These are the install roots.

**`[tool.uv.sources]`** gets `odoo` as a path to the OCB folder, and every module found on disk under `modules/` and `custom/` as an editable path source. Modules are found by looking for `__manifest__.py`, either at `modules/<repo>/<module>/` or `modules/<module>/`, and at `custom/<module>/`.

Everything inside the markers is overwritten on every run, so do not edit it by hand. Anything outside the markers, such as the `[dependency-groups]` block, is left alone. A third marker pair holds build dependencies for packages that only ship as sdists, and it is maintained from `uv.lock` for you.

If uv cannot resolve the environment, the add still finishes, prints a warning that `uv lock` failed, and leaves `modules.txt` and the submodules in place. Fix the conflict in `pyproject.toml` and lock again. For a real version conflict between packages, the odoo-nix README suggests uv's `override-dependencies` setting under `[tool.uv]`, which sits outside the managed blocks.

## Update modules and re-lock

`odoo project update` moves every submodule to the latest commit of its branch, regenerates the two blocks in `pyproject.toml`, and runs `uv lock`. By default it then migrates every database that matches `dbfilter`.

```
<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">project</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">update</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">project</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">update</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--no-migrate</span>
```

Use `--no-migrate` when you want to look at what changed before touching a database.

This is also the way to pick up a hand edit. If you edit `modules.txt` yourself, for example to remove a module, `odoo project update` is the command in the CLI that regenerates `pyproject.toml` from it. The CLI has no command that removes a module or a submodule, and this guide has not verified a removal workflow, so treat that as a manual git operation and review the diff.

## Pins, branches and submodules

Each submodule has two facts that matter: the commit your project records, and the branch named in `.gitmodules`.

**Series branch.** New OCA repos are added on the branch that matches your series, such as `18.0`.

**Recorded commit.** Git records an exact commit for each submodule in your project. Anyone who clones the project with `--recurse-submodules` gets those commits, which is what makes a deployment reproducible.

**Updates ignore the recorded commit.**`odoo project update` fetches the tip of the branch named in `.gitmodules` and checks it out. If you had checked out a specific older commit in a submodule, the update replaces it.

That last point decides how you hold a repo back. The CLI has no per-repo pin. These are the options the code supports:

Do not run `odoo project update` for that project until you are ready, and commit the submodule move when you are.

Point the submodule at a branch you control. Fork the repo, add it with `odoo module add owner/repo <BRANCH> <FOLDER>`, and keep that branch where you want it. The update then follows your branch.

Review the update before you commit it. After `odoo project update --no-migrate`, `git status` shows which submodules moved, and you can revert one you do not want.

Tip

After an update, run `git diff --submodule=log` from the project root to see the commits that came in for each repo before you commit the new pointers.

### How submodules are cloned

Submodules are cloned as partial clones: every commit and folder of the series branch, with file contents downloaded as you check them out. The commits of every other branch are fetched too, so `git switch` to another branch works. OCB is the exception, because its folder history is very large, so it keeps commits only. The first time you enter the dev shell in a new clone, odoo-nix checks out any submodule that clone has never had. It does not bring back one you removed on purpose, and tells you how to restore it instead.

If a submodule folder is registered but empty, the shell tells you, and this command checks out the commits your project records:

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">git</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">submodule</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">update</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--init</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--recursive</span>
```

### Where OCB comes from

In some projects OCB is not a submodule but a flake input, set through the `coreSource` option. In that case `odoo project update` does not move it. It prints a reminder to run `nix flake update` instead, and the lock step temporarily points `odoo/` at a writable copy so that uv can read it.

## Checklist

Run `odoo module add` or `odoo module add-bundle` from the project root.

Read the output for skipped repos, unknown modules and a failed `uv lock`.

Run `direnv reload`.

Run `odoo db provision` for a new database, or install the module on an existing one.

Commit `modules.txt`, `pyproject.toml`, `uv.lock`, `.gitmodules` and the new submodule pointers together.

## Related documents

[Odoo Development Environment with odoo-nix](/kb/nixos/odoo-dev-environment-with-odoo-nix/), for scaffolding the project and the daily `odoo` commands.

[Running Odoo as a NixOS Service](/kb/nixos/running-odoo-as-a-nixos-service/), for deploying the project once its modules are chosen.

Sources

- [github.com/Avunu/odoo-nix](https://github.com/Avunu/odoo-nix)
- [github.com/OCA](https://github.com/OCA)
- [github.com/sbidoul/whool](https://github.com/sbidoul/whool)

Need help with NixOS?

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

[Managed infrastructure](/services/infrastructure/)

[← PreviousA NixOS micro desktop for family and friends](/kb/nixos/nixos-micro-desktop-for-family-and-friends/)[Next →Build a Firefox web kiosk USB drive with web_kiosk](/kb/nixos/building-a-web-kiosk-usb-with-web-kiosk/)

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

- [How the pieces fit](#how-the-pieces-fit)
- [Add modules from the catalog](#add-modules-from-the-catalog)
- [What happens after you choose](#what-happens-after-you-choose)
- [Add a curated bundle](#add-a-curated-bundle)
- [Add a repo that is not in the catalog](#add-a-repo-that-is-not-in-the-catalog)
- [What goes into pyproject.toml](#what-goes-into-pyprojecttoml)
- [Update modules and re-lock](#update-modules-and-re-lock)
- [Pins, branches and submodules](#pins-branches-and-submodules)
- [How submodules are cloned](#how-submodules-are-cloned)
- [Where OCB comes from](#where-ocb-comes-from)
- [Checklist](#checklist)
- [Related documents](#related-documents)

[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/)
