OdooWiki OCA HUB

Stay Report Py3o

stay_report_py3o folder_open OCA/vertical-abbey open_in_new
Lodging License: AGPL-3

This module replaces the default Qweb report of the stay module by a Py3o report with a better layout.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

This module changes the stay reports in Odoo so they are generated with Py3o templates instead of the standard Qweb layout, giving a cleaner printed result.

This module does not add new screens or menus. It only changes how five existing stay reports are produced.

  • The stay journal report is now generated from a Py3o template and can combine several records into one document.
  • The meal report is also generated from a Py3o template and can combine several records into one document.
  • The arrival report is generated from a Py3o template.
  • The "to clean" report is generated from a Py3o template.
  • The fire report is generated from a Py3o template.

All five reports are produced as ODT files. The reports keep the same names and are still launched from the same places in Odoo as before; only the underlying report engine and layout change. No new business rules, checks, computed fields, emails or scheduled actions are added by this module. It relies on the Py3o reporting engine and on the stay module, and it touches the report definitions of the stay module (stay.report_stay_journal_print, stay.report_stay_journal_meal, stay.report_stay_journal_arrival, stay.report_stay_toclean, stay.report_stay_fire).

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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 with no information of 9 versions.

Sources · Odoo 14.0

Confirmed on 2026-11-03 in branch 14.0 of OCA/vertical-abbey.

terminal Installation and usage

No verified information

Installation 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.

info

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.