High-volume warehouse, retail and manufacturing teams lose real time to the browser print dialog. Every picking slip, shipping label and receipt means a click, a printer picker, and often the wrong tray or the wrong device — multiplied across dozens of stations and thousands of documents a day. Odoo out of the box hands PDFs to the browser and stops there: QWeb renders a beautiful report, but the operating system print dialog owns everything after that. There is no native way to force a specific stock.picking label to the Zebra beside the pack bench, silently, without a human touching the mouse. Native report_download and IoT-style bridges get you partway, but pixel-perfect ZPL, per-station defaults and event-driven auto-print are exactly where core runs out of road.

Silent Direct Printing is the module we build to close that gap for your environment. It pairs a cross-platform local print agent (a small Python/Node helper installed on each workstation or print server) with an Odoo-side app that talks to it over a secured WebSocket/HTTP channel. When a report is triggered, Odoo streams the rendered PDF — or a native command stream — to the agent, which pushes it straight to the chosen OS printer with no dialog and no user interaction. For thermal and label hardware we bypass the PDF path entirely: the agent passes raw ZPL (Zebra) and ESC/POS command streams through untouched, so barcodes, lot labels and receipts come out pixel-perfect at the printer's native resolution instead of being rasterized. On the Odoo side this is standard, upgrade-safe engineering: new models.Model records for printers, agents, mappings and queue jobs; compute/@api.depends fields to resolve the right device per user, company and warehouse at print time; ir.model.access.csv plus record rules so each site only sees its own hardware; OWL/XML config views and a diagnostics wizard; and Odoo base.automation (automated actions) wired to sale.order confirmation, stock.picking validation, account.move posting and mrp.production completion so the correct documents fire themselves. A print queue tracks every job with status, automatic retry, printer pools with offline fallback, and full error logging, and everything is exposed over the standard XML-RPC/JSON-RPC API for external triggers.

Because this is build-to-order, nothing ships as an anonymous download. We start with a scoping call to map your printers, stations, warehouses and the exact events that should auto-print, then we build against your Odoo version (17.0, 18.0 or 19.0; Community or Enterprise, with POS receipt/kitchen printing included where you run point_of_sale). Typical delivery is one working week from confirmed scope, and you receive the full source, a UAT pass on staging, and a support window after go-live. Pricing starts from $999 (indicative, single-company base scope); multi-company, multi-warehouse rollouts, additional printer protocols or bespoke report-routing rules increase the quoted scope. The from-price anchors a simple base; your fixed quote is set after the scoping call.