Most teams running Odoo hit the same wall the moment they need labels that actually match their operation. Odoo core can print a stock barcode from a product form and ships a couple of generic PDF label templates, but the second you need your own dimensions, brand marks, multi-language descriptors, batch/lot and expiry fields, GS1-encoded barcodes, or a specific thermal label-stock layout, the built-in options run out of road. Warehouse staff end up exporting to spreadsheets and pasting into a third-party design tool, mislabelled stock creeps in, and every label change becomes a manual re-print job that nobody owns. That fragmentation is exactly what this build-to-order module removes.

We build a dedicated labels engine as a proper Odoo module (__manifest__.py declaring dependencies on stock, product, and barcodes) that lives inside your database and reads directly from product.template, product.product, stock.lot, and stock.quant. The core is a label.template model (models.Model) that stores your physical label geometry — width, height, margins, columns per sheet or roll pitch — bound to a designer of field-driven label elements. Barcodes render server-side (EAN-13, UPC-A, Code128, QR, or GS1-128 application identifiers for lot and expiry) so scans are reliable at receipt, pick, and pack. Computed fields (@api.depends) derive human-readable descriptors, unit-of-measure suffixes, formatted prices, and multi-currency or multi-language variants, so a single template drives correct output across your whole catalogue.

Printing is delivered through QWeb report actions that emit either a paginated PDF for sheet labels (Avery-style grids) or a label-per-record stream sized for thermal roll printers, with optional ZPL/EPL output for direct-to-printer workflows. Users trigger printing from the product list, a stock.picking receipt, an inventory adjustment, or a batch wizard (TransientModel) that selects a template, quantity per product, and starting cell offset so partial label sheets are never wasted. Where your process demands it, we wire automated actions (base.automation) so labels queue automatically on events such as goods-in validation or a new lot being created, and we expose the same generation via the XML-RPC/JSON-RPC API so an external WMS, scale, or print server can request labels programmatically. Access is scoped with ir.model.access.csv and record rules so only the right warehouse teams manage templates versus simply printing them.

Because this is a build-to-order engagement, nothing ships as a shrink-wrapped download. After a short scoping call we confirm your exact label stock, printer models, barcode symbologies, field mapping, and Community-versus-Enterprise target, then build and test your version against Odoo 17.0, 18.0, or 19.0. You get the installable source, staging UAT, and a rollback plan before anything touches production. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company deployments, additional printer or ZPL/label-stock variants, deeper localization (multi-language and regulatory GS1 fields), and larger data-migration volume increase the quoted scope.