[0·1·1] · Core Product module · available

MATE Email Builder: structured Odoo templates without QWeb code.

In standard Odoo, conditional email copy, reliable placeholders, and selective attachments require manual QWeb expressions and developer privileges. MATE Email Builder equips business teams with a block-based editor, a three-level rules engine, Odoo Sign orchestration, and a side-effect-free send preview built directly on mail.template.

Odoo 20 Standard Native extension of mail.template & composer
3 Rule Levels Template selection, conditional blocks & dynamic attachments
Dry-Run Preview Real-record simulation without accidental sends
MATE Email Builder · DACH Quote Dry-Run OK
Email Builder Odoo 20 mail.template · MATE Reports & Sign

End-to-end email logic instead of scattered QWeb clones.

Rather than duplicating templates for every country, legal entity, and document combination, the module assembles emails modularly from approved building blocks and clear rules.

No-code block editor & reusable library

Business departments combine paragraphs, callout boxes, tables, buttons, and centrally maintained snippets into consistent templates. Updating a sign-off or legal footer in one place immediately updates every linked template.

Guided placeholders without developer rights

Dynamic fields from customer, quote, invoice, purchase order, or stock picking records are inserted as visible chips via a curated placeholder picker. Type-safe formatting for dates, currencies, and languages prevents broken expressions on save.

Three-level rules engine with plain-language checks

Level 1 automatically selects the right template by priority and fallback, Level 2 shows or hides individual text blocks based on record criteria, and Level 3 governs conditional file attachments — cleanly mapped to Odoo domains under the hood without requiring technical syntax.

Static, dynamic & Odoo Documents attachments

Standard PDFs, custom reports from ir.actions.report (such as DIN 5008 documents from MATE Reports), record attachments, and files from Odoo Documents are attached dynamically in a defined sequence.

Orchestrated Odoo Sign integration

Documents requiring signature are strictly separated from regular attachments. On send, the module creates a controlled signature request with mapped signer roles; the secure signing link appears directly inside the business email without triggering a second system email, and the signed PDF archives automatically on the source record.

Side-effect-free dry-run send preview

Before go-live, a validation assistant simulates the full send for any real Odoo record: chosen template, matched rules, resolved placeholders, visible blocks, generated PDF attachments, and planned Sign requests — completely without sending an actual email.

Architectural fit before rollout: prerequisites and clear boundaries.

Reliable tools grow out of clear process rules. We configure the Email Builder only once document logic, approvals, and template ownership are clearly defined.

When it fits & prerequisites

  • Odoo 20 Enterprise or Community: Runs on Odoo.sh or self-hosted servers with clean integration across mail, sale, account, purchase, and stock.
  • Optional extension bridges: Supports sign (Odoo Sign), documents (Odoo Documents), and optional GDPR-pseudonymized copy drafts via the MATE AI Bridge with human sign-off.
  • Multiple companies, countries, or document types: Especially effective when wording, tax notices, terms & conditions, or signature requirements vary by customer segment, order value, or destination country.
  • Protection for manual edits: Content adjusted manually inside the compose dialog is respected and never silently overwritten by automated rules.

Limits & honest boundaries

  • Not for Odoo Online (SaaS): Because Odoo Online does not allow custom Python modules, production operation requires Odoo.sh or self-hosting.
  • Not a newsletter or bulk marketing tool: The module is built for transactional business and process communication (quotes, order confirmations, deliveries, invoices, procurement, service) — not as a campaign newsletter platform.
  • Clear template ownership required: A rule set stays clean long-term only when a designated business owner approves new conditions and signs them off with the dry-run preview.
  • Controlled deployment after verification: Rollout follows structured delivery via MATE Hub or Git branch workflow (staging before production), never as an untested live experiment.

Frequently asked questions on MATE Email Builder.

What teams typically clarify before introducing rule-driven email templates in Odoo.

Does MATE Email Builder remain compatible with Odoo's standard mail.template?

Yes. The builder extends the native Odoo models mail.template and mail.compose.message instead of introducing a parallel mailing system. Existing templates can be imported, gradually converted into blocks, and used inside the familiar compose dialog.

How does the three-level conditional logic work without QWeb code?

Business users maintain guided filter rows with plain-language summaries across three levels: Level 1 automatically selects the right template for a record, Level 2 shows or hides individual content blocks, and Level 3 controls attachments and signature documents based on clear criteria.

How does the module prevent duplicate emails when using Odoo Sign?

Documents requiring a signature are cleanly separated from regular PDF attachments. When sending, the module creates the matching signature request in a controlled way, embeds the signing link directly into the business email, and suppresses separate default signature emails.

Does the send preview trigger real emails or signature requests?

No. For any real sample record, the dry-run preview simulates exact template selection, all matching rules, resolved placeholders, planned PDF attachments, and Odoo Sign actions completely free of side effects before the actual send.

Which Odoo hosting models support the module?

The module is built for Odoo 20 Enterprise and Community on Odoo.sh as well as self-hosted (on-premise) deployments. Custom Python modules are not permitted on Odoo Online; we clarify the cleanest hosting option upfront during our introductory call.

Walk through a real send scenario.

Briefly describe your Odoo version, hosting setup, and typical email cases (such as quotes, order confirmations, or Odoo Sign documents). In our introductory call, we give you an honest assessment of whether the module fits right away.

Matthias GrdanManaging Director · Process & ERP Architecture
Architecture & Modules TeamOdoo Engineering · Villingen-Schwenningen

The introductory call is non-binding. Your inquiry is delivered directly via our Google Workspace mail service — or prepared locally as an email draft.

Delivered via our Google Workspace mail service or as a local email preview without third-party trackers. Privacy Policy

Book a call