Where a quality control point defines that quality should be verified, a quality check is the actual verification, carried out and recorded. This piece explains quality checks in Odoo manufacturing.
The edition note
As with quality control points, the dedicated Quality capability in Odoo, including quality checks, is an Odoo Enterprise application. A quality-serious manufacturer should plan on Enterprise. This piece describes quality checks as they work in the Quality application.
What a quality check is
A quality check is an individual verification of quality, carried out where a quality control point requires it. The control point is the standing definition, "quality should be verified here, in this way". The quality check is the actual instance: the verification being done, at the moment it is due, with a result. Where the control point says what should happen, the quality check is what happens.
How quality checks fit into manufacturing
In Odoo manufacturing, quality checks fit into the flow of production. Because quality control points can be tied to manufacturing operations, a quality check appears as part of the work: when an operator runs a work order that has a quality check associated with it, the check is there, part of doing the operation. The operator carries out the verification the check requires, and records the result, as part of the work order. This is what makes quality checks effective in manufacturing, they are not a separate activity bolted on, but a step within the production work, happening at the operation where the quality matters.
What a quality check involves
A quality check involves the person carrying it out doing the verification the control point defined, a pass-or-fail confirmation, a measurement against a specification, an inspection, whatever the check requires, and recording the result. The recording is important: the quality check is not only a moment of verification but a recorded fact. Once recorded, the result of the check becomes part of the record of what was produced.
Why recording the check matters
The recording of quality checks matters for two reasons. The first is the immediate one: a recorded check that fails is a problem flagged, something that can be acted on, rather than a problem that passes by unnoticed. The second is the lasting one: the recorded quality checks build up into a quality history of what was produced. That history is part of traceability, it is the record of how quality was verified for a given batch or product, and it is what a manufacturer can show when a customer or an auditor asks, or review when investigating a problem. Quality checks recorded as they happen mean the quality record is a by-product of normal production, not something assembled afterward.
When a check fails
A quality check is only fully useful if a failed check leads to something. In Odoo's Quality capability, a failed check can lead to a quality alert, so the failure becomes a flagged issue to be addressed rather than just a recorded negative result. This is the difference between checking quality and managing it: the check finds the problem; the alert ensures the problem is acted on. Quality checks and quality alerts work together, the check is the verification, the alert is the response when the verification fails.
Quality checks and the operator
One practical point. Quality checks in manufacturing are carried out by operators, as part of their work. For the checks to be done properly and recorded honestly, they have to be quick and clear, the operator needs to know exactly what to verify and be able to record the result easily. A quality check that is clear and quick gets done faithfully; one that is vague or burdensome gets rushed or skipped. A manufacturer setting up quality checks should make them clear and easy, so the quality data they produce is genuine.
The takeaway
Quality checks in Odoo manufacturing, part of the Enterprise Quality application, are the actual verifications carried out where quality control points require them. They fit into production by appearing as part of work orders, so quality is verified within the flow of work. Each check is carried out and its result recorded, and that recording flags failures for action and builds a quality history. A failed check can raise a quality alert. Quality checks should be clear and quick so operators do them faithfully. For how we approach Odoo for manufacturers, see our manufacturing work.