What's the single most important factor in choosing a manufacturing ERP?

Workflow fit. An ERP that doesn't match your actual production process will fail regardless of features or price. Always test with your own products and workflows in the demo — don't accept generic walkthroughs.

Should we hire an ERP consultant to help with selection?

Sometimes. Useful for large enterprise deployments (₹1Cr+) where vendor lock-in risk is high. Often overkill for mid-market. A good test: if a consultant won't recommend custom or non-traditional vendors, they're probably tied to specific ERP partnerships and won't give you an objective read.

How long does ERP selection typically take?

For mid-market manufacturing: 4–8 weeks if done properly. Phase one is requirements gathering with internal stakeholders (2 weeks). Phase two is vendor demos and scoring (2–3 weeks). Phase three is reference checks, contract negotiation, and final selection (2–3 weeks). Compressing this rarely ends well.

What's the biggest mistake manufacturers make in ERP selection?

Letting the IT team or CFO drive the decision in isolation. The shop floor and production planning teams have to be in the room, and the demo has to test their actual workflows. Many failed ERP rollouts trace back to a system that was 'IT-perfect' but unusable by the people on the line.

How to Choose an ERP for Indian Manufacturing: A 12-Point Checklist

Most manufacturing ERP buyers start by collecting feature lists from three vendors and trying to compare them side by side. It never works. Vendors describe the same feature differently. "Multi-location" means three different things to three vendors. The real evaluation has to be process-driven, not feature-driven.

Here's a 12-point checklist we've evolved over a decade of building manufacturing ERPs. Use it on every vendor call. Score each one out of 10. The vendor with the highest total isn't necessarily the right one — but the one who fails three or more dimensions probably isn't.

The 12-point evaluation framework

1. Production planning fit

Make-to-stock, make-to-order, engineer-to-order — does the ERP support your model natively? Can it handle BOMs with multiple levels, alternates, scrap percentages, by-products? Run through your top 3 product types in the demo. If the vendor struggles, the rest of the demo is theatre.

Red flag: the demo always uses the same simple product. Force them to use yours.

2. Costing methodology

Standard costing, actual costing, FIFO, weighted average, job-based — which methods are supported, and can you mix them across product lines? Indian textile, pharma, and food manufacturers typically have specific costing needs that off-the-shelf ERPs handle poorly.

3. Quality and traceability

Lot/batch tracking from raw material through finished goods. In-process inspections, NCRs, COAs, supplier quality. For pharma: GMP, 21 CFR. For automotive: PPAP, APQP. For food: FSMA-style recall traceability. Test the recall scenario specifically: "given this batch ID, show me every customer who received product made from this raw material lot."

4. Shop-floor integration

Can the ERP receive real-time data from machines, scanners, weighing scales, RFID, IoT sensors? Or is shop-floor data manually entered at end of shift? The difference is the gap between a real-time business and a 24-hour-delayed business.

5. GST and Indian compliance

GST invoicing, IRN generation via IRP, e-way bill, TDS, RCM, schedule M for pharma, factory licence compliance — all native, not via partner add-ons. Ask specifically about: how GST council changes propagate (monthly updates? annual contract? extra cost?).

6. Multi-branch, multi-plant, multi-currency

Inter-company transfers, consolidated financials, branch-specific ledgers, common item masters, currency hedging. If you have multiple plants, demo this with your actual structure. Many ERPs technically support multi-branch but the workflows assume single-plant operations.

7. Mobile and field workflows

Mobile apps for floor supervisors, sales reps, drivers, warehouse staff, quality inspectors. Offline-first or online-only? What works in a plant with patchy WiFi? Show the apps actually running, not just screenshots.

8. Integration capability

Open API? Webhook support? Native connectors for Tally, banking, marketplaces, payment gateways, weighing scales, GST? Or every integration is a custom project at vendor rates? Get the integration roadmap in writing.

9. Reporting and BI

Out-of-the-box reports (P&L by SKU, plant productivity, scrap analysis, customer profitability) plus ability to build custom reports without dev work. Dashboard-builder for shop-floor managers. Export to Excel for the CFO who'll never give up Excel.

10. Implementation methodology and timeline

Waterfall (6-month gantt with UAT at end) or agile (2-week sprints with demos)? Who from the vendor will actually be on your project — the people you met in sales, or a different team? What's the realistic timeline for v1 vs full rollout? Get specific names and CVs of the implementation lead and architect.

11. Total cost of ownership over 5 years

Not just licence + implementation. Add: customisations, integrations, hardware, training, ongoing support, version upgrades, additional users, additional plants. Most vendor quotes cover year 1; the rest is added later. Force the 5-year view.

12. Exit and data portability

If you ever want to leave, can you export all your data in usable form? Source code (custom ERP) or data dump (SaaS)? Format? Cost? Get this in the contract before signing — it's the question vendors hate most.

Bonus checks — the questions vendors hope you won't ask

Can I talk to one of your existing customers in my industry? The strongest signal. Vendors with happy clients arrange it within a week. Others find reasons.
What happens when a critical bug hits at 2am on a Sunday? Real on-call structure, or "we'll get back to you Monday"? For manufacturing systems, this matters.
How often do you ship updates? When was the last major release? Stagnant products lose ground fast.
What's the deal if a key person on your team leaves mid-implementation? Documented continuity plan or "we'll figure it out"?
Show me the audit log for a sample transaction. Tells you whether the system was built for serious use or pretty demos.

Scoring and decision

Score each vendor out of 10 on each of the 12 dimensions. Weight by what matters to your specific business — production planning fit and compliance might be 2x for a pharma company; integration capability might be 2x if you have a complex existing tech stack. Total it up.

The decision rule we use:

Total above 90 (out of 120): strong fit, proceed
70–90: likely workable, but understand the gaps and budget for them
Below 70: walk away no matter how persuasive the sales rep
Any single dimension below 4: even if the total is high, this becomes the project's failure point. Address it or move on.

One last thing

The right ERP for your manufacturing business is the one that fits how you actually operate today and can grow with you over the next 5 years. Not the one with the longest feature list. Not the one with the most certifications. Not the one with the most familiar logo on your CFO's slide deck.

If the checklist surfaces that no off-the-shelf ERP fits your operations cleanly, that's not a failure of the checklist — it's a signal that custom is worth considering. Our take on ERP vs custom for Indian manufacturers goes deeper on that decision.

Either way, the worst ERP decision is the one made under sales pressure without testing the right things. Take the time. Use the checklist. Pick the right one for your shop floor, not the right one for the vendor's quarterly target.