A factory owner in Coimbatore told me last month that he'd evaluated seven ERPs in nine months, sat through fourteen demos, and was more confused now than when he started. Every vendor had a slick deck. Every demo looked perfect. But nobody told him what actually matters for a manufacturing SME doing ₹8-25 crore revenue with 40-200 people on the floor. This guide is the document I wish someone had handed him before he wasted a year.
If you run a manufacturing business in India — sheet metal, machining, fabrication, plastics, food processing, packaging, or any kind of job shop — this is the manufacturing ERP buyer's guide written for your reality. Not for a 5,000-person MNC. Not for a Silicon Valley startup. For the factory owner in Rajkot, Pune, Ludhiana or Chennai who needs a system that works without a 12-person IT department.
What a manufacturing ERP actually does (and what it does not)
Let us start with the basics because there is genuine confusion in the market. Most Indian SME owners have used Tally for years. Many assume an ERP is just a bigger version of Tally. It is not.
Tally is accounting software. It handles your books, GST returns, ledgers, and basic stock management. It does this extremely well. But it was never designed to answer the questions that keep a manufacturing owner up at night: What is the actual cost of producing this product? Which jobs are running behind schedule? How many metres of SS304 sheet do we actually have across three godowns? Why did we quote ₹4.2 lakh for this job but spend ₹4.9 lakh making it?
A manufacturing ERP connects the dots between your sales pipeline, product costing, raw material inventory, production floor, dispatch, and accounts. When a customer enquiry comes in, the ERP should help you build a Bill of Materials, calculate accurate costs, generate a professional quotation, convert it to a production order, track materials consumed, monitor job progress, manage dispatch, generate the GST invoice, and update your books — all as one connected flow.
The key word is connected. Most Indian factories today have these functions running in silos — quoting in Excel, inventory in a register or separate software, production tracking on a whiteboard, and accounting in Tally. The ERP replaces the gaps between these silos.
What an ERP is not
An ERP is not a magic wand. It will not fix broken processes. If your BOM is wrong, the ERP will calculate wrong costs faster. If your team does not enter data, the reports will be empty. An ERP is a structured system — it works when you work with it.
It is also not a replacement for domain expertise. The system will not tell you that SS316L welds differently from SS304 or that your powder coating vendor takes 3 days during monsoon. That knowledge stays with your team. The ERP organises it so it is accessible to everyone, not locked in one person's head.
The 10 features that matter for Indian manufacturing SMEs
After working with hundreds of factories, these are the ten capabilities that separate a useful manufacturing ERP from an expensive disaster. Evaluate every vendor against this list.
1. Quoting and estimation
This is where revenue starts. Your ERP should let a sales engineer generate an accurate, professional quotation within minutes — not hours. That means a product catalogue with base prices, a BOM-driven costing engine, configurable pricing rules (quantity slabs, customer categories, payment terms), and approval workflows so the owner only gets pulled in for exceptions.
The quotation should auto-calculate GST based on HSN codes, include your standard terms and conditions, and be shareable as a branded PDF on WhatsApp or email. If your ERP cannot do this without customisation, walk away.
2. Bill of Materials (BOM) management
For any manufacturer making assembled or engineered products, the BOM is the foundation. Your ERP needs multi-level BOM support (sub-assemblies within assemblies), the ability to handle alternate materials, wastage percentages, and bought-out components. The BOM should directly drive your costing, purchase requirements, and production planning.
3. Inventory management
Not just stock in, stock out. A manufacturing ERP should track raw materials, work-in-progress, finished goods, and scrap — across multiple locations. It should support batch tracking for materials where traceability matters, reorder point alerts, and physical stock reconciliation. Integration with barcode scanners is a bonus, but the basics must be solid first.
4. Production tracking
At minimum, the ERP should let you create production orders from confirmed quotations, assign them to work centres, and track progress by operation. You should be able to see which jobs are on the floor, which are waiting for material, and which are stuck at a bottleneck — without walking the shop floor and asking five people.
5. Job costing
This is the feature that pays for the ERP. Every job should accumulate its actual costs — material consumed, labour hours, outside processing charges, overheads — against the estimated cost from the quotation. When the job is done, you should see at a glance whether you made money or lost it, and by how much. Most Indian SMEs discover they are losing money on 15-25% of their jobs once they start tracking actual costs.
6. GST compliance
Non-negotiable for India. The ERP must handle CGST, SGST, IGST calculations correctly based on place of supply rules. It should generate e-invoices, e-way bills, and GST return data (GSTR-1, GSTR-3B) without manual intervention. HSN code mapping at the product level should be standard, not an add-on.
7. Dispatch and logistics
From packing list generation to transporter details to delivery tracking, the dispatch module closes the loop between production and revenue recognition. It should link back to the sales order so you can track fulfilment percentages and pending dispatches.
8. Dealer and distributor management
Many Indian manufacturers sell through a dealer network. The ERP should handle dealer-specific pricing, credit limits, outstanding tracking, and ideally a dealer portal where distributors can place orders and check stock availability without calling your sales team.
9. Reporting and dashboards
If you cannot see your order book, pending dispatches, cash flow, and margin analysis on a single screen, the ERP is not doing its job. Reports should be real-time, not batch processed overnight. And they should be accessible on a mobile phone — because Indian business owners do not sit at a desktop all day.
10. Mobile access
Your sales team is on the road. Your owner is in meetings. Your production supervisor is on the floor. If the ERP only works on a desktop browser inside the factory LAN, adoption will die within two weeks. Mobile access — at minimum for approvals, dashboards, and quote sharing — is essential.
Pricing models: understanding what you are actually paying for
ERP pricing in India is notoriously opaque. Here is how the models actually work, stripped of marketing language.
Per-user pricing
You pay a monthly or annual fee for each user who logs into the system. This is the most common model for cloud ERPs. It sounds simple, but it creates a perverse incentive — you end up restricting access to save money, which means the shop floor supervisor who should be updating job status does not have a login, and the data stays incomplete.
Flat pricing
A fixed monthly or annual fee regardless of user count. This is better for factories because you want maximum adoption. The risk is that "flat" sometimes means flat up to a limit — read the fine print.
Per-transaction pricing
Some vendors charge based on the number of invoices, quotations, or purchase orders processed. This model penalises growth. Avoid it.
Cloud vs on-premise
Cloud means the software runs on the vendor's servers and you access it via browser. On-premise means you install it on your own server inside the factory. Cloud is almost always the right choice for SMEs — no server maintenance, automatic updates, access from anywhere. The only exception is if you have extremely poor internet connectivity at your factory location, in which case a hybrid model (local server with cloud sync) may work.
Realistic pricing for Indian manufacturing SMEs
| Category | Monthly Cost (INR) | What You Typically Get |
|---|---|---|
| Entry-level cloud ERP | ₹3,000 - ₹8,000/month | Basic quoting, inventory, invoicing, GST. 3-5 users. Limited production tracking. |
| Mid-range manufacturing ERP | ₹8,000 - ₹25,000/month | Full quoting with BOM, production tracking, job costing, multi-location inventory, dealer management. 10-25 users. |
| Enterprise-grade ERP | ₹50,000 - ₹2,00,000/month | Advanced planning (MRP/MPS), shop floor execution, quality management, HR/payroll integration. 50+ users. |
| On-premise (one-time licence) | ₹3,00,000 - ₹15,00,000 one-time + ₹50,000-₹2,00,000/year AMC | Similar features to mid-range/enterprise but installed on your server. Requires IT staff. |
Most Indian manufacturing SMEs in the ₹5-50 crore revenue range will land in the mid-range category. That is ₹1-3 lakh per year — roughly the cost of one junior employee. The ROI math is not hard if the system is actually used.
Hidden costs that will blow your budget
The licence fee is never the full cost. Here is what vendors do not mention upfront.
Customisation
Every factory thinks it is unique. Most are not. But the 10-20% that genuinely needs customisation can get expensive. If the vendor quotes ₹2 lakh for the software and then ₹5 lakh for customisation, you are buying a custom-built system, not a product. Ask for the customisation cost estimate in writing before signing.
Standard range for customisation: ₹50,000 - ₹5,00,000 depending on complexity.
Data migration
Moving your customer master, product catalogue, opening stock balances, and historical data from Excel/Tally into the new ERP takes time. If the vendor charges per-hour for this, it adds up fast. A clean migration for an SME typically costs ₹25,000 - ₹1,50,000.
Training
Budget 2-4 days of training for your core team and 1-2 days for the wider team. If the vendor charges for training separately, expect ₹15,000 - ₹50,000. Some vendors include training in the implementation fee — confirm this explicitly.
Implementation and setup
This covers initial configuration — setting up your chart of accounts, tax rules, product categories, user roles, approval workflows, and templates. Typical cost: ₹50,000 - ₹3,00,000. Some cloud vendors include basic setup in the subscription. Others charge it separately.
Annual maintenance (on-premise only)
If you go on-premise, you will pay 15-22% of the licence cost annually for updates, bug fixes, and support. On a ₹10 lakh licence, that is ₹1.5-2.2 lakh per year — every year, forever.
Integration costs
If you need the ERP to talk to Tally, your e-commerce platform, a payment gateway, or a third-party logistics tool, each integration is a separate project. Budget ₹25,000 - ₹2,00,000 per integration depending on complexity.
The vendor evaluation checklist
Use this checklist when evaluating any manufacturing ERP vendor. Print it out and take it to every demo.
Before the demo
- Request a demo using YOUR data — your products, your customers, your BOMs. Generic demos hide problems.
- Ask for 3 reference customers in your industry and revenue range. Call them.
- Get the total cost of ownership in writing — licence, implementation, customisation, training, migration, and annual maintenance for 3 years.
- Ask about the implementation timeline. If they say less than 2 weeks for a manufacturing ERP, they are either lying or the system is too simple.
- Check the vendor's financial stability. An ERP is a 5-10 year relationship. If the vendor shuts down in Year 3, you are stuck.
During the demo
- Ask them to create a quotation for a custom product with a 3-level BOM. Time how long it takes.
- Ask them to show a job costing report — estimated vs actual — for a completed production order.
- Ask them to generate an e-invoice and e-way bill from a sales order.
- Ask them to show the system on a mobile phone. Not a separate app screenshot — the actual system.
- Ask what happens when internet goes down. Can transactions be queued? Is there offline mode?
- Ask how many clicks it takes to go from enquiry to quotation to sales order to production order. Count them.
After the demo
- Talk to the implementation team, not just the sales team. The people who configure the system are the ones who determine success.
- Ask about the support model — response time SLA, dedicated account manager or ticket queue, support hours.
- Request a 15-30 day pilot on your actual data before committing to an annual contract.
Red flags during demos
Over the years, these are the warning signs that predict a painful ERP experience.
"We can customise that" — If the vendor says this more than 3 times during a demo, the base product does not fit your needs. You will end up with a Frankenstein system that breaks with every update.
No manufacturing references — If every reference customer is a trading or services company, the vendor does not understand manufacturing. BOMs, job costing, and production tracking are fundamentally different from buy-and-sell workflows.
The demo data is perfect — Real factory data is messy. If the demo shows zero-error BOMs, perfectly categorised inventory, and clean customer masters, ask them to load your actual data and try again.
They avoid talking about implementation — Software is 30% of the problem. Implementation is 70%. If the vendor spends the entire demo showing features but cannot clearly explain how you get from purchase to go-live, be cautious.
Per-user pricing with no bulk option — If adding your 11th user costs the same as your 1st user, the pricing does not scale with you. Ask about user-tier pricing or flat-rate options.
No Tally integration story — In India, Tally is not going away. Your accountant will insist on it. If the ERP vendor has no answer for how their system coexists with Tally, they do not understand the Indian market.
The decision matrix
Use this scoring framework to compare your shortlisted vendors. Rate each criterion from 1-5 and multiply by the weight.
| Criterion | Weight | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| Quoting and estimation capability | 15% | _/5 | _/5 | _/5 |
| BOM and job costing depth | 15% | _/5 | _/5 | _/5 |
| Production tracking | 10% | _/5 | _/5 | _/5 |
| Inventory management | 10% | _/5 | _/5 | _/5 |
| GST compliance and e-invoicing | 10% | _/5 | _/5 | _/5 |
| Mobile access quality | 10% | _/5 | _/5 | _/5 |
| Total cost of ownership (3 years) | 10% | _/5 | _/5 | _/5 |
| Implementation timeline and approach | 8% | _/5 | _/5 | _/5 |
| Vendor stability and references | 7% | _/5 | _/5 | _/5 |
| Ease of use (your team's feedback) | 5% | _/5 | _/5 | _/5 |
| Weighted Total | 100% | __ | __ | __ |
The weights above reflect what matters most for a manufacturing SME. Quoting and BOM get the highest weight because that is where revenue and margin accuracy start. Adjust the weights based on your priorities, but do not drop any criterion below 5% — they all matter.
How to run a proper pilot
Do not sign an annual contract without a pilot. Here is what a good pilot looks like.
Duration: 15-30 days.
Scope: Pick one product line or one customer segment. Enter 20-30 real quotations, convert 5-10 to production orders, and run them through to dispatch and invoicing.
Team: Your best sales engineer, one production supervisor, and one accounts person. Three people is enough for a pilot.
Success criteria: Define these before the pilot starts. For example — quotation generation time under 10 minutes, accurate BOM costing within 2% of manual calculation, job costing report available within 24 hours of job completion.
Data: Use real data. Real customer names, real product specs, real pricing. A pilot on dummy data tells you nothing about whether the system fits your business.
Evaluation: At the end of the pilot, sit with all three users for 30 minutes. Ask two questions: Did this make your job easier? Would you use this every day? If both answers are not yes, either the system is wrong or the implementation needs work.
Making the final decision
After evaluating features, pricing, demos, references, and the pilot, the decision usually comes down to three factors.
Fit: Does the system handle 80% of your workflows out of the box? You can customise the remaining 20%, but if the base product needs heavy modification, you are buying the wrong product.
People: Do you trust the implementation team? ERP success depends more on the people configuring and supporting the system than on the software itself. If the implementation lead does not understand manufacturing, it does not matter how good the software is.
Economics: Is the total 3-year cost justified by the expected returns? For most manufacturing SMEs, an ERP that saves 2 hours per quotation, reduces material waste by 5%, and catches job cost overruns early will pay for itself within 6-12 months. If the numbers work, the decision is straightforward.
What to do next
If you are evaluating manufacturing ERPs and want to see how a system built specifically for Indian manufacturers handles quoting, BOM costing, production tracking, and job costing, take a look at QuoteERP. It is designed for the ₹5-100 crore SME segment, works on mobile, handles GST natively, and can be implemented in 30 days — not 12 months.
Book a demo with your own data and see for yourself whether it fits. No generic slides. No dummy data. Your products, your BOMs, your pricing — running in the system within 30 minutes of the call.