OdooWiki OCA HUB

Lot Barcode on the Production Order

mrp_order_report_lot_barcode folder_open OCA/manufacture-reporting open_in_new
Manufacturing License: AGPL-3

Lot Barcode on the Production Order

auto_awesome What this module does

AI-generated from the code · Odoo 16.0

Adds a Lot Barcode column to the Manufacturing Order components report, showing a scannable barcode and the lot/serial number for each raw material consumed.

This module customises the printed Manufacturing Order report (the components section) so that warehouse and production staff can scan lot or serial numbers directly from the paper document.

  • A new "Lot Barcode" column is added to the components table of the production order report, but only when at least one consumed raw material line actually has a lot or serial number. If no lots are used, the column stays hidden.
  • For every raw material move line that has a lot/serial number, the report prints a barcode image followed by the lot/serial number itself, so the same information can be read by eye or scanned.
  • The barcode is generated from the lot/serial number value, with a fixed width and height suitable for the report layout.
  • The change is purely a report template inheritance on mrp.report_mrp_production_components; no new models, menus, buttons, or business rules are introduced.
  • It affects the Manufacturing area only, specifically the printed production order document used on the shop floor.

Depends on

mrp

Text generated by AI (DeepSeek) from reading the Odoo 16.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

Sources · Odoo 16.0

Confirmed on 2026-11-03 in branch 16.0 of OCA/manufacture-reporting.

terminal Installation and usage

No verified information

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.

info

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.