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

WhatsApp is the dominant messaging channel in South Africa, and the chain's customers were already messaging individual store numbers informally with no record kept. The business wanted to formalise that, but the constraints were unusual. Load shedding interrupts store connectivity on a scheduled but disruptive basis, so any integration assuming a store is continuously online would fail predictably and often. Customer data costs matter — a substantial part of the customer base is price-sensitive about mobile data, so message payloads had to stay light and image-heavy promotional sends were a bad idea. POPIA governs direct marketing consent, and the chain had no reliable consent record for the customers already messaging them, so the consent position had to be rebuilt properly rather than assumed. The POS system was an older on-premise product per store with a database that could be read but no meaningful API, which ruled out a clean real-time integration and required something more defensive.

We built a Node.js service handling the WhatsApp Business API with MongoDB storing conversation state and message history. The POS integration was designed around intermittent connectivity from the start: a lightweight agent at each store reads order and collection status and pushes to the central service with a durable local queue, so a store losing power or connectivity accumulates events and syncs when it returns rather than losing them. Nothing in the design assumes a store is reachable at any given moment. Consent was rebuilt from zero — customers opt in explicitly through a documented flow with the consent record stored against their number, and opt-out is honoured immediately and permanently, which is what POPIA's direct marketing provisions require rather than an inherited list. Message templates were kept text-first and deliberately light on media to respect customer data costs, with promotional sends rate-limited and segmented rather than blasted. Order collection notifications are transactional and go out as status changes arrive from the store agent. Store staff have a simple console to see and respond to customer messages for their own store only. We built monitoring around the store agents specifically, so head office can see which stores are currently offline and for how long, rather than discovering a sync failure days later through missing notifications. Related: custom software development and our ecommerce and retail work.