Expert verified
Your board approved the ERP project six weeks ago. But with three different locations running different systems and processes, the real challenge is not selecting software, but finding the right implementation partner to standardise the business without disrupting it.
You have three ERP vendors shortlisted. Their demos are impressive, but implementation risk is the real concern. Only 31% of ERP projects reportedly go live fully on time and on budget, while 14% are abandoned. For manufacturers, average implementation costs reportedly run 215% over budget.
So you must find a partner who can make it work across the group.
This listicle compares top ERP consulting options for ₹100 Cr+ manufacturing businesses in India, including where PKC’s independent, process-first approach fits for mid-market and family-led manufacturers moving to a single group-wide system.
What Manufacturing Businesses Running Multiple Plants Should Look for in an ERP Consultant
A single-plant ERP rollout is largely about configuration. Across multiple plants, warehouses, or branches, it needs standardisation first, followed by configuration.
So before evaluating any consulting firm, here’s what you need look for an manufacturing ERP consultant:
Multi-entity data architecture:
Your consultant needs to have done this before. Consolidating data from three plants with different charts of accounts, different item codes, and different bill of materials structures is not the same as implementing ERP for a single entity. The consultant should be able to show you how they have handled multi-entity consolidations in the past.
Plant-level variation handling:
Your Pune plant makes different products from your Hosur plant. The production workflows are different. The quality control processes are different. A good consultant does not force the same template on every plant. They design a core ERP configuration that works for all plants, with plant-specific variations where needed.
Change management at scale:
Rolling out ERP across multiple plants means managing change across multiple sets of stakeholders and plant managers with different priorities. Your consultant needs a structured change management approach that works across locations.
Post-go-live support:
The vendor’s implementation team will move on to the next client after go-live. Your consultant should not. Multi-plant rollouts have issues that only surface when Plant 3 goes live, data reconciliation problems that take weeks to resolve, and user adoption challenges that emerge months after the system is in place. Your consultant needs to be there for all of it.
Industry-specific manufacturing knowledge:
Manufacturing ERP is different from retail ERP or services ERP. Your consultant needs to understand bills of materials, routings, work-in-progress tracking, production scheduling, and shop floor data collection. If they have never worked in a manufacturing environment, they will not know what questions to ask.
CFOs often wonder if they could just manage the implementation with the vendor’s support and skip the consultant entirely?
Your internal teams can handle parts of this project. Your finance team can define the financial reporting requirements, your IT team can manage the technical infrastructure, and the vendor’s implementation team can configure the software. But none of these groups can ensure the ERP actually improves how your manufacturing business runs across all plants.
If you have a single plant, clean processes, and a capable internal team, you may be able to manage the implementation with the vendor’s support. But if you are rolling out across multiple plants with inconsistent processes, the risk of getting it wrong is high and the cost of getting it wrong can be severe. You end up with a system that no one trusts, the manual workarounds never go away, and decisions get made on inaccurate data.
Vendor-Aligned Consultants vs Independent ERP Advisors
For a CFO, one of the most important ERP decisions is understanding the difference between a vendor-aligned implementation partner and an independent ERP advisor.
Vendor-aligned implementation partners are consulting firms that have a formal partnership with an ERP vendor like SAP, Oracle, or Microsoft. They are certified, they receive training from the vendor, and they have deep technical expertise in that vendor’s products. They are who the vendor will recommend when you ask for implementation support.
The concern is that their business is tied to a particular ERP ecosystem, so revenue can grow through additional modules, licences, customisation, and implementation. This does not mean improper conduct, but it can create a natural bias toward expanding the solution rather than questioning whether it is needed. Where existing processes do not fit, the answer may be customisation or changing the process, both have cost and operational implications.
Independent ERP advisors are vendor-agnostic and do not earn software licence commissions. Their role is to protect the business’s interests before and during implementation. They can:
- Assess process and organisational readiness before software selection
- Define business and control requirements across plants
- Compare ERP platforms against actual operational needs and budget
- Identify where processes should change and where customisation is justified
- Evaluate and manage the implementation partner
- Review whether the delivered system meets the agreed business requirements
The key difference is who is accountable for the decision. A vendor-aligned partner is primarily accountable for making the selected ERP work. An independent advisor is accountable for helping determine whether it was the right ERP and whether the implementation is delivering the expected business outcome.
For a manufacturer standardising ERP across multiple plants, this becomes more important. The challenge is creating common processes, controls, reporting, and data standards across plants that may have historically operated differently.
Which one do you need?
If you have already selected ERP and are confident in that decision, a strong vendor-aligned partner may be sufficient. If the ERP selection, process design, or implementation approach is still open, an independent advisor is a better option both commercially and operationally.
National Firms With Manufacturing-Specific ERP Practices at Enterprise Scale
For manufacturing businesses there is a large and diverse choice of ERP consultants. These include large, vendor-aligned systems integrators, mid-market specialists, and a small number of genuinely independent advisory firms.
Here’s a look at some popular names:
Accenture
Accenture has one of the largest ERP practices globally, with deep manufacturing expertise across automotive, industrial, and consumer goods. They are aligned with all major ERP vendors including SAP, Oracle, Microsoft and can handle multi-plant rollouts at enterprise scale.
The downside is that accenture is expensive, and for a ₹100–500 Cr manufacturer, you may not get the senior attention your project requires. Junior consultants often staff the bulk of the work.
Deloitte
Deloitte’s ERP practice is strong in manufacturing, particularly in India where they have worked with large automotive and engineering clients. They offer both vendor-aligned implementation services and independent advisory.
Their manufacturing-specific IP includes industry benchmarks and pre-built templates for common manufacturing processes. Like Accenture, they are expensive, and mid-market manufacturers may find themselves lower on the priority list.
TCS (Tata Consultancy Services)
TCS has deep ERP implementation capabilities, with a large pool of SAP and Oracle-certified consultants. They have significant manufacturing experience across automotive, pharmaceuticals, and engineering.
For Indian manufacturers, TCS offers the advantage of local presence and understanding of Indian regulatory requirements. However, TCS is a large systems integrator. The engagement model is usually project-based, with less emphasis on ongoing process advisory.
Infosys
Infosys has a strong ERP practice with manufacturing-specific offerings in automotive, aerospace, and industrial manufacturing. They have developed industry-specific solutions on top of SAP and Oracle that can accelerate implementation for manufacturers.
Like TCS, they are a systems integrator first and their strength is in technical implementation rather than process transformation.
Capgemini
Capgemini has a significant manufacturing ERP practice with expertise in SAP S/4HANA and Microsoft Dynamics. They have worked with Indian manufacturers across automotive, consumer goods, and industrial sectors.
Their approach combines technical implementation with business process consulting, though the business process work is often scoped separately and may not be included in the standard implementation engagement.
Wipro
Wipro’s ERP practice covers manufacturing, with particular strength in SAP implementations for discrete and process manufacturing. They have developed industry-specific accelerators that can reduce implementation time for manufacturers.
Like the other large systems integrators, Wipro’s engagement model is project-based, with post-go-live support typically scoped as a separate contract.
HCL Technologies
HCL has a strong manufacturing ERP practice with significant experience in automotive, aerospace, and industrial manufacturing. They offer end-to-end implementation services across SAP, Oracle, and Microsoft platforms.
Their India presence and understanding of local manufacturing dynamics make them a credible option for Indian manufacturers. However, like other large systems integrators, their engagement model is project-focused, and ongoing process advisory is often treated as a separate engagement.
Tech Mahindra
Tech Mahindra’s ERP practice covers manufacturing, with particular strength in SAP implementations for discrete manufacturing. They have worked with Indian manufacturers across automotive, engineering, and consumer goods.
Their scale and technical expertise are significant advantages, but mid-market manufacturers may find the engagement model impersonal and the resource mix heavily skewed toward junior consultants.’
IBM Consulting
IBM Consulting’s ERP practice covers manufacturing, with particular strength in SAP implementations for large, complex enterprises. They have worked with manufacturers across automotive, industrial products, metals, and consumer goods, including multi-site and global transformations. Their scale, industry expertise, and technology capabilities are significant advantages, but mid-market manufacturers may find the engagement model more complex and expensive than more specialized implementation firms.
Where PKC Fits: ERP Consulting for ₹100 Cr+ Mid-Market Manufacturers With Multiple Locations
If you are a ₹100–500 Cr manufacturer operating across 3 to 5 plants, your ERP challenge is different from that of a large enterprise. You need the discipline of an enterprise rollout, but not the cost, complexity, or layers of a large systems integrator.
This is where we at PKC fit.
We are a 35-year-old, CA-led consulting firm with a strong manufacturing expertise. We are independent ERP advisors, not software resellers. We work across multiple ERP platforms rather than being tied to one vendor.
This means our starting question is: which ERP and configuration best fit your business, processes, controls, and budget?
We start with your processes, not the software
Before recommending an ERP, we assess how your plants actually operate. We map procurement, production, inventory, finance, sales, and reporting processes across locations and identify where practices differ.
This is crucial because an ERP does not automatically fix inefficient processes. It can simply digitise them. If Plant 1 and Plant 3 follow different approval procedures or use different item codes, putting both on the same ERP does not create standardisation by itself.
PKC helps you define the processes and controls that should be common across the group, while identifying where genuine plant-level variations are necessary.
We bring a finance and controls perspective
PKC looks beyond whether the software functions correctly and asks whether it creates the controls your business needs.
That includes access rights, segregation of duties, approval workflows, master-data controls, and audit trails. For example, one user should not be able to create a purchase order and independently approve the related transaction without appropriate controls.
Building these controls into the ERP from the beginning is far better than discovering gaps during an internal or statutory audit after go-live.
We keep vendor selection independent
We work across 30+ ERP systems and do not earn software licence commissions. If you are evaluating SAP, Oracle, Microsoft Dynamics, or a mid-market platform, we compare realistic options against your actual requirements rather than a generic feature checklist.
PKC also evaluates the implementation partner. This gives you an independent view of both the ERP you select and the way it is implemented.
We help you standardise across plants
For a multi-plant manufacturer, the biggest risk often comes after the first successful rollout. By Plant 3 or 4, local teams may start requesting small variations that gradually undermine the original design.
We review each plant’s configuration against the agreed group-wide requirements. The objective is not to force every plant into an identical model, but to ensure that differences are deliberate, justified, and controlled.
The result should be one ERP environment that produces consistent financial and operational information, rather than several plants using the same software but generating different versions of the truth.
How PKC runs a multi-plant ERP consulting engagement:
The engagement for a manufacturer with multiple plants follows a phased approach.
- Process Audit (3 to 4 weeks): Visit each plant, map existing workflows, and identify process inconsistencies across locations.
- Software Selection (3 to 4 weeks): PKC evaluates ERP platforms based on industry fit, headcount, transaction volume, and budget.
- Implementation (8 to 12 weeks for pilot + 6 to8 weeks per additional plant: Implementation begins with a pilot at one plant, followed by a sequential rollout across the remaining plants.
- Post-Go-Live Support & Throughout rollout: On-site support is provided during the first week of each plant’s go-live, followed by remote support for issues that surface in the months after launch.
Evaluation Checklist for Shortlisting an ERP Consulting Partner for a Multi-Plant Rollout
Before you sign any engagement letter, run your shortlisted consultants through this checklist.
Process readiness assessment
Does the consultant assess your process readiness before recommending software?
Do they fix broken processes before digitising them?
Have they done this for a manufacturer with multiple plants?
Vendor alignment
Is the consultant vendor-aligned or independent?
If vendor-aligned, do they disclose their partnership and any incentives?
If independent, have they worked with multiple ERP vendors in manufacturing?
Multi-plant experience
Has the consultant rolled out ERP across multiple plants for a client like yours?
Can they show you a reference from a multi-plant manufacturer?
Do they understand plant-specific variations in production workflows?
Engagement model
Who will staff your project? Senior consultants or junior resources?
What is the ratio of on-site to offshore work?
Who is the single point of accountability?
Post-go-live support
What does post-go-live support look like for each plant?
How long does the support engagement last?
What happens if issues surface months after go-live?
Industry expertise
Has the consultant worked in your specific manufacturing sub-sector?
Do they understand your regulatory and compliance requirements?
Can they speak the language of your shop floor?
Questions to Ask About Post-Go-Live Support Across Every Plant Before You Sign
Post-go-live support is where you really find out the long-term value of a multi-plant ERP rollout. A system may work well at the pilot plant, but Plants 2, 3, and 4 can expose new issues because of different data, users, workflows, and operating practices.
Before signing the contract, ask exactly what support will look like for every plant, not just the pilot location.
1. What does support look like for each plant?
Ask who will support each location, when they will be available, and for how long. Will the team that supported the pilot remain involved, or will a different team take over?
Also clarify whether on-site support will be available during the first week of each plant’s go-live and the response time for critical issues.
2. How long does support continue after go-live?
Do not assume support ends when the system goes live. Data reconciliation problems, reporting gaps, performance issues, and user adoption challenges can appear months later.
Clarify whether support continues for 3, 6, 12, or more months and exactly what is covered.
3. What happens when Plant 3 faces an issue already seen at Plant 1?
Problems resolved at one plant can reappear elsewhere. Your support agreement should ensure that lessons from earlier rollouts are carried forward and recurring issues are fixed at the root rather than separately at each plant.
4. How will you prevent configuration drift?
Local teams may gradually request changes to suit their existing habits. Over time, this can create different versions of the ERP across plants.
Ask how change requests are evaluated and whether their impact on group-wide processes, controls, and reporting is reviewed before approval.
5. How will new users and plants be trained?
Training should be standardised across locations.
Ask who trains new employees after implementation, whether training materials are maintained, and whether refresher training is available. Otherwise, inconsistent system usage can eventually undermine consolidated reporting.
6. What is the handover process?
Clarify how finance, IT, and operations teams will take over day-to-day support. Ask what documentation, configuration records, administrator access, and training will be provided.
7. What happens if the relationship ends?
You should be able to change support providers without losing critical knowledge. Configuration documentation, process maps, design decisions, and administrator access should remain with the business.
8. What will post-go-live support cost?
Clarify whether support is included in the implementation fee or charged separately. If separate, understand whether pricing is fixed, time-and-materials, or retainer-based.
A CFO must assess the partner not only on how well they deliver go-live, but on whether they can keep every plant aligned, supported, controlled, and consistently using the ERP over the long term.
If you are the CFO of a mid-sized Indian manufacturing company and you are planning an ERP rollout across multiple plants, schedule a conversation with PKC.
FAQs
Q1: What is the difference between an ERP vendor and an ERP consultant for a multi-plant rollout?
An ERP vendor sells and develops the software: SAP, Oracle, and Microsoft. An ERP consultant acts as a bridge between your business reality and the software’s capabilities. For a multi-plant rollout, the consultant assesses process readiness, helps select the right platform, maps workflows, manages implementation, and stays engaged post-go-live. The consultant is your advocate; the vendor is selling you a product.
Q2: Why do manufacturing ERP implementations across multiple plants commonly run over budget or timeline?
The primary reasons are weak process readiness, poor stakeholder alignment across plants, treating go-live as the finish line rather than the start of adoption, and inadequate change management. When each plant has its own way of doing things, standardising on a single system requires more time, more customisation, and more user training than anyone anticipated.
Q3: What should a ₹100 Cr+ manufacturer check before appointing an ERP consulting partner?
Check whether the consultant assesses process readiness before recommending software, has multi-plant experience, is vendor-aligned or independent, can show you a reference from a similar manufacturer, and has a clear post-go-live support plan that covers all plants. Also check who will staff your project, senior consultants or junior resources, and what the engagement model looks like for ongoing support.
Q4: Does PKC recommend specific ERP vendors like SAP or Oracle for multi-location businesses?
No. PKC is vendor-agnostic and does not earn commissions on software licenses. They assess your business processes, identify your requirements, and recommend the platform that fits your industry, headcount, transaction volume, and budget. They work across 30+ ERP systems and have no formal partnership with any vendor.
Q5: What post-go-live support should be included in an ERP consulting contract across every plant?
Post-go-live support should include on-site support during the first week of each plant’s go-live, a clear response time for critical issues, coverage for issues that surface months after go-live, a structured handover to your internal team, and phased support that continues through the full rollout cycle. Do not accept a contract that ends at go-live.
Q6: How does PKC combine ERP consulting with process audit for a manufacturer running several plants?
PKC starts with a process audit before recommending any software. For a manufacturer running multiple plants, this means visiting each plant, mapping the existing workflows, identifying process inconsistencies across plants, and fixing broken processes before digitising them. Only after the processes are standardised does PKC recommend and implement the ERP system. This process-first approach is critical for multi-plant rollouts because you cannot standardise on a single ERP if your plants are not running standardised processes.
