Retail and Commerce

A retailer with several branches already keeps its prices and stock somewhere, usually in an ERP or accounting system the shops use every day. An online shop with its own copy drifts away from it within hours, because items keep selling in store. Customers then order things that are no longer on the shelf, and staff spend their time correcting orders.

The data in those systems is written for stock-keeping. Item names are short codes in capitals, there are no photos, and nothing describes the product in words a customer would search for.

An online order also raises questions a shop counter never does. One basket may hold items from two branches, and the customer may want to collect some and have the rest delivered. The payment has to be confirmed before anything leaves the shop. When the sale is complete, it has to reach the retailer's books once, or stock and accounts stop matching.

We treat the retailer's existing system as the source of truth. For SuperLovek, a phone and appliance retailer with more than 50 branches, the website and apps take prices and branch stock from its ECOUNT ERP every hour and check each item again at checkout. Each paid sale is posted back to ECOUNT once, at handover.

Product pages start as drafts written with AI from the ERP entries, and staff review every draft and photo before it is published. An order that spans branches is split into one pickup or delivery per branch, while the customer still sees one order and makes one payment.

DialGH, built for a group of entrepreneurs, sells airtime, data and bill payments through a USSD menu, so customers can buy from any phone without a website or an app.

The services that apply are web and mobile app development, payment and mobile money integration, USSD development and custom software.