Operations module
QUALITY / MODULEQuality
The inspector cannot release their own inspection, and a failed inspection automatically places an inventory hold — spanning receiving, production, stock, and returns.
Inspection to CAPA
- 01
Inspect
An inspection runs against the relevant quality plan for that stage.
- 02
Fail and hold
A failed inspection automatically places an inventory hold on the affected material.
- 03
Release (separate step)
Release requires a different person than the inspector — a hard-coded segregation of duties.
- 04
Raise non-conformance
A severity-graded NC record captures what went wrong.
What it is
The Vercentlabs Quality module enforces inspection checkpoints and disposition control across incoming receipts, in-process manufacturing, stock, and returns, with governed release and CAPA-driven resolution — a genuine cross-module inspection framework, not a module-local checklist.
Module atlas / operating conditions
Why Quality becomes difficult in fragments
Bad material or product silently enters stock or shipping
Without a governed inspection checkpoint, defective incoming material or finished goods can move forward with nothing to stop them.
No segregation of duties between inspection and release
The same person who inspects a lot can also release it, removing the independent check that segregation of duties is supposed to provide.
One-off defect notes instead of tracked corrective action
A defect gets noted somewhere, but there's no structured non-conformance record, root cause, or corrective action that gets verified as effective.
No supplier performance visibility
Supplier quality issues repeat because there's no structured scorecard or audit trail tying failures back to the source.
Operating outcomes
What changes when Quality shares one system of record
No one signs off their own work
Release is a separate, governed step from inspection completion, and the inspector cannot release their own inspection.
Automatic containment on failure
A failed inspection automatically places an inventory hold — no manual flag to remember.
Tracked corrective action, not a note
Severity-graded non-conformance links to a CAPA with root-cause analysis and effectiveness verification.
Supplier accountability with evidence
Periodic scorecards and structured audits link findings directly to corrective action.
Capability architecture
The module, decomposed by operating capability.
6 capability groups organised by the way the product works, not as a flat marketing feature wall.
Quality plans & inspection points
Reusable inspection definitions typed by where they apply.
- 01Plans typed by stage: incoming, in-process, final, stock audit, supplier, customer return
Inspection execution & release
Where the segregation-of-duties control actually lives.
- 01Release is a separate, governed step from inspection completion
Holds & disposition
What happens automatically when something fails.
- 01Automatic inventory hold on failed inspection (togglable)
Non-conformance & CAPA
Turning a defect into a tracked, verified fix.
- 01Severity-graded non-conformance
- 02Linked CAPA with root-cause analysis, corrective/preventive action, and effectiveness verification
Supplier quality & audits
Holding suppliers accountable with structured evidence.
- 01Periodic supplier scorecards
- 02Structured audits with findings linkable to CAPA
Traceability
A durable record of what happened, and when.
- 01Append-only quality event log
Primary operating sequence
A transaction-level view of how work progresses through Quality.
See it work
Inspection to CAPA
The ordered process a real Quality workflow follows inside Vercentlabs.
Trigger
A source event occurs — a receipt, a work order/production posting, a stock batch/serial, or a return.
- Inspect
An inspection runs against the relevant quality plan for that stage.
- Fail and hold
A failed inspection automatically places an inventory hold on the affected material.
- Release (separate step)
Release requires a different person than the inspector — a hard-coded segregation of duties.
- Raise non-conformance
A severity-graded NC record captures what went wrong.
- CAPA
Root cause, corrective action, and preventive action are tracked through to verified effectiveness.
Approvals
- 01Release cannot be performed by the same person who completed the inspection.
Automated actions
- 01Auto-hold on inspection failure (togglable)
- 02Append-only event logging
Connected modules in this workflow
Outcome
A defect that's contained automatically, tracked to root cause, and verified as actually fixed — not just noted and forgotten.
Operational proof
Quality, documented as an operating system.
Capability architecture
6 groups
Grouped by how the module is actually structured.
Primary operating sequence
Inspection to CAPA
Rendered above as an ordered process rather than a feature collage.
Connected system
4 modules
Adjacent modules are linked through the operating model on this page.
Business outcome
No one signs off their own work
Release is a separate, governed step from inspection completion, and the inspector cannot release their own inspection.
Ready to see Quality running on your own data?
Book a DemoSystem map
Quality does not operate alone.
The handoffs below are part of the operating model, not decorative cross-sells.
Incoming receipts can be a source for a Quality inspection before material is accepted into stock.
Stock batches and serials can be a source for a stock-audit inspection, and a failed inspection places a hold directly on that stock.
Output register
What Quality tells operators and managers
Open/failed/today's inspections, active holds, open NC/CAPA count
Audience / QA managers, plant quality engineers
Rule register
What the module can run on its own
A failed inspection automatically places an inventory hold, togglable per organization policy.
The system itself, not just a policy document, prevents an inspector from releasing their own inspection.
Control register
How Quality stays governed
Module-specific controls shown separately from the platform-wide security architecture.
The single most load-bearing control in the module — release requires a different person than the inspector.
Quality records are isolated at the database row level.
What to plan before going live.
- 01
Quality plans and inspection points are defined per stage (incoming/in-process/final/stock-audit/supplier/customer-return) before go-live.
- 02
Auto-hold policy is decided per organization — whether a failed inspection always holds stock or requires a manual step.
- 03
CAPA workflows and severity grading are configured to match your existing quality process.
- 04
Quality has no mobile presence today — it is a web-only workflow for inspectors.
Buyer questions
Questions teams ask about Quality
Can an inspector release their own failed inspection after fixing the issue?
No — release is a separate, governed step from inspection completion, and it requires a different person than the original inspector. This is hard-coded, not a configurable policy.
What happens automatically when an inspection fails?
An automatic inventory hold is placed on the affected material — batch, serial, receipt, work order, or return — so it can't move forward silently. This behavior is togglable per organization.
Does Quality only cover incoming receiving?
No — quality plans are typed by stage and span incoming, in-process manufacturing, final inspection, stock audits, supplier quality, and customer returns. It's a genuine cross-module framework, not a receiving-only checklist.