Quality control software holds the checks a factory performs and makes them usable afterwards. It covers incoming inspection of purchased material, in-process checks during production, final inspection before dispatch, non-conformance and how each was disposed of, corrective action, gauge and instrument calibration, retention samples, customer complaints and supplier quality performance. Pentoggle is an AI platform that generates production-ready software from a plain English description, which means a factory can build quality records around its own checks and specifications instead of adapting to a system built for someone else's process.
Most manufacturers in India already run Tally for accounting, some run Busy or Marg, and larger businesses may run SAP Business One. Those systems handle purchase, sales, GST and accounting well. This is not a proposal to replace them. Pentoggle builds the quality application around them, covering the workflows they were never designed for.
Two boundaries are worth setting before going further. Production tracking answers where a job is, and quality control answers whether it conforms. Traceability answers which lots went into what, and quality control uses those links rather than owning them. This page is about the checks themselves and what happens to the results.
Key takeaways
- Most factories collect a great deal of quality data and analyse almost none of it, because it is on paper in a register.
- Rejection counted as a total teaches nothing. The same rejection split by defect, machine, shift and supplier lot is a work list.
- A gauge found out of calibration puts every measurement taken since the last check in doubt, which makes calibration due dates a bigger risk than they appear.
- Non-conformance without a recorded disposition is where material quietly re-enters production.
- The number that matters in quality is the share of defects found by your customer rather than by you.
A note on certification
Manufacturers work to different quality standards depending on their industry and their customers, and what a certified system requires is defined by that standard, by your documented procedures and by your customers' specific requirements. Pentoggle applications hold operational quality records: inspection results, non-conformance, disposition, calibration status and complaint history. They are not a substitute for a certified quality management system and they do not certify compliance with any standard. Confirm what your system must contain, and in what form, with your quality head or certification body.
Why quality data usually goes unused
Almost every factory already inspects. There is an incoming inspection register at the stores, a checklist at each stage, a final inspection report, and a file of customer complaints. The data exists in quantity, and the number of factories that can answer a simple question from it is small.
The question is usually something like this: over the last three months, which defect cost us the most, on which machine, on which shift. Answering it requires pulling several registers, transcribing numbers, and trusting the handwriting. It takes a day, so nobody does it, so the analysis happens only when a customer complaint forces it and only for that complaint.
The result is that quality management becomes reactive by default. Defects are fixed one at a time as they surface, the same defect recurs on the same machine for a year, and the factory's response to a recurring problem is more inspection rather than less defect. More inspection is the most expensive possible answer, since it adds cost without removing the cause.
Recording the same checks in an application rather than a register does not, by itself, improve quality. What it does is make the analysis a query instead of a day, and factories that can ask the question cheaply start asking it.
What quality control software holds
Incoming inspection
Purchased material checked against specification on receipt, with results tied to the supplier, the lot and the purchase document, and the accepted or rejected quantity recorded.
In-process checks
The checks your control plan or work instruction requires at each stage, with the reading or result, the operator, the machine and the time.
Final inspection
Pre-dispatch checks against the customer's requirement, with the result attached to the lot or batch being shipped.
Non-conformance and disposition
What failed, how much, where it is physically held, and what was decided: rework, use as is under a documented concession, downgrade or reject.
Corrective action
Root cause and the actions taken, linked to the non-conformances or complaints that triggered it, with responsibility and a due date.
Gauge and instrument calibration
Every measuring instrument with its calibration date, due date and certificate, and an alert before it falls due.
Retention samples
What was retained, from which batch, where it is stored and when it can be disposed of.
Customer complaints
Complaints with the affected lots, the containment decided, the response sent and the corrective action linked.
Supplier quality
Incoming rejection by supplier and material over time, which is the basis of any vendor rating worth keeping.
Rejection has to be attributable to be useful
A monthly rejection percentage is a scorecard entry. It tells you whether this month was worse than last month and nothing about what to do.
The same rejections, recorded with the defect type, the machine, the shift, the operator and the supplier lot attached, become a different object. Now the concentration is visible: one defect accounting for most of the loss, or one machine producing most of one defect, or a rejection pattern that follows a particular incoming lot rather than anything you did. Each of those has a different owner and a different fix, and the aggregate figure hides all three.
This is the single highest-value design decision in a quality application, and it costs nothing at the point of entry. The inspector is already writing down the rejection. Recording what it was and where it came from, at the same moment, is the difference between a number reported upward and a work list produced downward.
The corollary matters too. Rejections found at final inspection and rejections found at the first stage are not equivalent, because a defect caught late has consumed every operation after the point where it was created. Recording where a defect was found alongside where it was caused is what tells you whether your checks are in the right place.
Calibration is a retrospective risk
Calibration is usually treated as a compliance chore, a sticker on an instrument and a due date in a file. Its real significance is different and larger.
When a gauge is found out of calibration at its next check, every measurement it took since the previous check is in question. That is not a documentation problem. It is potentially weeks of accepted production whose conformance can no longer be demonstrated, sitting at your plant, with your customer and in transit. The decision that follows is expensive whichever way it goes.
This is why the calibration due date deserves an alert rather than a register. An instrument checked on time carries a bounded risk. An instrument checked three months late carries a risk bounded only by how much you made in three months. The same logic applies to reference standards and to any instrument a customer's auditor will ask about.
The record itself is simple: instrument, location, calibration date, due date, certificate reference and current status. What makes it valuable is that it is visible before the date rather than after.
Non-conformance without disposition is where material comes back
A rejection is identified, the material is moved aside, and then a week passes. Somebody needs pieces, the pile is the right part, and material rejected for a reason nobody remembers goes back into production. This is one of the most common quality failures in Indian factories and it is almost never recorded, because by definition the record was the thing that was missing.
Preventing it requires three fields and one habit. What was rejected and how much. Where it is physically held. What was decided, by whom, and when. Until the third field is filled, the material has a status, and the status is what stops it being consumed by default.
The same record has a second use. Disposition decisions, reviewed together over a quarter, show how often the factory is accepting material under concession, which is a number most plants would rather not see and should.
Why building this is now practical
Quality modules in packaged systems are usually priced separately, configured last and abandoned first, because they arrive with someone else's inspection structure and a factory's checks are specific. A control plan written for your part, your customer and your process does not fit a generic template, so the module is used for a subset of checks and the registers continue alongside it.
With Pentoggle you describe your checks: what is inspected, at which stage, against what specification, by whom, and what happens when something fails. The application is built around that. When a customer adds a requirement, or you add a stage, or you decide to start recording where a defect was caused as well as where it was found, you describe the change and the application updates. Most factories start with incoming and final inspection, because those two have the clearest owners, then extend to in-process checks once entry has become routine.
Where quality control looks different by industry
- Auto Component Manufacturing Software, where the customer's PPM score is the measure that matters.
- Food Processing Software, where quality checks attach to the batch and carry into traceability.
- CNC and Machine Shop Software, where first article and in-process inspection tie to the job card.
- Garment Manufacturing Software, where defects per hundred units and alteration are tracked by line.
- Printing and Packaging Manufacturing Software, where shade approval and reprints are the quality record.
Why manufacturers choose Pentoggle for quality control
Your checks, your specifications
Inspection points and criteria as your control plan defines them, not a generic template.
Works alongside Tally and your certified system
Pentoggle holds operational quality records. Accounting stays with your CA, and your certified system stays where it is.
Recorded where the check happens
Results entered on a phone or tablet at the inspection point rather than transcribed at the end of a shift.
Analysis without an exercise
Defect, machine, shift, supplier and lot attached at entry, so the question can be asked any time.
Changes in days
A new customer requirement or a new check does not become a three month project.
The one number that runs quality control
The share of defects found by your customer rather than by you.
Internal rejection measures cost. This measures control. A factory with high internal rejection and nothing escaping has an expensive process and a working quality system. A factory with low internal rejection and regular customer complaints has a cheap process and no quality system, and its internal numbers will look better than the first factory's right up until the contract is lost.
Track it monthly per customer, and read it alongside internal rejection rather than instead of it. The two together tell you whether to work on the process or on the checks, which is the only diagnostic question in quality that actually changes what you do next.
Ready to build quality control software?
Every factory records quality. Very few factories read it.