One Odoo SMS framework routing through Twilio, Vonage, Plivo, MessageBird, Telnyx, TeleSign & D7 with failover and least-cost routing. One-time license from $199.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

One Odoo SMS framework routing through Twilio, Vonage, Plivo, MessageBird, Telnyx, TeleSign & D7 with failover and least-cost routing.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Odoo's native SMS gateway is single-provider by design: one IAP account, one route, one point of failure. If your primary provider throttles you, blocks a destination country, or has an outage, your OTPs, order alerts, and marketing blasts simply stop — and there is no built-in way to fall back or shop for a cheaper route per destination.
Pluggable provider framework — each gateway (Twilio, Vonage, Plivo, MessageBird, Telnyx, TeleSign, D7) is a self-contained `sms.gateway.provider` record with its own REST adapter, so new providers drop in without touching core dispatch code
Automatic failover: if the primary gateway returns an error, times out, or its balance hits zero, the routing engine retries the same message through the next healthy provider in priority order
Least-cost routing — a `sms.gateway.route` rate table matches the destination country/prefix and selects the cheapest eligible provider per message, logging the chosen route and unit cost
Per-country sender ID configuration: alphanumeric or numeric sender IDs mapped by destination (e.g. branded ID for UAE, long code for US) to satisfy each country's registration rules
Unified template layer built on Odoo's `sms.template` with placeholder rendering, so the same message body works no matter which gateway ultimately sends it
Consolidated delivery log (`sms.gateway.log`) capturing provider, route, cost, segment count, status, provider message ID, and error reason for every single outbound SMS
Multi-Provider SMS Gateway Hub replaces that single lane with a pluggable routing framework. ECOSIRE builds a custom Odoo module (sms_gateway_hub) that introduces a provider-abstraction layer on top of Odoo's sms.sms / sms.api stack, so every outbound message — transactional or bulk — is dispatched through a routing engine that evaluates health, cost, and per-country rules before it picks a gateway. Seven providers ship connected out of the box: Twilio, Vonage, Plivo, MessageBird, Telnyx, TeleSign, and D7, each implemented as a discrete sms.gateway.provider record with its own credentials, sender IDs, and REST adapter.
This is not an off-the-shelf apps.odoo.com download. It is a BUILD-TO-ORDER engagement: ECOSIRE scopes your provider mix, sender-ID and country requirements, and your existing SMS touchpoints, then builds, installs, and hands over a production-ready module tuned to your Odoo database. Typical delivery is 2–4 weeks depending on the number of gateways and any custom triggers you need wired in.
Architecturally the module is idiomatic Odoo. New models (sms.gateway.provider, sms.gateway.route, sms.gateway.log, sms.gateway.template) are declared with models.Model; computed fields such as live balance and rolling success rate use @api.depends; access is locked down with ir.model.access.csv plus record rules so only SMS administrators can edit credentials while agents can only read logs. Backend screens are standard XML/OWL views with a routing dashboard, and delivery reports render through QWeb. Because dispatch is intercepted at the sms.api layer, every existing SMS trigger you already use — automated actions, marketing SMS campaigns, portal OTP, sale/invoice confirmations — starts flowing through the hub with zero changes to those flows. An XML-RPC/JSON-RPC surface lets external systems queue messages into the same routing engine.
The result: provider redundancy so a single outage never silences you, least-cost routing so you stop overpaying on international traffic, and one unified template and log layer so compliance and support finally see every message in one place. Works on Odoo 17, 18, and 19, Community or Enterprise.
Runs Odoo across multiple countries and cannot afford OTPs and order alerts going dark when one SMS provider throttles or has an outage. Wants provider redundancy and a single place to see every message's delivery status.
Sends bulk promotional and lifecycle SMS at scale and is tired of overpaying on international routes. Wants least-cost routing, scheduled campaigns with quiet-hour windows, and per-country sender IDs that actually get delivered.
Depends on SMS OTP and fraud alerts where a failed message is a lost login or a security gap. Needs automatic failover, DLR-backed proof of delivery, and rate-limit-aware dispatch that keeps transactional traffic flowing.
Buy the license on ecosire.com and download the Multi-Provider SMS Gateway Hub 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-Provider SMS Gateway Hub, 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 |
|---|---|---|---|---|
| Multiple SMS providers in one system | Seven providers connected, add more anytime | Whatever you pay to build, one at a time | Usually one provider per app | |
| Automatic failover on outage or throttle | Yes — auto-retry via next healthy gateway | Only if explicitly built | Rare — no cross-provider fallback | |
| Least-cost routing per destination country | Yes — rate table picks cheapest eligible route | Possible but expensive to build | No | |
| Per-country sender ID configuration | Yes — mapped and registered per destination | Depends on scope | Limited to that provider's options | |
| Unified template & delivery log across providers | Yes — one log, one template layer, with DLR | You build and maintain it | Per-app, not consolidated | |
| Works on existing Odoo SMS triggers with no reconfig | Yes — intercepts at sms.api layer | Depends on implementation | Varies; often needs rewiring | |
| XML-RPC / JSON-RPC access for external systems | Yes | Only if built | Rare | |
| Odoo 17 / 18 / 19, Community & Enterprise | All three versions, both editions | Whatever you target | Varies by listing | |
| Ownership, support & documented handover | Full source + runbook + support window | You own it but self-support | Vendor-locked, ticket support |
This is a build-to-order module, not an instant download. Typical lead time is 2–4 weeks from kickoff, depending on how many gateways you use and whether you need custom triggers wired in. The process: (1) a scoping call to confirm your provider mix, target countries, and sender-ID needs; (2) ECOSIRE builds `sms_gateway_hub` against your Odoo version; (3) we install it on your server or Odoo.sh and run real test sends through each gateway; (4) go-live plus a handover training session. You never receive a half-built module — we deploy a tested, production-ready system.
Every engagement includes a defined post-go-live support window covering bug fixes, provider-credential adjustments, and compatibility with Odoo minor-version updates on your installed major version (17, 18, or 19). Within that window we fix defects at no extra charge. After it ends, you can move onto an ongoing ECOSIRE support and maintenance plan, or take the source code and self-maintain — the module is yours, fully commented, and documented with a runbook.
It works on both Community and Enterprise, on Odoo 17, 18, and 19. The hub sits on top of Odoo's standard `sms.sms` / `sms.api` framework, which exists in Community, so you are not forced onto Enterprise. If you use Enterprise-only features like Marketing SMS campaigns, those route through the hub automatically as well.
They keep working. Because dispatch is intercepted at the `sms.api` layer, every SMS you already trigger — automated actions, portal OTP, sale/invoice confirmations, marketing SMS — starts flowing through the routing engine with no changes to those flows. You configure providers and routes once; the rest of Odoo doesn't know or care which gateway ultimately sends the message.
For each message, the routing engine matches the destination country/prefix against your `sms.gateway.route` rate table to find eligible providers, then picks by your chosen strategy — lowest cost, or strict priority. If the selected gateway errors, times out, or is out of balance, the message is automatically retried through the next healthy provider. Every decision (chosen provider, route, unit cost, and any failover) is written to the delivery log so you can audit exactly what happened.
Yes. The module exposes an XML-RPC / JSON-RPC endpoint so external applications — or a second Odoo instance — can enqueue messages into the same routing engine. They get the same failover, least-cost routing, and unified logging without needing to integrate with any individual provider's API directly.
Yes. The provider layer is deliberately pluggable — each gateway is an independent adapter record. If you need a regional aggregator or an in-house SMPP route in addition to Twilio, Vonage, Plivo, MessageBird, Telnyx, TeleSign, and D7, we scope and build that adapter as part of the engagement or as a follow-up. Tell us during scoping and we'll price it in.
One Odoo SMS framework routing through Twilio, Vonage, Plivo, MessageBird, Telnyx, TeleSign & D7 with failover and least-cost routing.