Odoo ships one default invoice QWeb report, and every finance team eventually hits its ceiling. You need a second logo block for a subsidiary, a bank-details footer that changes per company, an itemized tax breakdown a regulator expects, a "Proforma" watermark on draft documents, or column widths that stop wrapping your product descriptions. Out of the box each of those means editing the account.report_invoice_document template, forking QWeb, or overriding CSS in a way that breaks on the next -u upgrade. Teams end up with brittle low-code tweaks, a developer ticket for every layout change, and inconsistent PDFs across companies. This is where Odoo native runs out of road: it gives you the report engine, but not a governed, reusable way for non-developers to shape what the invoice actually looks like.

The Invoice Format Editor is a build-to-order module ECOSIRE designs around your document standards. Technically it adds a configuration layer on top of Odoo's QWeb reporting rather than replacing it. We introduce a models.Model (for example invoice.format.profile) holding the layout options you care about — header and footer blocks, column visibility and order, font and spacing tokens, tax-summary style, per-company branding, and watermark rules for draft versus posted states — with typed fields, @api.depends compute methods for derived display values, and sane defaults. A thin QWeb template inherits account.report_invoice_document and reads the active profile at render time, so account.move records print through your chosen format with no per-invoice hand-editing. Settings live behind a clean form view (XML, with OWL widgets where an interactive preview helps), and access is scoped with ir.model.access.csv plus record rules so only Accounting managers can change formats while everyone else simply prints.

Because the module is data-driven, format changes become configuration instead of code. A new document type or a subsidiary that needs a different footer is a new profile, not a new fork. We can wire ir.actions.report variants (Invoice, Proforma, Credit Note) to distinct profiles, expose the resolved format over the XML-RPC/JSON-RPC API for downstream document systems, and trigger profile selection automatically via server actions or automated actions based on journal, company, or partner. Everything is built to survive upgrades: inheritance over template replacement, no monkey-patching of core, and a __manifest__.py that pins clean dependencies on account and web. We build for Community or Enterprise and target Odoo 17.0, 18.0, or 19.0 to match your environment.

Delivery is genuinely made-to-order. We start with a short scoping call, confirm your exact layout requirements, sample invoices, company structure, and Odoo version, then send a fixed quotation for the agreed scope. From confirmed scope, typical delivery is one working week: we build on a branch, hand you a staging build for UAT, iterate on the real PDFs, then install to production with a rollback plan. There is no instant download — this is software we write, test, and support for your specific setup. Pricing starts from $999 (indicative, single-company base scope); multi-company branding, regulator-specific tax layouts, additional document types, and localization depth increase the quoted scope.