How to specify a custom Odoo PDF report

A custom Odoo PDF report needs defined data, legal text, pagination, languages, currencies, print conditions, attachments, and acceptance samples.

A screenshot of an old report is a visual reference, not a complete requirement. Printed documents must remain correct across long addresses, many lines, discounts, taxes, multiple languages, currencies, and company identities. Define document meaning State when the report is printed, who receives it, whether it is legal or operational, and which record state is valid. Decide whether cancelled or draft documents need watermarks or should be blocked. Map every field and formula Identify source fields, fallback values, units, date formats, currency precision, tax treatment, totals, signatures, terms, and translations. Do not let the developer infer accounting formulas from a screenshot. Design variable content Test short and long addresses, missing optional data, multi-page lines, product descriptions, images, notes, terms, headers, footers, and page breaks. Layout must degrade predictably. Create acceptance samples Prepare a small set of approved documents that cover normal and difficult cases. Compare both values and rendered output. PDF generation should be checked in the real deployment environment. Practical checklist State audience, purpose, valid document state, and legal needs. Map fields, formulas, translations, and fallback values. Test long text, many lines, images, and page breaks. Cover companies, languages, currencies, taxes, and discounts. Approve rendered PDF samples from the deployment environment. Final decision A report is complete when users trust both its numbers and its printed behaviour across agreed cases, not when one carefully chosen document looks correct.