If you’re using the Odoo Direct Print (PRO) module and notice that reports, shipping labels, or other documents are printing twice or more, you’re not alone. This issue can be frustrating, especially when it wastes paper, labels, or leads to confusion during shipping or manufacturing.
Based on real-world support cases, we’ve identified three common reasons why this happens – and how you can fix it.
Multiple Direct Print or PrintNode Client Instances Running
If more than one instance of the Direct Print or PrintNode Client is running on the same computer (often under multiple user accounts), each instance will process the same print job, causing duplicates or even more prints.
Symptoms:
There is only single print job in History (https://print.ventor.tech/history ) but multiple documents printed
Solution:
Check the system task manager and terminate all duplicate client instances.
Restart the PC and ensure only one instance of the PrintNode Client is active.
If using multi-user setups, install the client as a Windows Service.
Odoo Retries Due to Concurrent Update
Odoo performs multiple database operations when you do different actions (e.g. validate transfers or complete manufacturing orders). If another process tries to update the same record at the same time, Odoo throws a ConcurrentUpdate error and automatically retries the entire operation – including the printing logic.
Symptoms:
There is only single print job in History (https://print.ventor.tech/history ), typically for the latest printed copy of document. For example, if there are duplicated shipping labels, there will be print job for the latest shipping label only.
Common causes:
Scheduled automations modifying records during transfer validation
Custom or third-party modules updating fields during delivery or MO processing
How to investigate:
Review Odoo logs at the time of the duplicate print
Look for
ConcurrentUpdateor retried job entries
Solution:
Refactor custom code to avoid conflicting record updates during validations
If you can’t debug it yourself, our support team can assist – see below
Third-Party or Custom Code Triggers Methods Multiple Times
Some custom or third-party modules may be improperly implemented and trigger the same method (e.g. transfer validation) more than once. Since the printing action is bound to these methods, every invocation results in an additional label being printed.
Symptoms:
There are multiple print jobs in Direct Print History page (https://print.ventor.tech/history )
No
ConcurrentUpdatefound in logs, but duplicated jobs still appear
Solution:
Review your code or ask your developer to audit custom modules that extend action which causes duplicated printing (e.g. button_validate).
Disable unverified third-party extensions temporarily to isolate the problem
Not sure if our connector will work for you or you need a demo?
If you’re unsure whether our module is the right fit for your business, don’t hesitate to reach out. Our support team is here to help! We can answer your questions, provide guidance, or even schedule a demo meeting to show you how our connector works in real-time.
Contact us: https://support.ventor.tech/
Useful resources
Ecosystem Marketplace: https://ecosystem.ventor.tech/
YouTube channel:
https://www.youtube.com/@VentorTech