A build-to-order Odoo module that renders pixel-accurate Word (.docx) documents straight from designer-friendly templates using Jinja-style tags bound to your Odoo records. ECOSIRE scopes, builds, installs, and supports it — no instant download. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A build-to-order Odoo module that renders pixel-accurate Word (.docx) documents straight from designer-friendly templates using Jinja-style tags bound to your Odoo records. ECOSIRE scopes, builds, installs, and supports it — no instant download.
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.
Finance, legal, HR, and operations teams inside Odoo routinely need documents that must ship as editable Word files, not locked PDFs: contracts, engagement letters, statutory filings, tender responses, inspection reports, appraisal forms, and board packs. Odoo's native reporting is QWeb — an HTML/CSS-to-PDF engine. It is excellent for invoices and pick lists, but it produces PDFs, not .docx, and every layout change means editing XML QWeb templates and redeploying. When a compliance officer or a client wants to tweak a clause, add a signature block, or restyle a cover page, they cannot — the template lives in code, and the output is not a Word file they can open, redline, and forward. Teams end up exporting data to spreadsheets and copy-pasting into Word by hand, which is slow, error-prone, and unauditable.
ECOSIRE builds the Docx Report Generator to close that gap. It is a made-to-order Odoo module (not an existing apps.odoo.com download) that lets your business users design report templates in Microsoft Word itself, drop in Jinja-style tags like {{ order.partner_id.name }} and {% for line in order.order_line %}...{% endfor %}, upload the .docx as an Odoo report definition, and then generate a fully-formatted Word document for any record — a sale order, invoice, project, employee, or a custom model — with one click or over the API. The rendering context is the actual Odoo recordset, so every field, related field, @api.depends computed value, and Many2many collection your template references is resolved through the ORM with the requesting user's access rights intact.
Technically, we register the generator as a first-class Odoo report bound to ir.actions.report so it appears in the Print menu and respects the binding_model_id you choose. Templates are stored as attachments (or on a dedicated model) and the engine substitutes tags server-side using a Word-aware templating layer that preserves styles, tables, headers/footers, page numbering, and embedded images, then streams the resulting .docx back to the browser or returns it as a base64 payload over XML-RPC/JSON-RPC for headless generation and batch runs. We wire loops and conditionals for order/invoice lines, expose safe filters (dates in the user's locale, monetary formatting, num2words for amounts in words), and can add QWeb-to-PDF conversion of the same document via LibreOffice headless if you also need an archival PDF. Access is governed by ir.model.access.csv plus record rules so template management and generation stay inside the roles you specify, and generated files are logged as ir.attachment records against the source document for a full audit trail. It ships tested on Odoo 17.0, 18.0, and 19.0, and we confirm Community vs Enterprise behaviour for your edition during scoping.
Because this is build-to-order, delivery follows a clear path: a scoping call to confirm which models, templates, and output fields you need; a fixed written quote; then we build against your requirements, run UAT on a staging database with your real templates, and deploy to production with a rollback plan and a handover of the git repository. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); the number of distinct report templates, complex nested-loop layouts, multi-company or multi-language rendering, and any bulk/batch or API-driven generation increase the quoted scope. You receive a firm, fixed price after the scoping call — never a surprise.
Need editable Word contracts, engagement letters, and statutory documents generated from Odoo sales, invoicing, and accounting records — with correct monetary formatting and amounts in words — rather than locked PDFs they cannot amend.
Want business users to self-serve report layouts in Word without touching QWeb XML, while keeping generation inside proper Odoo report actions, access rules, and the attachment audit trail.
Produce inspection reports, work orders, and appraisal forms as `.docx` from project, maintenance, or custom-model records — often in batch — so field staff and clients receive familiar, editable Word files.
Need to generate branded Word documents from Odoo data over XML-RPC/JSON-RPC for downstream systems, customer portals, or scheduled jobs without a user manually clicking Print.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Output format | Editable `.docx` (optional PDF via LibreOffice) | Whatever you build; depends on libraries chosen | Usually `.docx` only, fixed feature set | |
| Template authoring | In Microsoft Word with Jinja-style tags — no code | Author-defined; typically dev-owned | Word tags, but generic to the vendor's design | |
| Fit to your models/data | Built to your exact models, fields, and layouts | Fully bespoke if you have the dev capacity | Generic; you adapt your process to it | |
| Odoo integration depth | Proper `ir.actions.report`, Print menu, record rules, attachments | Depends on developer discipline | Varies; often shallow bindings | |
| API / batch generation | XML-RPC/JSON-RPC + batch + automated actions, scoped for you | Possible, but you design and maintain it | Sometimes; not always exposed | |
| Support & maintenance | Post-go-live window + git handover + version migrations quotable | You own all maintenance | Vendor tickets; roadmap not yours | |
| Odoo version coverage | Tested on 17.0 / 18.0 / 19.0 for your edition | Whatever you target and test | Vendor-listed versions; may lag | |
| Delivery model | Build-to-order: scope, fixed quote, UAT, rollback, 2-4 weeks | Your timeline and risk | Instant download, but you self-fit |
No. This is a build-to-order module. ECOSIRE designs, builds, installs, and supports it for your specific models and templates after you request a quotation — it is not an off-the-shelf apps.odoo.com download.
Typical delivery is 2-4 weeks from confirmed scope. The timeline depends mainly on how many distinct Word templates you need, how complex their loops and layouts are, and whether multi-company, multi-language, or API/batch generation is involved. You get a target date in writing with your fixed quote.
Pricing starts from $249 (indicative, single-company base scope). We hold a short scoping call to confirm the models, templates, filters, and delivery method you need, then send a firm, fixed written quote. Additional templates, complex nested layouts, multi-company/multi-language rendering, and API-driven or batch generation increase the quoted scope — you approve the fixed price before we build.
Every build includes a post-go-live support window for defect fixes and questions, plus handover of the git repository so your team owns the code. The module is delivered tested on Odoo 17.0, 18.0, or 19.0; migration to a newer major version or added templates later can be quoted separately as a small scoped engagement.
No. Authors design the layout in Microsoft Word using ordinary Word styling, then insert Jinja-style tags such as `{{ order.partner_id.name }}` and `{% for line in order.order_line %}`. They upload the `.docx` as a report definition — no XML/QWeb editing and no redeploys for layout changes.
Yes. We can trigger generation from an automated/server action on a state change (for example, when a sale order is confirmed) and attach the result to the record. We also expose headless generation over XML-RPC/JSON-RPC, returning a base64 `.docx` for external systems, portals, or scheduled batch runs.
Yes. Rendering runs through the ORM with the requesting user's access rights, and template management versus generation are governed separately via `ir.model.access.csv` and record rules. We confirm Community vs Enterprise behaviour for your edition during scoping and test on your target release.
A build-to-order Odoo module that renders pixel-accurate Word (.docx) documents straight from designer-friendly templates using Jinja-style tags bound to your Odoo records. ECOSIRE scopes, builds, installs, and supports it — no instant download.