Warehouse and shop-floor teams lose real minutes on every label. Odoo's stock and product labels ship as QWeb/PDF reports: an operator clicks Print, the browser downloads a PDF, they open it, choose the right printer, fight the scaling dialog, and only then does a label emerge — often shifted a few millimetres off the die-cut because a raster PDF was rasterized again by the printer driver. At scale — hundreds of putaway, pick, pack, or GS1 shipping labels a day — that click-download-open-print loop is both slow and error-prone, and it leaves label quality at the mercy of whatever driver is installed on each workstation. Odoo core has no concept of speaking a thermal printer's native page-description language, so barcodes drift, text blurs at 203/300 dpi, and there is no clean way to fire a label from an automated action or an external system.

Product Label & ZPL Report Direct Print is the module we build to close that gap. Instead of a PDF report, we author your labels as native ZPL (Zebra Programming Language) templates rendered through a QWeb-driven text report, so the printer receives crisp vector text, native ^BC/^BQ barcodes (Code128, GS1-128, QR, DataMatrix), and pixel-exact positioning at the printer's true dpi. The module adds a zpl.printer model (models.Model with fields for host, port, dpi, darkness, and default label size), plus a print-transport layer that sends the generated ZPL directly to the device — raw TCP to the printer's 9100 socket, a CUPS/IPP queue, or a lightweight local print agent for USB-attached units — chosen during scoping to match your network. A compute/@api.depends layer resolves the correct template and printer per product, per operation type, and per warehouse, so a pick label and a shipping label route to the right device automatically.

Technically it is a clean, upgrade-safe addon: a proper __manifest__.py declaring dependencies on stock/product, ZPL templates stored as versioned QWeb views you can edit without touching Python, ir.model.access.csv plus record rules so only warehouse roles manage printers and templates, and OWL/XML views that add a "Print to Zebra" action on products, stock moves, transfers, and lots/serials. Because printing is exposed as a server-callable method, we can wire it into Odoo automated actions (label on validation of a receipt), scheduled actions, or trigger it over the external XML-RPC/JSON-RPC API from a WMS, scale, or conveyor controller. It respects multi-company and multi-warehouse boundaries, logs every print for traceability, and degrades gracefully — if a printer is unreachable the job is queued and surfaced, never silently lost. It runs on Odoo Community and Enterprise alike; where Enterprise-only models are in play (e.g. certain barcode-app flows) we adapt the integration to your edition during scoping, and we deliver against Odoo 17.0, 18.0, or 19.0.

Because this is made to order, nothing is downloaded from an app store and installed blind. We start with a short scoping call, confirm your printer models, label stock, dpi, and the exact operations that need labels, then build and test against a staging copy of your database. Typical delivery is one working week from confirmed scope, followed by UAT sign-off, production install, and a support window. Pricing starts from $999 (indicative, single-company base scope); additional printer families, multi-company or multi-warehouse routing, GS1/regulatory label layouts, and integration with external systems over the RPC API increase the quoted scope. You receive a fixed quote after the scoping call.