A build-to-order Odoo module that gives your finance team real control over invoice report layout, branding, and formatting without hard-coding a new template for every variation. ECOSIRE designs, builds, installs, and supports it against your exact Odoo version and document standards. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A build-to-order Odoo module that gives your finance team real control over invoice report layout, branding, and formatting without hard-coding a new template for every variation. ECOSIRE designs, builds, installs, and supports it against your exact Odoo version and document standards.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Odoo.
You go live in about 2–4 weeks, with a post-launch support window.
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 2 to 4 weeks: 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 $299 (indicative, single-company base scope); multi-company branding, regulator-specific tax layouts, additional document types, and localization depth increase the quoted scope.
Owns the look and compliance of outgoing invoices. Needs to change layouts, tax breakdowns, and footers without filing a developer ticket every time, and wants consistency across all companies and document types.
Maintains the instance and dreads upgrades breaking a forked report. Wants customizations delivered as an upgrade-safe module with clean dependencies, access controls, and documentation they can support.
Runs several legal entities in one Odoo database, each needing its own branding, bank details, and regulator-specific invoice format. Needs per-company profiles that resolve automatically at render time.
Runs the business on Odoo and wants professional, on-brand invoices that match customer and regulator expectations, delivered and supported by a partner rather than pieced together from generic tweaks.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Delivery model | Built, installed & supported by us in 2-4 weeks from confirmed scope | In-house dev time, often months and competing with other priorities | Instant download, but you install and adapt it yourself | |
| Upgrade safety | QWeb inheritance, no core patching; upgrade notes provided | Depends entirely on your team's discipline | Varies by vendor; forks may break on major versions | |
| Non-developer control | Format profiles editable from a governed settings form | Whatever you choose to build, if scoped that way | Usually a fixed option set you cannot extend | |
| Multi-company branding | Per-company profiles resolved automatically at render time | Buildable, adds significant effort | Often single-company or limited overrides | |
| Fit to your standards | Designed around your exact layouts, taxes & document types | Fully bespoke if you have the specification and budget | Generic feature set; you bend to its assumptions | |
| Access control | `ir.model.access.csv` + record rules scope who edits formats | Only if you design and implement it | Rarely granular beyond standard report access | |
| Support & accountability | Post-go-live support window, single accountable partner | Owned entirely by your internal team | Best-effort vendor support, variable SLAs | |
| Total cost | Indicative from $299, fixed quote after scoping | Highest — full dev, QA & maintenance on you | Low sticker price, hidden adaptation & upkeep cost |
This is a build-to-order module, not an instant download. After a scoping call to confirm your layout requirements, Odoo version, and company structure, typical delivery is 2 to 4 weeks from confirmed scope. That covers build on a branch, a staging build for your UAT, iteration on the real PDFs, and production install with a rollback plan.
Pricing starts from $299 as an indicative from-price for a single-company base scope. It is not a fixed price: after a short scoping call we send a fixed quotation for your agreed scope. Drivers like multi-company branding, regulator-specific tax layouts, extra document types (proforma, credit notes), and localization depth increase the quote.
Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because we inherit `account.report_invoice_document` instead of replacing it and avoid core monkey-patching, the module is designed to survive `-u` upgrades. We can also quote a maintenance arrangement or a paid migration when you move to a newer Odoo major version.
It is specifically engineered not to. We use QWeb template inheritance over template replacement, keep the `__manifest__.py` dependencies clean, and store your layout choices as configuration data on a dedicated model rather than baking them into forked templates. We deliver upgrade notes and can validate against your target Odoo version.
Yes. We build against your exact environment and target Odoo 17.0, 18.0, or 19.0, on Community or Enterprise. Some capabilities differ between editions; we confirm what applies to your edition during scoping and document any version-specific behavior in the handover.
Yes. The module is built around reusable format profiles. Each legal entity, journal, or document type (invoice, credit note, proforma) can map to its own profile, with per-company logos, footers, and bank details resolved automatically at render time — no per-invoice editing.
Yes. The resolved format and invoice data are accessible over Odoo's XML-RPC/JSON-RPC API, so downstream document-management, archiving, or e-invoicing pipelines can consume consistent output. We scope any specific integration during the requirements call.
A build-to-order Odoo module that gives your finance team real control over invoice report layout, branding, and formatting without hard-coding a new template for every variation. ECOSIRE designs, builds, installs, and supports it against your exact Odoo version and document standards.