Odoo Multi-Company Setup: A Practical Guide

Groups with more than one legal entity often ask the same question early in an Odoo project: one database or several? For most groups that trade between their entities or share products and customers, the answer is one Odoo database with multiple companies.

What multi-company means in Odoo

In a multi-company database, each company has its own:

• Chart of accounts, journals and taxes
• Fiscal localisation and currency
• Warehouses and stock locations
• Bank accounts and payment methods
• Document numbering and report layouts

Users can be given access to one or more companies and switch between them from the top bar. Reports can be run per company or across several where Odoo supports it.

Shared and separate data

The most important design decision is what to share. Products, contacts and some configuration can be shared across companies or restricted to one. A typical setup:

Sharing products avoids duplicate catalogues, but costing is still kept per company. Decide this before import, because changing ownership of thousands of records later is painful.

Inter-company transactions

When one company sells to another, Odoo can create the matching document automatically. A sales order in Company A generates a purchase order in Company B, or an invoice in A generates a vendor bill in B. This removes double entry and keeps inter-company balances aligned.

Set this up early and test it with real scenarios, including returns and partial deliveries, before go-live.

Users and access

Multi-company access is controlled per user. Give each user only the companies they work in, and set a default company. Record rules then stop users from seeing documents of companies they do not belong to. Test this with a real user account, not as an administrator.

Common mistakes

1. Creating companies after go-live. It works, but it is far easier to plan all entities up front.
2. Sharing everything. Shared price lists or warehouses cause confusing results. Share only what is truly common.
3. Forgetting consolidation. If you need group reporting, plan account mapping for consolidation from the start.
4. One admin user for everything. It hides access problems until real users log in.

When separate databases are better

Separate databases make sense when entities share nothing, run different Odoo versions or editions, or must be fully isolated for legal or ownership reasons. You lose inter-company automation, so weigh that carefully.

Getting it right

Multi-company setups are one of the areas where a few hours of design saves weeks of clean-up. If you are planning a group rollout, our Odoo implementation team can design the company structure, sharing rules and inter-company flows with you, or you can start with a free consultation.