WhatsApp Business API Integration for Kwa**** Stores, South AfricaCase Study

Customer conversations on WhatsApp were happening store by store with no central record, no consistency and no link to order status. Formalising this was attractive, but the constraints were unusual. Scheduled load shedding regularly cut store power and connectivity, so any integration that assumed stores were always online would fail predictably and often.

Many customers were sensitive to data costs, which made image-heavy promotional broadcasts a poor fit. POPIA's direct marketing provisions require proper consent, and the chain had no reliable consent record for the customers already messaging it, so the consent base had to be rebuilt rather than inherited.

The point-of-sale software was an older on-premise product at each store, with a readable database but no usable API. A clean real-time integration was therefore impossible, and the design had to be defensive from the outset. Replacing the POS software across every store was not an option, so the integration had to read what existing systems could expose and tolerate their limitations.

PapaSiddhi built a Node.js messaging service on the WhatsApp Business API, with MongoDB storing conversation state and message history. A lightweight agent at each store reads order and collection status from the POS database and pushes events to the central service through a durable local queue. When power or connectivity drops, events accumulate locally and sync once the store is back online, so nothing relies on a store being reachable at any given moment.

Consent was rebuilt from scratch through an explicit, documented opt-in flow, with the record stored against each number and opt-outs honoured immediately and permanently — designed to support POPIA's direct marketing requirements. Templates are text-first and light on media to respect customer data budgets, while promotional sends are segmented and rate-limited. Order collection notifications go out as transactional messages the moment status changes arrive.

A React console lets staff read and reply to messages for their own store only. Delivered on a fixed-price basis, the build also included monitoring of the store agents, so head office can see which branches are offline and for how long instead of discovering sync gaps days later.