Quality control - Stock (OCA)
This module defines triggers that creates inspections when stock moves are done.
It also adds some shortcuts on picking and lots to these inspections.
Table of contents
Configuration
Configure 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.
Known issues / Roadmap
Put trigger in all languages.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es>
Simone Rubino <simone.rubino@agilebg.com>
Andrii Skrypka <andrijskrypa@ukr.net>
Ignacio José Alés <ignacio.ales@guadaltech.es>
Pimolnat Suntian <pimolnats@ecosoft.co.th>
-
Pedro M. Baeza
Carlos Roca
-
Antoni Marroig <amarroig@apsl.net>
-
Manuel Regidor <manuel.regidor@sygel.es>
-
Aung Ko Ko Lin
Yoshi Tashiro
-
Dante Pereyra <dante.pereyra@solvos.es>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/manufacture project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-quality-control-stock-oca 18.0.1.2.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_quality_control_stock_oca-18.0.1.2.0.5-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_quality_control_stock_oca-18.0.1.2.0.5-py3-none-any.whl |
Release files / odoo_addon_quality_control_stock_oca-18.0.1.2.0.5-py3-none-any.whl
| Download URL | odoo_addon_quality_control_stock_oca-18.0.1.2.0.5-py3-none-any.whl |
|---|---|
| Size | 76.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cab75c35ee128a2f7382eeca4b50768657e2eb561c7b0550ce96549c2777ad7
|
|
BLAKE2b-256 checksum How to use checksums |
76e4119058402e154f585764139210bd1881afd7555695aa6897499fa7914858
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-quality-control-stock-oca 18.0.1.2.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
