Track Quality Issues in ERP: Inspection to Disposition

Track quality issues by linking the observation, affected material or job, hold status, approved disposition and follow-up evidence in one traceable record. A pass/fail field is useful, but the team also needs to know which quantity is affected and who can decide its next use.

Use this workflow for incoming inspection, an in-process defect, final inspection or a customer complaint. The source record changes; the need to preserve identity and an authorised decision remains. A complaint may require tracing the dispatch back to its job and material lot before the scope is known.

Record the issue where it is found

Capture the item, specification revision, lot or serial identity where applicable, operation, event time, inspector and affected quantity. Attach the measurement, photograph or test report needed to understand the observation. Record the requirement that was not met rather than only writing “quality problem.”

ERPNext's quality-inspection documentation illustrates inspection records connected with operational documents. For incoming material, retain the purchase receipt and supplier reference. Confirm the supported links and permission rules in the system you actually use.

Separate held quantity from usable stock

Assign a visible hold status, location or other approved control so the affected material cannot be mistaken for available stock. Agree how planning, stores and dispatch see that status. Test whether the configured system prevents the relevant transaction; an inspection record alone does not prove that issue or dispatch is blocked.

In this example, three of the five held parts pass inspection after approved rework; two receive an approved scrap disposition. The final accepted quantity is 48. Do not add the three reworked parts as a new receipt while also leaving all five on hold: that would count the same material twice.

Approve disposition and retain the history

Record who may approve rework, return, scrap or another permitted disposition, and the evidence required for each. Reworked material needs the specified reinspection before release. Keep the original defect and rework reference after acceptance so a later report does not erase the first failure.

Investigate patterns without declaring a cause too early

Group defects consistently enough to compare them by operation, item, supplier lot or period. Retain the underlying measurements. A pattern on one shift or batch is a lead to investigate; it does not, by itself, establish that the shift or supplier caused the failure.

Distinguish containment from corrective action. Holding a suspect lot protects the next handoff. Changing an approved work instruction, inspection method or process control may address a verified cause. Assign an effectiveness check so closing the action means more than completing a task.

Use the scrap and rework guide for improvement work and the stock reconciliation checklist for quantity control. In an Optiwise production demo, trace one inspection hold through planning, authorised release and the final stock balance.

Questions from manufacturing teams

What should an ERP quality issue record contain?

Record the requirement, observed evidence, affected item and lot/job, quantity, hold status, disposition approval and follow-up owner. Link the inspection to the relevant receipt, production or dispatch record.

Does creating an inspection automatically block stock?

The effect depends on the configured workflow and permissions. Demonstrate the intended issue, planning and dispatch restrictions using held material before relying on them.

How do I reconcile reworked material?

Keep the original held quantity and record the approved rework outcome. Move accepted and scrapped quantities to their proper statuses without creating an additional receipt for material already counted.