A build-to-order Odoo module that gives teams one unified inbox across Gmail, Outlook/Microsoft 365, and IMAP mailboxes, with OAuth2 authentication and background synchronization. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 environment. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that gives teams one unified inbox across Gmail, Outlook/Microsoft 365, and IMAP mailboxes, with OAuth2 authentication and background synchronization. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 environment.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Teams that live inside Odoo still bounce out to a separate mail client all day — reading a customer reply in Gmail, re-typing the context onto a CRM lead, then hunting for the same thread in a shared Outlook mailbox. Odoo's native Discuss and the incoming/outgoing mail plumbing (fetchmail.server for polling, ir.mail_server for sending) were built to log messages onto records and run mail gateways, not to be a day-to-day email client. There is no true unified inbox spanning personal and shared mailboxes, no OAuth2-based interactive folder browsing, and no way to triage raw email — read/unread, star, archive, reply — without leaving whichever record it happens to be attached to. That gap is exactly where a stock configuration runs out of road.
Unified inbox model aggregating Gmail, Outlook/Microsoft 365, and generic IMAP accounts into one Odoo view
OAuth2 authorization-code flow for Gmail and Microsoft 365 with encrypted refresh-token storage and automatic token renewal
App-password / credential authentication path for standards-based IMAP servers that do not offer OAuth2
Background synchronization via a dedicated `ir.cron` worker so mailbox polling never blocks the UI or web workers
Incremental, idempotent sync using per-folder IMAP UIDVALIDITY/UID high-water marks and provider delta/history cursors
New `models.Model` entities for mail accounts, folders, and messages with typed `fields` and thread grouping
This is a build-to-order module that ECOSIRE designs, builds, and installs for you — not an existing apps.odoo.com download. We implement a first-class mailbox layer inside Odoo: new models (models.Model) for mail accounts, folders, and messages, plus a background sync worker driven by an ir.cron job so IMAP and Graph/Gmail API polling never blocks a user request. Accounts authenticate with OAuth2 against Gmail and Outlook/Microsoft 365 using the authorization-code flow with encrypted refresh-token storage, and with app-password or credential auth for generic IMAP servers. Folder and message state is modeled with typed fields and @api.depends compute methods (unread counts, thread grouping), rendered through OWL client-side components and standard XML views, so the inbox feels native to whichever Odoo version you run.
Under the hood the sync is incremental and idempotent: we track per-folder UIDVALIDITY/UID high-water marks for IMAP and delta/history cursors for the API providers, so a re-run never double-imports and a token refresh never loses a message. Access is governed the Odoo way — ir.model.access.csv for base CRUD rights and record rules so a user only sees their own accounts while shared team mailboxes are exposed to the right groups. Sends route through the account's authenticated transport, and every message can be logged back onto the related partner or lead via the existing mail.thread chatter, keeping your CRM the single source of truth. The JSON-RPC/XML-RPC API remains available for any external automation you need on top.
Delivery is build-to-order. We start with a short scoping call to confirm which providers, how many mailboxes, shared-inbox rules, and any record-logging behavior you need, then produce a fixed quote and build against your Odoo 17.0/18.0/19.0 (Community or Enterprise) environment. Typical delivery is 2–4 weeks from confirmed scope, ending with UAT on staging, a rollback plan, and handover of the git repository. Pricing starts from $499 (indicative, single-company base scope); adding more OAuth provider integrations, shared-mailbox routing rules, high-volume historical email migration, or multi-company deployment increases the quoted scope.
Wants the whole team triaging customer email inside Odoo instead of switching to Gmail or Outlook, with replies logged against the right partner so nothing falls through the cracks.
Needs OAuth2 done correctly against Google Workspace and Microsoft 365, encrypted token storage, and record-rule-based isolation so users only see their own and permitted shared mailboxes.
Wants inbound and outbound email threaded onto leads and opportunities via chatter, keeping the CRM as the single source of truth without manual copy-paste.
Runs a handful of shared inboxes (info@, sales@, support@) and wants them consolidated into one Odoo screen with clear read/unread and reply handling for the team.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Email Client & Unified Inbox – Basic-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Email Client & Unified Inbox – Basic“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Delivery model | Scoped, built, installed and supported by us for your environment | You hire and manage developers to build it in-house | Generic download you install and configure yourself | |
| Unified inbox across providers | One inbox spanning Gmail, Microsoft 365, and IMAP | Possible, but you specify and build the whole model | Often single-provider or limited folder support | |
| OAuth2 (Gmail / Microsoft 365) | Authorization-code flow with encrypted refresh tokens | You implement and maintain both provider flows | Varies; may rely on app passwords or partial OAuth | |
| Background sync | Incremental, idempotent `ir.cron` worker with cursors | You design cron cadence and de-duplication logic | Present but rarely tuned to your volume or folders | |
| Security / access isolation | `ir.model.access.csv` + record rules for personal vs shared | You define and test the full access matrix | Generic rules; shared-mailbox handling often thin | |
| Odoo version fit | Built against your 17.0/18.0/19.0, Community or Enterprise | Whatever your team targets and maintains | Version support depends on the listing; may lag releases | |
| Fit to your workflow | Shared-inbox rules and CRM logging tailored in scoping | Fully bespoke, at full build cost and timeline | Configurable within the module's fixed assumptions | |
| Ongoing support | Support window plus optional retainer and upgrade path | Your team owns all maintenance and upgrades | Vendor support varies; upgrades on their schedule |
No. This is a build-to-order module. ECOSIRE scopes, builds, installs, and supports it for your specific Odoo environment. It is not an existing apps.odoo.com download and there is no instant-download or trial.
Typical delivery is 2–4 weeks from confirmed scope. After a short scoping call we lock the providers, mailbox count, and shared-inbox rules, then build against your Odoo version, run UAT on staging, and hand over. Complex multi-provider or high-volume migrations sit at the longer end of that range.
Pricing starts from $499 as an indicative single-company base scope. After the scoping call we issue a fixed written quote. Additional OAuth provider integrations, shared-mailbox routing rules, large historical email migrations, or multi-company deployment increase the quoted scope.
Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. We build the module against your exact target version so views, OWL components, and mail APIs match your environment.
Every build includes a post-go-live support window for defect fixes and configuration adjustments. Beyond that we offer optional support and maintenance retainers, including version-upgrade work when you move to a newer Odoo release. You receive the git repository, so you are never locked in.
Yes. We use the OAuth2 authorization-code flow with your own Google Cloud / Azure app registrations, and refresh tokens are stored encrypted in the database. Access is governed by `ir.model.access.csv` and record rules so users see only their own accounts and permitted shared mailboxes.
Optionally, yes. We can log messages back onto related partners, leads, or opportunities through Odoo's native `mail.thread` chatter, so your CRM stays the single source of truth. The exact logging behavior is confirmed during scoping.
A build-to-order Odoo module that gives teams one unified inbox across Gmail, Outlook/Microsoft 365, and IMAP mailboxes, with OAuth2 authentication and background synchronization. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 environment.