Odoo quality control points: inspect at the right moment

For an Odoo business in Belgium or France, a useful quality check is not simply another approval. It must appear at the operation where risk actually arises: supplier receipt, manufacturing, packing or delivery. Quality Control Points in Odoo Enterprise can automate that trigger, provided every check is connected to a clear operational decision.

Start with the defect the team needs to prevent

Before creating control points, name the defect, its detection point and its consequence: a damaged component at receipt, an out-of-tolerance measurement in production, or an incorrect label before dispatch. This prevents the same check from being placed at every step. It also makes it possible to decide who performs the check, who handles a failure and where the product waits for a decision.

In Odoo, a Quality Control Point can target a specific operation and, where relevant, a product or product category. In manufacturing it can target a work-order operation. Its scope should remain obvious to an operator: “Check tightening torque — assembly” is more actionable than a generic label.

Choose a trigger that is proportional to the risk

Odoo supports checking by operation, product or quantity. An operation check suits a global verification; a quantity check supports sampling. Frequency can be every time, random, periodic or on demand. Checking 100% of every item is not automatically better: it can shift risk towards rushed, unreliable confirmations.

Begin with a simple, measurable rule. For receipts of sensitive components, for example, trigger a measurement check for each received lot, then compare the rejection rate, processing time and customer incidents. Adjust sampling based on observed data, rather than inherited habit.

Plan the decision when a check fails

A failed check without a next step creates a record, not protection. Define the instruction: isolate the item, raise a quality alert, request a second review, or approve a documented deviation. Odoo failure locations can help prevent rejected product from returning to available inventory. Identify the decision owner and escalation deadline as well.

This discipline matters especially when Belgian and French teams use the same Odoo database. Labels, failure reasons and instructions must mean the same thing in both languages; an approximate translation of a product non-conformity leads to inconsistent treatment.

Acceptance test the entire flow, not just the screen

Fictional Underside scenario: a business receives a lot of 50 components. The receipt control point requests measurements on five items; one is out of tolerance. Acceptance testing must confirm that the user can record the measurement, that failure sends the item to the right location, that the responsible person receives the information, and that available stock stays correct.

• Test a passing result, a failure and a measurement close to tolerance.
• Test a check on the wrong product to confirm the scope is correct.
• Test a periodic or random control across several successive receipts.
• Have another user take over the case and verify rights, instructions and history.
• Verify return to stock or scrap after the decision, with no invisible manual correction.

Track a few metrics, tied to decisions

Track failures by product, supplier or operation, time to resolve non-conformities, and overdue checks. These metrics should improve receipt, production or dispatch processes; they should not become an isolated dashboard. Our guide to Odoo lots and expiry dates complements traceability, while the cycle-counting guide helps make inventory reliable.

Official source and scope

Reference: Odoo 19 documentation on Quality Control Points. Verify the settings available in your Odoo edition and installed modules. The framing rules, acceptance test and metrics are Underside’s analysis.