How to Set Up Quality Inspection in ERPNext Manufacturing

Quality Inspection in ERPNext is a gate, not a tracker. It does not continuously monitor — it blocks a specific transaction (Stock Entry, Purchase Receipt, Delivery Note) until an inspector records readings and marks the inspection as Accepted or Rejected. The power is in the blocking. But the blocking only works when the configuration is complete. I am Manoj, ERP implementation lead at Mith Tech in Bengaluru, and setting up quality gates in ERPNext manufacturing is one of the most common requests from our ISO-certified clients.

When does Quality Inspection trigger?

Quality Inspection in ERPNext is not automatic — it is a gate that blocks specific transactions. The gate activates at different points depending on the transaction type:

The critical point: if "Quality Inspection Required during Manufacture" is not enabled in Manufacturing Settings, Stock Entries of type "Manufacture" submit without any inspection check. The item can have a QI template linked, but without the setting enabled, ERPNext does not enforce it.

Designing your inspection template

A Quality Inspection Template defines what gets inspected — the parameters, acceptable ranges, and measurement units. The Template Builder below lets you design one interactively:

When designing templates, follow these principles:

1. Numeric parameters with min/max ranges are most useful — they give you data for statistical analysis (Cpk, trends) and leave no room for subjective interpretation.
2. Visual/pass-fail parameters (no numeric range) are for checks that cannot be measured: surface finish, colour match, label presence. Use sparingly — they depend on inspector judgement.
3. One template per product family, not per product. If five shaft variants share the same quality requirements, use one template. Link it to each Item individually.
4. Keep parameters under 10. More than 10 parameters per inspection slows down the inspector and increases error rates. If you need more, consider splitting into incoming material inspection and final inspection templates.

The automation scripts

Three scripts complete the QI workflow: auto-creation (so inspectors do not manually create QI docs), rejection handling (so rejected items move to the right warehouse), and a dashboard query (so you can track pass/fail rates):

# Server Script: auto-create Quality Inspection
# on Stock Entry (Manufacture) submission
# Trigger: Before Submit on Stock Entry
# See: GitHub #53784, Forum #149464

import frappe

def before_submit(doc, method=None):
    if doc.stock_entry_type != "Manufacture":
        return

    for item in doc.items:
        if not item.t_warehouse:
            continue  # skip source items

        # Check if item requires inspection
        qi_template = frappe.db.get_value(
            "Item",
            item.item_code,
            "quality_inspection_template",
        )
        if not qi_template:
            continue

        # Check if QI already linked
        if item.quality_inspection:
            continue

        # Auto-create Quality Inspection
        qi = frappe.new_doc("Quality Inspection")
        qi.inspection_type = "In Process"
        qi.reference_type = "Stock Entry"
        qi.reference_name = doc.name
        qi.item_code = item.item_code
        qi.sample_size = item.qty
        qi.inspected_by = frappe.session.user
        qi.quality_inspection_template = qi_template

        # Load template parameters
        template = frappe.get_doc(
            "Quality Inspection Template", qi_template
        )
        for param in template.item_quality_inspection_parameter:
            qi.append("readings", {
                "specification": param.specification,
                "min_value": param.min_value,
                "max_value": param.max_value,
                "formula_based_criteria": param.formula_based_criteria,
                "acceptance_formula": param.acceptance_formula,
            })

        qi.insert(ignore_permissions=True)
        item.quality_inspection = qi.name

    frappe.msgprint(
        "Quality Inspections created. Fill in readings before submitting.",
        alert=True,
    )

QI readiness checklist

Before going live with quality inspection in manufacturing, verify every configuration item. The checklist below tracks the eight requirements:

What to know before you commit

QI slows down submission. Every Manufacture Stock Entry now requires an inspection step. If your production floor submits 50 Stock Entries per day, that is 50 inspections. Plan for the time — each inspection takes 2–10 minutes depending on parameter count. Consider whether 100% inspection or sampling (inspect every Nth batch) is appropriate.

Formula-based criteria. ERPNext supports formula-based acceptance criteria in QI templates (e.g., reading_value > min_value and reading_value < max_value). Use these for complex acceptance logic like "reading must be within 2 standard deviations of the mean". Set formula_based_criteria = 1 on the template parameter.

QI for Purchase Receipts. The same template mechanism works for incoming material inspection. Enable "Quality Inspection Required during Purchase" in Stock Settings. This blocks Purchase Receipt submission until the received material passes inspection. Link a different QI template for raw materials vs finished goods.

Batch-wise inspection. If your items use batch numbers, create one QI per batch, not per Stock Entry. This lets you trace quality issues back to specific batches. Set the batch_no field on the Quality Inspection document.

Quality Inspection in ERPNext works as a gate — it blocks transactions until readings pass. But the gate only closes if three configuration items are in place: QI template on the item, the manufacturing setting enabled, and a QI document linked to the Stock Entry. The auto-creation script removes the manual step that most manufacturing teams skip. The rejection handler closes the loop by moving defective items out of the production flow.