ERPNext quality management and inspections

What ERPNext quality management covers and when teams implement it

Manufacturers and distributors that need inspection checkpoints on goods, and a documented quality system around them, use ERPNext quality management to run both. The module covers quality checks at various stages, inspection templates, non-conformance management, batch tracking and supplier quality, so quality results sit next to the stock and purchase records they describe. The Quality Management DocTypes (Quality Goal, Quality Procedure, Quality Review, Quality Meeting, Quality Action, Quality Feedback and Non Conformance) are on the version-16 branch of the ERPNext repository, so confirm which branch and version your rollout will run before you plan the DocType set. The ERPNext quality management documentation is the starting point for the feature list.

Most of the work is configuration, not new software. Quality Inspections attach to item receipts and deliveries, so the decisions sit in stock and buying flows: which item groups require inspection on incoming goods, which on outgoing goods, what each inspection template measures, and who records the result. The reader should decide early whether inspection is required by item, by supplier or by batch, because that choice shapes receiving, putaway and batch records. This is also not a certification. ERPNext records the checks, reviews and non-conformances your team performs, but an auditor or certification body decides whether a quality management system meets ISO 9001 or any other standard.

Teams usually implement this when inspection currently happens on paper or in spreadsheets, when supplier defects are tracked outside the purchasing system, or when an assessor asks for traceable evidence of corrective action. Before the build starts, confirm the inspection points, the templates and parameters per item family, the batch and serial rules that link a failed lot to its receipts and customers, and the roles that can approve, reject or close a non-conformance. A small pilot on one item family, reviewed against real receipts, shows gaps in the templates before they spread across the catalog.

What the quality modules do in ERPNext

ERPNext splits quality work into two layers: inspections that gate goods as they move in and out of the business, and the Quality Management DocTypes that record how the wider quality system is run. The cards below cover both layers, along with the checks to make before you rely on either one in production.

Quality inspections on incoming and outgoing goods

A Quality Inspection record can be required on purchase receipts for incoming products or on delivery notes for outgoing products. Use it to decide, per item, whether a receipt or shipment must be inspected before stock is accepted or sent. Confirm which document types enforce the inspection requirement in your version, and test whether a blocked or rejected inspection stops the stock movement in your own setup.

Inspection templates and parameters

Inspection templates hold the parameters an inspector records, such as numeric ranges, acceptance values and text checks, and they are attached to items. The design work is in the parameter list: each one needs a defined unit, a tolerance and an owner who agrees what a pass means. Review templates with quality and engineering before go-live, because a poorly defined parameter produces inconsistent results that are hard to correct later.

Batch tracking and traceability

ERPNext quality checks can be tied to batches, so an inspection result follows the lot through stock movements rather than only the item code. This matters when a defect is found after shipment and you need to identify every affected batch and customer. Confirm how batch numbers are assigned and whether inspection results are linked to batches in the release you run, and test a recall-style lookup with real sample data.

Supplier quality

Supplier quality links inspection outcomes to the vendors that supplied the goods, so repeated failures can be seen by supplier rather than by item alone. Use it to support supplier evaluation and corrective requests. Ask your quality lead which supplier metrics they need on a report, and confirm which of those the standard reports provide before deciding what to build as a custom report.

Quality Management DocTypes

The Quality Management module adds Quality Goal, Quality Procedure, Quality Review, Quality Meeting, Quality Action, Quality Feedback and Non Conformance records. These cover goals, documented procedures, reviews, meetings and corrective actions, which map onto the structure of an ISO 9001 style quality system. The DocTypes are documented on the version-16 branch, so confirm they exist and match the fields you need in the version you deploy before planning around them.

Non conformance records

Non Conformance records capture a nonconforming product, process or service, along with the investigation and corrective action that follows. In practice, the record is only useful if it connects to inspection failures, quality actions and reviews, so auditors can trace a finding from detection to closure. Map your nonconformance workflow, including who can close a record and how approval is evidenced, before configuring the DocType.

Which inspection and quality settings fit your process

This table compares the main configuration choices for ERPNext quality inspections and the Quality Management module, with the process conditions that favor each option. Read each row against your receiving, shipping and production flows to see which setting matches how your organization actually releases stock.

Decision	Option and when it fits	Trade-off to weigh
Stock movements that require inspection	Purchase receipts when incoming material carries supplier risk or regulatory traceability needs. Delivery notes when customers require certificates of conformance. Manufacturing when in-process checks must gate the next operation.	Each added checkpoint adds handling time at the dock or on the shop floor. Start with the movements where a defect would be costly to trace later.
Inspection trigger scope	Mandatory per item when a specific part or material always needs checking. Mandatory per supplier when a vendor's quality history drives the need, so new items from that vendor are also checked.	Per-item settings are precise but need upkeep as the catalog grows. Per-supplier rules catch new items automatically but can over-inspect reliable suppliers.
Sampling and parameter design per template	One template per item family with numeric parameters for measurable specifications and formula-based or accepted/rejected parameters for visual or pass/fail checks. Set sample size from your written inspection plan.	Too many parameters slow inspectors and produce inconsistent records. Too few leave gaps that an auditor will ask about. Confirm the sampling basis with your quality lead before building templates.
Batch or serial level tracking	Batch tracking fits consumables and bulk materials where lot-level traceability is enough. Serial tracking fits high-value or individually identified units that need unit-level history.	Batch and serial settings must be decided before stock moves. Changing them later usually means a data migration of existing stock records.
Source of non-conformance records	Raise records from inspection failures when defects are found at receipt, shipment or in process. Raise them from audits and quality reviews when the problem is systemic, such as a procedure gap or repeated supplier issues.	Inspection-driven records are fast and specific. Review-driven records capture root causes but depend on meeting discipline and linked corrective actions being tracked to closure.

How the quality rollout runs from item master to go-live

The sequence starts by mapping where quality matters in your stock flows and ends with trained users running inspections and a quality system that people actually use. Each step produces an artifact that the next one depends on.

Map quality points against stock flows
Walk through receipts, transfers, production and deliveries with the quality lead and warehouse supervisor, and mark every point where goods should be inspected, whether incoming, outgoing or both. Record which items, suppliers and customers trigger a check, and which ones do not need one. Confirm with the team that the map matches how goods physically move through your sites. The output is a signed-off quality point map that names each stock movement and its inspection direction, which becomes the specification for every later configuration step.
Build item and supplier quality data
Update item master records and supplier records so that the quality flags, batch or serial tracking settings and supplier quality contacts reflect the map. Decide which items need batch tracking so that inspection results can be tied to lots. Load these changes in a test copy first, then check a sample of items and suppliers by hand. The output is a validated item and supplier data set with quality attributes that match the map, and a short list of items where the data is still missing and an owner for each gap.
Design inspection templates and parameters
Write one Quality Inspection Template for each distinct check, listing every parameter, its expected reading or acceptance criteria, and the method used to measure it. Keep templates reusable across items where the checks are identical, and split them where they differ. Have the quality lead review each template against the current inspection plan or customer specification, and confirm the units and limits. The output is an approved set of templates with parameters and acceptance values, along with a record of who approved each one.
Configure required inspections
Turn on quality inspection requirements at the item, item group or settings level for the receipt and delivery flows identified in step one, and link each item to its template. Test each rule with a dummy document to confirm that the system blocks posting until the inspection is recorded, and that outgoing checks appear where expected. Keep a configuration log that lists each setting, its value and the person who changed it. The output is a working set of required inspection rules with a test result for each flow.
Define the Quality Management structure
Set up the Quality Management module with the goals, procedures and review cadence your quality system needs, as described in your quality manual or ISO 9001 style documentation. Create Quality Goal records with measurable targets, Quality Procedure records for the controlled processes, and a schedule for Quality Review and Quality Meeting entries. Define how Non Conformance and Quality Action records link back to inspections. Confirm the DocType set on your ERPNext version, since the module's records vary across branches. The output is a documented quality structure with owners and review dates that the team can follow.
Run test receipts and deliveries
Process test purchase receipts and delivery notes with real or sample goods, including at least one pass case, one fail case and one batch or serial item. Check that inspection records post correctly, that rejected quantities do not enter available stock, and that Non Conformance records open when a failure is logged. Compare results with the expected outcome on your test plan and log every defect for a fix. The output is a signed test report listing each scenario, the expected and actual result, and the fix or accepted risk for every deviation.
Train users and hand over
Run role-based sessions for receiving staff, inspectors, production supervisors and quality reviewers, using the templates and test documents from earlier steps so people practice on familiar records. Give each role a short procedure that covers what to do when an inspection fails. Agree on ownership of templates, goals and procedures after go-live, and record who maintains each part. The output is trained users, a handover document with named owners and a change process for templates and settings, and a confirmed go-live date agreed with the quality lead.

How incoming and outgoing inspections flow through stock

Incoming inspection is tied to receipt of goods from a supplier. In ERPNext, the check is usually triggered when a Purchase Receipt is prepared for an item that has inspection required on receipt enabled, either at the item level or in the stock settings. The quality inspection record captures the sampled readings against the parameters in the linked inspection template, and the reviewer records whether the batch is accepted or rejected. Your team needs to decide who may accept stock, how rejected goods are segregated, and what happens to the supplier record after a failure.

Trigger: The inspection requirement is set on the item or the buying settings, so receipt of goods creates a pending check before the stock is usable.
Inspection record: Each parameter reading is stored on a Quality Inspection linked to the Purchase Receipt item row and, where batches are tracked, to the batch.
Accept outcome: Accepted quantity moves into the warehouse and becomes available for production, sales or transfer.
Reject outcome: Rejected quantity is kept out of usable stock, and the workflow for returning it to the supplier or scrapping it should be defined before go-live.
Supplier quality: Repeated failures can feed supplier scorecards, so agree who reviews them and how often.

Confirm with your quality lead whether inspection is required for every receipt or only for specified suppliers and items, and test the accept and reject paths with a sample receipt in a non-production site.

What drives quality implementation effort and cost

This table lists the main factors that change how much work a quality setup in ERPNext takes, how each one can be kept manageable, and what to request in a written quote. Read each row as a lever: the larger the driver, the more scope and review time your partner should price explicitly. No figures are given here because none were supplied; ask for them in the quote.

Driver	Why it changes effort	How to keep it down
Items and suppliers needing inspection	Each item or supplier that requires an inspection needs a template, a link to the item or supplier, and a clear rule for when inspection is required on receipt or dispatch.	Start with high-risk or regulated items and key suppliers, then extend coverage once the first cycle runs cleanly.
Parameters per inspection template	Every parameter needs a defined method, acceptance range or value, and a decision on what happens when it fails. More parameters mean more testing of the template with real records.	Group parameters by test method, reuse templates across similar items, and remove checks that do not change a decision.
Batch and serial tracking complexity	Batch and serial numbers decide which inspection result attaches to which physical unit. Mixed batch rules, shelf-life items and serialized goods add configuration and reconciliation work.	Confirm which items truly need batch or serial control before build, and document the traceability rule your quality team expects.
Quality procedure documentation volume	Procedures, goals and review criteria must be written, approved and loaded as Quality Procedure records. Large or inconsistent document sets slow both the build and the sign-off.	Inventory existing documents first, retire outdated ones, and load only the procedures that the system will actively enforce.
Existing paper or spreadsheet records to migrate	Historic inspection logs, supplier scorecards and non-conformance registers need mapping to DocTypes. Data quality problems usually surface during import and cost time to correct.	Decide which history must move and which can stay archived. Import in batches and expect the Data Import tool to need repeated test runs.
Approvers and review cycles	Each approval step, review meeting and action owner adds routing rules, permission checks and testing. Long chains of sign-off extend the acceptance phase.	Keep the approval chain as short as your procedures allow, and agree on who signs off each Quality Review and Non Conformance record.
Access and audit evidence requirements	If records must meet a formal evidence standard such as 21 CFR Part 11 or an ISO 9001 style audit, electronic signature, change history and access control need extra design and documented testing.	Confirm early which regulations apply, and ask the partner which controls they configure versus which your auditor must review.

Loading inspection templates, quality records and history

Inspection templates, item and supplier quality setup, and any open quality records are loaded through the Data Import tool, which reads CSV or Excel files built from downloadable templates and supports child table rows, so a template's parameters can travel with its header. Load master data first (items, suppliers, then the inspection templates they reference), because an import will fail or leave orphan rows when a linked record does not exist yet. The documentation advises importing only a few thousand records per run, so plan batches by DocType and keep each file small enough to check by hand before you commit it. Run a small test batch on a non-production site first and confirm that parameter order, numeric limits and status values come through as you expect.

Decide what moves into the new system by what the quality team will act on. Migrate active inspection templates and any open non-conformance records that still need corrective action, along with the quality goals and procedures that are currently in force. Archive closed non-conformances, superseded template versions and completed quality reviews and meetings. Confirm with your quality lead which fields are mandatory for an open record in your procedures, since an import can populate a field that a later workflow then expects to be filled differently. Also confirm whether batch and serial references on past receipts need to be linked to the new records, because a reference that points to nothing will break traceability reports.

Historical audit evidence usually stays in the source system or in a controlled document store, not in ERPNext. Signed inspection reports, scanned certificates of conformance, supplier audit files and the change history that auditors ask for are often easier to preserve, index and restrict in the place where they were created, with a clear reference from the ERPNext record to that archive. Ask your auditor or certification body what evidence they expect to sample for the migration period, and whether a read-only export of closed records is sufficient. Electronic records and signatures in regulated sectors carry their own requirements, so confirm with your compliance owner whether any migrated signature or approval must be reproduced rather than referenced.

How quality connects to the rest of ERPNext and your systems

How does quality inspection connect to stock and batch tracking?

Quality inspections attach to stock movements, so a receipt or delivery can be held until an inspection is recorded as accepted or rejected. The connection depends on batch or serial tracking being enabled on the items you inspect, because a rejection is only useful if it can be traced to the exact batch that failed. Confirm which items need batch numbers, which warehouses hold rejected stock, and whether your team wants rejected goods blocked from issue or simply flagged. Test the full path with a sample receipt, an inspection, a rejection and a stock issue before you rely on it.

What does supplier quality need from the buying setup?

Incoming inspection works best when purchase receipts for specific suppliers or item groups trigger a required inspection, and when the inspection template matches the supplier's agreed specification. You need clean supplier master data, item-level inspection settings, and a clear owner for accepting or rejecting goods. Supplier quality findings can then feed into Non Conformance records. Confirm which suppliers are audited, how corrective actions are sent back to them, and whether supplier certificates of conformance will be stored against the supplier or the batch.

How do manufacturing checks use the same inspection templates?

Manufacturing checks use inspection templates and parameters for in-process or finished-goods inspection tied to work orders or job cards, so the same parameter definitions can be reused across receiving and production. The engineering effort lies in agreeing which parameters are measured at which operation, and what counts as a failure. Confirm the process steps that require inspection, the measurement tolerances engineering signed off, and whether production should stop automatically or only raise a warning when a check fails.

Which roles and permissions should control who approves quality records?

Approval rights for quality records should be granted through ERPNext roles and permissions, not through shared accounts or informal sign-off. Inspectors, quality managers and auditors usually need different levels of read and write access, and document-level permissions can limit who may edit a Quality Review or close a Non Conformance. Confirm the approval chain for each record type, which roles can override an inspection result, and how role changes are reviewed. Test each role with a real user account in a staging site before go-live.

Can approvers sign in through LDAP or Social Login Key?

Yes, ERPNext supports LDAP login against Active Directory or OpenLDAP through LDAP Settings, with SSL/TLS options and automatic mapping of LDAP groups to ERPNext roles at each login. Frappe's Social Login Key feature supports providers such as Google, Microsoft and GitHub, along with custom OAuth or OpenID Connect endpoints. For approvers, the choice affects offboarding: group-based mapping removes role access when directory membership changes. Confirm which identity provider is authoritative, how group names map to quality roles, and whether multi-factor authentication is enforced at the identity provider.

What do external document control and regulated records require?

The Quality Management module helps structure procedures, reviews and non-conformance records, but it does not by itself make records compliant with external rules. If your records must meet an electronic records and signatures regime such as 21 CFR Part 11, you need to define audit trails, signature meaning, access controls and retention, then have your quality or compliance team and an independent assessor check how ERPNext meets them. DeployOpen can prepare systems, controls and evidence for those assessments but does not issue certifications. Confirm the applicable requirements before configuring signatures or document approval workflows.

Who should own the quality configuration after go-live?

A named quality owner should hold the inspection templates, goals, procedures and approval rules after go-live, with the ERPNext administrator handling roles, scripts and integrations. Changes to parameters or thresholds affect historical comparisons, so they need a change record and a review step. Confirm who can edit templates, how versions are tracked, and who signs off changes to items that are inspected at receipt. Ongoing support can be handled internally or through a DeployOpen retainer, depending on how often the rules change.

Where ISO 9001 style quality meets security and regulatory obligations

ERPNext quality records support an ISO 9001 style quality system, but they do not make your organization certified. Goals, procedures, reviews, meetings, actions, feedback and non-conformance records in the Quality Management module give you evidence of how the system runs. Certification is decided by an accredited certification body that assesses the whole system, including management commitment, document control and how nonconformities are corrected. Before you build anything, ask your certification body which records it expects to sample and how it wants them retained, and confirm that the ERPNext configuration produces them in that form.

Manufacturers often face obligations that sit next to the quality system rather than inside it. Depending on your products and markets, these may include the ISA/IEC 62443 series for industrial automation and control systems, NIS2 incident reporting for entities in manufacturing, and the Cyber Resilience Act for products with digital elements. Each one places its own duties on your ERP data, access control and incident handling, so the quality system cannot be scoped in isolation. Confirm with counsel which of these apply to your entity and product line, and map which ERPNext records and integrations fall within that scope.

If you operate in regulated life sciences, 21 CFR Part 11 governs electronic records and electronic signatures that you use in place of paper. Whether ERPNext records, approvals and audit trails meet that rule depends on how you configure user access, signing steps, validation and change control, and it is a question for your quality assurance function and counsel rather than for the software vendor. Ask your auditors and counsel to confirm applicability in writing before go-live, and plan validation evidence as part of the project rather than after it.

Questions buyers ask before bringing in a partner for quality setup

How long does quality inspection setup in ERPNext take?

The duration depends on how many items need inspection, how many inspection templates and parameters the quality team already has written down, and how many incoming and outgoing checkpoints the process requires. A narrow setup covering incoming goods for a few supplier categories is far shorter than one that also covers in-process checks, batch-level sign-off and supplier quality reviews. No duration is fixed here. Ask for a timeline in the written scope, and confirm which items, templates and approval steps are included before work starts. Your quality documents and sample inspection records are the biggest factor you control.

Can our in-house team configure quality inspections without a partner?

Yes, for a basic setup. ERPNext lets a stock or quality user enable inspection requirements on items, create Quality Inspection Templates with parameters, and require inspections on purchase receipts or delivery notes. The harder work is agreeing the parameters, acceptance criteria and sampling rules with the quality team, and testing how stock, batch and supplier records behave when a lot fails. A partner adds value when the process spans several modules or when you need a documented quality system around the configuration. Your team should test each path with real receipts before go-live.

What do quality, production and IT staff need to provide?

Each group has a distinct role. Quality owns the inspection criteria, the procedures, the acceptance rules and the approval of non-conformance dispositions. Production or warehouse staff explain how goods are received, sampled, moved and recorded on the floor, and they test the workflow with real material. IT owns the ERPNext environment, user roles, permissions, backups and any change control on customizations. Expect to name one accountable owner in each group. Without those owners, templates tend to drift from the practice on the floor.

What does a fixed-scope quote for quality setup include?

A fixed-scope quote lists the agreed scope, the deliverables, the timeline and the exclusions in writing before work starts. For this topic, ask whether it covers the items and suppliers in scope, the inspection templates and parameters, incoming and outgoing inspection settings, the Quality Management DocTypes you choose to use, user testing, training and handover documentation. Ask also what happens if the scope changes during the build. Confirm whether a retainer for later changes or upgrades is separate. DeployOpen does not publish a price list, so a quote follows from the written scope.

Does DeployOpen certify ISO 9001 compliance?

No. DeployOpen does not issue ISO 9001 certificates, audit reports or attestations. It can help prepare the ERPNext configuration, records and evidence that a quality system needs, such as inspection records, procedures, reviews and non-conformance records. An accredited certification body performs the certification audit. Ask your certification body early which records it expects to sample, and confirm with it how ERPNext evidence will be presented. The certification decision stays with the certification body and your organization.

How does the ERPNext version affect Quality Management features?

The feature set depends on the version you run. The Quality Management module on the version-16 branch includes Quality Goal, Quality Procedure, Quality Review, Quality Meeting, Quality Action, Quality Feedback and Non Conformance DocTypes. Confirm which of these exist in your installed version before you design the process around them. Also check the support status of your version on the Frappe supported versions page, since version 14 reached end of life on January 31, 2026. Plan the upgrade path before you build, so the quality records you create survive the move.

What ongoing work follows go-live?

Quality setup needs regular upkeep. ERPNext ships frequent minor releases on supported branches, so you will need a process for testing and applying them. Inspection templates change when specifications change, and new suppliers or items need their own settings. Review and meeting records need owners who keep them current. Ask whether support is covered by a retainer, what response expectations apply, and who approves template changes. If you run ERPNext on Frappe Cloud, confirm the support plan that matches your version before you rely on vendor warranty coverage.

How DeployOpen scopes and delivers ERPNext quality implementations

DeployOpen plans, implements, customizes, documents and supports self-hosted open-source platforms inside your own infrastructure, and that includes ERPNext quality management and inspections. Engagements start from a written scope that sets out which inspection points, templates and Quality Management records are in play before any configuration begins.

How we scope

Map each goods receipt and delivery point that needs a quality inspection, and who performs it.
List the inspection templates and parameters each item group or supplier requires, with acceptance criteria agreed in writing.
Confirm which Quality Management records your system will use, such as goals, procedures, reviews and non-conformance records.

How we build

Configure Quality Inspection settings for incoming and outgoing goods, and test them against your stock entry flows.
Build templates, parameters and any custom fields or scripts needed, with each change recorded for review.
Test inspection failures, rejection paths and non-conformance handling with sample data before any live use.

How we hand over

Document the inspection setup, roles, approval steps and record ownership so your team can maintain them.
Walk your quality and warehouse staff through daily inspection work and the non-conformance workflow.
Provide configuration records and test evidence that your internal or external auditors can review.

How we support

Offer ongoing support, upgrades and testing as a retainer after go-live, when your quality process changes.
Plan ERPNext version upgrades in advance, confirming supported versions and how quality module changes affect your setup.
Confirm with your auditors which records and controls they expect, since DeployOpen prepares evidence but does not issue audit reports or certifications.