GCC WhatsApp & SMS Compliance Pack

Key Features

Bilingual (AR/EN) Message Template DocType with RTL-aware rendering and WhatsApp header/body/footer component structure

Consent Log DocType capturing opt-in source, channel, and timestamp for an auditable marketing-consent trail

Opt-Out Registry checked in a pre-send hook so every WhatsApp/SMS dispatch is suppressed for opted-out numbers

Automatic inbound unsubscribe parsing (Arabic and English STOP keywords) via BSP webhook, written back to the registry

UAE TDRA and KSA CITC sender-ID and WhatsApp template registration helpers, storing approved IDs against each channel

Pluggable BSP/gateway adapter layer normalizing regional providers behind a single whitelisted send interface

hooks.py doc-event triggers to send transactional messages on ERPNext events (e.g. Sales Invoice submit, Delivery Note status)

Scheduler events for time-based bilingual campaign dispatch and delivery-status reconciliation

Whitelisted server methods exposing a clean REST-callable send API for storefront/POS integration

Per-message delivery-receipt and failure logging with exportable records for BSP and regulator audits

Role profiles and DocType permissions separating template editing, campaign launch, and consent-audit read access

Client scripts adding RTL-correct message previews and channel/consent validation in the ERPNext desk

Template variable binding to ERPNext fields (Customer, Contact, Sales Order) with AR/EN fallback resolution

Compatible with Frappe/ERPNext v15 and v16, installed as a standalone app on your bench

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2-4 weeks from confirmed scope, followed by a post-go-live support window.

What you get

Installable source code for your version of the app (Frappe app installable on your bench)

Installation and configuration on your staging and production ERPNext v15/v16 sites

Technical documentation: DocTypes, hooks, scheduler events, adapter interface, and REST endpoints

End-user guide plus a live training session for template editors and campaign operators

UAT on a staging bench with your real templates/test numbers, plus a documented rollback plan

Post-go-live support window for defect fixes and configuration assistance

Git repository handover with full commit history and branching

BSP/gateway and sender-ID registration configuration walkthrough for your chosen GCC providers

Who this is for

GCC retail marketing manager

Runs WhatsApp and SMS promotions to Arabic-speaking customers and needs bilingual templates, sender-ID compliance, and a defensible consent record without spreadsheets.

ERPNext administrator / IT lead

Owns the ERPNext v15/v16 site and wants messaging built as a clean app with proper DocTypes, permissions, and hooks — not fragile ad-hoc server scripts.

Compliance / operations officer

Accountable for UAE/KSA marketing and data rules; needs an auditable opt-in/opt-out ledger and exportable delivery logs to answer BSP and regulator queries.

Customer service / dispatch team lead

Sends transactional order and delivery updates triggered from ERPNext events and needs reliable, receipt-tracked WhatsApp/SMS with Arabic content.

How GCC WhatsApp & SMS Compliance Pack Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Arabic RTL templates	Bilingual AR/EN Message Template DocType with RTL-aware rendering	Possible but hand-built per template	Usually English-first, weak RTL handling	Generic notifications, no first-class RTL
Sender-ID registration (UAE/KSA)	Guided TDRA/CITC helpers, approved IDs stored per channel	Manual process you script yourself	Rarely GCC-aware	Not addressed
Consent & opt-out compliance	Consent Log + Opt-Out Registry gated on every send	DIY, often spreadsheet-based	Basic unsubscribe at best	No structured consent ledger
Regional BSP/gateway support	Pluggable adapter built for your chosen providers	One-off integration per gateway	Fixed to the vendor's provider list	Generic SMS Settings only
ERPNext event triggers	hooks.py doc events + scheduler events + whitelisted API	Freehand server scripts to maintain	Limited or opaque triggers	Notification framework, limited scope
Fit to your v15/v16 site	Built and UAT-tested against your exact version	Depends on your team's Frappe depth	Generic, may lag ERPNext versions	Ships with ERPNext
Audit & delivery logging	Per-message receipts, exportable for BSP/regulator	Build and maintain yourself	Vendor dashboard, limited export	Minimal logging
Ownership & support	Source + git handover, docs, training, support window	You own it and all maintenance	Subscription; no source access	Community support only

Frequently Asked Questions about GCC WhatsApp & SMS Compliance Pack

Is this a ready-made app I can download and install today?

No. The GCC WhatsApp & SMS Compliance Pack is build-to-order. ECOSIRE builds your version around your GCC markets, chosen BSP/SMS gateways, and ERPNext triggers, then installs and configures it on your site. There is no instant-download package.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The timeline depends on how many markets and gateways you use, how many templates and ERPNext trigger events are in scope, and BSP/sender-ID approval turnaround on your side. We confirm dates after the scoping call.

Which WhatsApp providers and SMS gateways do you support?

The app uses a pluggable adapter layer, so we integrate the regional BSP or SMS gateway you already use (or plan to use) in the UAE, KSA, or Qatar. We confirm the exact providers during scoping and build the adapter for them as part of your version.

How does it keep us compliant with GCC sender-ID and consent rules?

Sends are gated against a Consent Log and Opt-Out Registry via a pre-send hook, inbound Arabic/English unsubscribe keywords auto-update the registry, and sender-ID/template registration helpers guide UAE TDRA and KSA CITC approval and store the approved IDs. Every message is logged with a delivery receipt for audit.

Which ERPNext versions does it support?

We build for Frappe/ERPNext v15 and v16. Tell us your exact site version during scoping and we target it; the app installs as a standalone Frappe app on your bench alongside ERPNext.

What support and updates do we get after go-live?

Delivery includes a post-go-live support window for defect fixes and configuration help, plus a git repository handover so you own the code. Longer-term maintenance, new gateway adapters, or feature additions can be arranged as a separate engagement.

Can it trigger messages automatically from ERPNext transactions?

Yes. It hooks into ERPNext doc events (for example Sales Invoice submit or Delivery Note status changes) and scheduler events, and exposes whitelisted REST-callable methods so your storefront or POS can trigger sends programmatically.