Native ERPNext Quality Inspection is a single DocType with a flat table of readings — you record a value, mark each parameter as accepted or rejected, and attach it to a receipt or work order. That is fine for a spot check, but it collapses the moment a quality manager needs a statistically defensible process. There is no sample-size logic tied to lot quantity, no accept/reject number driven by an AQL, no separation of critical versus major versus minor defects, no automatic disposition of the whole lot, and no Certificate of Analysis to hand a customer. Quality teams end up running the real inspection in a spreadsheet and re-keying a conclusion into ERPNext, which means the ERP no longer reflects how goods are actually released.

Quality Inspection Plus is a proper Frappe app (its own module, installed via bench get-app and bench install-app) that layers a sampling and disposition engine on top of the stock Quality Inspection DocType instead of replacing it. We add DocTypes such as Sampling Plan (ISO 2859-1 / ANSI-ASQC Z1.4 tables — inspection level, AQL, code letter, sample size, Ac/Re numbers), Defect Type (classed critical / major / minor with its own AQL), and Lot Disposition (the audit record of a pass, fail, hold, or conditional-release decision). A hooks.py doc_events handler fires on the inspection's validate and on_submit: it reads the linked lot quantity, resolves the correct sample size and acceptance number from the plan, tallies defects by class, and computes disposition. If critical defects exceed zero or the major/minor counts breach their Ac numbers, the lot is routed to Hold and the linked Purchase Receipt / Stock Entry / Work Order is blocked from onward movement.

The disposition writes back into ERPNext where it matters. A hold sets the received items into a quarantine warehouse or blocks the receipt from being submitted; a pass releases them; a conditional release records a deviation with an approver. Certificate of Analysis generation is a server-side Jinja print format populated from the inspection readings, specification limits, sampling parameters and final disposition, rendered to PDF via Frappe's print engine and optionally emailed on submit. Everything is exposed through the Frappe REST API and @frappe.whitelist() methods so your QC scanners, label printers or a customer portal can pull a CoA or push a reading without touching the desk UI. Role handling uses dedicated role profiles (QC Inspector, QC Manager) with permission rules and submit-level control so an inspector can record but only a manager can override a hold. Client scripts add live sample-size preview and defect tallies on the inspection form, and a scheduler event can sweep aging Hold lots and escalate them.

Because this is build-to-order, nothing ships until we agree exactly which sampling standard, defect taxonomy and CoA layout your auditors and customers expect. We start with a short scoping call, confirm scope in writing, then build against a staging bench on Frappe/ERPNext v15 or v16. Typical delivery is one working week from confirmed scope. You receive the installable app source, UAT on staging with a rollback plan, documentation, a training session and a post-go-live support window — and the git repository is handed to you so you are never locked in.