Odoo Quality: control points, checks, and alerts explained

What is Odoo quality control?

Odoo quality control is the Quality application in Odoo’s manufacturing and inventory family. It ensures product quality throughout manufacturing processes and inventory movements: employees conduct quality checks, the system automates inspection frequency via quality control points, 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 completes it inline rather than in a separate system. Odoo’s product framing stresses non-blocking, order-integrated inspections: you can complete checks from the MO or transfer without opening the Quality app, and you can request a check for an entire MO or a single work order step.

The module is organized around three building blocks: quality control points (the rules), quality checks (the execution), and quality alerts (the exceptions). Adjacent inventory features such as failure locations close the loop when rejected units must leave sellable stock. Understanding how those pieces fit together is the fastest way to evaluate whether Odoo Quality covers your inspection needs—and to outrank a pure UI walkthrough with operational outcomes SMEs actually care about.

Quality control points: the rule layer

A quality control point (QCP) is the rule that decides when and where a check is created. Configure QCPs at Quality → Quality Control → Control Points → New. Each QCP binds several things together: a Title, optional Products and Product Categories, required Operations, optional Work Order Operation (when Manufacturing is selected), Control per, Control Frequency, check Type, Team, Responsible, and instruction/failure-message tabs.

The Operations field can be set to Manufacturing (which then exposes Work Order Operation to target a specific step such as Assembly), Receipts, Delivery, or other inventory operation types. At least one operation must be listed. Products and Product Categories can be left blank to apply the QCP to every instance of that operation—useful for plant-wide gates, less useful when only a few SKUs need inspection.

The Control per field determines when a check is created: Operation (one check for the whole operation), Product (one check per unique product on the order—for example a delivery of one table and four chairs yields two checks), or Quantity (a check for a percentage of items via a Partial Test value; 100% creates one check for the full quantity). Control Frequency then sets how often those conditions fire: All, Randomly (a configured % of the time), Periodically (every N days/weeks/months), or On-Demand (manual request only).

• →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 (also unlocks Failure Locations).
• →Path in UI: Quality → Quality Control → Control Points.

Quality check types: when to use each one

Once a QCP fires, it generates a quality check of a specific type. Match the type to the work being done: binary visual decisions, numeric tolerances, photo evidence, production accounting, or structured worksheets. 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 workhorse quantitative type: set a Norm value plus a Tolerance (optionally a Device), 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 into the MO’s material and output accounting. Take a Picture stores photographic evidence for later review. Spreadsheet and Worksheet types validate against a Success cell or Success Conditions on a template.

For QCPs whose Type is Register Production, Pass-Fail, Measure, Spreadsheet, or Worksheet, the Message If Failure tab appears—use it to tell the operator to raise a quality alert, scrap, or rework when the check fails.

• →Instructions: a procedural step attached to a work order (or other operations if created manually as a QCP).
• →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.

Why Quantity checks are blocked on manufacturing orders

A common stumbling block in Odoo quality control is the Quantity control-per / quantity-oriented check pattern on manufacturing. Odoo deliberately restricts quantity-based quality checks for manufacturing operations. The Quantity pattern is designed for transfer-based operations (receipts, deliveries, internal moves) where the operator records “I’m moving X units—do they pass?” against a fixed expected quantity from the source document (stock.move product quantity).

Manufacturing orders work differently: produced quantity is the output of the operation, not a pre-validated input. By the time a check runs at a work order, quantity is either already implied by the MO or still being recorded as actual production—so a “quantity check” on an MO is ambiguous. Odoo forces Measure or Pass-Fail (and related types) instead for manufacturing contexts.

Practical workarounds that cover almost every SME case: (1) Use Measure with Norm and Tolerance when you need “we should produce 100 ± 2 units” or any numeric gate. (2) Put a Quantity-capable QCP on the component consumption picking or finished-goods receipt-into-stock transfer, not on the manufacturing operation itself. (3) Reserve custom overrides only if you truly need Quantity semantics at the work-order level—and accept upgrade fragility. For 99% of “quantity check on manufacturing” requests, Measure with tolerance is the supported pattern.

• →Quantity-style checks fit receipts, deliveries, and internal transfers with a fixed expected move quantity.
• →On MOs, prefer Measure (Norm + Tolerance) or Pass-Fail for unambiguous semantics.
• →For component or finished-goods count gates, attach the QCP to the related stock picking, not the manufacturing operation type.
• →Custom overrides of the quality-point consistency validator are possible but upgrade-sensitive.

Quality checks: the execution layer

Odoo quality checks are manual inspections conducted by employees. Most 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 a one-off inspection.

Each check carries Pass and Fail controls 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 batch, work center, and operator—essential for later corrective action and vendor scorecards. Odoo’s product positioning emphasizes order integration: complete checks without leaving the manufacturing or inventory document.

One important limit: quality checks for specific work order operations can only be created by a QCP. You cannot 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. Granular inspections can target an entire MO or one work order step depending on how the QCP’s Operations and Work Order Operation fields are set.

Failure locations: quarantine rejected stock

Catching a defect only helps if rejected product cannot be picked for a customer. Odoo’s Failure Locations feature (added in Odoo 17) lets a QCP name one or more inventory locations where failed units are sent. The feature appears when Control per is set to Quantity on the QCP—quantity-based transfer checks are the path that unlocks Failure Locations.

Prerequisites: enable Storage Locations under Inventory → Configuration → Settings so you can create sub-locations (for example WH/Quality-Fail or WH/Quarantine). Failure locations work best for storable products, because Odoo tracks on-hand quantities for storables; consumables can still be sent to a failure location, but exact counts there are not inventory-tracked the same way.

On a receipt (or other transfer) with a quantity-based QCP, open Quality Checks, Fail the check, enter Quantity Failed and Failure Location, Confirm, then Validate the transfer. Passed units go to normal storage; failed units go to the failure location. From Inventory → Configuration → Locations → select the failure location → Current Stock, you can see what is parked. Treat quarantine as an internal location under review—not Virtual/Scrap—until disposition (rework, return-to-vendor, or scrap) is decided, so valuation and on-hand reporting stay honest.

1. 01
   Enable storage locations

   Inventory → Configuration → Settings → Storage Locations, then create a failure or quarantine child location under the warehouse.

2. 02
   Set Control per to Quantity on the QCP

   Only Quantity control-per exposes Failure Locations on the control point form; select one or more locations.

3. 03
   Fail the check and route stock

   On the transfer, process the quality check, enter Quantity Failed, choose Failure Location, Confirm, then Validate so failed and passed quantities split correctly.

4. 04
   Disposition the quarantine

   Rework via manufacturing, return to vendor, or scrap—do not leave rejected stock in a sellable location or forget disposition indefinitely.

Quality alerts: CAPA from fail to fix

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 (when a check has been requested for the MO), from an inventory order, from a work order in Shop Floor (⋮ menu → Create a Quality Alert), or directly in Quality → Quality Control → Quality Alerts.

An alert carries the context the team needs: Title, Product / Product Variant, Work Center, Picking, Responsible Team and employee, Tags, Root Cause, and a one-to-three-star Priority. Tabs cover Description, Corrective Actions, Preventive Actions, and Miscellaneous (Vendor, Company, Date Assigned). Alerts live on a Kanban board by review stage so the team can triage, assign CAPA, and close the loop. Root Cause tags turn one-off fires into trends—recurring supplier or process issues become visible.

Concrete SME example — incoming inspection fail on a purchase receipt: A metal-fab shop receives 200 brackets on a PO. A QCP on Receipts (Control per Quantity, Partial Test 10%, Pass-Fail or Measure) creates a check. The inspector fails 20 units for out-of-tolerance hole diameter, routes them to WH/Quality-Fail via Failure Location, validates the receipt so 180 units enter sellable stock, and raises a quality alert linked to the picking with Root Cause “Vendor dimensional variance,” Priority two stars, Vendor set on the Miscellaneous tab. Corrective Actions: quarantine hold + RMA request for the 20 units. Preventive Actions: tighten supplier AQL, add Measure QCP Norm/Tolerance for the next three lots, and tag Purchasing for scorecard review. The Kanban card moves from New → Confirmed → Corrective Action → Done once the RMA closes and the Measure QCP is live—scrap/rework inventory and CAPA stay on the same database as MRP and purchasing.

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
   Close inventory disposition

   Align scrap, rework, or return-to-vendor moves with the alert so financial inventory and quality status do not diverge.

6. 06
   Move the alert through review stages

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

A typical SME quality setup in Odoo

For a small or mid-sized manufacturer, start with three inspection moments without over-engineering. First, one QCP per critical work-center operation (for example Assembly on a Coffee Table) at All frequency with Pass-Fail or Measure. That guarantees every unit passes the critical step before it moves on—and avoids the Quantity-on-MO trap by using Measure for numeric gates.

Second, a Receipts QCP for incoming-goods inspection. Use Periodically or Randomly for stable suppliers and All or high Partial Test sampling for new or high-risk vendors. Prefer Control per Quantity on receipts when you need Failure Locations and partial-lot quarantine. Third, a Delivery QCP on critical outbound SKUs (Pass-Fail or Picture) so bad packaging never ships.

Fourth, encourage operators to raise quality alerts early with Root Cause and Vendor tags, and review the Kanban weekly. Aggregated root causes surface recurring supplier defects or worn tooling before customer returns. Practitioners consistently describe quality as a full workflow—inspect, verify defects, trend performance—not a standalone checklist; linking QC to MRP inventory and job costing is what makes the ERP-native approach worth it versus spreadsheets.

• →One QCP per critical work-center operation at All frequency with Pass-Fail or Measure.
• →Receipts QCPs with Quantity control-per when you need failure-location quarantine.
• →Delivery QCPs on money or regulated SKUs before ship.
• →Quality alerts with Root Cause and Vendor tags to surface recurring defects.
• →Work-order checks executed in the Shop Floor module where operators actually work.
• →Optional adjacency: Maintenance/TPM for equipment-driven quality issues; PLM when product design changes are the fix.

The Dynamics 365 equivalent: Quality and nonconformance management

If you are comparing platforms, the Dynamics 365 Supply Chain Management equivalent is Quality and nonconformance management under Inventory management. The conceptual shape is the same—trigger rules generate an inspection, and exceptions are tracked separately—but the configuration surface is 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 Quality management for warehouse processes for advanced warehouse flows. Odoo’s Failure Locations cover a lighter quarantine path on quantity-based QCPs without the full nonconformance cost model.

• →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—typically part of Odoo Enterprise manufacturing stacks—with QCPs, checks, and alerts in one place. It suits SMEs that want quality inspection embedded in 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.

Frequently asked questions