Multi-Vendor Marketplace Development: How We Built ETK Mall (Case Study)
A live Nigerian e-commerce marketplace built for vendor onboarding, product catalog at scale, and Paystack payments
The problem ETK Mall set out to solve
Commerce in Nigeria is fragmented. A vendor selling fashion in Onitsha, an electronics trader in Alaba, and a cosmetics shop in Abuja all sell to the same Nigerian buyer, but they each have to build their own storefront, negotiate their own payment integration, and pay to acquire traffic from scratch. Most small and mid-sized vendors never get past WhatsApp catalogs and Instagram DMs because the lift required to run a real online shop is too high.
ETK Mall was created to collapse that gap. Instead of every merchant building their own site, ETK Mall offers a single, trusted Nigerian marketplace where vendors sign up, list their products, and start selling inside a shared checkout and payment pipeline. Musskart Technology was brought in to design, build, and support the platform end to end, and the result is etkmall.com — a live multi-vendor marketplace serving multiple sellers and thousands of products.
This case study walks through what we built, the decisions we made along the way, and what other Nigerian founders can learn from the project if they are thinking about multi-vendor marketplace development in Nigeria.
Project overview
| Client | ETK Mall |
| Live URL | https://etkmall.com/ |
| Industry | E-commerce, multi-vendor marketplace |
| Region served | Nigeria (national) |
| Engagement type | Full platform build plus ongoing support |
| What was built | Vendor signup and onboarding, product listings, cart and checkout, payment processing, admin panel, scalable multi-seller architecture |
The goal agreed with the client was a production-grade marketplace that any Nigerian vendor could register on, upload products to, and start selling through, with payments routed through a trusted Nigerian gateway. Everything else — design, architecture, deployment, support — was on Musskart.
The challenge: what is actually hard about a multi-vendor marketplace
A lot of people underestimate how different a marketplace is from a single-vendor online shop. A single shop has one owner, one inventory, one bank account, and one shipping workflow. A marketplace has many of all of those, and the platform itself is responsible for keeping them untangled. On ETK Mall we had to get the following right from day one.
Vendor onboarding and verification
Any vendor can register, but not every signup should be allowed to sell. We needed a flow where a vendor creates an account, submits business details, and waits for admin approval before their products go live. Without this step, the platform becomes a dumping ground for low-quality or fraudulent listings and loses buyer trust.
Inventory isolation per seller
Every product, stock count, and price must be owned by exactly one vendor. Queries that list products must respect that ownership, and so must the APIs the vendor dashboard uses. A bug here is not cosmetic — it is a vendor seeing someone else's stock or editing someone else's price.
Payments and split settlement
When a buyer pays for a cart that contains items from three different vendors, the platform has to collect the money once, take the platform commission, and settle the remainder to each vendor. In Nigeria that means integrating Paystack or Flutterwave and making peace with how their split payment APIs handle fees, refunds, and chargebacks.
Role-based permissions
Three distinct roles share the same codebase: buyers, vendors, and admins. Each role gets a different dashboard, different allowed actions, and different access to data. Getting this wrong is how marketplaces leak information.
Dispute handling and trust
Buyers and vendors will disagree — wrong item, late delivery, description mismatch. The platform needs a clear way to log a dispute, pause the payout, communicate with both sides, and resolve without sending emails into a void.
Our solution: architecture at a glance
We broke ETK Mall into clearly scoped modules, each with its own data ownership and API boundary. This is what a working Nigerian marketplace actually needs behind the scenes.
Vendor portal
Self-service dashboard where a vendor signs up, submits verification, adds products, manages stock, views orders, and tracks payouts. It is the vendor's version of the website.
Product catalog
Central catalog that indexes products from every approved vendor. Supports categories, attributes, variants, images, search, and filters. This is the engine behind the homepage and every listing page.
Cart and checkout
One unified cart that can contain items from multiple vendors. At checkout the totals, shipping rules, and vendor breakdown are computed server-side so the client cannot tamper with prices.
Payment gateway
Paystack integration handles card, bank transfer, and USSD payments natively in Naira, with webhook-based order confirmation. A split-payout layer separates the platform fee from the vendor share on each order.
Admin panel
Operator console where Musskart or the ETK Mall team approves vendors, moderates products, resolves disputes, views orders across the platform, and reads revenue reports.
Notifications
Transactional emails on signup, order placement, shipment updates, and payout events, plus in-dashboard notifications so vendors never have to refresh to see new orders.
Tech stack we committed to
For ETK Mall we committed to a PHP and Laravel backend with a MySQL database, a server-rendered frontend enhanced with Bootstrap and Vue components for interactive pieces like the cart and vendor dashboard, and Paystack as the primary payment gateway. This is a deliberately boring stack, which for a Nigerian marketplace is a feature, not a bug.
Laravel gives us Eloquent ORM for clean multi-tenant queries (always scope by vendor_id), Sanctum for API authentication on the vendor and admin dashboards, and queues for anything that has to happen off the request lifecycle — sending emails, firing payout webhooks, regenerating sitemaps. MySQL is well understood by every Nigerian devops hand we may need to hire later, which matters when the project needs to outlive the original build.
The frontend is intentionally server-rendered first because it is faster on the slow and inconsistent connections that still dominate large parts of Nigeria. We layer Vue components on top of that server HTML for the parts that genuinely need to be dynamic — live cart updates, image galleries, vendor dashboard tables — rather than forcing the entire site through a single-page app.
Results: what the client says
ETK Mall is live at etkmall.com, runs real vendor traffic, and continues to grow under a maintenance retainer with Musskart. The most useful summary of the outcome comes directly from the client, so rather than dress it up we are quoting it verbatim.
"Musskart Technology developed etkmall.com, our multi-vendor e-commerce marketplace. The platform handles vendor signups, product listings, and payments seamlessly. Their team built a scalable system that supports multiple sellers and thousands of products. The quality of work and ongoing support has been exceptional."
— ETK MallWe are intentionally not publishing internal GMV, revenue, or user-count numbers. Those belong to the client, not to us. What we will say is that the platform has held up under multi-vendor, multi-thousand-SKU load without requiring a re-architecture, which is the real proof that the scalability work done at the start paid off.
Lessons for Nigerian founders thinking about a marketplace
1. Nail vendor verification before you launch
The cheapest way to lose buyer trust is to let every signup sell immediately. Build manual approval into the vendor flow from day one and only automate it later once you have data on what a legitimate Nigerian vendor looks like.
2. Pick Paystack or Flutterwave, not both on day one
Both are excellent and both are widely adopted in Nigeria. Picking one and integrating it fully — webhooks, refunds, split payouts — is much more valuable than half-integrating two. Adding the second is a week of work once the first one is solid.
3. Scope by vendor, not by product
Every database query, every cache key, every API route should have vendor_id in it by default. It is far harder to retrofit multi-tenancy later than to design with it now.
4. Your admin panel is your unfair advantage
Nigerian buyers expect a human to resolve disputes. A great admin panel lets your ops team do that quickly — without writing custom SQL. Treat it as a first-class product, not a leftover.
5. Launch with a narrow category and widen later
Going live with five categories you can actually moderate is better than going live with fifty you cannot. Narrow focus builds a brand reputation that attracts vendors in adjacent categories on its own.
Frequently asked questions about multi-vendor marketplace development in Nigeria
Planning your own Nigerian marketplace?
We built ETK Mall from the ground up. We can do the same for your vendor network, wholesale platform, or niche e-commerce idea.
