This module defines triggers that creates inspections when stock moves are done.
It also adds some shortcuts on picking and lots to these inspections.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically creates quality control inspections from stock transfers and lots, and adds shortcut buttons on pickings and lots to see how many inspections were created, done, passed or failed.
This module links the Quality Control app with Inventory. When a stock transfer is confirmed, the system looks for quality control triggers configured for that operation type and creates the matching inspections, either before the transfer is processed or planned ahead.
- On a transfer (picking) you get a set of buttons showing the number of inspections created, done, passed and failed; each button opens the corresponding list of inspections.
- The same counters and shortcuts are added on lot/serial number records.
- Inspections can now be linked to a transfer, a stock move or a lot/serial number, and the product, quantity and lot are filled in automatically from the stock move.
- A trigger can be limited to a specific operation type, and you can ask for one inspection per lot/serial number used in the transfer.
- When a transfer is validated, planned inspections become ready and inspections for the 'after' timing are created; when a transfer is cancelled, planned inspections are cancelled too.
- Changing the date of a stock move updates the date of its existing inspections.
It touches qc.inspection, qc.inspection.line, qc.trigger, stock.move, stock.picking, stock.picking.type and stock.lot.
Depends on
Required by other modules
Models and fields (7)
- stock.lot · extends an existing modeldone_inspections (Done inspections), failed_inspections (Inspections failed), passed_inspections (Inspections OK), qc_inspections_ids (Inspections), created_inspections (Created inspections)
- qc.trigger · extends an existing modelpicking_type_id, inspection_per_lot
- stock.move · extends an existing model
- qc.inspection · extends an existing modellot_id, picking_id, picking_origin (Picking Source Document)
- stock.picking · extends an existing modeldone_inspections (Done inspections), failed_inspections (Inspections failed), passed_inspections (Inspections OK), qc_inspections_ids (Inspections), created_inspections (Created inspections)
- qc.inspection.line · extends an existing modellot_id, picking_id
- stock.picking.type · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/manufacture.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0Configure a QC trigger in the product, product template, or product category to define the conditions for creating inspections:
- Trigger: Choose the trigger to activate the inspection process.
- Test: Define a group of questions with valid values for the inspection.
- Responsible: Assign a user responsible for the QC inspection.
- Partner: Optionally specify partners to limit the test to actions involving them.
- Timing: Determine when inspections are generated:
- Before: On picking confirmation.
- After: On picking completion.
- Plan Ahead: On picking confirmation, generating a non-editable plan inspection that becomes executable post-picking completion.
To create a quality inspection for each lot/serial number used in a stock move you need to:
- Go to Quality Control> Configuration > Triggers.
- Activate the "Inspection Per Lot" option in those triggers which need to force a different inspection for each lot/serial number used in a stock picking.
No verified information in OCA: Installation, Usage.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.