Warehouse teams lose real time at the label printer. When a receipt lands, an internal transfer moves, or a manufacturing order finishes, someone still has to identify each product, figure out how many labels to run, drop in the right barcode, and reprint the ones that came out crooked or unscannable. Odoo core does print product barcode labels from the Products screen and offers basic label formats, but it stops well short of the shop floor: you cannot easily trigger the exact label you need from the stock.picking you are actually processing, the built-in layouts are fixed, and there is no clean way to bind a specific label template to a warehouse, an operation type, a customer, or a product category. Off-the-shelf apps.odoo.com modules narrow the gap but hard-code a template, a paper size, or a symbology that rarely matches the label roll and scanners you already own.

This is a build-to-order module. We design and build a stock.product.label capability around your operations: a QWeb-based label report (label paper, thermal roll, or A4 sheet), a configurable label.template model so layouts are data-driven rather than baked into code, and print actions that fire directly from stock transfers, receipts, delivery orders, internal moves, and manufacturing outputs. Technically it is a proper Odoo addon — a __manifest__.py declaring the report, models extending stock.picking / stock.move / product.product, a compute layer (@api.depends) that resolves quantity-to-print from move lines, lots/serials, or packaging, and QWeb templates that render the barcode via Odoo's barcode widget in your chosen symbology (Code128, EAN-13, GS1-128, QR, or a DataMatrix render where your scanners need it). Security is wired through ir.model.access.csv and, where you run multiple warehouses or companies, record rules so warehouse operators only see and print their own labels. Optional automated actions (base.automation) can queue a label print the moment a transfer is validated, and everything is reachable over the XML-RPC / JSON-RPC API for label kiosks or external print servers.

We build against your real constraints: the physical label dimensions and margins, how many labels per unit versus per lot versus per package, which fields belong on the face (internal reference, sales description, lot/serial, expiry, weight, price, customer part number), and whether print happens per line, per picking, or batched across a wave. Community and Enterprise are both supported — the module targets the standard stock and product models, so it runs on Community; where you are on Enterprise we integrate cleanly with the barcode app and Studio-added fields rather than fighting them. Built and validated for Odoo 17.0, 18.0 and 19.0, pinned to the version you actually run.

Build-to-order delivery works in the open: a short scoping call to confirm label formats, trigger points, symbology and volume, then a fixed written quote and timeline. Typical delivery is 2-4 weeks from confirmed scope, and you receive the installable source, staging UAT with a rollback plan, and a support window after go-live. Pricing starts from $249 (indicative, single-company base scope); multi-warehouse and multi-company record-rule work, extra label templates and symbologies, thermal/print-server integration, and localization depth increase the quoted scope. You get a firm number before any build begins — never a surprise.