Quality

This page is generated from the in-app guide content — edit featureToggleGuides and run pnpm gen:feature-toggle-docs.

Auto-Create NCR on Fail

Automatically create a minor Non-Conformance Report when an inspection fails (manufacturing operation inspections get their NCR from Manufacturing).

How it works

When submitted inspection results compute to Failed, a minor non-conformance report (NCR) linked to the inspection is created automatically.

When ON

Each failed inspection opens one NCR with severity Minor and a generated title. If an NCR approval workflow is active, the NCR starts in Pending approval like any NCR created by hand.

When OFF

(Default for existing companies) No NCR is created; QA raises one manually from the inspection if needed.

Screens, documents and reports affected

Inspection submit, NCR list, Quality overview.

Caveats

Inspections of manufacturing operations and production reports are skipped — Manufacturing creates their NCR itself. The NCR is created after the result is saved; if creation fails, the inspection stays Failed and a note “[auto-ncr-failed] …” is added to the inspection so QA can raise the NCR by hand. On for new companies.

Example

An incoming batch fails 3 of 5 checks; NCR “Auto-generated NCR for failed inspection QC-0042” appears in the NCR list for triage.

Auto-Hold on Inspection Fail

Flag a failed inspection as On hold until it is released. Only the inspection record is flagged — stock and documents are not blocked.

How it works

When submitted results compute to Failed, the inspection itself is flagged On hold with the reason “Automatically held due to failed inspection”.

When ON

Failed inspections show the On-hold badge and are counted in the On-hold tile of the Quality overview until someone uses Release on the inspection.

When OFF

(Default for existing companies) Failed inspections are not flagged; inspectors can still put any inspection on hold manually.

Screens, documents and reports affected

Inspection detail (hold badge, Release), Quality overview On-hold count.

Caveats

The flag lives only on the inspection record — it does not block stock, sales, the goods receipt or the work order. To block received stock use “Hold received stock until inspection”. A failed inspection never reaches Pending approval, so only Release clears the flag. On for new companies.

Example

QA filters the overview by On hold each morning to review yesterday’s failures, then releases them once an NCR is raised.

Auto-inspect on goods receipt

Automatically create a quality inspection when a goods receipt is confirmed

How it works

When a goods receipt is confirmed (from Inventory, from a purchase order, or from POS store operations), an incoming inspection seeded from the receipt lines is created automatically.

When ON

Each confirmed receipt gets one Pending inspection referencing it. The inspection cannot be cancelled by hand; its result drives the release of held stock.

When OFF

(Default for existing companies) No inspection is created; QA can create one from the receipt manually.

Screens, documents and reports affected

Goods receipt confirm (Inventory, Procurement), Inspections list, incoming QC.

Caveats

Creation runs after the receipt is confirmed; if it fails (or no user can be recorded as its creator), the receipt stays confirmed, the error is logged, and any stock held for it is released at once. Turning the switch off while receipts are held releases the held stock of receipts that never got an inspection. Required by “Hold received stock until inspection”. On for new companies.

Example

A supplier delivery is confirmed; inspection QC-0050 appears in the incoming queue for the receiving inspector.

Due Date Required on NCR Assignment

Require a due date when assigning an NCR to a responsible person.

How it works

Assigning an NCR to a responsible person requires a due date.

When ON

Assigning without a due date is rejected with an error.

When OFF

(Default for existing companies) The due date is optional when assigning.

Screens, documents and reports affected

NCR assignment, overdue NCR list and overdue badge.

Caveats

Checked both when assigning and when creating an NCR with an assignee. NCRs assigned before the switch was turned on may still have no due date and never show as overdue. On for new companies.

Example

QA assigns an NCR to the line supervisor with due date 3 days out; it shows as overdue on day 4.

Hold received stock until inspection

Received quantity stays on hold (not available to sell or issue) until the goods-receipt inspection is decided; rejected quantity stays held until returned to the supplier

How it works

Quantity received on a goods receipt is placed on hold (not available to sell or issue) in the same transaction as the receipt, until its automatic incoming inspection is decided.

Conditions for it to take effect

Needs “Auto-inspect on goods receipt” on. If it is off, nothing is held even with this switch on.

When ON

Passed or conditionally passed: everything is released except quantity recorded as rejected on the inspection lines. Failed: only quantity recorded as accepted is released; the rest stays held until it is returned to the vendor or the receipt is voided. With “Require inspection approval” on, release waits for the approval.

When OFF

(Default) Received stock is available immediately. Receipts linked to sales-order lines reserve the stock for that order at once.

Screens, documents and reports affected

Goods receipt confirm, stock on hand vs available, issues and sales from held items, vendor returns, inspection submit and approve.

Caveats

Turning it off does not release stock already held — it is released by the inspection decision as usual. Record accepted/rejected quantities on the inspection lines before submitting a failure, otherwise nothing is released. If a receipt is held but no inspection exists after 10 minutes, a background check releases it and logs the event. For purchase-for-sales-order lines, the order reservation happens after the hold is released.

Example

200 units received, inspection fails with 180 accepted and 20 rejected: 180 become available, 20 stay held until the vendor return.

Require Corrective Action

Block resolving an NCR without documenting the corrective action plan.

How it works

Moving an NCR to Resolved requires a corrective action in the same request.

When ON

(Default) Moving to Resolved without a corrective action is rejected with an error.

When OFF

An NCR can be resolved with the corrective action left blank.

Screens, documents and reports affected

NCR detail (status buttons), NCR status changes from the approval inbox.

Caveats

The check uses the corrective action sent with the change or, if none is sent, the one already saved; text made only of spaces does not count. NCRs already resolved are not affected.

Example

An engineer marks an NCR resolved; the system requires “replace fixture, retrain operator” before accepting.

Require Inspection Approval

Passing inspection results wait in Pending approval until someone with quality:approve (or the approval workflow) approves them; failed results are final immediately.

How it works

When an inspector submits results that pass (passed or conditionally passed), the inspection waits in Pending approval instead of becoming final. A failed result is always final immediately.

When ON

(Default) Passing results save as Pending approval and are sent to the “qc_inspection” approval workflow if one is active; without a workflow, someone with quality:approve approves on the inspection page. Approving recomputes the outcome from the stored results and makes it final; rejecting sends the inspection back to Pending so the inspector can correct and resubmit. For goods-receipt inspections with held stock, the stock is released only when the inspection is approved.

When OFF

Passing results become final as soon as they are submitted.

Screens, documents and reports affected

Inspection detail (Submit results, Approve, Reject), approval inbox, incoming QC on goods receipts, inspections of manufacturing operations and production reports (they go through the same submit step).

Caveats

Turning it off does not finalize inspections already Pending approval — approve or reject them. Migration 1809 set the switch back to on for companies that had saved it as off. The person who submitted results cannot approve them unless “Allow self-approval” is on.

Example

A receiving inspector records all checks as pass; the QA lead approves it in the inbox, and only then does the received stock become available.

Require Root Cause

Block moving an NCR to Under review without a root cause.

How it works

Moving an NCR to Under review requires a root cause in the same request.

When ON

(Default) Moving to Under review without a root cause is rejected with an error.

When OFF

An NCR can move to Under review with the root cause left blank.

Screens, documents and reports affected

NCR detail (status buttons), NCR status changes from the approval inbox.

Caveats

The check uses the root cause sent with the change or, if none is sent, the one already saved; text made only of spaces does not count. Existing NCRs are not checked when the switch is turned on.

Example

A supervisor tries to start review on a scratch-defect NCR; the system asks for the root cause “worn fixture” first.

Verification Notes Required on Close

Require verification notes when verifying a resolved NCR — verification is the step before closing.

How it works

An NCR can only be closed after it has been verified (Verify on the NCR page, requires quality:approve). With this switch on, verification also requires notes.

When ON

Verify without notes is rejected with an error, so a resolved NCR cannot be closed until someone verifies it with notes.

When OFF

(Default for existing companies) Verification notes are optional; the NCR must still be verified before it can be closed.

Screens, documents and reports affected

NCR detail (Verify panel), Unverified NCRs list.

Caveats

Closing (Resolved → Closed) is blocked for every NCR that has not been verified, whatever this switch says; the Close button (web and mobile) appears only after verification. Sending the NCR back to Open or Under review, or changing the corrective action while Resolved, clears the verification so the new fix must be verified again. NCRs closed automatically when their production report is voided are not affected. On for new companies.

Example

QA verifies an NCR with the note “re-inspected 20 units, all within tolerance”.