Country SMS Gateway Pack (GCC & Africa)

Características clave

Drop-in adapters for Unifonic, Msegat, Mobily.ws, 4jawaly and ksa-sms covering KSA, UAE and wider GCC SMS aggregators

Africastalking adapter for Kenya, Nigeria, Uganda, Tanzania and other sub-Saharan markets

Single SmsTransportInterface service contract — swap the active gateway via di.xml virtual types and Stores → Configuration, no code change

Arabic-script (UCS-2/Unicode) message handling with correct 70-char part counting and multi-part concatenation

Sender-ID / brand-name (alphanumeric originator) configuration per provider, including the registration metadata each aggregator requires

Observers on checkout_submit_all_after and sales_order_save_after for automatic order-placed, shipped and status-change SMS

REST and GraphQL endpoints for OTP send/verify and headless (PWA Studio / Hyvä) checkout flows

Cron-driven balance polling and delivery-report (DLR) reconciliation written back to a dedicated admin grid

Admin ACL resource so SMS settings, logs and credentials are role-restricted; secrets stored via Magento's encrypted core_config_data

Per-store-view configuration so multi-website merchants can route different brands or countries to different aggregators

Retry-with-backoff and provider fallback so a single aggregator outage does not silently drop OTP traffic

Full send/error logging with request IDs for support, plus optional masking of phone numbers in logs for PDPL/GDPR hygiene

Hecho a medida, listo para ti

Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.

Haces el pedido

Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.

Creamos e instalamos

ECOSIRE la crea, la configura y la instala en tu Magento 2.

En marcha + soporte

Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.

Sobre este producto

Magento 2 and Adobe Commerce ship with no native SMS transport — the platform sends transactional notifications by email only. Global SMS extensions on the Adobe Commerce Marketplace almost always assume Twilio, Nexmo/Vonage, or MessageBird, which are expensive, poorly deliverable, or not supported for Sender-ID traffic in Saudi Arabia, the UAE, and much of sub-Saharan Africa. Merchants in those markets buy SMS credit from local aggregators instead — and then discover none of them have a Magento connector.

This is a build-to-order extension. ECOSIRE builds the module against your specific Magento 2 / Adobe Commerce version, installs it on your store (or staging first), wires it to the aggregator account you already hold, and supports it afterwards. It is not an instant Marketplace download — there is an honest delivery lead time while we configure and harden it for your environment.

The pack ships as a proper module under app/code/Ecosire/SmsGateway with a SmsTransportInterface service contract and one adapter per provider — Unifonic, Msegat, Mobily.ws, 4jawaly, ksa-sms, and Africastalking. A di.xml virtual-type pool lets you switch the active gateway in Stores → Configuration without touching code. We register observers on events like checkout_submit_all_after and sales_order_save_after so order-status SMS fires automatically, expose REST/GraphQL endpoints for OTP and headless checkouts, and handle Arabic-script (UCS-2) encoding, multi-part concatenation, and Sender-ID / brand-name registration quirks per provider. A cron job polls balance and delivery reports so failed sends surface in the admin grid behind a dedicated ACL resource. You get the source, a README runbook, and a support window.

lo que obtienes

Custom Magento 2 module (Ecosire_SmsGateway) built and version-matched to your Magento Open Source or Adobe Commerce release, delivered as installable source under app/code

Configured adapters for the specific providers you use (chosen from Unifonic, Msegat, Mobily.ws, 4jawaly, ksa-sms, Africastalking)

Installation on your environment — staging first where available — with bin/magento setup:upgrade, di:compile and cache flush performed by ECOSIRE

Sender-ID / brand-name setup guidance and the per-provider registration metadata wired into configuration

Admin configuration walkthrough plus a README runbook covering credentials, fallback order, cron and DLR reconciliation

Post-delivery support window for bug fixes and a Magento minor-version compatibility check

¿Para quién es esto?

GCC eCommerce merchant on Adobe Commerce

A Saudi or UAE retailer who must send OTP and order SMS through Unifonic, Msegat or Mobily because Twilio/Vonage Sender-ID traffic is restricted locally, and needs those aggregators wired into Magento cleanly.

Pan-African store operator

A merchant across Kenya, Nigeria or Uganda using Africastalking for low-cost local SMS who wants automatic order and delivery notifications plus OTP without paying for a custom build.

Magento agency or systems integrator

A partner delivering a GCC/Africa storefront who needs a ready, service-contract-based SMS layer they can hand off, rather than estimating a from-scratch integration for every regional aggregator.

Cómo se compara Country SMS Gateway Pack (GCC & Africa)

Criterio	ECOSIRE	Construcción personalizada	Competidor
Native connectors for GCC aggregators (Unifonic, Msegat, Mobily, 4jawaly)	Incluido	Apoyo parcial	No incluido
Africastalking connector for sub-Saharan markets	Incluido	Apoyo parcial	No incluido
Arabic-script (UCS-2) encoding & multi-part counting	Incluido	Apoyo parcial	Apoyo parcial
Sender-ID / brand-name registration support	Incluido	Apoyo parcial	Apoyo parcial
Service-contract / di.xml architecture (swap gateway via admin)	Incluido	Apoyo parcial	Apoyo parcial
REST & GraphQL endpoints for OTP / headless checkout	Incluido	Apoyo parcial	Apoyo parcial
Balance & delivery-report (DLR) polling via cron	Incluido	Apoyo parcial	Apoyo parcial
Installed, configured & supported on your store by the vendor	Incluido	No incluido	No incluido
Instant self-serve download (no lead time)	No incluido	No incluido	Incluido

Preguntas frecuentes sobre Country SMS Gateway Pack (GCC & Africa)

How long does delivery take, since this is build-to-order?

This is not an instant Marketplace download. After purchase we confirm your Magento 2 / Adobe Commerce version, which aggregators you use, and your account details. Typical delivery is a few business days for a single-provider, single-store setup, longer for multi-website routing, custom OTP flows or Sender-ID registrations that depend on aggregator approval timelines. We give you a concrete date during onboarding before any work starts.

What do I get for ongoing support and updates after install?

The one-time price includes a post-delivery support window for bug fixes and a compatibility check against your next Magento minor upgrade. We hand over the full module source and a README runbook so your team or agency can maintain it. Longer-term retained support, new-provider additions, or major-version migration (for example Magento 2.4.x to a future 2.5) are quoted separately as small change requests.

Does Magento have any native SMS feature this replaces?

No. Magento Open Source and Adobe Commerce send transactional notifications by email only and have no built-in SMS transport. This module adds that layer through a proper SmsTransportInterface service contract and event observers, rather than bolting on inline cURL calls.

Which providers are included, and can you add one that isn't listed?

The pack covers Unifonic, Msegat, Mobily.ws, 4jawaly, ksa-sms and Africastalking. Because every adapter implements the same SmsTransportInterface, adding another aggregator (for example a different African gateway with an HTTP API) is a contained change we can scope as an add-on rather than a rebuild.

Will it work with a headless or Hyvä storefront?

Yes. SMS sending is triggered server-side through observers and a service contract, so it is independent of the frontend theme. For OTP and custom flows we expose REST and GraphQL endpoints, which is exactly what PWA Studio, Hyvä Checkout or a custom headless frontend needs.

How are Arabic messages and Sender IDs handled?

Arabic and other non-Latin text is encoded as UCS-2/Unicode, so the module counts message length at 70 characters per part (not 160) and concatenates multi-part messages correctly. Alphanumeric Sender-ID / brand-name originators are configured per provider, including the registration metadata each GCC aggregator requires before alphanumeric traffic is approved.