Multi-Branch and Multi-Company ERP
Run more than one company and many branches from one login, with the right access and approvals for every person.
Can one ERP run several companies and branches?
Yes. TradeFlow supports more than one company, with branches and departments within each. Each branch has its own code, address and GSTIN, key documents record their branch, custom roles decide who sees and changes what, you can set approval rules recording who should approve which amounts, and an audit log covers changes to companies, branches, departments and settings.
Who it is for
- Business groups with more than one GSTIN or legal entity
- Businesses with branches in several cities
- Owners who need control without doing every approval themselves
Common problems for multi-branch businesses
- 01
A separate system for every company
Each entity runs its own software or file, and the owner switches between them to see the group.
- 02
Branches with their own GSTIN
Branches in different states have their own registrations and addresses, kept outside the ERP.
- 03
Which branch made this sale?
Orders and receipts are not tagged by branch, so branch performance is guesswork.
- 04
Everyone can see everything
Staff can see or change modules they do not work in, such as accounts or pricing.
- 05
Large transactions go through unapproved
Big orders and discounts are approved informally, or not at all.
- 06
No trail of who changed what
When a figure changes, there is no way to see who changed it or when.
How TradeFlow addresses them
01A separate system for every company
More than one company runs from one login.
- Multiple companies
02Branches with their own GSTIN
Each branch has its own code, address, contact details and GSTIN.
- Branch GSTIN & details
- Branches & departments
03Which branch made this sale?
Sales orders, delivery challans, purchase orders, goods receipts, credit notes and journal entries record their branch.
- Branch on documents
04Everyone can see everything
Role-based permissions control access to each module, and custom roles can be created alongside the built-in ones.
- Role-based permissions
- Custom roles
05Large transactions go through unapproved
Approval rules set, for each module, the minimum amount and the role required to approve, and invoices can be routed to named approvers.
- Amount-based approval rules
- Approval matrix
- Invoice approvals
06No trail of who changed what
The audit log records who changed what, and when, for companies, branches, departments and settings, plus a growing set of other records — not every module yet.
- Audit log
Setting up a group in TradeFlow
- 1
Companies
Add each company in the group.
- 2
Branches
Add branches with code, address and GSTIN.
- 3
Departments
Set up departments within the company.
- 4
Warehouses
Add the warehouses each business runs.
- 5
Roles
Use built-in roles or create your own, with module permissions.
- 6
Approval rules
Set minimum amounts and approving roles per module.
- 7
Transact
Orders, challans, receipts and journals record their branch.
- 8
Review
Check the audit log for who changed what.
Your group structure, inside the ERP
More than one company from one login; branches with their own code, address, contact details and GSTIN; departments within each company; warehouses per business.
- Multiple companiesRun more than one company from one login.
- Branches & departmentsSet up branches and departments within a company.
- Branch GSTIN & detailsEach branch has its own code, address, contact details and GSTIN.
- Multiple warehousesRun several warehouses, each with its own stock.
Every key document knows its branch
Sales orders, delivery challans, purchase orders, goods receipts, credit notes and journal entries record the branch they belong to.
- Branch on documentsSales orders, delivery challans, purchase orders, goods receipts, credit notes and journal entries record their branch.
The right access and the right approvals
Module-level permissions, custom roles, approval rules by module, amount and role, and invoice approvals.
- Role-based permissionsControl who can view or change each module.
- Custom rolesCreate your own roles alongside the built-in ones.
- Amount-based approval rulesApproval rules set, for each module, the minimum amount and the role required to approve.
- Approval matrixDefine who approves what.
- Invoice approvalsRoute invoices to named approvers before they go out.
A record of key changes
The audit log shows who changed what, and when, for companies, branches, departments and settings, plus a growing set of other records. It does not yet cover every module.
- Audit logSee who changed what, and when.
Who TradeFlow multi-branch is suitable for
- Business groups with more than one company or GSTIN
- Traders and distributors with branches in several cities or states
- Owners who delegate approvals by amount
- Businesses that want every order, challan and journal entry tagged with its branch
- Teams where each person should see only their own work
- Businesses that need an audit trail
Frequently asked questions
Can TradeFlow run more than one company?
Yes. More than one company can be run from one login.
Can each branch have its own GSTIN?
Yes. Each branch has its own code, address, contact details and GSTIN.
Which documents record the branch?
Sales orders, delivery challans, purchase orders, goods receipts, credit notes and journal entries record the branch they belong to.
Can I create my own roles?
Yes. Custom roles can be created alongside the built-in ones, with permissions per module.
Can approvals depend on the amount?
You can configure them to. Approval rules record, for each module, the minimum amount and the role required to approve — but TradeFlow does not yet enforce these amounts automatically or route approvals based on them. Approving a purchase order or an expense is a manual step, taken by whoever holds permission for that module.
Can I see who changed a record?
For many records, yes. The audit log covers changes to companies, branches, departments and settings, and to a growing set of other records. It does not yet cover every module — for example, changes to expenses, journal entries, sales invoices and products are not currently logged.
See companies and branches set up in TradeFlow
Book a demo and we will show branches, roles, approval rules and the audit log on a sample group.