GCC retailers and service firms running ERPNext quickly hit a wall when they try to message Arabic-speaking customers at scale. ERPNext core ships a generic Notification and SMS Settings framework and a basic WhatsApp integration, but none of it is tuned for the Gulf: there is no first-class Arabic RTL template handling, no awareness of UAE TDRA / KSA CITC sender-ID registration rules, no structured consent and opt-out ledger to satisfy local data and marketing regulations, and no adapter layer for the regional BSPs and SMS gateways your customers actually route through. Teams end up bolting together freehand server scripts, manual opt-out spreadsheets, and hard-coded gateway credentials — fragile, non-auditable, and risky the moment a regulator or the BSP asks for proof of consent.

ECOSIRE builds the GCC WhatsApp & SMS Compliance Pack as a proper Frappe app (its own module, DocTypes, and hooks.py) installed onto your bench alongside ERPNext. At its core are dedicated DocTypes: a bilingual Message Template (AR/EN body, RTL-aware rendering, WhatsApp template category and header/body/footer components), a Messaging Channel that stores per-provider gateway config and the registered sender ID / WhatsApp phone-number ID, a Consent Log that records opt-in source, timestamp, and channel, and an Opt-Out Registry that is checked before every send. Sending is wired through hooks.py doc events and scheduler events so campaign and transactional messages fire on ERPNext lifecycle triggers (for example a Sales Invoice submit or Delivery Note status change), and whitelisted methods expose a clean server-side send API. A pluggable adapter layer normalizes regional BSP/gateway APIs behind one interface, so the same template can dispatch over WhatsApp or SMS depending on channel availability and consent.

Compliance is engineered in rather than assumed. Every outbound message is gated against the Opt-Out Registry and the Consent Log via a before_save / pre-send hook, unsubscribe keywords (Arabic and English) are parsed from inbound webhooks and written back to the registry automatically, and sender-ID / template registration helpers guide operators through the UAE and KSA approval workflows and store the approved IDs against the channel. Role profiles and DocType permissions separate who can edit templates, who can launch a bilingual campaign, and who can read the consent audit trail. Delivery receipts and failures are logged per message so you have an exportable record for both the BSP and any regulator. Client scripts add RTL-correct previews in the ERPNext desk, and the Frappe REST API lets your storefront or POS trigger sends programmatically.

Because this is build-to-order, nothing is shipped blind. We start with a short scoping call to confirm your GCC markets, chosen BSP/SMS gateways, the ERPNext events you want to trigger on, and your v15 or v16 target. We then build your version of the app, install and configure it on a staging bench, run UAT with your real templates and test numbers, and hand over installable source, documentation, a git repository, and a training session before go-live. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window.