The three questions manufacturing software has to answer
Every manufacturer we talk to is trying to answer the same three questions, and usually answering them by walking to the floor and asking somebody.
What can we promise? Not what is in stock — what is in stock, minus what is already committed to open orders, plus what is arriving and when. A stock figure alone routinely leads to promising material that is already spoken for.
Where is this job? Which operation, on which machine, waiting on what. Without it, a customer asking for a date gets a guess.
What did it cost? Material actually issued, time actually booked, scrap actually produced — against what was quoted. Businesses that cannot answer this often discover their most-loved product is their least profitable.
What changes on the floor
| Activity | On paper | In an ERP |
|---|---|---|
| Material issue | Slip to the storekeeper, entered later | Issued against the job; stock and WIP move immediately |
| Operation complete | Marked on a travelling card | Booked against the operation, with time and machine |
| Quality check | Separate register | Stock held in QC; pass or reject decides where it goes |
| Scrap and rework | Often unrecorded | Recorded against the job, so the cost lands on the job |
| Finished goods | Counted at the end | Received against the order, by batch |
| Job cost | Estimated afterwards | Accumulated as it happens |
Batch traceability, and why Indian auditors ask
For food, pharma, chemicals and anything with a shelf life, the question is not whether you track batches — it is whether you can follow one in both directions. Backwards: which raw material batches went into this finished batch, from which supplier, with which test result. Forwards: which customers received it, on which invoice, on which vehicle.
Doing that on paper is an afternoon in a file room. Doing it in an ERP is one search, because the batch travelled with every document rather than being written on each of them separately. If you are ever in a recall, that difference is the whole ballgame.
Job work, which most generic ERPs handle badly
Sending material out to a job worker and receiving it back processed is ordinary in Indian manufacturing and unusual in ERP products designed elsewhere. The material is still yours while it sits at the job worker; there is a challan rather than an invoice; and the GST treatment of the movement is specific.
An ERP that treats a job-work dispatch as a sale, or that cannot show you stock lying at a job worker, will cause a reconciliation problem every month. We have written a separate guide on what job work management should actually do.
What it will not fix
It will not make the floor record things it does not record today. If operations are not booked as they complete, the ERP shows yesterday’s picture just as the whiteboard did — the difference is that it shows the gap clearly, which is useful but is not the same as solving it.
It will not fix a bill of materials that is wrong. Costing is only as good as the BOM behind it, and cleaning BOMs is usually the longest part of a manufacturing implementation.
And it will not schedule the factory for you. Most SME ERPs, ours included, give you visibility and sequencing rather than finite-capacity scheduling. If you need genuine APS, ask specifically and do not accept a Gantt chart as an answer.
In short
- The three questions are availability, where jobs are, and what they cost.
- The value comes from recording events on the floor as they happen, not afterwards.
- Two-way batch traceability is one search in an ERP and an afternoon on paper.
- Job work is an Indian requirement that generic ERPs often model wrongly.
- Bad BOMs and unrecorded operations are not fixed by software; they are exposed by it.