PMIS Base Company

Features

• Administrator-only Convert to Independent Company action on branch forms.

• Read-only Parent Company field; ordinary hierarchy edits remain blocked.

• Checks the original hierarchy, including the parent, siblings, and archived branches, for accounting, sales, purchasing, inventory, manufacturing, and point-of-sale transactions when the corresponding apps are installed.

• Rejects drafts as well as completed transactions.

• Validates company-checked configuration references after separation, including archived records and company-dependent contact/product properties.

• Rejects branch accounts without a code under the new independent root.

• Preserves descendants and updates their hierarchy paths and root company.

• Rolls back the conversion if existing configuration is incompatible.

Configuration

Requires Odoo 18 Community, base, and web. No accounting or inventory app is installed by this addon. Checks adapt to the installed apps.

The converting user must have Settings administration rights and write access to the branch. The operation does not expand that user's company permissions.

Usage

1. Open Settings > Users & Companies > Companies.

2. Open the parent company and navigate to the branch through Branches.

3. Open the branch and select Convert to Independent Company.

4. Review the branch and its current parent, then choose Convert.

The company form reopens after successful conversion. Refresh other open sessions to reload their company hierarchy. Child branches remain attached to the converted company, including archived children.

Canceling the confirmation leaves the hierarchy unchanged. A company that is already independent cannot be converted again. The action never reparents a company beneath a different company.

Known limitations

• This is a setup correction for unused hierarchies, not a business separation or transaction migration. An empty branch cannot be detached from a parent or sibling that already has transactions in the checked applications.

• No chart of accounts, taxes, journals, defaults, or parent-owned records are copied. Absence of invoices alone does not prove configuration is compatible. Shared parent configuration can require a separate migration.

• Company references are checked using installed models' declared check_company contracts and company-dependent relational fields. Other custom relationships and external integrations require their own assessment before conversion.

• The conversion enters the base ORM directly for the validated parent-field update because Odoo has no extension hook around its hierarchy prohibition. Company-specific write overrides are not called for that update; ORM access checks, constraints, dependencies, hierarchy paths, and write metadata still apply. Custom hierarchy integrations need explicit compatibility review.

• Company archiving is provided separately by OCA res_company_active. This addon neither installs nor replaces it.

TODO

Support for separating hierarchies with transactions or migrating shared parent configuration is outside the current implementation.

Bug Tracker

Bugs are tracked on PMISuite Repository Issues. Before opening a new issue, check whether it has already been reported. Include the module and Odoo versions, steps to reproduce, and expected and actual results. Use synthetic examples and redact sensitive information.

Credits

Maintainers

Current maintainer:

This module is maintained by Luxim d.o.o., a company dedicated to the development of program management tools and solutions, as a part of PMISuite.com project.

Luxim is an active member of OCA (Odoo Community Association).