Client work · 2026
Netcart
One marketplace, four audiences, built end to end
- Customers · Stores · Couriers · AdminAudiences
- Email · Storage · PaymentsProvider adapters
- OpenAPIAPI contract
What it actually does
The home screen ships from the server
Banners, categories and featured stores are described by the backend and rendered by the app, so merchandising changes go live without an App Store review.
Invoices and receipts generate themselves
The API renders them as both PDF and image, so the same document works as a download, an email attachment and a WhatsApp share.
Nothing is load-bearing
Email, file storage and payments each sit behind adapters — switch Cloudinary for Firebase, or one processor for another, without touching business logic.
A separate surface for the people delivering
Couriers get their own flow — available, claimed, active, history — with an online toggle and shift tracking, rather than a customer app with extra buttons bolted on.
Stores are tenants, not rows in a table
Each store carries its own catalogue, promotions and earnings, and courier companies group riders under their own umbrella. Four groups of people use this system and none of them sees the others' screens.
Operations, not just a dashboard
The portal covers fleet management, order escalations, fraud controls and analytics: what running the business needs, not just what looks good in a demo.
What we built
Customers ordering, stores selling, couriers delivering and admins running the whole thing — each with their own surface, over a single API. Built from an empty repository to a system that handles catalogue, orders, payments, earnings and payouts.
Stack
- Flutter
- Next.js 16
- React 19
- TypeScript
- Express 5
- Prisma
- MongoDB
- Paystack
Start here
Start a Reaction
Tell us what you are building and what is currently in the way. We reply to every enquiry within two working days — with a real answer, not a calendar link.