Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $149.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Vonage (Nexmo) SMS Gateway for Odoo
A build-to-order Odoo module that routes all SMS through your Vonage (Nexmo) account for global transactional and bulk messaging. ECOSIRE builds, installs, and supports it on your Odoo 17, 18, or 19.
$149.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Overrides Odoo's native SMS transport (`sms.api`/`sms.sms` send path) so all existing SMS features route through Vonage instead of Odoo IAP
Dedicated `vonage.account` model storing API key/secret or JWT application credentials, guarded by `ir.model.access.csv` and record rules
Vonage Messages/SMS API integration with server-side retry, timeout, and per-account rate handling
Inbound delivery-receipt (DLR) webhook controller (JSON-RPC/HTTP route) that writes `delivered`/`failed` + Vonage error code back onto each `sms.sms` record
Bulk-vs-transactional routing: queued cron/scheduled-action batching for campaigns, immediate send for OTPs and order events
Per-country and per-company sender ID configuration, including registered alphanumeric sender IDs where the destination allows
Template support reusing Odoo `mail.template`/QWeb rendering so `${object...}` placeholders resolve identically to email
Order-event automation via Odoo Automated Actions on `sale.order`, `stock.picking`, and `account.move` state changes
Delivery status surfaced in the record chatter and in list/kanban views through a compute/`@api.depends` chain on the message state
Cost/segment awareness: Unicode vs GSM-7 encoding detection and multi-part message segment counting before send
Opt-out / consent handling with a suppression check so blocked numbers are skipped and logged
XML-RPC/JSON-RPC exposure so external systems trigger governed sends through the same Vonage gateway
Configurable send logging and audit trail (payload, Vonage message UUID, response) for troubleshooting and reconciliation
Multi-database/multi-company safe credential scoping so subsidiaries can use distinct Vonage accounts or sender IDs
इस उत्पाद के बारे में
Odoo ships a native SMS layer (the sms.sms model, the "Send SMS" composer, and SMS steps in Marketing Automation), but out of the box it is wired to Odoo's own IAP SMS service. If your organization is already standardized on Vonage (formerly Nexmo) for deliverability, pricing, sender-ID governance, and unified reporting, that native path forces you off your existing carrier relationship, gives you no control over the underlying route, and cannot honor your registered alphanumeric sender IDs or country-specific compliance settings. The moment you need Vonage-specific features — messages-API delivery receipts, per-country sender IDs, or account-level throughput — Odoo's built-in IAP gateway runs out of road.
Vonage (Nexmo) SMS Gateway for Odoo क्यों चुनें
Overrides Odoo's native SMS transport (`sms.api`/`sms.sms` send path) so all existing SMS features route through Vonage instead of Odoo IAP
Dedicated `vonage.account` model storing API key/secret or JWT application credentials, guarded by `ir.model.access.csv` and record rules
Vonage Messages/SMS API integration with server-side retry, timeout, and per-account rate handling
Inbound delivery-receipt (DLR) webhook controller (JSON-RPC/HTTP route) that writes `delivered`/`failed` + Vonage error code back onto each `sms.sms` record
Bulk-vs-transactional routing: queued cron/scheduled-action batching for campaigns, immediate send for OTPs and order events
Per-country and per-company sender ID configuration, including registered alphanumeric sender IDs where the destination allows
We build a dedicated gateway module that overrides Odoo's SMS transport so every message the system already knows how to send — order confirmations, marketing blasts, OTPs, reminders — leaves through the Vonage Messages/SMS API instead of Odoo IAP. Technically, the module extends the sms.api / sms.sms send path and introduces a vonage.account model holding your API key, secret (or JWT application credentials), and default sender ID, all secured with ir.model.access.csv and record rules so only authorized users touch credentials. Outbound calls are made server-side with proper retry and rate handling; Vonage delivery-receipt webhooks are received on a JSON-RPC/controller endpoint and written back to a state field (sent, delivered, failed, with the Vonage error code) via a compute chain so agents see real delivery status in the chatter and in list/kanban views, not just "queued".
On top of the transport we build the pieces your persona actually asked for: a bulk-vs-transactional routing policy (queued through a scheduled action / cron for large sends, immediate for OTPs and order events), sender-ID configuration per country or per company in a multi-company setup, and template support that reuses Odoo's mail.template / QWeb rendering so placeholders like ${object.partner_id.name} resolve exactly as they do for email. Order-event automation is delivered as Odoo Automated Actions (base automation) triggered on sale.order, stock.picking, or account.move state changes, so "your order shipped" texts fire without anyone clicking send. Everything is exposed to your other systems through the standard Odoo XML-RPC/JSON-RPC API, so external apps can trigger sends through the same governed gateway.
Because this is build-to-order, nothing is a shrink-wrapped download. After a short scoping call we confirm exact triggers, sender IDs, target countries, and Odoo edition (Community vs Enterprise changes what Marketing Automation hooks are available), then build against your Odoo 17.0, 18.0, or 19.0. You get the module built for your version, installed and configured against your Vonage account, tested on a staging database, and handed over with source and docs. Typical delivery is 2 to 4 weeks from confirmed scope, and we support it after go-live.
What you get
- Installable module source code built for your exact Odoo version (17.0, 18.0, or 19.0)
- Installation and configuration on your environment, wired to your Vonage (Nexmo) account and sender IDs
- UAT on a staging database with a documented rollback plan before touching production
- Technical documentation: models, security rules, webhook endpoint, and Automated Action triggers
- End-user guide plus one live training session for admins and messaging users
- Post-go-live support window for defect fixes and configuration adjustments
- Private git repository handover with full commit history
- Vonage credential and webhook setup checklist (API key/secret or JWT app, DLR callback URL)
Who this is for
Global SMB standardized on Vonage
A growing business already sending SMS through Vonage/Nexmo for other channels and wanting Odoo to use that same account, sender IDs, and reporting instead of Odoo IAP.
E-commerce / operations lead
Needs automatic order-event texts (confirmed, shipped, delivered) fired from `sale.order` and `stock.picking` transitions without staff manually sending each message.
Marketing manager running SMS campaigns
Wants bulk campaign sends with templated, personalized content and real delivery reporting, while keeping OTP and transactional messages on a separate immediate lane.
Odoo administrator / IT owner
Responsible for credential governance, multi-company sender-ID rules, and integrating external apps via XML-RPC, and needs it done cleanly against the org's Odoo edition and version.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Vonage (Nexmo) SMS Gateway for Odoo module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Vonage (Nexmo) SMS Gateway for Odoo, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Vonage (Nexmo) SMS Gateway for Odoo Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| SMS carrier / routing | Your Vonage (Nexmo) account, your routes and sender IDs | Whatever you wire yourself | Often locked to the vendor's chosen gateway | |
| Built for your Odoo version | Targeted to your 17/18/19, Community or Enterprise | Depends on your team | Generic build, version support varies | |
| Order-event automation | Automated Actions on sale/stock/invoice states | Must be designed and built in-house | Limited or fixed triggers | |
| Delivery receipts (DLR) | Vonage webhook writes real status back to the record | You build the callback handler | Frequently just 'queued', no true DLR | |
| Sender ID governance | Per-country / per-company registered sender IDs | Hand-rolled logic | Usually single global sender | |
| Templates & personalization | Reuses Odoo mail.template/QWeb placeholders | Reimplemented per project | Basic variable substitution | |
| Credential security | Scoped model with ir.model.access.csv + record rules | As secure as you make it | Varies by vendor quality | |
| Support & ownership | Support window + git handover, you own the source | You own and maintain everything | Vendor support tiers, source often closed |
Frequently Asked Questions about Vonage (Nexmo) SMS Gateway for Odoo
How long does delivery take?
This is a build-to-order module, not an instant download. After a short scoping call to confirm triggers, sender IDs, target countries, and your Odoo edition, typical delivery is 2 to 4 weeks from confirmed scope — including build, staging UAT, and installation on your environment.
Which Odoo versions are supported?
We build for Odoo 17.0, 18.0, or 19.0, Community or Enterprise. Because the module is built per engagement, it targets your exact version. Note that some Marketing Automation SMS hooks differ between Community and Enterprise; we confirm that scope during the call.
Do we use our own Vonage account?
Yes. The module sends through your Vonage (Nexmo) account using your API key/secret or JWT application credentials and your registered sender IDs. You keep full control of billing, deliverability, and Vonage-side reporting; nothing routes through Odoo IAP or through ECOSIRE.
How do we get updates and support after go-live?
Every build includes a post-go-live support window for defect fixes and configuration adjustments, plus a private git repository handover so you own the source. Beyond the included window, we offer ongoing support and version-upgrade work (for example migrating the module to a newer Odoo release) as a separate engagement.
Does it replace Odoo's native SMS or add a new one?
It overrides the existing native SMS transport. All the SMS features Odoo already has — the Send SMS composer, marketing SMS, reminders — keep working, but the messages leave through Vonage instead of Odoo IAP, so you don't retrain users or rebuild your flows.
Can it fire SMS automatically on order events?
Yes. We deliver Odoo Automated Actions on models like `sale.order`, `stock.picking`, and `account.move` so texts fire on state changes (confirmed, shipped, invoiced). Content uses Odoo templates so placeholders such as the customer name and order reference are rendered automatically.
Can external systems send through it too?
Yes. The gateway is reachable through Odoo's standard XML-RPC/JSON-RPC API, so your other applications can trigger governed sends through the same Vonage account, sender-ID rules, and logging as messages sent from within Odoo.
कोटेशन का अनुरोध करें
Vonage (Nexmo) SMS Gateway for Odoo
A build-to-order Odoo module that routes all SMS through your Vonage (Nexmo) account for global transactional and bulk messaging. ECOSIRE builds, installs, and supports it on your Odoo 17, 18, or 19.
- Overrides Odoo's native SMS transport (`sms.api`/`sms.sms` send path) so all existing SMS features route through Vonage instead of Odoo IAP
- Dedicated `vonage.account` model storing API key/secret or JWT application credentials, guarded by `ir.model.access.csv` and record rules
- Vonage Messages/SMS API integration with server-side retry, timeout, and per-account rate handling
- Inbound delivery-receipt (DLR) webhook controller (JSON-RPC/HTTP route) that writes `delivered`/`failed` + Vonage error code back onto each `sms.sms` record