OdooPLM — Product Lifecycle Management for Odoo

OdooPLM is an open-source PLM/PDM extension for Odoo, developed and maintained by OmniaSolutions. It integrates Odoo with the most popular CAD editors and provides document management, BOM versioning, revision workflows, and a browser-based 3D/2D viewer.

This branch targets Odoo 19.0 and contains 36 modules, all built on the core plm module.

📖 Wiki (install, CAD client, user guide, FAQ): https://github.com/OmniaGit/odooplm/wiki 🌐 Full documentation: https://odooplm.omniasolutions.website 🐛 Issues and support: https://github.com/OmniaGit/odooplm/issues 🚀 Live demo: https://v19.odooplm.cloud — admin / admin

Run it with Docker

OdooPLM is published as a ready-to-run Docker image, on GitHub Container Registry and on Docker Hub. A single command gives you Odoo with the whole community PLM suite in the addons path, a PostgreSQL database and a working PLM server on the first boot — no database wizard, no dependency installation.

git clone --branch 19.0 https://github.com/OmniaGit/DockerOdooPLM.git odooplm-19
cd odooplm-19
docker compose up

Then open http://localhost:8069.

Each variant also has a -demo tag that boots already populated — the sample product of plm_demo over three BOM levels, its 3D models, ballooned assembly drawings and the spare parts manual that prints from them. Log in with admin / admin.

The images are rebuilt every week, against both the PLM sources and the official Odoo image, and every build is started and verified before it is published. Images, Compose stack and documentation: https://github.com/OmniaGit/DockerOdooPLM

CAD Client

The desktop CAD client (connector) is hosted on SourceForge:

https://sourceforge.net/projects/openerpplm/

It is a proprietary application distributed by OmniaSolutions; the server modules in this repository are open source.

The client supports the following CAD editors:

The client communicates with Odoo via the REST API exposed by the plm module (/plm_document_upload/login, /plm_document_upload/upload, etc.) over HTTP on port 80.

Modules

Core

Document & Viewer

BOM

Product & Weight

Manufacturing & Production

Purchasing & Sales

Reporting & Language

Misc

Not an Odoo module

Architecture Overview

Versioned objects — revision.plm.mixin

Every PLM object (product, document, BOM) inherits plm/models/plm_mixin.py. It provides:

• engineering_code + engineering_revision — unique pair, DB-enforced
• engineering_state — lifecycle state machine: draft → confirmed → released ↔ undermodify → obsoleted
• Write-protection in confirmed, released, undermodify, obsoleted states
• Chatter (mail.thread) and activity tracking

Key models

Installation

The Docker images are the quickest way to a running server. To add OdooPLM to an Odoo instance you already run, follow this section.

Requirements

The core plm module declares no external Python dependency — it installs on a stock Odoo 19.0, and pulls in base, board, product, mrp and stock_account. The extra packages belong to specific optional modules:

aaa_requirements.txt collects the whole set, with the versions the conversion stack needs pinned:

pip install -r aaa_requirements.txt

Install from PyPI

The whole suite is published as a single wheel, versioned after the plm module:

pip install odooplm            # the modules alone
pip install "odooplm[full]"    # with every optional module's dependency

Extras follow the modules that declare them: cad (the conversion stack), pack (plm_pack_and_go), translate (plm_auto_translator), full (all). The addons land in odoo/addons, so they are on the addons path with no further configuration.

cadquery is installed from git in aaa_requirements.txt, because no PyPI release carries the OCP build the STEP reader needs. PyPI forbids a URL in a wheel's dependencies, so pip install "odooplm[cad]" takes the PyPI release instead. For server-side conversion, install from aaa_requirements.txt.

plm_demo is not in the PyPI package. It exists to be looked at, not to be installed on the production database a pip install is meant for, and it carries several MB of CAD payload. Get it from a git clone or from the Docker -demo tags.

Get the source

The 3D and DXF viewer libraries are git submodules, so clone recursively:

git clone --recurse-submodules -b 19.0 https://github.com/OmniaGit/odooplm.git

Add the directory to addons_path in odoo.conf, restart Odoo and install from the Apps menu, or from the command line:

# Core only
odoo -d <database> -i plm

# Core, web viewer and server-side conversion
odoo -d <database> -i plm,plm_web_3d,plm_automated_convertion

# A populated PLM to look at — evaluation and training only,
# and only from a git clone: the PyPI package leaves plm_demo out
odoo -d <database> -i plm_demo

Development

# Auto-reload XML (frontend development)
odoo --dev=xml

# Run all PLM tests
odoo --test-tags=odoo_plm

# Run specific module tests
odoo --test-tags=odoo_plm,odoo_plm_web_revision,plm_automatic_weight

Commit message format: [TAG] | Description — tags: FIX, ADD, IMP, MOD.

Code quality: pre-commit run --all-files

The hooks are deliberately small: the checks that find real breakage without rewriting a line — check-xml, check-yaml, merge and case conflicts, broken symlinks, debug statements, docstring first — plus flake8 as a report only, and a local hook that bumps the __manifest__.py patch version of every module with staged changes. The formatters (black, isort, prettier) were dropped: they no longer install on current Python, and bringing them back means reformatting the repository in one go. See the comment at the top of .pre-commit-config.yaml.

See the Contributing wiki page before opening a pull request.

Python dependencies are generated

aaa_requirements.txt is generated — do not edit it. A module's python packages are declared in the external_dependencies of its __manifest__.py, their versions in scripts/requirements_pins.txt, and the file is written from both:

python3 scripts/sync_requirements.py           # regenerate
python3 scripts/sync_requirements.py --check   # fail if it drifted

The pre-commit hook regenerates and stages it whenever a manifest changes, and the same data feeds extras_require in setup.py, so the requirements file and the wheel cannot disagree.

Releasing

Tag the commit v19.0.<something> and .github/workflows/publish.yml builds the sdist and wheel, verifies the requirements file matches the manifests, runs twine check and publishes to PyPI through an OIDC trusted publisher. The package version is the plm module's version, which a pre-commit hook bumps on every commit so a tag is always publishable.

License

The suite is deliberately split in two.

The core module plm is LGPL-3: it can be integrated into other products, including proprietary ones, without those products having to be published.

Every other module is AGPL-3: extending them, distributing the result or serving it over a network carries the obligation to publish the work under the same licence. The intent is simple — anyone is welcome to build on the core, and whoever builds a business on top of the extensions gives back what they add.

The licence of each module is declared in its __manifest__.py, which is the authoritative source, and repeated in the header of its sources.

The desktop CAD client is a separate, proprietary product and is not covered by these licences.

LICENSING.md is the full reference: the module-by-module map, what the split means for integrators, hosters and researchers, the licensing of the aggregates (git, PyPI, Docker) and of the vendored third-party components. The root LICENSE carries the AGPL-3.0 text, the strongest obligation present in the aggregate; it does not relicense plm.

© OmniaSolutions — https://www.omniasolutions.website