WhatsApp + SMS OTP & Transactional Notifications

This is a build-to-order module, not an instant download. Typical lead time is 2–4 weeks depending on how many events and which provider you need. After purchase we scope your triggers, provider and templates in a short kickoff, build against your Odoo 17/18/19 (Community or Enterprise) database, test in a staging copy, then install and verify go-live with a real test number. You receive the source code, documentation and a training session at handover.

A 30-day post-delivery support window is included by default, covering bug fixes and configuration adjustments (new templates, tweaked rate limits, event changes). Because you receive the full source, you own the module. We offer optional extended support and SLA plans, and paid version-migration when you upgrade your Odoo major version — the code is written to be upgrade-friendly, but provider APIs and Odoo internals do change over time.

We build against a provider abstraction layer and wire the gateway you prefer: Meta WhatsApp Business Cloud API for WhatsApp, and Twilio, Vonage, MessageBird or a regional SMS gateway for the SMS fallback. You do need your own WhatsApp Business / provider accounts and approved message templates (we guide you through template approval). Provider messaging fees are billed by them directly, not by ECOSIRE.

Every notification attempts your primary channel first (usually WhatsApp). If WhatsApp returns an error, the destination number isn't WhatsApp-enabled, or no delivery confirmation arrives within a configurable window, the module automatically re-sends the same templated message over SMS. An ir.cron scheduled action also handles retries with backoff, and each attempt is recorded in the message log with its channel and status.

OTP codes are never stored in plain text — the otp.request model keeps a salted hash, an expiry timestamp and an attempt counter, and verification compares against the hash. Access is locked down with ir.model.access.csv and record rules so only authorized users can view OTP records and message logs. Rate limiting per number and per event prevents brute-force and abuse, and provider credentials live in configuration rather than in code.

Yes. The module exposes XML-RPC/JSON-RPC methods to generate, send and verify OTPs from an external storefront, mobile app or middleware. It is multi-company and multi-language aware: messages respect company boundaries through record rules, and QWeb templates render in the recipient partner's language automatically.