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.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets warehouse operators run a reception's quality control inspections directly from the Barcode app, answering each check and attaching a photo when a check fails.
This module adds a Quality tab to the reception screen in the Barcode app, for incoming operations only. The tab lists the quality inspections that the reception already generated, showing the test name, the product and the lot or serial number, plus a status badge (Pending, Passed, Failed or To review).
- For each inspection still to be answered, the operator picks one of the offered answers for qualitative questions or types a measured value for quantitative ones. The Confirm inspection button stays disabled until every question has an answer; a blank measure is treated as no answer, not as zero.
- Once confirmed, the answers are shown read-only with a green or red icon per question, and a message tells whether the inspection passed or failed.
- When an inspection is waiting for review or has failed, the operator can attach a photo as evidence. Photos are shrunk and re-encoded before upload, and only image files are accepted; they are stored on the inspection and visible in its chatter.
- An inspection confirmed from the scanner can be put back to draft with a Back to draft button, keeping its answers, but only while no supervisor has decided it and the reception is still open.
Only users in the Quality Control user group can run inspections; others see a message saying so. The module extends stock.picking and qc.inspection and does not change the Barcode app itself.
Depends on
Models and fields (2)
- qc.inspection · extends an existing modelbarcode_scanner_confirmed (Confirmed from the scanner)
- stock.picking · 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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/barcode-interface.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0- 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.
No verified information in OCA: Installation, Configuration.
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.