Mr. Umesh Loona · CEO, Apex Mart · Botswana / South Africa · 2021
A manufacturing group of 11+ companies on one Odoo multi-company platform across Botswana and South Africa.
← All case studies
Apex Group
11+ companies on one Odoo multi-company platform.
Apex Group of Companies needed one Odoo system that could carry 11+ legal entities across Botswana and South Africa without collapsing their books into a single company. We ran implementation and migration across multiple Odoo versions in the same engagement: shared master data, per-entity accounting, and the access design multi-company operations actually need. CRM, sales, PoS, ecommerce, and PayFast payments sit on the same stack.
11+
Companies on one platform
2
Countries · Botswana · South Africa
2021
Engagement started
Several companies that had to operate as one, without losing their own books.
Apex Group is not a single-company back office scaled up. It is 11+ entities across Botswana and South Africa that need shared operations and separate statutory reality: accounting, inventory, sales, and HR that can see across the group where governance allows, and stay ring-fenced where it must.
Stock Odoo can open multiple companies. The hard part is the design single-company rollouts skip: who sees which company, how master data is shared, how inter-company flows post, and how group reporting stays true when each entity keeps its own books.
That is the shape of the problem the engagement was handed. Implementation and migration ran together across multiple Odoo versions, because putting eleven entities on one platform is both a build and a cutover problem.
Three layers: the multi-company core, the commercial surface, the payment edge.
Layer 01
The multi-company core
Odoo as the system of record across the group. Accounting, inventory, sales, and human resources configured for multi-company operation: shared master data where it belongs, per-entity books where compliance requires it, access rules that match how the group actually governs. The consolidation and visibility design is the part that has to be right before PoS or ecommerce matter.
Layer 02
The commercial surface the group sells through
CRM and sales for relationship and pipeline. Point of sale for counter and branch transactions. An ecommerce storefront (Apex Mart) so the group sells online on the same inventory and customer truth the back office runs. Sales and PoS feed the same stock and reporting layer rather than a second spreadsheet.
Layer 03
The PayFast payment edge
PayFast on the Odoo ecommerce stack so customers in the South African market can pay online against the same orders the ERP owns. Payment confirmation lands back in Odoo; the storefront is not a disconnected checkout.
Multi-company fails quietly when access, stock, and books disagree.
Listing modules is easy. Trust breaks when company A can see company B’s journals, when a PoS sale depletes the wrong warehouse, or when group reporting cannot be reconciled to the entity ledgers finance actually signs.
The hard part of an Odoo multi-company implementation is keeping those seams honest under load: access rights that match governance, shared products that still post to the right company, inter-company flows that leave an audit trail, and ecommerce or PoS tickets that never invent a second inventory truth.
That is the work that decides whether eleven companies on one platform is an architecture or a liability.
The group runs on one Odoo platform, not eleven disconnected systems.
11+
Companies on one platform
2
Countries · Botswana · South Africa
2021
Engagement started
11+ companies across Botswana and South Africa sit on a single Odoo platform with shared master data and per-entity books. CRM, sales, PoS, and the Apex Mart storefront use the same operational stack. Online payments run through PayFast on that ecommerce layer.
The engagement started in 2021 and ran to completion: implementation and migration across multiple Odoo versions, delivered as one programme rather than a perpetual rewrite.
Engagement facts
- Sector
- Manufacturing · multi-company group
- Client since
- 2021 · engagement complete
- Model
- Odoo implementation + migration
- Platform
- Multiple Odoo versions
- Scope
- 11+ companies · accounting · inventory · sales · HR · CRM · PoS · ecommerce
- Footprint
- Botswana · South Africa
- Commerce
- Apex Mart storefront · Odoo PoS
- Integrations
- PayFast (ecommerce payments)
- Localisation
- Southern Africa payment rails · multi-entity books
This proves
Multi-company is an access and books problem first.
Apex Group is the canonical case for putting many legal entities on one Odoo platform without flattening them into one company. Shared masters, per-entity books, commercial surfaces and payments on the same stack, across Botswana and South Africa.
FAQ
Common questions about Odoo multi-company
Can Odoo handle 11+ companies on one platform?
Yes. Odoo multi-company is built for exactly that: many legal entities in one database, with shared masters where you want them and separate books where you must. The work is not flipping a setting. It is access design, inter-company flows, and reporting that still reconcile when each company keeps its own accounts. Apex Group runs 11+ companies that way.
What is the difference between multi-company and multi-database in Odoo?
Multi-company keeps entities in one database with company-aware records, access rights, and consolidation. Multi-database means separate Odoo databases per entity (or per cluster), which avoids some coupling but forces you to reconcile master data and reporting across systems. For a group that needs shared products, customers, and day-to-day visibility, multi-company is usually the right architecture. Multi-database is the exception when isolation or hosting constraints demand it.
How do inter-company transactions and access rights get handled?
Inter-company flows have to post cleanly on both sides and leave an audit trail finance will sign. Access rights have to match governance: who can switch company, who can see only their entity, who can report across the group. That seam is where multi-company implementations earn trust or lose it. We design those rules up front, then prove them against real PoS, sales, and accounting traffic.
Can implementation and migration run in the same engagement?
Yes, when the cutover is part of putting the group on one platform. Apex’s programme combined implementation with migration across multiple Odoo versions so the entities did not land on a stack that needed a second programme immediately. Discovery names the version path, the entity map, and the risks before build starts.
→ Next
Running several companies that need one Odoo multi-company platform?
Tell us how many entities you run and what has to stay separate. We’ll come back with a real assessment, not a demo.