A marketplace ecosystem for an Indian operator: vendor dashboards, a customer portal, administrative oversight, commission logic, payments and automated notifications on one platform.
A marketplace operator in India needed the whole ecosystem rather than a shop: customers, vendors who list and fulfil their own stock, administrators overseeing both, and the orders, payments and notifications connecting them.
We built it as three connected experiences on one platform. Vendors get a dashboard for their products, stock, orders and payouts. Customers get a storefront and an account area holding their orders and history. Administrators get oversight of the whole marketplace -- approving vendors, settling disputes, watching the catalogue, and seeing the commercial picture across every seller.
The commission logic is what makes a marketplace a marketplace, and it is where these builds usually go wrong. Every order has to split correctly between platform and vendor, hold up when an order is partly refunded or partly cancelled, and reconcile at the end of a payout period without anyone recalculating it by hand. It is handled in the system, against the order records themselves.
Payments run through integrated gateways, and automated WhatsApp and email notifications keep three audiences informed of the same event: the customer that their order shipped, the vendor that they have one to pack, the administrator when something needs attention.
Inventory is managed per vendor but enforced centrally, so the catalogue cannot sell what a vendor does not have -- the failure that costs a young marketplace its vendors as fast as its customers.
The client owns the platform outright, code, database and gateway accounts, and onboards new vendors without us.
What this project actually used. We pick a stack to suit the problem and the people who will maintain it, so this is not the same list on every project.
Each page below covers the process, the stack and the questions buyers usually ask about that kind of work.
A storefront and the operations behind it built as one system: orders processed, stock synchronised and customers updated on WhatsApp without anyone re-entering anything.
Read the case studyUnited Arab EmiratesA custom ERP for a UAE trading and distribution business: sales, purchasing, stock, invoicing and customer records in one system, with the repetitive work between them automated.
Read the case studyUnited KingdomWhatsApp enquiries, follow-ups and status updates handled automatically for a UK services business, with every conversation attached to a CRM record instead of living on someone's handset.
Read the case studyTell us where your situation differs and we will tell you which parts of this would carry over and which would not — including where we think you need less than this.
Talk to us