Teams collect data through Odoo forms — website enquiries, intake questionnaires, inspection checklists, survey responses, application forms — but the moment someone needs a clean PDF of a single submission, the native path runs out of road. Odoo can print list and form views, and the website builder can capture submissions into a target model, but there is no out-of-the-box way to render an individual submission as a designed, letterheaded document with computed fields, conditional sections, and a filename that reflects the record. People end up copy-pasting into a word processor, which is slow, error-prone, and impossible to automate. This is a productized service page: the module described here is built to order for your instance, not an existing download.

ECOSIRE builds a dedicated QWeb report bound to the model your forms write into. Technically, we deliver a proper module with its own __manifest__.py, a report.report_action (report_type = 'qweb-pdf') and a matching QWeb <template> that walks the submission record and its related fields. Where the raw submission stores loosely-typed answers, we add models.Model extensions with typed fields and compute/@api.depends methods so the PDF shows properly formatted totals, dates, currencies, and derived values rather than dumped strings. The report inherits web.external_layout so your company header, footer, address, and logo are applied consistently, and we implement _get_report_values in an AbstractModel so the template receives exactly the data it needs — including many-to-one and one-to-many lines rendered as tables. Optional QR codes, barcodes, page-break control, and multi-language rendering (t-lang) are handled in-template.

Beyond the document itself, we wire the automation you actually want. Using Odoo's automated actions (or a small server action), a PDF can be generated and emailed the instant a form is submitted, attached to the record as an ir.attachment, pushed to a partner via a mail template, or filed into Documents. For headless and integration scenarios the same report is renderable over the XML-RPC/JSON-RPC API, so an external portal or another system can request the PDF for a given record id. Access is locked down properly with ir.model.access.csv and record rules so users only render reports for records they are allowed to see, and multi-company setups get the correct company branding per record.

Delivery is build-to-order. After a short scoping call we confirm the exact source model, the fields and layout of the report, the trigger conditions, and your Odoo version — we support Odoo 17.0, 18.0, and 19.0, and account for Community vs Enterprise differences (for example, Studio-created fields or Enterprise-only Documents routing). You receive a fixed written quote, then we build on a staging copy, run UAT with you, and deploy with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope covering one source model and one report layout); additional report layouts, complex conditional logic, multi-company branding, extra integrations over the RPC API, and localization depth increase the quoted scope.