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.

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.