How to choose a reward platform in Africa — 8 questions to ask before you buy

The procurement process for a reward platform in Africa is full of vendors who look identical on a slide deck: all of them claim Africa coverage, local currency support, and instant delivery. Here are the eight questions that reveal the real differences — and what the right answers look like.

Choosing a reward platform is a consequential decision. The platform you select will determine whether your programme reaches 40% or 95% of intended recipients, whether rewards arrive in 2 seconds or 2 days, whether you have real-time visibility into programme performance or end-of-month reports, and whether adding a new market takes an afternoon or a quarter.

The problem is that these differences aren't visible in a standard vendor pitch. Every platform will claim Africa coverage. Every platform will claim local currency support. Every platform will show a polished dashboard screenshot. The differences emerge when you ask the right questions — questions that require specific, operational answers rather than marketing claims.

These are the eight questions that consistently reveal the real state of a reward platform's Africa capability.

Question 1: Show me the specific brands in the redemption catalogue for Lagos and Nairobi

Not "do you have a Nigerian catalogue?" — that's yes/no and almost every vendor will say yes. Ask for the specific list of brands available to recipients in Lagos and Nairobi today. The response reveals whether the catalogue is genuinely local (Shoprite, Jumia, Chicken Republic, Carrefour KE, Naivas) or whether "local Africa coverage" means a global catalogue of international brands technically available in-country.

A catalogue that contains Amazon, Sephora, and Google Play as the primary options for a Nigerian recipient is not a local catalogue. A catalogue with 15 Nigerian grocery, food, connectivity, and fashion brands is.

The right answer is a specific, named list of 10–20 local brands per major market, refreshed regularly as new brands are onboarded. If the vendor can't produce this list in the sales conversation, the catalogue isn't what they've claimed.

Question 2: What's the average delivery time from API call to recipient notification?

Not "do you offer instant delivery?" Ask for the measured median delivery time from API call to confirmed recipient delivery, broken down by channel (WhatsApp, USSD, SMS) and by market (Nigeria, Kenya, South Africa).

The right answer is under 5 seconds for WhatsApp and SMS in major markets. USSD sessions are interactive — the delivery is the session initiation, which should be near-instant. If a vendor can't give you a specific number with market breakdown, their delivery infrastructure is likely inconsistent or they don't measure it.

Be suspicious of "instant delivery" claims accompanied by vague descriptions of batch processing windows, next-business-day settlement, or "typically within 24 hours." Those phrases describe something other than instant.

Question 3: What delivery channels do you support — specifically for feature phone users?

Ask explicitly about USSD support. Many platforms support WhatsApp and SMS but don't have USSD capability — which means they can't reach feature phone users at all. In Nigeria and East Africa, feature phone users may represent 40–60% of your intended recipient population.

The right answer includes: USSD (with a description of how the redemption session works), SMS (for code delivery and confirmation), WhatsApp (for smartphone users), and web (for branded redemption page). All four, with clear descriptions of how each works and which markets each is available in.

If the answer is "WhatsApp and email" — the platform is designed for a different market. It will technically work in Africa; it won't reach most of it.

Question 4: How does the currency denomination work — are rewards issued in local currency at issuance?

The key distinction: are reward values set and issued in local currency (NGN, KES, ZAR), or are they set in USD and converted to local currency at redemption?

The right answer is local currency at issuance. The Nigerian recipient receives a ₦5,000 reward card. Not a "$6 reward card." The amount is fixed in Naira the moment it's issued. It doesn't fluctuate with exchange rate movements between issuance and redemption.

USD-at-issuance with local conversion at redemption is the wrong architecture for African markets with volatile currencies. It creates uncertain recipient experience, potential for perceived value reduction, and complex reconciliation requirements. If the vendor's architecture is USD-first, ask specifically how Naira volatility is handled. If the answer isn't satisfying, it's a red flag.

Question 5: Walk me through the API integration — what does the call look like and what does the response return?

Ask to see an actual API call and response, not a slide with arrows. The technical quality of the API — its structure, its documentation, its error handling — reveals the maturity of the underlying platform.

The right answer includes: a clean REST API with JSON request and response bodies, clear field names, an idempotency key parameter, a synchronous response with reward status and delivery confirmation, and webhook events for asynchronous status updates (delivery confirmed, redeemed, expired). If any of these are missing or vague, the integration will be more complex and error-prone than the vendor has implied.

Ask specifically about idempotency handling. "What happens if my server sends the same request twice due to a network retry?" If the answer isn't "we deduplicate on the idempotency key and return the original response" — you'll issue double rewards under normal failure conditions.

Question 6: Which African markets are fully supported today — and what does "supported" mean specifically?

Every vendor will list a number of African countries. The question is what "supported" means for each one. There are three meaningfully different levels:

• →
  Full support: Local currency denomination, local brand catalogue, local delivery channel infrastructure (USSD/SMS/WhatsApp), local compliance, live programmes running today
• →
  Partial support: Currency handled but limited local catalogue, email delivery only, no USSD, limited brand partnerships
• →
  Listed but not operational: Country appears on a coverage map but no live programmes, no local catalogue, no local delivery infrastructure

The right answer is a specific list of fully-supported markets with evidence: active customer names (or anonymised case studies), brand catalogue screenshots, delivery channel documentation. If the vendor can't demonstrate live programmes in the markets you need, treat listed coverage with appropriate scepticism.

Question 7: What does the analytics and reporting look like — show me a live dashboard

Ask to see a live dashboard during the demo, not a screenshot. The live dashboard reveals what data is actually available, how it's presented, and whether it's in real-time or batch.

The right answer includes real-time data on: issuance rate (what percentage of qualifying events resulted in a reward), delivery rate (what percentage of issued rewards were confirmed delivered), redemption rate (what percentage of delivered rewards were used), breakdown by market and channel, and a reward-level log where you can look up the status of any individual reward issuance.

If the dashboard shows only aggregate totals updated once per day, the analytics capability is limited. If it shows real-time event-level data with the ability to drill into any individual reward, the platform is built for programme operators who want visibility, not just volume numbers.

Question 8: What's the support structure when something goes wrong — specifically for an Africa time zone issue?

This question is often overlooked and reveals platform maturity quickly. Reward delivery problems tend to happen in real time — a programme goes live on a Nigerian FMCG promotion Monday morning and something isn't working. Who do you call? What's the response time? What timezone are they in?

The right answer for African market operations: support coverage during West African Time (WAT) and East African Time (EAT) business hours, with a dedicated technical contact who understands African market delivery infrastructure specifically. Generic global support with 24–48 hour ticket response times is inadequate for live programme issues.

Ask for a specific SLA for critical issues (programme not issuing, mass delivery failure) versus non-critical issues (reporting discrepancy, individual redemption query). The difference in response time and escalation path tells you how seriously the vendor treats Africa market operations.

The right vendor answers these eight questions with specific operational detail. The wrong vendor answers them with marketing language and redirects to the slide deck.