> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alforse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quality

> Issues and corrective-action workflows, plus incoming inspection that gates received goods.

The quality module provides **issues** for recording and resolving defects, and **inbound inspections** for holding received goods until they pass inspection. Both retain links to their source records.

## Issues

An **issue**, a non-conformance or NCR, records something that went wrong and the work to resolve it. It moves through three states: **Registered**, **In Progress**, **Closed** (closed is terminal and locked). Each carries a **priority** (Low / Medium / High / Critical), a **source** (Internal or External), a type, and links to whatever it concerns: a job operation, a purchase or sales order line, a receipt, a supplier.

Issues open from several places: by hand, from the shop floor in MES, from Slack, or **automatically** when an inbound inspection is rejected.

### Workflows and actions

An issue can run a configurable workflow, often an **8D**. The workflow attaches **required actions** and **approvals** as tasks; each task advances *Pending → In Progress → Completed* (or *Skipped*) as the team works it. Adding a **Material Review Board** approval gates closing the issue: it can't close until a **disposition** is chosen for the affected material. The five options are *Pending* (not yet decided), *Return to Supplier*, *Rework*, *Scrap*, and *Use As Is*.

Closing the issue posts each disposition's stock movement to the general ledger. *Scrap* and *Return to Supplier* write the material off — relieving its inventory cost layers and posting **debit Scrap / Cost of Quality, credit Inventory** — so scrapped and returned value lands on a dedicated cost-of-quality account rather than distorting on-hand inventory. *Use As Is* and *Rework* keep the material as stock, restoring any value an earlier rejection had written off. Once an issue has posted these entries it can no longer be reopened; a correction is booked forward as a new adjustment, never by unwinding the original.

NOTE

There's no dedicated supplier scorecard in Alforse. **Supplier quality is a derived metric**, counted from the issues linked to each supplier. The data comes from the issues themselves, not a separate record.

## Inbound inspection

When goods arrive for an item that **requires inspection**, posting the receipt opens an inbound inspection and holds the received units **On Hold**. They're not available stock yet. Inspection is lot-based, with sample sizes drawn from AQL standards (ANSI / ISO).

An inspection moves through **Pending**, **In Progress**, and one of three outcomes: **Passed**, **Failed**, or **Partial**. Dispositioning the lot decides what happens: **Passed** accepts it and the units become available; **Failed** rejects it, marks the units rejected, and opens an issue automatically; **Partial** clears some and holds the rest.

NOTE

Inbound inspection only fires on **purchase-order receipts** of items flagged to require it. Until a lot is dispositioned, its units sit On Hold: received, but not yet stock you can sell or consume.

### Executing an inspection

Whatever raised it, an inspection is worked on one screen: a features × samples grid laid over the item's ballooned drawing. Each column is a sample (scanned serials and batches label their own column); each row is a feature to measure, recording a value or a pass/fail. Sample and lot status are derived from those readings against tolerance. The same screen serves an inbound lot held off a receipt and an in-house **Inspection** job operation — an Inspection operation resolves the part's inspection document and runs this grid on the shop floor.

## Also in quality

The module also covers [**gauges and calibration**](/docs/reference/calibration.md) (with calibration-due tracking), **controlled documents** (versioned procedures and work instructions, with one active version at a time), **inspection documents** (ballooned FAI drawings and their features), and a **risk register**.

## Related

**Receipts**

How received goods are posted — and held for inspection.

[Open](/docs/reference/receipts.md)

**Approvals**

A quality document can require sign-off before it goes Active.

[Open](/docs/reference/approvals.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.