Multi-company and multi-plant
This feature does not exist. Running several legal entities and plants in one workspace with a consolidated view is Wave 2 direction, indicatively Q3 2027, with no committed date.
In short
Multi-company and multi-plant support is not built. The intent is one KanchanFlow workspace holding several legal entities and plants, each invoicing correctly, with consolidated reporting across them. It is Wave 2 with a Q3 2027 direction and no committed date. Several Enterprise features in our matrix reference it, and none of them are available yet either.
Where this actually stands
A manufacturer with two legal entities and three plants currently has an ugly choice: one workspace that cannot invoice correctly per entity, or separate workspaces with no consolidated view of a customer who buys from both. Neither is good, and we do not have a third answer today. Saying so on a public page is better than letting it surface in month two.
The intent is entities as first-class objects with their own tax registration, numbering and bank details, plants underneath them, and customer, pipeline and receivable roll-ups across the group. Our feature matrix already lists multi-entity as an Enterprise capability; that row describes the intended state, not a shipping one, and this page exists to say so.
Capabilities
What this would cover if we build it
What is intended
Legal entities with their own tax registration, document numbering, bank details and terms, with plants underneath, in one workspace.
Consolidated customer view
A customer group buying from two of your entities seen as one relationship with combined exposure — the Enterprise roll-up that customer 360 references.
Correct documents per entity
An invoice belongs to one entity and must carry that entity's registration and numbering. Getting this wrong is a tax problem, not a cosmetic one.
Cross-entity reporting
Pipeline, order book and receivables reported per entity and consolidated, in one base reporting currency.
What breaks without it today
A second legal entity means a second workspace, which means no shared customer view, no consolidated pipeline and duplicate account records. That is the honest cost of the current design, and it is why this is on the Wave 2 list.
Step by step
Where the work stands
There is no workflow to walk through yet. This is what the current position actually is.
- 1
Nothing works yet
One workspace is one operating entity today. Multi-entity is not implemented in any partial form.
- 2
It is a data model change
Entity has to sit above almost every record, which is why it is a Wave 2 item rather than something we can slot in.
- 3
Several features depend on it
Enterprise multi-entity roll-up in customer 360, multi-plant milestones on orders and multi-entity territory all wait on this.
- 4
Status would change here first
If it enters development this page gets a milestone and a progress figure, and the changelog gets an entry on release.
- 5
What to do in the meantime
Run one workspace per operating entity and accept the duplicate customer records, or run the group from one entity and invoice the second outside the system. Neither is good and we are not going to describe them as workarounds.
What this is not
This is not available today — a workspace is a single operating entity, and any matrix row referencing multi-entity describes the intended state.
This is not an ERP, MRP, CAD, BOM, or advanced CPQ system — it manages customer RFQs, quotes, follow-ups, and order handoff.
Tier availability
What you get on each plan
These rows come from the same feature matrix the pricing page publishes. If the two ever disagree, the matrix is wrong and we fix it.
| Plan | Availability |
|---|---|
| Starter | Not available. |
| Professional | Not available. |
| Enterprise | Planned for Enterprise. Not built, no committed date. |
Starter is $39 per user per month, Professional $49, Enterprise $99 plus a $2,000 monthly platform fee. Annual billing is 17% lower. See the full matrix.
Interface
What it looks like
No screenshot. There is nothing built to capture.
We do not publish mockups of unbuilt features as if they were interface captures.
No screenshot. Multi-currency roll-up to one base reporting currency is live and is shown on that feature's page.
Placeholder retained so this page's structure matches every other feature page.
Screenshots are described rather than mocked up. Captures are taken from the build current at the date shown in the changelog, on a sample workspace.
Questions about multi-company and multi-plant
No. A workspace is a single operating entity. If you need two, you need two workspaces, and there is no consolidated view between them.
Related features
Customer 360
Customer 360 with plants and stakeholder mapping
Read moreMulti-currency
Multi-currency quotes, invoices and forecasting
Read moreOn-premise deployment
On-premise deployment
Read moreWhat's shipping today
All 47 features grouped by status on one page, with the newest releases alongside.
Read moreSee a live quote draft built from a real RFQ
Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.
- Delaware LLC
- SOC 2 Type II
- USA Data Centers (AWS)