Ekashop

01

Context

Township commerce is substantial, established and almost entirely undigitised. The spaza shop, the kitchen, the liquor outlet and the apparel brand each run on cash, memory and foot traffic. National delivery platforms have not reached them, largely because the economics of those platforms assume formal addresses, card penetration and margins that township retail does not carry.

• Stock tracked from memory, with sales lost to phantom inventory
• Customer reach limited to walking distance
• No delivery capability without owning vehicles
• Commission structures from national platforms that do not fit local margins

02

Strategy

Build for the merchant first. A marketplace with no supply is an empty catalogue, so the platform had to be worth using on the first day — before any buyer arrived — by solving inventory and payments. Delivery was designed as a shared service rather than a requirement, so a shop without a vehicle is not excluded.

• Merchant utility before marketplace scale
• Logistics as a shared service, not a barrier to entry
• Commission structured for township retail margins
• Distinct verticals rather than one undifferentiated catalogue

03

Product

Four merchant verticals sharing one commerce and logistics backbone, each with its own compliance and presentation requirements.

• Spaza — stock management and digital payment acceptance
• Township food — menu and order handling for local kitchens
• Alcohol — compliance-aware ordering and delivery for licensed outlets
• Local apparel — a dedicated storefront for township fashion brands
• Real-time inventory sync across devices
• Logistics-as-a-service using ecosystem drivers

04

Technology

A three-sided system — merchants, drivers and buyers — each with different needs from the same underlying data. Payments run through Paystack, chosen for local card and bank coverage.

• Multi-sided architecture serving merchant, driver and buyer roles
• Real-time inventory synchronisation across sessions and devices
• Paystack payment integration for South African rails
• Driver dispatch and fulfilment coordination
• Vertical-specific rules, including licensed-goods handling

05

Growth

A marketplace grows on two sides at once, and getting that sequence wrong is how most of them fail. Merchant acquisition leads, because supply density within a delivery radius is what makes the buyer experience credible.

• Merchant-led acquisition, geographically concentrated
• Supply density before demand spend in any given area
• Driver recruitment matched to order volume rather than ahead of it
• Vertical expansion once density holds