eCommerce and Retail
Odoo for online and physical retail: connected shops, accurate stock across channels, fast fulfilment and clean accounts.
Enterprise and Multi Entity Groups
Odoo for groups with several companies, countries and currencies, where consolidation, controls and governance matter as much as features.
Odoo is often thought of as a system for small companies. It is also used by groups with many legal entities, and the way it handles multiple companies in one database makes it a practical choice for that structure. What changes at this scale is the weight of governance: who can see what, how intercompany transactions are handled, how the group reports, and how change is controlled once dozens of departments depend on the system.
We work with groups on the design that makes multi company Odoo work: the company structure, the chart of accounts, shared and local master data, access rights, intercompany rules and the reporting layer. We also bring the project discipline that larger organisations expect, including formal change control and documented decisions.
What we set up for groups
- Company structure in a single database, with shared or separate charts of accounts as your reporting requires
- Country localisations for each entity, covering tax, statutory reports and local formats
- Intercompany sales, purchases and stock transfers with automatic mirror documents
- Shared master data for products, customers and suppliers, with local overrides where needed
- Access rights and record rules per company, role and region
- Consolidated reporting through Odoo, or an export to your consolidation or BI tool
- Approval workflows for purchases, expenses and journal entries
- Documents, e signature and audit trails for compliance
Why groups work with us
- We design the company and account structure before configuration, because it is the hardest thing to change later.
- We work with your finance, IT and compliance functions as separate stakeholders with separate sign offs.
- Roll out is planned entity by entity, with a template that each new company inherits.
- We are comfortable with procurement processes, security questionnaires and formal contracts.
The usual problem and how we work instead
The usual problem
- Each entity was implemented separately and the configurations have diverged
- Intercompany transactions are entered twice and reconciled at year end
- Access rights were set up as everyone sees everything and never revisited
- The group has no single view of stock, receivables or margin
How we work instead
- A group template that defines shared configuration, with documented local exceptions
- Intercompany rules that create the matching document on the other side automatically
- A role matrix agreed with compliance and implemented as record rules
- Group dashboards and reports built on a consistent chart of accounts and analytic structure
A typical group programme
Design
Company structure, chart of accounts, master data ownership, intercompany model, reporting requirements and governance, agreed with group finance and IT.
Template build
The first entity is implemented as the template, with every configuration decision documented.
Roll out
Further entities are onboarded in waves, each with local tax and legal configuration, data migration and training.
Steady state
The group moves into managed service with a change board that approves configuration changes across entities.
Frequently asked questions
Do you provide project management when another company is doing the implementation?
Yes. We act as an independent project manager alongside another Odoo partner or an internal team. Roles and responsibilities are set out in writing at the start so that there is no ambiguity about who owns what.
What does change management mean in practice?
Deciding who is affected by the new system and how their work changes, telling them why the change is happening before telling them how, training them by role close to go live, and checking that each department is ready before the date is confirmed. It is planned from the first week of the project rather than added when adoption problems appear.
How do you control scope?
Every change request is estimated, its effect on the plan and budget is shown, and the sponsor decides. Nothing is added to the scope by agreement in a workshop alone. This is uncomfortable in the moment and saves the project later.
How do you report progress?
A short written status every week: what was done, what is next, what is at risk and what decisions are needed. Steering meetings at each milestone review the plan, the budget and the risk register.
What if the project is already in trouble?
We start with a short review of scope, plan, decisions, data and readiness, and give you a written view of what is wrong and what it would take to recover. Recovery usually means narrowing the first go live and rebuilding the plan around readiness rather than a date.
Other industries
Services and Consulting Firms
Project based businesses use Odoo to plan work, record time, bill accurately and see which engagements actually make money.
Manufacturing and Supply Chain
Odoo Manufacturing, Inventory, Purchase and Quality configured for make to order, make to stock and subcontracted production.
Insights on this topic
Odoo Studio: when no code customisation is the right answer, and when it is not
What Odoo Studio does well, where it causes problems, and the rules we apply before adding a field, view or automation with it.
What Is Odoo ERP? The Complete Guide to Odoo ERP, Apps, Features, and Pricing
Odoo ERP is an integrated business management platform that brings different business functions into one system. It includes applications for accounting, sales, CRM, inventory,…
How to run a requirements workshop for Odoo
A practical method for the discovery workshops that shape an Odoo implementation: attendees, agenda, questions and outputs.