Every business that prints invoices, delivery slips, quotations, or purchase orders from Odoo eventually hits the same wall: the standard QWeb report renders the same header, footer, terms block, and signature area on every single page of a multi-page document. You end up with the bank details and full terms and conditions repeated on page 3 of a long invoice, or a "continued overleaf" note you cannot place only where it belongs. Odoo's report layouts and the web.external_layout templates give you a global header and footer, but out of the box there is no per-page conditional — QWeb has no native awareness of which physical page an element is landing on, because pagination happens later in the wkhtmltopdf/report_pdf rendering step, not in the template loop. Teams work around this with brittle CSS page-break hacks that break the moment a line item count changes.

Report QWeb Element Page Visibility is the module we build to give you real, declarative control over where report elements appear. We add a small extension to the QWeb reporting stack so any element in your report templates can carry a visibility rule — show only on the first page, only on the last page, only on a specific page number, or on every page except the first or last. Technically this is delivered through a targeted report.layout/ir.actions.report extension plus a lightweight rendering pass that annotates the generated PDF pages, driven by data attributes you place on the QWeb nodes (for example a t-page-visibility="first|last|nth" convention). Because the logic keys off the actual paginated output rather than guessing in the template, it stays correct whether a document renders as one page or twenty. We wire it cleanly into your existing web.external_layout_standard/_boxed/_bold templates or your custom report views, so your bank-details block lands only on the last page, your signature line prints only where it should, and repeated legal text disappears from the interior pages.

Under the hood we keep everything on standard Odoo foundations: a proper __manifest__.py declaring the web and base dependencies and the QWeb template assets, any configuration surfaced through ir.model fields with ir.model.access.csv entries and record rules so only report designers can edit the rules, and views built in XML/OWL that fit the native Settings and Technical menus. No core files are patched — the behavior is layered through inheritance so your Odoo stays upgrade-safe. The module is built and tested against Odoo 17.0, 18.0, and 19.0, works on both Community and Enterprise (Enterprise's additional report layouts are supported where present), and exposes its configuration over the standard XML-RPC/JSON-RPC API so it can be provisioned or scripted alongside the rest of your deployment.

Because this is a build-to-order engagement, delivery starts with a short scoping call where we confirm which reports need per-page control, your exact page-placement rules, and your target Odoo version and edition. There is no instant download — we build the module to your requirements, test it on a staging copy of your database, run UAT with your team, and then install to production with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional report templates, deep Enterprise layout customization, multi-company placement rules, or bespoke pagination logic beyond the standard first/last/nth cases increase the quoted scope. You receive a firm fixed quote after the scoping call — the from-price is a starting indication, not a final figure.