Manufacturing ERP Software Implementation for Indian Factories
Choosing manufacturing ERP is the easy part. Getting it to run your shop floor, your job work and your GST filing without a nine-month overrun is the job. We do the selection, the rollout and the rescue work, and we don't sell licences.
Why manufacturing ERP projects go wrong
Four failure patterns account for most of the overruns we get called in to fix. None of them is really a software problem, which is why changing product rarely solves them.
The misfit is discovered late, and then paid for twice
Panorama Consulting's 2026 ERP Report found that more than a quarter of organisations exceeded their project budgets, and named additional technology needs as the leading cause. Their own explanation is the useful part: organisations discover fatal misfits late in the project, and respond by buying more technology, expanding scope and commissioning custom builds. By then the licence is signed and the sunk cost is doing the arguing.
A misfit found in week three of selection costs a conversation. The same misfit found in month five of implementation costs a change request, a delay and usually a bolt-on product. This is the entire argument for spending real effort before you sign, and it is why our selection work is deliberately slower than a vendor demo cycle.
A note on the statistics you will see elsewhere. Search for ERP failure rates and you will be told that 73% of manufacturing ERP projects fail and that cost overruns average 215%, all attributed to Panorama. Those figures do not appear in Panorama's own press release or report summary. We checked the source before citing it, found the real number is materially smaller and less dramatic, and used that instead. Treat any consultant quoting the bigger numbers with care.
Compliance stopped being a module you bolt on later
E-invoicing became mandatory for businesses above ₹5 crore aggregate turnover under Notification No. 10/2023 – Central Tax, dated 10 May 2023. Since 1 April 2025, businesses at or above ₹10 crore have had a 30-day window to report an invoice, credit note or debit note to an invoice registration portal. Miss it and the document cannot be registered at all.
The change that lands today, 1 August 2026, matters more to manufacturers than to anyone else. Where an invoice carries separate bill-to and ship-to parties, the ship-to GSTIN becomes a mandatory field, with "URP" required where the recipient is unregistered. Factories ship to depots, to customer sites, to job workers and to third-party warehouses constantly. That makes this a master-data problem rather than a tax problem, and master data is exactly what a badly scoped ERP rollout leaves until last.
If your invoicing runs outside your ERP today, our comparison of billing software built around the 2026 e-invoicing rules covers the standalone options and where they stop.
Generic business software stops at the shop floor
Most systems sold to Indian SMEs as "ERP" are accounting packages with inventory attached. They handle purchase, sales, stock and GST competently. They do not plan production. The line between the two is sharper than vendors admit, and it sits at roughly five capabilities: multi-level bills of material, material requirement planning, routings and work centres, capacity planning, and job work.
Job work is the one that catches Indian manufacturers specifically. Sending material out for plating, heat treatment or stitching requires a delivery challan under rule 45, tracking of what went out against what came back, and quarterly ITC-04 reporting. A generic system will let you raise the challan. It will not reconcile the return or build the ITC-04. We have seen that single gap turn a working implementation into a spreadsheet again.
The table further down draws the line explicitly. If your requirement turns out to be stock accuracy rather than production planning, our page on inventory management software for manufacturing units is the more useful starting point, and it is a considerably cheaper class of product.
Your master data is the project
Every stalled implementation we have audited had the same shape: the software was configured on time and the data was not ready. Item codes that mean different things in two departments. Bills of material that live in an engineer's head and disagree with the drawing. Units of measure that convert inconsistently between purchase, production and dispatch. Opening stock that has never actually been counted.
Cleaning that up is unglamorous, it cannot be outsourced entirely to a vendor because only your people know which version is right, and it is the single largest predictor of whether a go-live holds. We plan for it explicitly rather than discovering it in month four, and we say so at the scoping call because it is the part clients most often want to skip.
Where you are right now
The right first move depends far more on your size and structure than on which product is trending. Find yourself below.
You are outside the e-invoicing mandate and almost certainly below the point where production planning pays for itself. Stock accuracy and clean billing will return more, sooner, than a full ERP. We will tell you this at the scoping call rather than sell you the bigger project.
This is the band where a cloud manufacturing ERP genuinely pays back, and where a bad choice hurts for five years. The decision is mostly about fit with your production mode and your job-work volume, not about feature counts on a comparison sheet.
Multiple registrations, inter-unit transfers and consolidated reporting change the shortlist entirely, and several products that suit a single plant handle this badly or charge steeply per location. That decision has to be made before the demo, not after.
If go-live has slipped twice and the vendor is proposing more modules, stop. Roughly half the stalled projects we review are recoverable on the current product. The other half are not, and knowing which one you have is worth more than another change request.
Generic business software vs manufacturing ERP
Ten capabilities separate the two categories. Scroll horizontally on mobile. If you need fewer than four of the rows marked as manufacturing-only, you probably do not need manufacturing ERP.
| Capability | Generic accounting / inventory software | Manufacturing ERP |
|---|---|---|
| Multi-level bill of materials | Single level at best | Multi-level with revisions |
| Material requirement planning | Reorder levels only | Demand-driven MRP run |
| Routings and work centres | Not modelled | Operation sequence per item |
| Capacity planning | Not modelled | Finite or infinite capacity |
| Job work and subcontracting | Challan only, no reconciliation | Issue, receipt and ageing |
| ITC-04 quarterly return | Manual from spreadsheets | Generated from job-work data |
| Batch and serial traceability | Batch in better products | Forward and backward trace |
| Quality control at goods receipt | Rarely present | Inspection plans and rejection |
| Standard vs actual costing | Purchase cost only | Variance by work order |
| GST e-invoicing and e-way bills | Widely supported | Widely supported |
The last row is deliberate. E-invoicing is the capability every vendor leads with and the one that least distinguishes them, because almost everything on the market now does it. It is not a reason to buy manufacturing ERP. The nine rows above it are.
For the products themselves, we keep two separate write-ups rather than repeating them here: manufacturing ERP systems for discrete and process industries covers the global and enterprise-tier products, and cloud ERP software in India covers what SMEs here actually shortlist. If artificial intelligence features are on your requirement list, our review of AI-enabled ERP systems separates the shipped capabilities from the roadmap slides.
ERP Selection
A requirements-led shortlist, scored against your actual production mode, with the commercial terms read before you commit.
We start on your shop floor, not in a demo. What do you make, in what mode, in what batch sizes, with how much sent outside for job work, and where does the current process actually break? That produces a requirement document written in your language, which then becomes the script every vendor demo has to follow. Demos run to our script rather than theirs, which is the single biggest change most clients notice.
What you get
A documented requirement set agreed with your team, a scored shortlist of three to five products with the reasoning shown, scripted demos run against your own sample data, a five-year cost model including users, locations, add-ons and renewal increases, and a read of the contract terms before signature. Delivered as a document your board can act on.
What it is not
It is not a reseller relationship. We take no commission from any ERP vendor, which means we can recommend the cheaper product or tell you to stay on what you have. It is also not a guarantee that a product exists that fits perfectly. Sometimes the honest recommendation is a smaller system plus a deliberate manual process, and we will say so.
Best for: manufacturers between ₹5 crore and ₹50 crore turnover who have been through two or three vendor demos and noticed that every product appeared to do everything.
Implementation & Rollout
Configuration, data migration, parallel run and go-live, managed against a plan that treats master data as the critical path.
We run implementation in phases with a working system at the end of each one, because a nine-month project with a single go-live date is a nine-month project that slips. Finance and inventory first, then production, then quality and costing. Each phase has an agreed definition of done and a named owner on your side, and we do not start the next one until the last is live and being used.
Master data gets its own workstream from day one. Item master rationalisation, bill of material capture and verification against drawings, unit-of-measure conversion rules, opening stock counts, and supplier and customer masters with the GSTINs your invoicing will now depend on. That last item is no longer optional given the bill-to and ship-to requirement that took effect today.
What you get
Phased configuration, a documented data migration with reconciliation you can audit, user training by role rather than by module, a parallel run before cutover, and hypercare after go-live. We work alongside your vendor's implementation team where one exists, and we represent your interest in that room rather than theirs.
What it is not
It is not a replacement for your people. Master data cleanup needs your production and stores staff because only they know which item code is correct, and no consultant can supply that. It is also not custom development. Where a genuine gap exists we will scope a change, but our first answer is always to check whether the process can change instead.
Best for: factories that have chosen a product and want the rollout run by someone whose incentive is your go-live rather than the vendor's revenue recognition.
ERP Audit & Recovery
An independent read on a stalled implementation, and a recommendation you can act on without another change request.
Stalled projects share symptoms: go-live has moved twice, staff have quietly gone back to spreadsheets, reports do not tie to the books, and the vendor's proposed fix involves buying something else. We review the configuration against your requirement, test the data, interview the people who are supposed to be using it, and tell you which of three situations you are in.
Either the product fits and the implementation was run badly, which is recoverable and usually the cheapest outcome. Or the product does not fit your production mode, in which case continuing to spend is the expensive choice. Or the requirement was never defined well enough for anyone to succeed, which is more common than vendors like to admit and is fixable before you change anything else.
What you get
A written finding on which of those three situations applies, with the evidence. A recovery plan with sequence and effort if the system is salvageable. A migration assessment if it is not, including what data can realistically be carried across. And a plain read of your contractual position before you have the conversation with your vendor.
What it is not
It is not an expert-witness or litigation service, and it is not a way to build a case against a vendor. We report what we find, which sometimes means telling a client that the vendor delivered what was signed and the requirement was the weak part. If you want a report that reaches a predetermined conclusion, we are the wrong firm.
Best for: manufacturers who have spent real money, are being asked for more, and want an opinion from someone with nothing to sell on either side.
The sequence, every time
Diagnose before prescribing. The order is the method, and skipping a step is how the overruns start.
- Scoping call, free. We ask what you make, how you make it, what breaks today and what you have already tried. If ERP is not your bottleneck we say so on this call, and a fair number of these calls end that way.
- Process walk. We walk the floor and the office: order to production, purchase to stores, stores to shop floor, job work out and back, dispatch to invoice. Written as it actually happens, not as the SOP claims.
- Requirement definition. The walk becomes a numbered requirement set, separated into must-have, should-have and nice-to-have, signed off by your team before any vendor sees it.
- Shortlist and scripted demos. Three to five products, scored against the requirement, demonstrated against your own sample data using our script. Vendors are told to skip the corporate deck.
- Commercial modelling. Five-year cost including users, locations, add-on modules, implementation effort and renewal increases. The headline licence price is rarely the number that decides it.
- Phased implementation. Finance and inventory, then production, then quality and costing. Each phase live and in use before the next begins, with master data running as a parallel workstream throughout.
- Go-live and hypercare. Parallel run, cutover, then intensive support while the first month-end and the first GST filing pass through the new system. Those two events are the real test, not the go-live date.
What we verified for this page
The site's other pages carry verification dates and mean them. This one is no different.
- Compliance facts were taken from the government portal, not from vendor blogs, which dominate search results for these queries and are frequently out of date. The ₹5 crore threshold, the 30-day reporting window and the bill-to and ship-to change effective 1 August 2026 were confirmed on the GST e-invoice portal on 1 August 2026.
- The Panorama figure was read from Panorama's own release, dated 4 March 2026, rather than from the secondary sources that quote it. Those sources attribute failure rates and cost-overrun percentages to Panorama that do not appear in the source material, which is why our stats band carries the smaller number.
- We take no commission from ERP vendors. No reseller margin, no referral fee, no partner tier. That is what allows a selection engagement to end with a recommendation to keep what you have.
- Product comparisons live on separate pages, and are dated there. We do not repeat pricing on this page because vendor pricing moves faster than a service page gets updated, and a stale number is worse than no number.
What we will not claim
- We will not promise a percentage improvement in on-time delivery, inventory turns or gross margin before seeing your data. Anyone who quotes such a figure in a proposal is quoting a brochure.
- We will not promise a go-live date at the scoping call. The date depends on the state of your master data, which nobody knows accurately at that point, including you.
- We do not implement every product on the market. Where a chosen system is outside our experience we will say so and help you appoint someone who knows it, rather than learn on your project.
- We are not tax advisors. We build systems that produce compliant documents and we cite the government sources for the rules, but your GST positions belong with your chartered accountant.
Frequently asked questions
What is manufacturing ERP software, and how is it different from ordinary ERP?
Manufacturing ERP is enterprise software that plans and records production alongside the usual finance, purchase, sales and inventory functions. The distinction is not marketing: a generic system tracks what you bought and what you sold, while a manufacturing system additionally models how the one becomes the other. That means multi-level bills of material, material requirement planning that works backwards from demand, routings through work centres, capacity planning, and job-work tracking for material sent outside your factory. The comparison table on this page lists the ten capabilities that separate the two categories. If you need fewer than four of them, a generic system with good inventory management will serve you better and cost considerably less.
How long does a manufacturing ERP implementation take in an Indian SME?
Honestly, it depends almost entirely on the state of your master data rather than on the software. Configuration of a cloud manufacturing ERP for a single plant is rarely the constraint. Cleaning item masters, capturing and verifying bills of material against current drawings, fixing unit-of-measure conversions and counting opening stock is the constraint, and that work sits with your staff because only they know which version is correct. We phase engagements so that finance and inventory go live first and production follows, which gets value flowing earlier and stops the whole project depending on one distant date. We will not quote a timeline before the process walk, because a number given at that stage is a guess dressed as a commitment.
What changed for manufacturers on 1 August 2026?
Where an invoice has separate bill-to and ship-to parties, the ship-to GSTIN became a mandatory field when reporting to an invoice registration portal, with "URP" required where the recipient is unregistered. This affects manufacturers disproportionately because factories routinely ship to depots, customer sites, job workers and third-party warehouses rather than to the billing address. In practice it is a master-data requirement: every ship-to location in your customer master now needs a valid GSTIN recorded against it. If your ERP or billing software holds ship-to addresses as free text, that needs fixing before it becomes a rejected invoice at month-end.
Do we need ERP if our turnover is below the e-invoicing threshold?
Usually not yet, and we will tell you so rather than sell you a project. Below ₹5 crore aggregate turnover you are outside the e-invoicing mandate, and at that scale the return on production planning is generally smaller than the return on simply knowing your stock accurately and billing cleanly. The sequence that works is inventory discipline first, then proper accounting software, then manufacturing ERP when order volume or product complexity genuinely outgrows them. Buying ERP early tends to produce an expensive system used as a billing package, which is the most common form of wasted spend we see in this segment.
How do you handle job work and ITC-04?
Job work is where Indian manufacturing requirements diverge most sharply from what global ERP products assume, so we treat it as a selection criterion rather than an implementation detail. Material sent for processing needs a delivery challan, tracking of quantities issued against quantities returned including wastage, ageing of material lying with the job worker, and the data to build the quarterly ITC-04 return. Plenty of products can raise the challan. Far fewer reconcile the return or generate the ITC-04 without a spreadsheet in the middle. If job work is a meaningful share of your process, we test this specifically during scripted demos using your own transactions.
Are you a reseller for any ERP vendor?
No. We hold no reseller agreement, partner tier or referral arrangement with any ERP vendor, and we take no commission on licences. This matters because it changes what advice is possible: a selection engagement can honestly conclude that you should keep your existing system, choose the cheaper of two products, or defer the project entirely. Where our writing elsewhere on this site does carry affiliate links, those are marked as such and appear on product comparison articles rather than on service pages like this one. Our fee comes from you, which is the only arrangement under which independence is real.
Can you take over an implementation that has already stalled?
Yes, and it is a significant share of our work. The first step is always an audit rather than a rescue plan, because the useful question is whether the product fits and was implemented badly, or does not fit at all. Those two situations have opposite answers and the same symptoms. Roughly half the stalled projects we review are recoverable on the current system, usually by returning to a proper requirement definition and rebuilding the configuration against it. The other half need migration, and knowing which case you are in before spending more is worth considerably more than another change request. We report what we find, including when the finding is that the vendor delivered what was actually signed.
Tell us what you make, and how
The scoping call is free and often ends with us saying ERP is not your bottleneck. That is a useful outcome too.
Book a free scoping call