# E-commerce and retail messaging over SMS, WhatsApp and RCS - Canonical URL: https://www.broadnet.me/solutions/ecommerce-retail - Language: en - Last updated: 2026-10-01 - Publisher: BroadNet (https://www.broadnet.me) - Markdown version of the page above, generated from the rendered page. Conversion on every channel. The orders, the shipping updates, the carts that almost made it, the loyalty tier you just unlocked — every retail moment is a message. BroadNet ships them on the channel each customer actually opens, with the fallback rules and compliance baked in. [Improve order notifications](https://www.broadnet.me/contact?topic=order-notifications&industry=retail) [Build omnichannel retail journeys](https://www.broadnet.me/contact?topic=retail-journeys&industry=retail) Live retail traffic on BroadNet Order events Shipping Marketing Support ![The BroadNet snow leopard striding beside a stream of glowing parcels heading to shoppers' phones](https://www.broadnet.me/marketing/solutions/sol-ecommerce.webp) BroadNet · e-commerce Commerce journeys 300M+ messages / day 200+ countries 99.99% SLA Retailers, marketplaces, and logistics teams sending on BroadNet [See customer stories →](https://www.broadnet.me/customers) Regional ecommerce marketplace Cross-border retail group Large logistics platform Pan-MENA airline High-volume fintech platform Multinational hospitality brand Tier-1 GCC operator African mobile operator group For commerce engineering ## One API. Every shopper channel. Order confirmations, RCS shipping cards, cart-recovery flows and checkout OTPs share a single REST surface. Channel selection, consent and STOP-keyword handling are decided at the edge — per shopper, per template, on every send. Meta WA BSP · Google RBM partner Unified consent ledger POST · api.broadnet.me/sms/sendSms Example ``` 1# Order confirmation2curl -X POST https://api.broadnet.me/sms/sendSms \3 -H "Authorization: Bearer $BROADNET_TOKEN" \4 -H "Content-Type: application/json" \5 -d '{6 "senderId": "MyShop",7 "destinationNumber": "447700900123",8 "message": "Order N-77182 confirmed (3 items, AED 428.00). Track: https://shop.example/t/77182",9 "messageType": "TEXT"10 }'11 12# → 200 OK — the response body is the message ID, e.g. 2603121407537573731 ``` The retail message stack ## Six moments that move the metric. Retail messaging isn't one flow — it's a portfolio. Each moment has a different channel logic, a different latency budget, and a different definition of success. BroadNet ships them as composable building blocks, not a black box. Journeys triggered by Shopify, Magento and WooCommerce order events Channel fallback rules configurable per use case Local-language templates auto-translated & reviewed ### Order confirmation The first message after checkout. Branded sender, deep link to receipt, alternative channel fallback if SMS doesn't land within 12 seconds. SMS WhatsApp Fallback if SMS doesn't land ### Shipping & delivery Picked → dispatched → out-for-delivery → delivered. Driver name and live ETA via WhatsApp; SMS where the customer hasn't opted in to chat. WhatsApp RCS SMS Live ETA in the chat ### Cart abandonment recovery Timed nudges 1h, 6h, 24h after drop-off — each one branded, each one with a one-tap return to checkout. Stop after the customer engages. WhatsApp SMS One-tap return to checkout ### Marketing campaigns Segment by RFM and channel preference, schedule by local sending window, throttle to operator capacity. RCS where supported for rich product cards. RCS WhatsApp SMS Throttled to operator capacity ### Loyalty rewards Tier upgrades, point balances, exclusive previews. Personalised down to product affinity — sent only when the message earns the open. WhatsApp SMS Personalised to product affinity ### Customer support (WhatsApp) Two-way conversational support with quick replies, list pickers, agent handover. Bot resolves the easy questions; humans handle the rest. WhatsApp Bot first, human handover On-device previewWhatsApp Business ## See exactly what your customer sees, the moment it arrives. Illustrative example — sample content, not a real customer message. Aster Souq 9:41 AS Aster Souq online Today Cart reminder sent by SMS · continued on WhatsApp Hi Layla 👋 You left 2 items in your cart. Here's 10% off to finish up — code SAVE10, today only. 9:41 AM Wireless Earbuds Pro Active noise cancelling · 30h battery SAR 249.00 Buy now View cart 9:41 AM Buy now 9:42 AM Message Customer story · GCC marketplace ## From a patchwork of SMS vendors to one orchestrated stack. A regional marketplace was running order confirmations on one aggregator, OTPs on another, marketing on a third, and WhatsApp direct with Meta. Receipts were inconsistent. Compliance reporting was manual. The product team couldn't experiment. They consolidated on BroadNet. One contract, one dashboard, one SLA. Order confirmation moved to a WhatsApp-first journey with SMS fallback. Cart recovery got a 1h / 6h / 24h cadence with automatic stop-on-conversion. Support migrated to the WhatsApp Business API with an agent handover from their existing helpdesk. [Read more customer stories](https://www.broadnet.me/customers) [Build omnichannel retail journeys](https://www.broadnet.me/contact?topic=retail-journeys&industry=retail) The stack One stack. Every retail message. Channels in use SMS WhatsApp RCS Retail & marketplace customers ## What the channel mix does to the unit economics. Regional ecommerce marketplace Marketplace · MENA AE SA EG **Challenge** SMS-only order confirmations capped delivery NPS and left no two-way path for shoppers. **Approach** Order updates moved to a WhatsApp-first flow with BroadNet's channel selector deciding per shopper on consent and device capability. VP logistics communications (reference under NDA) Southeast Asian ecommerce marketplace Marketplace · APAC ID **Challenge** The 'out for delivery' moment was a plain text message with low shopper engagement. **Approach** Live-courier RCS cards replaced text in markets with broad Android RCS support, with SMS fallback elsewhere. Director, product engineering (reference under NDA) Southern African supermarket group Retail · Southern Africa ZA **Challenge** Scaling up marketing sends under a national privacy regime risked complaint escalations. **Approach** SMS, WhatsApp Business and email run through one consent ledger, with STOP keywords honoured in every language the brand sends in. Head of CRM (reference under NDA) Channel mix ## One channel doesn't fit every moment. SMS for the receipts. WhatsApp for the conversations. RCS for the campaigns. BroadNet's omnichannel engine picks the right one per message, per market, per customer — with deterministic fallback when delivery falters. [SMS The universal receipt. Order confirmations, OTPs, dispatch notifications. Lands on every handset, no app required. Cheapest per message at scale. Failover behaviour Always-on fallback for WhatsApp and RCS Channel details](https://www.broadnet.me/products/a2p-sms) [WhatsApp Business Two-way, conversational. Support, cart recovery, post-purchase nudges, loyalty. Quick replies, list pickers, agent handover, rich receipts and shipping cards. Failover behaviour Falls back to SMS after 12s if undelivered Channel details](https://www.broadnet.me/products/whatsapp-business-api) [RCS Business Rich product cards. Marketing carousels, product launches, branded sender with logo and verified badge on Android. Higher CTR than SMS where supported. Failover behaviour Auto-degrade to SMS for non-RCS handsets Channel details](https://www.broadnet.me/products/rcs-messaging) How shopper notifications route ## From order placed to the shopper's preferred channel. The channel selector evaluates consent, device capability and operator quality on every send — and picks the cheapest channel that satisfies the experience. STOP keywords are honoured within sixty seconds across SMS, WhatsApp and RCS. 1. 01 · Order Order system Magento, Shopify, Salesforce Commerce, or in-house OMS emits the event. Order ref + locale + consent flags only. p50 < 25ms 2. 02 · Edge BroadNet edge Auth + idempotency check. Template lookup. Per-shopper consent and STOP-keyword ledger validated before routing. p50 < 35ms 3. 03 · Selector Channel selector Picks cheapest channel that satisfies UX: RCS where the device supports it, WhatsApp where opted-in, SMS fallback always. p50 < 8ms 4. 04 · Carrier Operator / Meta SMPP for SMS, WhatsApp Cloud API for WA, RBM for RCS. SMS rides direct operator binds in 86 countries and labelled partner routes elsewhere — no grey routes. p50 < 1.4s 5. 05 · Shopper Shopper + reply Message delivered. Two-way replies (TRACK, STOP, support questions) route back to your OMS or helpdesk via webhook. p50 < 2.4s 6. ← shopper reply · STOP / TRACK / support · webhook to OMS 01 · Order Order system Magento, Shopify, Salesforce Commerce, or in-house OMS emits the event. Order ref + locale + consent flags only. p50 < 25ms 02 · Edge BroadNet edge Auth + idempotency check. Template lookup. Per-shopper consent and STOP-keyword ledger validated before routing. p50 < 35ms 03 · Selector Channel selector Picks cheapest channel that satisfies UX: RCS where the device supports it, WhatsApp where opted-in, SMS fallback always. p50 < 8ms 04 · Carrier Operator / Meta SMPP for SMS, WhatsApp Cloud API for WA, RBM for RCS. SMS rides direct operator binds in 86 countries and labelled partner routes elsewhere — no grey routes. p50 < 1.4s 05 · Shopper Shopper + reply Message delivered. Two-way replies (TRACK, STOP, support questions) route back to your OMS or helpdesk via webhook. p50 < 2.4s Compliance & trust ## Consent and residency, enforced on every send. Retail messaging lives and dies on consent. BroadNet runs a single consent ledger across SMS, WhatsApp and RCS — STOP keywords honoured within sixty seconds, per-market quiet hours enforced at the edge, and data-residency options across the UAE, KSA and EU. Checkout and refund links carry tokenised references, never card data. ISO 27001 GDPR + UAE PDPL Delivery logs [Compliance overview](https://www.broadnet.me/compliance) Integrations ## Plug into the storefronts you already run. Connect the platforms that move retail inventory through their order webhooks and the BroadNet REST API. Prove your first journey on test access and keep your existing checkout untouched. Shopify Webhooks + REST API Webhooks + API Subscribe to Shopify order, fulfilment and checkout webhooks; your handler calls the BroadNet REST API to send the SMS or WhatsApp post-purchase message. Magento Open Source & Adobe Commerce Webhooks + API A Magento 2 observer on order and shipment events calls the REST API for transactional SMS and abandoned-cart reminders, per store view and language. WooCommerce Order-status hooks Webhooks + API A WooCommerce order-status hook or webhook calls the REST API for order confirmation, shipping and recovery messages, with your own branching by country and order value. [See all integrations](https://www.broadnet.me/integrations) Questions retail buyers ask ## Eight answers, benchmarked across MENA marketplaces. WhatsApp Business charges per delivered template message. Since 1 October 2026 Meta also bills utility templates and replies sent while a shopper's 24-hour service window is open per message, at the market's utility rate; free-form replies are billed only after a free tier of 1,000 service messages per business phone number per month (both were free until 30 September 2026). Utility rates sit below Marketing on Meta's rate card, which keeps two-way flows like delivery updates with shopper replies economical, and competitive with premium A2P SMS for one-way utility messages. We pass through Meta's per-market rate card with no markup and surface a per-shopper unit-economics report so your finance team can model channel mix. Yes. RCS Business Messaging is live across operators in UAE (e&, du), KSA (STC, Mobily, Zain), Egypt (Orange, Vodafone) and most major Android estates globally via Google's RBM platform. We render carousel cards, suggested actions, calendar invites and verified-sender badges. Devices without RCS support fall back automatically to a plain SMS variant of the same template — no developer effort required. Per shopper, per template, evaluated at send time. The channel selector picks the cheapest channel that satisfies: (1) the shopper's explicit channel preference, (2) the consent class required by the template (utility vs marketing), (3) device capability (RCS-capable handset), and (4) the operator's current quality metrics. Decisions are logged so you can A/B test policies or override per-segment. Unified consent ledger keyed to shopper MSISDN. STOP, UNSUB, إلغاء, ARRET, KESH and 30+ other localized opt-out keywords are honoured within 60 seconds across every channel — even if the opt-out arrives on a different channel than the original send. Re-opt-in flows are supported and audited. We expose the consent ledger via API so it can mirror into your CRM. Yes, through webhooks and the REST API. Shopify, Magento 2, Salesforce Commerce Cloud and headless stacks (commercetools, Saleor, in-house) send order and fulfilment events to an endpoint you host, which calls the BroadNet REST API. BroadNet does not publish marketplace apps for these platforms: ask for the setup guide and we will walk your team through event mapping, templates and test access. Per-shopper frequency caps and quiet-hours windows are enforced at the edge — both globally per shopper and per template family. During seasonal peaks our predictive throttler also down-weights non-essential sends if delivery quality on the destination operator dips, so transactional messages (order, OTP, delivery) always get priority over promotional ones. You set the policy; we enforce it message-by-message. Lift depends on channel, offer and audience, so we don't quote a benchmark. WhatsApp Business templates with one-tap checkout and RCS rich cards with imagery give shoppers a richer, tappable path back than an SMS-only nudge. We provide an attribution webhook that ties recovered orders back to the message ID so your growth team can measure lift on your own traffic. Inbound messages on WhatsApp Business and RCS are routed to your helpdesk via webhook — Zendesk, Freshdesk, Intercom, Salesforce Service Cloud and Kustomer are all pre-integrated. Conversation context (last 30 days), order history and shopper profile are passed through so agents pick up mid-thread. AI-assisted triage and translation between Arabic / English / French are available on the Conversations tier. Need a channel-mix or unit-economics review? [Build omnichannel retail journeys →](https://www.broadnet.me/contact?topic=retail-journeys&industry=retail) ![Carrier-grade messaging coverage across global industries](https://www.broadnet.me/marketing/generated/viz-coverage.png) Built for your industry ## Your industry, on a carrier-grade network. Compliant, reliable messaging tuned to your sector — across MENA, Africa and Asia. 200+ Countries 60,000+ Enterprises Since 2003 Operator-direct [Talk to sales](https://www.broadnet.me/contact) Built for retail since 2003 ## Make every retail message a conversion. A reply to your test-access request within one business day, a working WhatsApp post-purchase journey soon after, and a retail specialist on the line in your timezone. [Improve order notifications](https://www.broadnet.me/contact?topic=order-notifications&industry=retail) [Build omnichannel retail journeys](https://www.broadnet.me/contact?topic=retail-journeys&industry=retail) $ curl -X POST https://api.broadnet.me/sms/sendSms -H "Authorization: Bearer $BROADNET_TOKEN" -d '{ "senderId": "BroadNet", "destinationNumber": "447700900123", "message": "Your order has shipped", "messageType": "TEXT" }' Related guides & answers Go deeper on the concepts behind this product. [How do I send bulk SMS Read](https://www.broadnet.me/answers/how-to-send-bulk-sms) [SMS marketing vs transactional SMS — what's the difference Read](https://www.broadnet.me/answers/sms-marketing-vs-transactional) [RCS vs SMS — compared Read](https://www.broadnet.me/answers/rcs-vs-sms) [How do I handle SMS opt-outs Read](https://www.broadnet.me/answers/how-to-handle-sms-opt-outs)