How to Customize Header and Footer for All Reports in Odoo 17

Introduction

Odoo reports such as invoices, quotations, purchase orders, delivery slips, and other business documents often need consistent branding. A standard logo and company address may be enough initially, but growing businesses usually require custom headers, legal information, contact details, tax information, page numbering, brand colors, or region-specific content.

With Odoo 17 report customization, businesses can manage these requirements through document layout settings, Odoo Studio, or advanced QWeb report customization.

For organizations using Odoo across operations in the USA, UK, or multiple international locations, consistent report design also helps maintain a professional brand identity across customer-facing and internal documents. Working with an experienced Odoo software development company can help ensure these changes remain scalable, maintainable, and compatible with future Odoo upgrades.

Quick: To customize headers and footers across Odoo 17 reports, businesses can configure the default Document Layout for basic branding or inherit Odoo's shared QWeb external layout for advanced requirements. Reports using the shared external layout can then display consistent logos, company details, legal text, page numbers, and other customized information.

What Are Headers and Footers in Odoo Reports?

In Odoo, the header and footer form part of the report layout surrounding the main report content.

A header may contain:

• Company logo and business name
• Registered address
• Phone number and email
• Tax or VAT registration details
• Website information
• Document-specific information

The footer can contain:

• Legal disclaimers
• Payment or banking information
• Company registration details
• Contact information
• Terms and conditions
• Page numbers

Odoo 17's external report type automatically supports company information in the header and footer information with page numbering. Document layout configuration is company-specific and can apply across reports.

For businesses operating across the UK and USA, this can be particularly useful when different companies, subsidiaries, or legal entities need their own corporate information while maintaining the same overall report design.

How Odoo Report Customization Works

Odoo 17 primarily creates reports using QWeb templates, which combine XML and HTML-style structures with dynamic Odoo data. Odoo's official documentation explains that QWeb reports are written in HTML/QWeb and that PDF output is rendered from these templates.

A typical report includes:

• A report action that defines how the report is generated
• A QWeb template containing the report structure
• A shared external layout for common header and footer elements
• CSS for visual formatting
• Dynamic fields connected to company or transaction data
• Paper-format settings for margins, orientation, and dimensions

This architecture is what makes Odoo report customization scalable. Instead of adding the same company header manually to every invoice, quotation, and purchase report, developers can customize a reusable layout.

For organizations with more complex processes, a customized Odoo ERP can also conditionally display information depending on company, customer, country, report type, or business workflow.

How to Customize Header and Footer in Odoo 17

There are two main approaches depending on the level of customization required.

1. Configure the Standard Document Layout

For straightforward changes, navigate to:

Settings → Companies → Configure Document Layout

From here, businesses can adjust items such as the document layout, logo, colors, font, company information, footer, and paper format.

Odoo 17 provides standard layout styles including Light, Boxed, Bold, and Striped. These settings are useful when a company wants consistent visual branding without creating a custom module.

This is usually appropriate for basic Odoo PDF report customization.

2. Customize the QWeb Layout

When the requirement involves custom HTML structures, conditional information, additional fields, unique styling, multiple companies, or industry-specific data, QWeb customization provides greater control.

Rather than directly changing Odoo's core files, developers should create an inherited template inside a custom module.

A simplified structure may look like:

<template id="custom_external_layout"
          inherit_id="web.external_layout_standard">

    <xpath expr="//div[contains(@class, 'header')]"
           position="inside">
        <div class="custom-report-header">
            Additional company or report information
        </div>
    </xpath>

</template>

The exact XPath and target template should always be checked against the installed Odoo version and selected document layout.

Customizing Report Headers Using QWeb Templates

A custom header can use dynamic information instead of fixed text. This makes the same Odoo report template reusable across different records or companies.

Typical dynamic fields include the company name, logo, registration number, tax number, address, telephone number, website, customer reference, document date, or report title.

Conditional QWeb logic can also control what appears.

For example, a UK entity may need one legal footer while a US entity requires different corporate information. Rather than maintaining completely separate reports, developers can apply conditions using company or country data.

This approach makes Odoo 17 QWeb reports especially useful for multi-company ERP environments.

Customizing Report Footers and Page Numbers in Odoo 17

Footers often require more attention because business documents can run across multiple pages.

A customized footer may include:

• Legal company information
• Payment instructions
• Website and email address
• VAT or tax registration number
• Confidentiality statements
• Page numbering

Odoo's external PDF report structure already supports footer content and page numbers, which can then be adapted through report customization.

When implementing advanced footer designs, always test multi-page invoices, long sales orders, large purchase documents, different paper formats, and PDF output rather than checking only the HTML preview.

Applying a Custom Header and Footer Across Odoo Reports

The biggest advantage of using a shared external layout is centralized control.

Many Odoo reports call a common external layout. When that shared layout is extended correctly, the branding can flow across reports that use it without repeating the same code.

This approach can improve:

Brand consistency:  Customer-facing documents follow the same visual identity.

Maintenance:  Future changes can be made centrally instead of editing numerous templates.

Multi-company management:  Company-specific information can be populated dynamically.

Scalability:  Newly developed reports can reuse the same design framework.

However, not every custom report necessarily uses the same external layout. Blank, internal, heavily customized, or third-party reports should therefore be reviewed individually before assuming the global customization will apply.

Managing Custom Report Requirements in Odoo

Report requirements often become more complex as an ERP implementation expands.

A company might require different headers by legal entity, localized tax information, multilingual footer content, customer-specific notes, signatures, barcodes, approval information, bank details, or different layouts for different document types.

During an Odoo implementation service, these requirements should be documented before development begins.

A practical requirements checklist should define:

• Which reports need customization
• Whether changes apply globally or only to selected reports
• Which fields are dynamic
• Whether different companies require different layouts
• Which languages and currencies must be supported
• Whether legal content differs between the UK, USA, or other markets
• Whether the layout must remain compatible with future upgrades

Planning these requirements early prevents unnecessary template duplication and reduces long-term maintenance.

Common Issues When Customizing Odoo Headers and Footers

Even relatively small Odoo custom header and footer changes can introduce formatting problems if they are implemented directly in standard templates.

Common issues include incorrect XPath expressions after upgrades, headers overlapping report content, footers being cut off, missing CSS in generated PDFs, images failing to load, inconsistent margins, multi-company information appearing incorrectly, and layouts working in HTML but not in the final PDF.

Odoo's developer documentation notes that report rendering depends on the report engine being able to access styles and related resources correctly.

For production environments, test the final PDF with realistic data and long, multi-page documents before deployment.

Best Practices for Odoo Report Customization

For reliable Odoo QWeb report customization, avoid changing standard Odoo source templates directly whenever possible.

Instead:

• Use template inheritance through a custom module.
• Keep branding logic centralized.
• Use dynamic company information rather than hardcoded details.
• Keep custom CSS organized and minimal.
• Test both HTML and PDF versions.
• Validate multi-page documents.
• Test every company in a multi-company environment.
• Maintain changes in version control.
• Revalidate inherited templates during Odoo upgrades.
• Keep backups and documentation for production changes.

Odoo's newer documentation also recommends duplicating standard reports when working through its report editor rather than unnecessarily altering the original report.

Ongoing Odoo support and maintenance services are especially valuable when report customizations depend on core templates, because upgrades can introduce changes to XML structures, layouts, fields, or styling.

What About Odoo 20 Report Customization?

Odoo 20 should now be part of the planning conversation for businesses starting new ERP projects or preparing upgrades. As of September 2026, Odoo is already publicly presenting Odoo 20 capabilities in official events, including Odoo 20 logistics improvements.

The broader principle for report customization remains important: keep customizations modular and separate from standard code.

Businesses upgrading from Odoo 17 to Odoo 20 should not assume every existing XPath, template identifier, CSS rule, or inherited report structure will continue to work unchanged. The safest approach is to review custom modules, compare report templates, test headers and footers, and validate every important PDF after migration.

This makes upgrade-friendly QWeb development far more valuable than directly modifying core templates.

Conclusion

Customizing headers and footers in Odoo 17 is not simply a visual improvement. A properly structured Odoo report customization strategy gives businesses consistent branding, localized corporate information, easier maintenance, and better control over important ERP documents.

Basic requirements can usually be handled through Document Layout configuration, while advanced needs are better managed through inherited Odoo QWeb report templates and custom modules.

For companies operating across the UK, USA, or multiple legal entities, centralized and upgrade-safe customization is particularly important. With Odoo 20 now entering enterprise planning and adoption, keeping report logic modular today can also reduce migration complexity tomorrow.