Silent Direct Printing

Key Features

Cross-platform local print agent (Python/Node helper) that bridges Odoo to OS printers over a secured WebSocket/HTTP channel with token authentication

Silent raw printing of any QWeb/PDF Odoo report to a chosen printer with zero browser print dialog and no user interaction

Native ZPL (Zebra) raw-command passthrough for pixel-perfect barcodes, lot and package labels at the printer's native resolution

ESC/POS thermal-receipt raw-command passthrough for kitchen tickets and customer receipts, bypassing PDF rasterization

Per-user, per-company and per-warehouse default-printer resolution computed automatically at print time via @api.depends fields

Automated-action auto-print rules (base.automation) firing on sale.order confirm, stock.picking validate, account.move post and mrp.production done

Multi-target routing so a single action sends each report type to the right device (invoice to laser, product label to Zebra)

Print queue with per-job status, configurable automatic retry, and full error logging on a dedicated model

Printer pools with offline detection and fallback routing to a designated backup device

Label-quantity rules to print N labels per product, lot, package or delivery line automatically

Test-print and printer-diagnostics wizard to validate connectivity, driver and output on each configured device

POS integration for hands-free kitchen and customer receipt printing on point_of_sale sessions

Agent heartbeat monitoring with auto-reconnect for multi-printer, multi-location deployments

XML-RPC / JSON-RPC endpoints so external systems and scripts can trigger direct prints programmatically

ir.model.access.csv plus record rules so each site, company or warehouse sees and controls only its own printers and jobs

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2–4 weeks from confirmed scope, and you receive the full source, a UAT pass on staging, and a support window after go-live. Pricing starts from $499 (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.

What you get

Installable Odoo module source code for your version (17.0, 18.0 or 19.0) plus the cross-platform local print agent

Installation and configuration on your environment: printers, agents, per-station default mappings and auto-print rules

Technical documentation: models, security model, agent protocol, configuration reference and troubleshooting guide

User guide plus a live training session for operators and administrators

Post-go-live support window for defect fixes and configuration adjustments

UAT on a staging database with a documented rollback plan before production cutover

Git repository handover with full commit history and versioned releases

Printer-diagnostics runbook and heartbeat-monitoring setup for ongoing operational visibility

Who this is for

Warehouse Operations Manager

Runs high-volume picking, packing and shipping-label workflows across many stations. Needs picking slips and carrier labels to fire automatically on validation to the correct Zebra beside each bench — no dialog, no wrong-tray reprints, no operators clicking through print menus all shift.

Retail / POS Manager

Manages multi-lane stores or counters on point_of_sale. Needs customer receipts and kitchen tickets to print silently and reliably to the right thermal device per lane, with offline fallback so a jammed or dropped printer never stalls a sale.

Manufacturing Plant Supervisor

Oversees shop-floor work orders and product/lot labeling. Needs labels to print in the correct quantity per lot or production line the moment an MO completes, in native ZPL for scannable, compliant barcodes at speed.

IT / ERP Administrator

Owns the Odoo deployment and workstation fleet. Wants an upgrade-safe module with clean security rules, a queue with retry and error logging, agent heartbeat monitoring, and API-driven triggers rather than brittle browser hacks or manual per-machine driver juggling.

How Silent Direct Printing Compares

Criterion	ECOSIRE	Custom Build	Competitor	Odoo Native
Delivery model	Build-to-order for your exact stack, 2–4 weeks from confirmed scope	In-house build; timeline depends on your team's bandwidth	Instant download, generic to all installs	Already in core, nothing to install
Browser print dialog	Eliminated via local agent; fully silent printing	Achievable but you build the agent and channel yourself	Usually removed, but only for the vendor's fixed flows	Always present; every print needs a manual dialog
Native ZPL / ESC-POS output	Raw command passthrough tuned to your label and receipt hardware	Possible; you handle every printer language and edge case	Often supported for common models, limited customization	None; only rasterized PDF via the OS driver
Auto-print on record events	base.automation rules on SO confirm, picking validate, invoice post, MO done	You design and maintain each automated action	Fixed set of triggers, hard to extend	Not available; printing is always manual
Per-user / company / warehouse routing	Default-printer mapping resolved automatically per station and report type	Build your own resolution logic and models	Basic per-user defaults, limited multi-site depth	None; user picks the printer every time
Queue, retry and fallback	Tracked queue with retry, error logging, printer pools and offline fallback	You implement the queue and monitoring stack	Varies; often basic status with limited fallback	No queue; a failed print is simply lost
Source code and lock-in	Full source plus git repository handover, no lock-in	You own it entirely by definition	Often obfuscated or license-gated; no repo handover	Core source, but no direct-print capability to own
Odoo version and edition fit	Built and tested against your 17/18/19, Community or Enterprise	Whatever you target and maintain yourself	Per-version listings; upgrades depend on the vendor	Ships with every version but lacks the feature

Frequently Asked Questions about Silent Direct Printing

How long does delivery take?

Because Silent Direct Printing is build-to-order, we build it for your specific stack rather than shipping a generic download. Typical delivery is 2–4 weeks from confirmed scope, depending on the number of printer protocols, stations, warehouses and auto-print events involved. The scoping call establishes the exact timeline before any work begins.

Is this an instant download from the App Store?

No. This is a productized service, not an existing off-the-shelf listing. ECOSIRE scopes, builds, installs and supports the module for your environment. You receive the full source and a git repository handover on delivery, but the code is written and tested against your Odoo version and hardware first.

How does pricing and scoping work?

Pricing starts from $499 (indicative, single-company base scope). Drivers such as multi-company or multi-warehouse rollouts, additional printer protocols, POS lanes, or bespoke report-routing rules increase the quoted scope. We give a fixed quote after a short scoping call — the from-price is an anchor, not the final number.

Which Odoo versions and editions are supported?

We build against Odoo 17.0, 18.0 or 19.0, on Community or Enterprise. POS receipt and kitchen printing is included where you run point_of_sale. We confirm your exact version, edition and hosting (Odoo.sh, on-prem or self-managed) during scoping so the module and agent are built to match.

How does the silent printing actually work without a print dialog?

A small local print agent (Python/Node) runs on each workstation or print server and holds a secured WebSocket/HTTP connection to Odoo. When a report is triggered, Odoo streams the rendered PDF — or a raw ZPL/ESC/POS command stream — to the agent, which sends it directly to the target OS printer. Nothing passes through the browser print dialog, so no operator interaction is required.

What happens if a printer is offline or a job fails?

Every print is a tracked queue job with status and full error logging. Failed jobs retry automatically per your configured policy, and printer pools route to a designated backup device when the primary is offline. Agent heartbeat monitoring flags disconnected stations so issues surface before they stall the floor.

What kind of support and updates do we get after go-live?

Delivery includes a post-go-live support window for defect fixes and configuration adjustments, plus documentation and a training session. Because you receive the full source and git repository, you are never locked in. Longer-term maintenance, new auto-print rules, or a version upgrade (for example moving to Odoo 19.0) can be arranged as a follow-on engagement.