Odoo Quality: control points, checks, and alerts explained

What is Odoo Quality?

Odoo Quality is the Quality application within Odoo's Manufacturing (MRP) family. Its job is to ensure product quality throughout manufacturing processes and inventory movements: employees conduct quality checks, the system automates the frequency of inspection, and quality alerts are raised when issues arise.

Unlike bolt-on quality tools, Odoo Quality is wired into the orders it inspects. A check appears directly on the manufacturing order (MO) or inventory transfer where the work happens, so the person doing the job is prompted to complete it inline rather than in a separate system. That tight coupling is the main reason SMEs running Odoo Manufacturing adopt the Quality app.

The module is organized around three building blocks: quality control points (the rules), quality checks (the execution), and quality alerts (the exceptions). Understanding how those three fit together is the fastest way to evaluate whether Odoo Quality covers your inspection needs.

Quality control points: the rule layer

A quality control point (QCP) is the rule that decides when and where a check is created. Each QCP binds several things together: an operation it triggers on, optionally a target product or product category, a control-per rule, a control frequency, and a check type.

The Operations field can be set to Manufacturing (which then exposes a Work Order Operation field to target a specific step such as Assembly), Receipts, or a delivery operation. At least one operation must be listed when creating a QCP. Products and Product Categories can be left blank to apply the QCP to every instance of that operation.

The Control per field determines when a check is created: Operation (one check for the whole operation), Product (one check per unique product in the operation), or Quantity (a check for a percentage of items via a Partial Test value).

• →Operation: triggers one check for the entire manufacturing order or transfer.
• →Product: triggers one check per unique product on the order.
• →Quantity: triggers a check on a percentage of items, controlled by a Partial Test value.

Quality check types: from pass-fail to spreadsheets

Once a QCP fires, it generates a quality check of a specific type. Odoo supports a range of check types so inspection can match the work being done:

An Instructions check behaves like a step on a work order for a manufacturing order. When a step is added to a work order, Odoo stores it in the Quality app as a QCP, so work-order instructions and quality instructions stay in sync.

Measure checks are the most common quantitative type: you set a Norm value plus a Tolerance, and the operator enters a measured value that must fall within tolerance to pass. Pass-Fail is the simplest binary inspection. Register Consumed Materials and Register Production checks tie quality directly into the MO's material and output accounting, so inspection and production reporting happen together.

• →Instructions: a procedural step attached to a work order.
• →Take a Picture: capture photographic evidence of the operation result.
• →Register Consumed Materials: confirm which materials were used during the operation.
• →Register Production: confirm output quantities on the manufacturing order.
• →Print Label: generate a label as part of the inspection step.
• →Pass-Fail: a binary accept/reject decision.
• →Measure: a numeric reading validated against a Norm and Tolerance.
• →Spreadsheet: a check validated by a configured Success cell.
• →Worksheet: a check validated by defined Success Conditions.

Quality checks: the execution layer

Odoo quality checks are manual inspections conducted by employees. The majority are created automatically by a QCP and appear on the manufacturing or inventory order where the employee processing the order is prompted to complete them. A single check can also be created manually from Quality > Quality Control > Quality Checks when an inspector needs to record a one-off inspection.

Each check carries Pass and Fail buttons so the result is recorded against the order itself. Because the check lives on the MO or transfer, the result is traceable back to the exact batch, work center, and operator involved, which is essential for any later corrective action.

One important limit: quality checks for specific work order operations can only be created by a QCP. It is not possible to manually create a single quality check assigned to a specific work order operation. Those work-order checks are processed in the Shop Floor module, which is part of Odoo's Manufacturing app family.

Quality alerts: the exception layer

When a check fails, or when a defect is spotted outside any check, Odoo uses quality alerts to notify the quality team. Alerts can be raised from a manufacturing order via the Quality Alert button, from an inventory order, from a work order in the Shop Floor module, or directly in the Quality app under Quality Control > Quality Alerts.

An alert carries the context the team needs to act on it: a Title, the related Product, Product Variant, Work Center, or Picking, a Responsible Team and employee, Tags, a Root Cause field, and a one-to-three-star Priority. The form is organized into tabs for Description, Corrective Actions, Preventive Actions, and Miscellaneous (Vendor, Company, Date Assigned).

Alerts appear on a Kanban board organized by review stage, so the quality team can triage open defects, assign corrective and preventive actions, and track them to closure. The Root Cause field is what makes alerts useful over time: tagged root causes let you spot recurring supplier or process issues rather than treating each defect as a one-off.

1. 01
   Raise the alert at the source

   Use the Quality Alert button on the manufacturing order or inventory transfer so the alert is automatically linked to the exact batch and operation.

2. 02
   Capture root cause and priority

   Set the Root Cause tag and one-to-three-star Priority so the alert can be triaged and aggregated with similar defects later.

3. 03
   Assign a responsible team

   Name the team and employee accountable for resolution so nothing sits unowned on the Kanban board.

4. 04
   Plan corrective and preventive actions

   Use the Corrective Actions and Preventive Actions tabs to document both the immediate fix and the systemic change that prevents recurrence.

5. 05
   Move the alert through review stages

   Drag the alert across the Kanban board from open to closed, keeping the description and miscellaneous details (vendor, company, date) intact for audit.

A typical SME quality setup in Odoo

For a small or mid-sized manufacturer, the pragmatic starting pattern uses QCPs to cover three inspection moments without over-engineering. First, put one QCP per critical work-center operation, for example Assembly on a Coffee Table, running at All frequency with a Pass-Fail or Measure check. That guarantees every unit passes the critical step before it moves on.

Second, add a Periodically QCP on Receipts for incoming-goods inspection. A periodic frequency on Receipts covers supplier quality without inspecting every delivery, which is usually enough for SME volume.

Third, encourage operators to raise quality alerts early with a Root Cause tag. Aggregated root-cause tags are how a small team spots a recurring supplier defect or a worn tooling issue before it becomes a customer return.

• →One QCP per critical work-center operation at All frequency with a Pass-Fail or Measure check.
• →A Periodically QCP on Receipts for incoming-goods supplier inspection.
• →Quality alerts with Root Cause tags to surface recurring defects.
• →Work-order checks executed in the Shop Floor module where operators actually work.

The Dynamics 365 equivalent: Quality and nonconformance management

If you are comparing platforms, the Dynamics 365 Supply Chain Management equivalent is the Quality and nonconformance management module under Inventory management > Setup > Quality management. The conceptual shape is the same, trigger rules generate an inspection, and exceptions are tracked separately, but the configuration surface is markedly larger.

Where Odoo uses QCPs, D365 SCM uses Quality Associations that generate Quality Orders for a specific item, an item group, or all items based on trigger points such as at product receipt for inbound operations or at product pick-up for outbound operations. Where Odoo uses a single Measure check with Norm and Tolerance or a Pass-Fail, D365 defines Tests with minimum, maximum, and target values, qualitative-versus-quantitative outcomes, item sampling (fixed quantity, percentage, or full license plate), and an Acceptable Quality Level (AQL) to govern tolerances, plus dedicated Test Instruments and Test Groups.

Where Odoo uses Quality Alerts with Corrective and Preventive Actions tabs, D365 uses Nonconformances linked to problem types, diagnostic types, quarantine zones, operations, and correction handling that schedules corrective tasks and records the cost of the nonconformance (spare parts, miscellaneous charges, timesheet hours). D365 SCM also supports inventory blocking during inspection and the Quality management for warehouse processes feature for advanced warehouse flows.

• →Trigger: Odoo QCPs vs D365 Quality Associations with at-receipt / at-pick-up trigger points.
• →Inspection: Odoo check Types (Pass-Fail, Measure, Picture, Worksheet) vs D365 Tests with min/max/target, AQL, item sampling, and Test Instruments.
• →Exception: Odoo Quality Alerts with Root Cause and corrective/preventive tabs vs D365 Nonconformances with problem types, quarantine zones, diagnostics, and cost tracking.
• →Setup weight: Odoo consolidates into one app; D365 separates tests, test variables, test groups, problem types, quarantine zones, and diagnostic types.

When each platform fits an SME

The two products target different segments and that shapes which one fits a given SME. Odoo's Quality app is a single integrated application, often bundled in Odoo Enterprise, with QCPs, checks, and alerts in one place. It suits SMEs that want quality inspection embedded in their day-to-day manufacturing and inventory work without a large configuration project, and who value having quality, MRP, inventory, and purchasing in the same database.

D365 SCM Quality Management is a module within the larger Dynamics 365 Supply Chain Management suite. Its separate setup for tests, test variables, test groups, problem types, quarantine zones, and diagnostic types reflects an enterprise posture, and it pairs naturally with advanced warehouse processes, financials, and broader Microsoft supply-chain tooling. It tends to fit mid-market and upper-mid-market manufacturers who already run, or plan to run, the wider D365 SCM stack.

As a dual-platform partner, Flectic helps SMEs in Canada, the UK, and the USA choose the right fit based on their existing systems, scale, and inspection complexity rather than forcing one platform. Our AI-accelerated delivery approach is designed to deliver up to 3x faster, and it applies equally to Odoo Quality rollouts and Dynamics 365 SCM Quality Management projects.