Report to printer - Mail extension
This module disables the print of a report on a selected printer, when the report has been triggered from a mail template.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0When a report is generated from an email template, this module prevents it from being sent to a printer. It only affects automatic report generation triggered by mail templates.
This module adds a safeguard between the email template system and the printer functionality. Normally, when Odoo generates a report, the Report to Printer module can send it to a configured physical printer. However, when that report is generated as part of an email template (for example, to attach a PDF to an automatic email), you usually do not want a paper copy to be printed as well.
With this module installed, any report generated through a mail template is automatically flagged to skip the printer. This happens behind the scenes: the mail template code sets a context flag that tells the printer logic to ignore the report. No new menus, screens, or buttons are added.
- It works with the
mail.templatemodel, which is used for automated emails. - It relies on the
base_report_to_printermodule for the actual printing behaviour. - The module is set to install automatically when both
mailandbase_report_to_printerare present.
This means users who send reports by email will not accidentally trigger a print job on a configured printer. The change is transparent and requires no configuration.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/report-print-send.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.