Case study 01 / 06
Weblanda
Online stores for Nigerian small businesses, run entirely from a phone.
A multi-tenant SaaS e-commerce platform that gives Nigerian small businesses their own online store, with real checkout, delivery and a seller dashboard, all manageable from a phone. Every store runs on its own subdomain.
- Role
- Founder, solo build
- Type
- Multi-tenant SaaS e-commerce
- Since
- July 2026
- Company
- Weblanda Technologies Ltd
01
The problem
A small business that wants to sell online needs more than a catalogue. It needs a checkout that actually takes payment, a way to get orders delivered, and one place to keep track of products, stock and customers.
Weblanda is built for owners who run their business from a phone, so every one of those jobs has to work on a phone screen, not only on a laptop.
Then there is the money. When a customer pays, the seller should be paid, without waiting for a platform to pass the money on and without giving up a share of every sale.
02
What I built
Weblanda gives each business its own online store on its own subdomain, with real checkout, delivery and a seller dashboard. I built the whole platform alone: product, engineering, payments, brand and content.
01
A store in minutes
A seller picks a name and the shop is live, free for the first 14 days.
02
Products from a phone
A photo, a name and a price is all it takes to add a product to the shop.
03
Orders, stock and customers
See who bought what and which orders are paid. Stock updates as items sell, low items are flagged before they run out, and every customer's spend and last order are on record.
04
Paid directly
Checkout runs on Paystack, and every payment settles into the seller's own Paystack subaccount. Money never passes through Weblanda, and Weblanda takes no cut of sales.
05
Analytics
Sales, orders, products, customers and marketing on one date range, on a desktop or a phone.
06
Its own address
Every store runs on its own subdomain, such as veek3footies.weblanda.shop, with its own checkout and dashboard.
03
How it works
Architecture
Hover a component to trace its connections.
- 1
The seller sets up
From the dashboard on their phone, the seller names the shop and adds products. The shop goes live on its own subdomain.
- 2
Each address finds its store
One Next.js app on Vercel serves every store. Wildcard subdomain routing reads the address a visitor arrived on and loads that store.
- 3
A shopper checks out
The shopper pays through Paystack. The payment settles into the seller's own subaccount, not into a Weblanda account.
- 4
The seller fulfils the order
The order lands in the seller's dashboard marked as paid, and stock updates on its own.
04
Tech stack and why
Next.js (App Router)
One app serves every storefront and every seller dashboard.
Supabase (PostgreSQL)
The database behind every shop's products, orders, stock and customers.
Vercel with wildcard subdomains
Any subdomain reaches the same app, so a new shop gets its own address with no change to the infrastructure.
Paystack subaccounts
Each seller has their own subaccount, which is what lets every payment go straight to the seller.
05
Challenges and what I learned
Many stores, one codebase
Every shop needed its own address, checkout and dashboard without a separate deployment for each one. Wildcard subdomain routing lets a single Next.js app serve them all, so opening a new shop never touches the infrastructure.
Never holding sellers' money
Weblanda is designed so it never holds a seller's money. With Paystack subaccounts, each payment settles straight into the seller's own account, so there are no payouts to run and no cut to explain.
A dashboard that fits a phone
Everything a seller does had to work on a phone screen. Each dashboard screen focuses on one job: adding a product, checking orders, watching stock or seeing who buys.
Building the business, not just the code
Beyond the software, I registered the company as Weblanda Technologies Ltd, onboarded the first sellers across fashion, handmade accessories, furniture and gadgets, and set up their storefronts myself.
What I learned
- Deciding early that sellers are paid directly shaped checkout, payouts and onboarding across the whole platform.
- Setting up real sellers' storefronts myself showed me what a seller actually needs from a dashboard, and what they never touch.
06
Screens
Every screen shows a demo shop with demo figures, not a real seller's business. Customer contact details are blurred.
Sales, orders, products, customers and marketing, on one date range.
See how your shop is doing
Open your shop in minutes
Add products from your phone
Every order in one place
Know what's running low
Know who buys from you
Sales, orders, products, customers and marketing, on one date range.
07
Links
See Weblanda for yourself.
Have something like this in mind?
Have a project, role or research opportunity in mind? Let's talk.