On a busy shop floor, the label is the last mile of every manufacturing order. Operators finish an mrp.production, then leave Odoo to hand-key SKUs, lot numbers, and quantities into a separate label designer or a spreadsheet that feeds a thermal printer. Odoo core does ship a product-label print action, but it prints from product.template/product.product with a fixed set of QWeb layouts — it has no native awareness of the manufacturing order that just closed. It cannot pull the produced quantity, the assigned stock.lot (production lot/serial), the MO reference, the linked work order, or the finished-goods context onto the label. Teams end up with generic labels, transcription errors, and a printing step that lives outside the ERP the rest of the plant runs on.

We build a productized Odoo module that adds a "Print Labels" action directly on the manufacturing order. The module extends mrp.production with a server action — and, optionally, an automated action wired to the MO's "done" transition — that reads the finished product, the produced quantity, and the lot/serial context, then renders one label per unit (or one per pack, per your rule) through a dedicated QWeb report. Barcodes are generated with Odoo's built-in barcode reporting widget, so the same symbology your stock.picking operations already scan is what prints — Code128, EAN-13, or GS1-128/DataMatrix where your scanners require it. A configurable label.template model lets you set label size, printable fields, and layout per product category, so a raw-material tote label and a finished-goods retail label come off the same MO without operator guesswork.

Technically, the work is a clean, upgrade-safe module: a __manifest__.py declaring mrp and product as dependencies, ORM models with compute/@api.depends fields for the derived label data (barcode payload, human-readable batch string, print quantity), QWeb report templates and paperformat records sized for your label stock, XML/OWL view extensions to surface the action button and the per-template configuration, and access control via ir.model.access.csv plus record rules so only Manufacturing users can print and only within their allowed companies. Where you want unattended printing, we expose the same routine over the XML-RPC/JSON-RPC API so an external print controller or a station PC can trigger a batch reprint. It runs on Odoo Community and Enterprise; if you are on Enterprise we can also hand the label payload to the native report/printer proxy, and we note any Community-vs-Enterprise differences during scoping.

Because this is build-to-order, delivery follows a short, defined path: a scoping call to lock the label templates, symbologies, and print triggers; a fixed quote; a build on a staging branch matching your Odoo version (17.0, 18.0, or 19.0); UAT on your data with real MOs and your actual label printer; then production install and a support window. Typical delivery is 2–4 weeks from confirmed scope, depending on how many label variants and print triggers you need. Pricing starts from $249 (indicative, single-company base scope); multi-company printing rules, additional label templates per product category, GS1/DataMatrix compliance work, and physical printer/label-stock integration increase the quoted scope.