Barcode Stock Quality
Run a reception’s quality control inspections directly from the Barcode app.
When a reception (incoming picking) generates quality inspections through quality_control_stock_oca (from the operation type and product quality triggers), this module surfaces them as a Quality tab inside the reception screen. The operator answers each check — picking a value for qualitative checks, entering a measure for quantitative ones — and confirms; when an inspection does not pass, a photo can be attached to it as evidence.
This is a feature module on top of barcode_stock: it adds the Quality tab by extending the reception screen, without modifying barcode_stock itself.
Table of contents
Usage
Configure which quality tests apply to which products for receptions: on the incoming operation type’s quality trigger (created by quality_control_stock_oca), add trigger lines on the product, its template or its category pointing at the test to run.
Operators run inspections from the scanner with the same rights as in the back office: they need to be Quality Control users. Others see the Quality tab tell them so.
In the Barcode app, open a reception. If it has quality inspections, a Quality tab appears; answer each check and confirm.
Every question needs its answer; a measure left blank is not taken as 0. When an inspection does not pass, tap Attach photo evidence to add a photo to it (only images are taken).
Answers not confirmed yet are kept while you look at another tab of the reception.
A confirmed inspection shows its answers read-only. If you confirmed it by mistake from the scanner, tap Back to draft: it reopens with its answers filled in, to correct what was wrong and confirm again. This is only offered while no supervisor has decided it — a rejection (Failed) is theirs — and the reception is still open; an inspection confirmed in the back office is not reopened from the scanner.
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
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.
Current maintainer:
This module is part of the OCA/barcode-interface 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-barcode-stock-quality 18.0.1.0.0.4
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 | Reset |
|---|---|---|---|---|
| odoo_addon_barcode_stock_quality-18.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_barcode_stock_quality-18.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_barcode_stock_quality-18.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 46.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9816698785cc075cf065bbda3633e2fcd74b12108cf8330b662bbb0b1931f0e
|
|
BLAKE2b-256 checksum How to use checksums |
0d55cad24d35726af03ce77993790695c6f131344f194b99bde3afc6231c1f9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-barcode-stock-quality 18.0.1.0.0.4
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.
