Multi-Company Odoo for a Textile Group: From Paper to One System

Real client project, name withheld. Delivered at Master Software Solutions; my role is set out below. The client's name and identifying details are left out.

A silk textile business made up of several companies replaced paper records, spreadsheets and a standalone CRM with one multi-company Odoo database, with intercompany transactions created automatically.

The problem

The group runs several companies that buy from, sell to and move stock between each other. Stock existed only on paper, so nobody knew what was available. Every intercompany sale was keyed in twice, finance reconciled the companies by hand, and there was no way to see the group as a whole.

The existing process

Paper records in every department, spreadsheets, and a CRM used only for taking orders, with no connection to stock, production or accounts. Textile details such as fabric type, roll quantities, colour codes and weave specifications were recorded inconsistently.

Business requirements

My role

I delivered this project at Master Software Solutions as consultant, tech lead, project manager and delivery manager: mapping each company's processes and designing the multi-company setup, leading the MSS developers who built the custom parts, planning and running all six stages from discovery to hypercare, and owning delivery through go-live.

The solution

One Odoo database with a company for each entity, each with its own chart of accounts and role-based access. Sales and CRM, inventory, manufacturing and accounting were configured together, so an order flows from the salesperson through stock and production to an invoice. When one company sells to another, the matching purchase order, stock transfer and accounting entries are created on the other side automatically.

Key decisions

Odoo modules used

Customizations

Implementation

Six stages: discovery and process mapping with each team; solution design; configuration and customisation; data migration, with old CRM data and paper records cleaned, mapped and checked against the source; user acceptance testing with the client's team; and go-live with hands-on support through the first weeks.

Challenges

Results

What I’d tell a similar business

  • If your companies trade with each other, decide early whether they belong in one database. Automated intercompany flows depend on it.
  • Agree your product attributes before migration. Free-text fields become unreportable very quickly.
  • Paper records need cleaning before they’re migrated, not after. Budget time for it.

Related guides: how to set up multi-company in Odoo, common multi-company mistakes and how to set up reordering rules.

Running several companies that trade with each other?

Tell me how your companies buy from and sell to each other today, and I'll explain how a multi-company Odoo setup would handle it.

Get in touch View services