Why quality management software belongs inside the ERP
Quality management software records what was checked, what was found and what was done about it. Many factories keep these records in registers, standalone spreadsheets or separate QMS tools. The trouble is that quality decisions affect stock, production, purchase and sales, so records kept outside the ERP are always one step behind.
In DotOne, quality is part of the transaction flow. A lot that fails incoming inspection cannot be issued to production. A batch on quality hold cannot be dispatched. A rejection is linked to the vendor, machine, operator or process step responsible. This makes quality data useful for running the business, not just for passing audits.
Inspection at every stage
Inspection plans define what is checked, how and how often. The ERP lets you create plans per item, item group, customer or process, with parameters, specification limits, methods, instruments and sampling rules. Inspectors record results on desktop or tablet, and the system decides pass, fail or conditional acceptance based on the limits.
Incoming inspection
When material arrives, the goods receipt note sends the lot to quality. Parameters such as dimensions, thickness, moisture, viscosity, GSM, hardness or visual defects are recorded. Accepted quantity moves to usable stock, rejected quantity to a rejection store, and partially accepted lots are split accordingly.
In-process inspection
Checks can be attached to specific operations in the routing, such as after pressing, coating, moulding, cutting or welding. Inspectors record results against the job card, so defects are caught before more value is added to a faulty piece.
Final and pre-dispatch inspection
Finished batches are inspected before they move to saleable stock or before dispatch. Customer-specific checks can be added, and the results feed the test certificate or certificate of analysis that accompanies the shipment.
Quality holds and stock status
One of the most valuable controls an ERP provides is stock status. Material can be marked as under inspection, accepted, rejected, on hold or for rework. Only accepted stock is available for issue or sale, which removes the risk of someone picking up uninspected material during a busy shift.
If a problem is found later, such as a customer complaint or a failed lab test, you can place an entire batch on hold across all locations. The hold blocks issue and dispatch until quality releases it. This links closely to batch traceability, which shows where every unit of the affected batch has gone.
Non-conformance, root cause and CAPA
Finding a defect is only useful if it leads to action. The ERP records each non-conformance with its source, quantity, severity and immediate disposition: use as is, rework, return to vendor or scrap. Serious or repeated issues can be escalated to a corrective and preventive action record.
- Non-conformance report: what failed, where, when and how much, with photos attached.
- Containment: immediate steps such as holds, sorting or replacement.
- Root cause analysis: structured methods such as five whys or fishbone categories recorded in the system.
- Corrective action: what will be changed, by whom and by when.
- Preventive action and verification: checks that the fix worked and is applied to similar processes.
Open CAPAs appear on owners dashboards with due dates, so they are not forgotten after the audit is over.
Supplier quality and customer complaints
Incoming inspection results build a quality history for every vendor. Rejection percentage, recurring defects and corrective actions are visible in the vendor scorecard used by the purchase management team. Rejected material can be returned with a debit note directly from the inspection record.
Customer complaints are logged against the invoice and batch. The complaint record follows the same NCR and CAPA flow, and credit notes or replacements are tracked against it. Over time, complaint data shows which products, customers or processes generate the most issues.
Calibration, documents and audit support
Inspection results are only as reliable as the instruments used. The ERP can maintain a register of gauges and instruments with calibration due dates, certificates and status, and warn when an instrument is due or overdue. We configure this to suit the instruments your plant uses.
Many manufacturers work to ISO 9001 or customer-specific quality requirements. The ERP does not certify anyone, but it holds the records auditors typically ask for: inspection results, NCRs, CAPAs, calibration history, training records and controlled document versions. Retrieving evidence becomes a search rather than a hunt through files.
Training records for inspectors and operators can also be linked to the processes they are authorised to check, so the system can warn when an untrained person records results for a critical parameter.
AI and Vision AI in quality control
DotOne includes AI capabilities that support quality teams rather than replace them. Analysis agents review inspection and rejection data to find patterns that are hard to see manually, such as a defect that rises on one shift or with one raw material lot.
Vision AI can be applied where visual inspection is repetitive, for example checking surface defects, labels or packaging. Cameras capture images, a model trained on your accepted and rejected samples classifies them, and results are recorded in the inspection log. Whether this suits a given line depends on lighting, speed and defect types, so we assess it case by case. Read more on our AI-powered ERP page.
- Pattern alerts linking defects to shifts, machines, operators or vendor lots.
- Summaries of open NCRs and overdue CAPAs for weekly quality reviews.
- Vision AI inspection on suitable lines, configured and trained per product.
Quality reports and the cost of poor quality
Quality reports should help you decide where to act. The ERP provides rejection analysis by product, process, machine, vendor and defect type, as well as trend charts and Pareto views that show the few causes behind most problems.
- Incoming rejection by vendor and item.
- In-process rejection and rework by operation and machine.
- Customer complaint trend and closure time.
- Open NCR and CAPA status by owner.
- Cost of scrap, rework and returns from linked costing data.
Because scrap and rework are recorded against production orders, the cost of poor quality appears in product costing rather than disappearing into overheads.
Management can see these figures by month and by plant, which turns quality from a compliance activity into a measurable business lever. When a corrective action is closed, the same reports show whether rejection actually fell in the following weeks, so improvement efforts are judged by results rather than by paperwork.
How do you choose quality management software for a factory?
Look first at whether inspection results change stock status automatically, because that is what prevents bad material from moving forward. Then check whether the system supports your parameters and units, the way your inspectors actually work, and the certificates your customers expect.
Finally, ask how quality data connects to purchase, production and costing. A QMS that sits apart from the ERP can produce tidy reports, but it rarely changes behaviour on the shop floor. Integrated quality records do.
It also helps to start small. Many plants begin with incoming and final inspection on their critical items, then add in-process checks, CAPA and calibration once inspectors are comfortable with the screens.
