A build-to-order foundation module that extends Odoo Discuss with the core plumbing to send and receive mobile messages through a provider gateway. ECOSIRE scopes, builds, installs and supports it — this is a made-to-order engagement, not an off-the-shelf download. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifiesto de la app
Diseñado en torno a tu flujo de trabajo
A build-to-order foundation module that extends Odoo Discuss with the core plumbing to send and receive mobile messages through a provider gateway. ECOSIRE scopes, builds, installs and supports it — this is a made-to-order engagement, not an off-the-shelf download.
Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.
Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.
ECOSIRE la crea, la configura y la instala en tu Odoo.
Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.
Most teams that run Odoo eventually hit the same wall: customer conversation lives in one place (Discuss, mail.thread, the chatter) while the channel customers actually reply on — their phone — lives in a disconnected mobile app or a browser tab nobody logs. Sales confirmations, delivery notices, service updates and one-off replies get copy-pasted by hand, or worse, never reach the record they belong to. Odoo core gives you email and internal messaging, but out of the box it has no notion of an outbound/inbound mobile messaging gateway, no delivery-state tracking, and no clean abstraction layer to bolt a third-party provider onto. That is exactly the gap this base module fills.
This is the foundation layer — a deliberately provider-agnostic base module that gives your Odoo the reusable scaffolding every mobile-messaging feature depends on. Technically, we ship a new set of ORM models (models.Model) for message envelopes, delivery status and per-channel configuration, wired into the existing mail.thread / mail.message backbone so a mobile message logs into the same chatter timeline as email and notes. The module defines a mailing.gateway-style connector interface (an abstract base you subclass per provider), outbound send methods, a webhook controller endpoint for inbound and delivery-receipt callbacks, and @api.depends computed fields for message state (queued, sent, delivered, failed). Everything is exposed through the standard XML-RPC/JSON-RPC API so external systems and your other custom modules can enqueue messages programmatically.
Because it is the base, it is built to be extended rather than to lock you in. The __manifest__.py declares clean dependencies (mail, base) and no heavyweight extras, so it installs on Community or Enterprise. Security is real, not an afterthought: dedicated groups plus ir.model.access.csv entries and record rules scope who can view message logs and who can configure gateways — with multi-company record rules where you run more than one company. We include the views (XML list/form for configuration and message logs, an OWL-friendly structure ready for later interactive widgets), an automated action / server-action hook so other modules can trigger sends on state changes, and optional QWeb templates for message-body rendering. The result is a stable, documented contract that your team — or a future ECOSIRE feature module — can build channel-specific behavior on without re-plumbing the fundamentals.
Delivery is build-to-order. After a short scoping call we confirm exact scope in writing — your Odoo version (17.0, 18.0 or 19.0), Community vs Enterprise, which provider gateway you intend to connect, single- vs multi-company, and any data or workflow specifics. We then build against a staging copy of your database, run UAT with you, and only deploy to production with a documented rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company topology, additional provider integrations, deeper localization, and data-migration volume increase the quoted scope. You always get a fixed written quote after the scoping call — never a surprise.
Runs Odoo in-house and wants a clean, documented base layer to build mobile-messaging features on, rather than hacking a one-off script into an existing module. Needs proper models, security and an extension contract they can maintain.
Wants outbound notifications and inbound replies to land on the right Odoo record in the chatter, so the team stops copy-pasting between a phone app and Odoo. Cares about delivery-state visibility and audit trail.
Delivering a project for their own client and needs a reliable, provider-agnostic messaging foundation they can extend per provider. Values the abstract gateway interface, git handover and version compatibility across 17/18/19.
Runs several companies in one Odoo database and needs message logs and gateway credentials scoped per company via record rules, with a base that supports that topology from day one.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| Fit to your setup | Built to your exact version, edition and provider intent | Fully bespoke but you specify and own everything | Generic; you adapt your process to it | |
| Mobile gateway abstraction | Provider-agnostic abstract base class to subclass | Only if you design it that way | Often hard-wired to one provider | |
| Chatter / mail.thread integration | Logs into the record chatter natively | Depends on developer discipline | Varies; sometimes a siloed log | |
| Security model | Dedicated groups, ir.model.access.csv, multi-company record rules | As good as you build it | Baseline access rules, rarely multi-company | |
| Delivery-state tracking | Computed state fields + webhook receipts | Build from scratch | Basic or absent | |
| Extensibility for future features | Documented contract designed to be extended | Yours to maintain | Hard to extend cleanly | |
| Ongoing cost & support | Fixed quote + post-go-live support window | Full dev cost + you own maintenance | Licence/subscription, generic support | |
| Handover | Full source, git repo, docs, training | Whatever your team documents | Compiled/limited-source, docs vary |
No. This is a build-to-order engagement, not an existing marketplace download. ECOSIRE builds the module against your specific Odoo version, edition and requirements, then installs and supports it. You receive installable source code and a git repository, but it is produced for your scope — not pulled off a shelf.
Typical delivery is 2–4 weeks from confirmed scope. The clock starts once we finish the scoping call and you sign off the written scope. Simpler single-company builds land toward the shorter end; multi-company topology, extra provider integrations or data migration extend it.
Pricing starts from $249 as an indicative from-price for a single-company base scope. We never quote a firm price before understanding your setup. After a short scoping call we send a fixed written quote; drivers such as multi-company, additional integrations, localization depth or migration volume adjust it. The indicative price is a starting point, not the final figure.
Every engagement includes a post-go-live support window for defect fixes and configuration questions, plus version-compatibility notes. Because we hand over the full git repository and technical docs, your team can maintain it too. Longer-term maintenance or upgrades to a new Odoo major version can be arranged as a separate scoped engagement.
The base module depends only on core `base` and `mail`, so it installs on both Community and Enterprise. We confirm your edition during scoping and test against it. It is built and validated for Odoo 17.0, 18.0 and 19.0.
The base module is deliberately provider-agnostic — it ships an abstract gateway interface designed to be subclassed per provider. Connecting a specific provider (credentials, endpoint, message format) is done as a channel layer on top of this base, which we scope with you. We describe capability generically; the base gives you the reusable foundation either way.
We build and test on a staging copy of your database, run UAT with you against it, and only then deploy to production — with a documented rollback plan in hand. Additive ORM models and access rules mean the change is contained and reversible.
A build-to-order foundation module that extends Odoo Discuss with the core plumbing to send and receive mobile messages through a provider gateway. ECOSIRE scopes, builds, installs and supports it — this is a made-to-order engagement, not an off-the-shelf download.