Multi-entity manufacturing — separate legal entities, shared masters, inter-entity transfers, per-entity costing, consolidated reporting — is exactly where off-the-shelf ERPs require the heaviest customization. Custom ERP designed around the entity structure delivers the same capabilities without the customization tax. Typical Indian projects: ₹20L–₹40L+, 5–8 months, full audit trail across entities and consolidated reporting.
Why multi-entity manufacturing breaks generic ERPs
Most Indian manufacturing groups grow into multi-entity structures naturally — separate legal entities for different product lines, manufacturing units, sales arms, or family-owned partitions. The ERP problem starts the day inter-entity flows become operational rather than occasional.
Three places where generic ERPs typically struggle:
- Inter-entity stock transfers. Indian inter-state and inter-entity movements have GST implications (IGST on transfers, input credit handling) that generic ERPs handle through manual workarounds.
- Shared masters across entities. Product, vendor, and customer masters often need to be shared across entities while letting each entity maintain its own pricing, terms, and tax setup.
- Consolidated reporting. Group-level P&L and operational dashboards need intercompany eliminations done right. Spreadsheet-based consolidation is the norm in groups that have outgrown their ERP.
“Most Indian groups do not have an ERP problem. They have an inter-entity flow problem that their ERP made worse. The fix is not more ERP. It is a system designed around the group’s actual entity structure.”
What multi-entity custom ERP covers
| Area | What the system handles |
|---|---|
| Entities & legal structure | Each entity as a first-class object with separate statutory books |
| Shared masters | Products, vendors, customers shared across entities; per-entity pricing and terms |
| Inter-entity stock transfers | GST-compliant transfers, IGST handling, input credit flow |
| Inter-entity billing & services | Internal cross-charging for shared services, with eliminations |
| Per-entity statutory | GST returns, TDS, statutory reports per entity |
| Consolidated reporting | Group-level P&L, balance sheet, operational metrics with intercompany eliminations |
| Audit trail | Full per-entity and cross-entity transaction history |
| Role-based access | Users tagged to entities; cross-entity views for group roles |
What custom delivers that off-the-shelf cannot
| Capability | SAP S/4HANA | NetSuite | Odoo / ERPNext | Custom ERP |
|---|---|---|---|---|
| Multi-entity native | Yes — heavy | Yes | Available — limited | Designed around your structure |
| Inter-entity GST handling | Configurable, costly | Configurable | Customization-heavy | Native to data model |
| Consolidated reporting | Available, license-gated | Available | Limited | Built around your group's actual reporting |
| Implementation cost (Indian mid-market) | ₹60L+ | ₹40L+ | ₹15L–₹40L | ₹20L–₹40L+ |
| Customization tax over 5 years | Highest | High | Medium | None |
| Code & data ownership | Vendor-controlled | Vendor-controlled | Self-hosted | Client-owned |
For full TCO across these options, see Custom ERP vs SAP / Oracle / NetSuite: 5-year TCO.
What drives multi-entity ERP cost
- Number of entities — 2 entities vs 8 entities is a different schema
- Complexity of inter-entity flows — simple transfers vs shared services with cross-charging
- Statutory scope per entity — GST, TDS, state-specific filings, ROC compliance
- Consolidated reporting depth — basic group P&L vs investor-grade reporting
- Audit trail and access control — basic vs forensic-level with role-based per-entity access
- AI / analytics layer — group-level dashboards, forecasting, anomaly detection
When multi-entity custom is the right call
- Group has outgrown spreadsheet-based consolidation and is closing books late every quarter
- Inter-entity transfers and cross-charging are operational, not occasional
- Existing ERPs are deployed per entity, with manual reconciliation between them
- Tried to standardize on SAP / NetSuite and the cost or fit broke down
- Need a system the group can own — not a vendor-controlled stack that locks consolidation behind license tiers
When it is not
- Single dominant entity with one or two small subsidiaries — handle subsidiaries in the main entity's ERP with department or branch tagging
- Group is part of a larger conglomerate with mandated SAP / Oracle standardization
- Each entity operates independently with no shared masters or inter-entity flows — separate ERPs are simpler
Group operations stuck across multiple ERPs?
If consolidation is a spreadsheet job, inter-entity transfers are a manual reconciliation, or per-entity ERPs don’t talk to each other, the right answer is one ERP designed around your group structure. 30-minute call.