Product Catalogue PDF Generator

Key Features

`product.catalogue` model storing reusable catalog definitions — product selection, layout, branding, and theme are saved and re-runnable, not rebuilt each time

Flexible product selection by product category, product tag, pricelist, saved filter, custom `domain`, or a hand-picked set of `product.template` records

QWeb PDF report (`ir.actions.report`, `report_type='qweb-pdf'`) rendering the selection into a print-ready, paginated document

`@api.depends` compute fields resolve per-product price against the chosen `pricelist` and currency at render time, so PDFs are never stale

Reusable QWeb template components: configurable cover page, back page, category dividers, per-product cards, and an auto-generated table of contents

Per-product card layout you control — product image, internal reference, sales description, selectable variants/attributes, unit of measure, and price

Multiple selectable catalog themes (fonts, colors, spacing, logo placement) driven by your brand, editable in XML/QWeb rather than hard-coded

Multi-currency and multi-pricelist support so the same product set can be published as distinct market/price editions

Multilingual and RTL-aware rendering, honoring Odoo translated product fields (`name`, `description_sale`) for locale-specific catalogs

Optional server/automated action to generate a catalog from a button on the product or pricelist form, or on a recurring schedule (`ir.cron`)

XML-RPC/JSON-RPC endpoint to trigger catalog generation and retrieve the PDF programmatically from an external portal, PIM, or website

Configurable image handling — resolution/DPI and fallback placeholder so missing product images never break the layout or blow up file size

Security enforced via `ir.model.access.csv` plus record rules, keeping catalog access and product scope correct in multi-company databases

Packaged as a clean installable module with a proper `__manifest__.py`, version-pinned and tested for Odoo 17.0, 18.0, and 19.0 on Community or Enterprise

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Sales teams that run Odoo constantly need a polished, up-to-date catalog to send to a prospect, hand out at a trade show, or attach to a quotation — but Odoo core has no built-in way to produce one. The stock product.template QWeb reports print a single record, not a curated multi-product brochure, and the website eCommerce module only renders catalogs as HTML pages behind a browser. So teams fall back to exporting to a spreadsheet and rebuilding the layout by hand in a page-layout tool every time a price changes or a product is added. The result is a catalog that is out of date the moment it is printed, plus hours of repetitive manual work no one wants to own.

We build a dedicated Odoo module that generates customizable product catalogs as PDF directly from your live product data. Technically, it adds a product.catalogue model (models.Model) that captures a catalog definition — the product selection (by category, tag, pricelist, custom domain, or a hand-picked set), the cover and back-page content, the field layout, and the theme — plus a QWeb PDF report (ir.actions.report, report_type='qweb-pdf') that renders the selected product.template/product.product records into a print-ready document. @api.depends compute fields resolve the correct price per the chosen pricelist and currency at render time, so the PDF always reflects the catalog as it exists today, not a stale export. The report template is built from reusable QWeb components (cover, category dividers, per-product cards with image, code, description, variants, and price, and a table-of-contents), so layout changes are edits to XML, not a rebuild. Where you need it, we wire a server action or automated action so a catalog can be generated on a schedule or from a button on the product/pricelist form, and we expose generation over the XML-RPC/JSON-RPC API so an external portal or PIM can request a fresh PDF programmatically. Access is governed by ir.model.access.csv plus record rules so, in a multi-company database, each company only builds catalogs from its own products.

Everything is delivered as a proper installable module with a clean __manifest__.py, versioned for your exact Odoo release, and tested against Odoo 17.0, 18.0, or 19.0 on either Community or Enterprise. We confirm the QWeb-to-PDF rendering path (wkhtmltopdf/ir.actions.report) works consistently for your fonts, page sizes, and RTL/multilingual needs, and we handle the differences between Community and Enterprise cleanly so the module behaves the same on either edition.

Because this is build-to-order, nothing is downloaded off the shelf — we build your version to your confirmed scope. After a short scoping call we agree the product selection logic, the fields and branding to appear on each catalog, and any automation or API needs, then fix the quote. Typical delivery is 2–4 weeks from confirmed scope, and we install it on your staging environment for UAT before touching production. Pricing starts from $249 (indicative, single-company base scope); heavier localization depth (multilingual and RTL catalog layouts, per-market pricelists), additional integrations, and multi-company rollout increase the quoted scope.

What you get

Installable module source code for your specified Odoo version (17.0/18.0/19.0), built to your confirmed scope

Installation and configuration on your staging environment, then production go-live support

Technical documentation — data model, QWeb report structure, configuration options, and API usage

End-user guide plus a live training session for your team on defining and generating catalogs

UAT on a staging clone with a documented rollback plan before any production deployment

Post-go-live support window for defect fixes and questions

Git repository handover with full commit history and tagged release

Branding/theme setup applying your logo, fonts, and colors to the initial catalog template

Who this is for

Sales & Business Development Teams

Reps who need a current, branded PDF catalog to send with a quotation or hand out at an event, without waiting on marketing to rebuild it every time a price or product changes.

Marketing & Brand Managers

Owners of the catalog's look and feel who want on-brand fonts, layout, and cover pages generated automatically from live Odoo data instead of manual page-layout work.

Wholesale & Distribution Operators

B2B sellers publishing different price editions per customer segment or region, needing catalogs driven by specific pricelists, currencies, and product categories.

Odoo Administrators & IT Managers

The team that owns the Odoo instance and needs a clean, version-pinned, permission-scoped module that installs cleanly, respects multi-company boundaries, and is documented and supportable.

How Product Catalogue PDF Generator Compares

Criterion	ECOSIRE	Custom Build	Competitor
Delivery model	Built to your scope, installed and supported by us	You brief and manage in-house or contractor developers	Generic download, configure it yourself
Product selection logic	Category, tag, pricelist, custom domain, or hand-picked — your rules	Whatever you build and maintain yourself	Fixed options the module ships with
Live pricing accuracy	Resolved per pricelist/currency at render time via compute fields	Depends on your implementation	Usually current, but tied to the module's assumptions
Branding & layout control	Your themes, editable QWeb components, cover/back pages	Fully yours to design and maintain	Preset themes with limited overrides
Automation & API	Scheduled actions and XML-RPC/JSON-RPC generation, if scoped	Build it yourself	Rarely included or shallow
Multi-company & security	Record rules + `ir.model.access.csv` scoped to your structure	You design the access model	Basic access, may ignore multi-company scope
Odoo version fit	Version-pinned and tested for 17.0/18.0/19.0, Community or Enterprise	You own every version upgrade	May lag your Odoo version
Support & ownership	Post-go-live support window plus full git repo handover	Entirely your team's burden	Vendor-dependent, varies by listing

Frequently Asked Questions about Product Catalogue PDF Generator

Is this an app I can download and install right now?

No. This is a build-to-order module — ECOSIRE scopes, builds, installs, and supports it for you. It is not an off-the-shelf apps.odoo.com download. After a short scoping call we agree the exact selection logic, fields, branding, and automation, then build your version and deploy it to staging before production.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The timeline depends on the complexity of your product-selection rules, branding, multilingual/RTL needs, and any integrations. We give you a firm schedule with the fixed quote after the scoping call.

How does pricing and scoping work?

Pricing starts from $249 as an indicative single-company base scope. It is not a firm price until we scope the work. After a 15–45 minute scoping call we confirm requirements and send a fixed quote. Drivers like deep localization (multilingual/RTL editions, per-market pricelists), extra integrations, and multi-company rollout increase the quoted scope.

What support and updates do I get after go-live?

Every build includes a post-go-live support window for defect fixes and questions, plus the full git repository so your team owns the code. We can also provide an ongoing support and version-upgrade agreement to keep the module current as you move between Odoo 17.0, 18.0, and 19.0.

Will it work on Odoo Community or only Enterprise?

It works on both. We build and test against Odoo 17.0, 18.0, or 19.0 on Community or Enterprise and handle the edition differences cleanly, since the catalog generation relies on the standard QWeb-to-PDF reporting engine present in both.

Can catalogs be generated automatically or from another system?

Yes. We can wire a scheduled action (`ir.cron`) or a button on the product/pricelist form to generate catalogs, and expose generation over the XML-RPC/JSON-RPC API so an external portal, website, or PIM can request a fresh PDF programmatically. These are scoped and quoted as part of your build.

How current is the data in a generated PDF?

The report renders directly from your live product records at generation time, with prices resolved against the selected pricelist and currency via compute fields. There is no intermediate export, so the catalog always reflects your catalog as it exists at the moment you generate it.