Warehouse and retail teams running Odoo constantly hit the same wall at print time: the stock label is a fixed layout. The built-in product barcode and reception labels print a barcode and a name, but the moment you need a QR code that encodes a lot number, a shelf-life date pulled from expiration_date, a variant attribute value, a two-currency price, a supplier reference, or your own GS1 Application Identifiers, Odoo native runs out of road. Teams end up exporting to a spreadsheet, hand-designing labels in a third-party tool, and re-printing whenever a field changes — which breaks traceability and wastes hours every week. Community edition compounds this because some label and report tooling differs from Enterprise, so what a colleague demoed may not exist on your build at all.

Dynamic Product Labels is a build-to-order Odoo module that ECOSIRE designs and develops specifically for your data model. At its core it adds a label.template model (with label.template.line element rows) that lets you compose a label from any field reachable from product.product, product.template, stock.lot, or stock.quant — including related and @api.depends computed fields you already maintain. Each placed element is a text block, a 1D barcode (Code128, EAN-13, UPC-A, ITF-14), or a 2D code (QR or DataMatrix), and its content is a safe evaluated expression such as object.lot_id.name or a formatted price, so a label always reflects the live record. Rendering is a QWeb report (ir.actions.report) at an exact physical size in millimetres, so output lands on your Zebra/Brother/Dymo stock without manual scaling.

Technically, the build stays inside Odoo conventions so your team can own it afterwards. Barcodes and QR codes reuse Odoo's own /report/barcode/ image controller (backed by python-barcode/qrcode) rather than a bundled binary, security is enforced through ir.model.access.csv plus record rules so warehouse users can print but only managers edit templates, and a Print Labels action is wired onto the relevant list/form views via XML so it appears exactly where operators expect it. Optional automation — an ir.actions.server or automated action that auto-prints a label when a lot is created or a transfer is validated — is scoped per project. Everything is exposed over the standard XML-RPC/JSON-RPC API, so an external scale, WMS, or line printer can trigger a label render programmatically.

Because this is made to order, delivery is a short collaboration rather than a download. After a scoping call we confirm exact fields, label dimensions, symbologies, and printer models, then build against your Odoo 17.0, 18.0, or 19.0 (Community or Enterprise) database, validate on a staging copy through UAT, and deploy with a rollback plan. Pricing starts from $999 (indicative, single-company base scope); the number of distinct label templates, symbology and localization depth (GS1 AIs, RTL/CJK text, multi-currency pricing), auto-print automation, and multi-company or multi-warehouse rollout increase the quoted scope. You receive the final fixed quote after the scoping call, never a surprise on delivery.