A build-to-order Odoo module that gives every company in your database its own outgoing email identity — sender address, branded signature, and reply-to — so mail always leaves under the correct brand. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0, 18.0, and 19.0. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that gives every company in your database its own outgoing email identity — sender address, branded signature, and reply-to — so mail always leaves under the correct brand. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0, 18.0, and 19.0.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
When you run several legal entities or brands inside one Odoo database, email is where the separation quietly falls apart. A quotation from your Dubai entity, an invoice from your UK company, and a delivery note from a subsidiary all leave through the same outgoing mail server and, worse, under the same From address and a generic footer. Odoo core lets you configure ir.mail_server records and a system-wide signature, but it does not reliably bind a specific sender identity, reply-to, and signature to the res.company that actually owns the document being sent. Customers end up replying to the wrong mailbox, footers name the wrong entity, and mismatched sender domains push your mail toward spam. This is the exact gap Multi Company Email Communications is built to close.
Extends `res.company` with per-company outgoing `from`, `reply_to`, and display-name fields resolved on the mail send path
Per-company HTML signature rendered from a dedicated QWeb template (logo, address, legal footer) instead of a single global signature
Company inference from the source document's `company_id` (sale order, invoice, project, helpdesk ticket) so mail leaves under the owning entity
Override of the `mail.thread` message-post / `_get_default_from_address` pipeline that maps each company to its matching `ir.mail_server`
Graceful fallback to standard Odoo behaviour when a company has no custom identity configured — nothing existing breaks
Per-company reply-to enforcement so customer replies land in the correct entity's mailbox, not a shared inbox
We build a module that makes the company the first-class driver of email identity. It extends res.company with per-company email fields — outgoing from address, reply_to, display name, and a QWeb-rendered HTML signature block — and adds a resolution layer on the mail send path. Whenever a mail.mail or mail.message is generated from a record, the owning company is inferred from the source document (company_id on the sale order, invoice, project, helpdesk ticket, etc.), and the matching outgoing ir.mail_server plus sender identity are applied via an override of _get_default_from_address / the mail.thread message-post pipeline. Signatures render from a per-company QWeb template so each brand keeps its own logo, address, and legal footer. Access is governed through ir.model.access.csv and record rules so a user only sees and edits the mail configuration for companies in their allowed set, and everything is exposed in clean settings views (XML/OWL) rather than raw technical fields.
Because the send-path override touches core mail behaviour, we build defensively: the resolution falls back gracefully to the current Odoo behaviour when no per-company identity is configured, so nothing that works today breaks. We handle the Community vs Enterprise differences (Enterprise's marketing and social mailing paths differ from core mail), and we test against your real transactional documents — sales, invoicing, and any custom flows you rely on. Optional add-ons we can scope in the same engagement include catch-all/bounce routing per company, alias-domain separation, and automated actions that stamp a company-specific reply-to on inbound-to-outbound conversions.
Delivery is build-to-order: you request a quotation, we run a short scoping call to confirm your entities, mail servers, and the documents in scope, then build on a staging copy of your database, run UAT with you, and deploy with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); the number of companies, extra outgoing mail servers and domains, catch-all/bounce routing, and depth of localization or signature templating increase the quoted scope.
Runs several legal entities in one Odoo database and needs invoices, quotations, and statements to leave under each entity's own sender address and legal footer for compliance and brand trust.
Maintains the `ir.mail_server` records and domain authentication. Wants sender identity bound to company automatically so support tickets and mailings stop going out under the wrong From address and tripping spam filters.
Operates distinct customer-facing brands from shared back-office. Needs each brand's outgoing email, reply-to, and signature to stay separate so customers reply to the correct team.
Implements Odoo for clients with subsidiaries and needs a reliable, supported per-company email-identity module rather than maintaining brittle custom overrides in-house.
Buy the license on ecosire.com and download the Multi Company Email Communications module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Multi Company Email Communications, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Per-company sender identity | Bound automatically to the document's owning company | Possible but you build and maintain the override yourself | Generic per-company mapping, may not cover all document types | |
| Per-company signature | QWeb template per company with logo and legal footer | Hand-coded per project; upkeep on you | Basic text signature, limited templating | |
| Reply-to routing | Enforced per company so replies reach the right mailbox | Achievable with effort, easy to miss edge cases | Often partial; inbound conversions may be missed | |
| Security / access control | `ir.model.access.csv` + record rules scoped to allowed companies | Depends on developer discipline | Varies; not always company-scoped | |
| Fit to your workflows | Scoped to your real documents and mail servers | Fully bespoke but slow and unsupported | Fixed feature set; you adapt to it | |
| Support & warranty | Post-go-live support window + git handover | Only if you retain the developer | Vendor support varies, often forum-only | |
| Version coverage | Built and tested for 17.0/18.0/19.0, Community & Enterprise | Whatever you commission and re-test each upgrade | Depends on listing; upgrades may lag | |
| Delivery model | Build-to-order, staging UAT + rollback, 2–4 weeks | Open-ended timeline and cost | Instant download, then self-integrate |
No. Multi Company Email Communications is build-to-order. ECOSIRE scopes your entities, mail servers, and in-scope documents, then builds, installs, and supports the module for your Odoo version. It is not an instant apps.odoo.com download.
Typical delivery is 2–4 weeks from confirmed scope. After a short scoping call we build on a staging copy of your database, run UAT with you, and deploy with a rollback plan. The exact timeline is fixed in your quotation once scope is agreed.
Pricing starts from $249 (indicative, single-company base scope). The number of companies, additional outgoing mail servers and domains, catch-all/bounce routing, and localization depth affect the quote. You get a fixed quote after the scoping call — the from-price is indicative, not a firm fixed price.
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Enterprise's mailing and social paths differ from core `mail`, so we confirm which sending flows you use during scoping and handle those differences in the build.
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments, plus a git repository handover so you own the code. When you upgrade to a future Odoo major version we provide an upgrade advisory and can quote the migration work separately.
No. The send-path resolution falls back to standard Odoo behaviour whenever a company has no custom identity configured, so existing flows keep working. We test against your real transactional documents on staging before anything reaches production.
Yes. Identity resolution runs server-side on the mail pipeline, so mails triggered through the XML-RPC/JSON-RPC API, scheduled actions, or automated actions all receive the correct company sender, reply-to, and signature.
A build-to-order Odoo module that gives every company in your database its own outgoing email identity — sender address, branded signature, and reply-to — so mail always leaves under the correct brand. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0, 18.0, and 19.0.