Not answered here? Email support@ventor.tech — or read the documentation.
Neither — one machine is enough, as long as it can see all the printers you need. We recommend a dedicated PC for the job; a Raspberry Pi is plenty, and that is what we run in our own office.
It doesn't matter whether the printers are on a local or an external network. If the Direct Print Client can see them, you can print to them.
Odoo Online is the one exception. The version Odoo hosts for you at odoo.com does not allow third-party modules to be installed, and Odoo Direct Print PRO is a module — so it cannot run there. That is a platform restriction, not something we can work around.
Everything else is fine: Odoo.sh, on-premise, Docker, Kubernetes, or any external host — as long as your Odoo server has internet access. Moving from Odoo Online to Odoo.sh is the usual route, and Odoo can migrate the database for you.
No VPN is needed. You install the Direct Print Client on any local machine on the same network as the printers. CUPS is only involved if that machine runs Linux.
It is usually one of two things:
To tell which, download the document as a file — via the Download dropdown, or from the attachments — and send that file directly to the printer from your computer, bypassing Odoo entirely. If it still prints wrong, the file is wrong and the ZPL needs fixing. ZPL is a programming language, and a stray symbol can throw off even a calibrated printer badly enough that it needs calibrating again.
Yes — printing itself. Direct Print is built on PrintNode, a paid cloud printing service with a monthly subscription.
What we add is that the setup is done for you, rather than being the long manual process it otherwise is. Our prices for printing match PrintNode's own, and we are the only officially recognised Odoo integration by PrintNode.
They pay for different things. The subscription pays for printing. A web application cannot send a document to a local printer without a relay service in between — that is a limitation of the printing protocol, and it applies to any web software, not just Odoo. Services like PrintNode exist to solve it, and most of what you pay us for printing goes straight to PrintNode.
The module payment funds the module: its development, its support, and its release for each new Odoo version. The changelog on the App Store shows what that buys — we release improvements most months.
Yes. Email support@ventor.tech and we will get back to you.
We can help with the desktop client itself too, as long as you subscribe through us. If you have a subscription directly with printnode.com, their support handles client questions.
You buy a separate module for each new Odoo version. That is the official Odoo Apps policy, not ours — the sales conditions are here.
Your printing subscription carries over unchanged. See Get Started for the upgrade path.
Odoo have confirmed to us that the App Store has no way to notify you automatically about new module versions, so for now you have to check manually.
We plan to build release notifications into the module itself. In the meantime, our newsletter and YouTube channel carry the announcements.
From the Odoo App Store, signed in as the account that made the purchase. Find the module for the Odoo version you bought, and you can always download the current release.
Yes — and in most cases your developers will not need us. If we do not already have a print scenario that fits, the module is built to be easy to call directly.
First, get the current user's printer and tray. Without a printer defined for the user there is nothing to print to:
user = self.env.user
printer_id, printer_bin = user.get_report_printer(report.id)Then print:
options = {'bin': printer_bin} if printer_bin else {}
printer_id.printnode_print(
report,
objects,
copies=1,
options=options,
)report — an ir.actions.report record: the report you want printed.objects — the records to print that report for. A list of invoices, sales orders, or whatever the report is about.copies — how many copies to print.