Commerce plus fintech
Glotrade is not just a marketplace. The codebase combines shopping, payments, wallet logic, vendor settlement, and investment infrastructure in one unified product surface.
Back to selected work
Case study
Glotrade is a marketplace, wallet, investment, and operations platform built as a serious multi-system product.
The repository shows a platform with far more surface area than a typical e-commerce build. It blends commerce, vendor management, fintech workflows, GDIP investment infrastructure, referral systems, and admin operations inside one product ecosystem.
Visit live project
Category: Marketplace + fintech ecosystem
Platform snapshot
97
web app files in the App Router surface
35
API route files in the TypeScript backend
31
database models covering commerce and fintech flows
42
service-layer files supporting platform operations
What NEXGEN built
A layered ecosystem spanning commerce, payments, investments, and platform governance.
Multi-vendor commerce marketplace with product discovery, checkout, cart, orders, reviews, and store pages
Integrated wallet system for buyers and vendors with balance management, top-ups, transfers, withdrawals, and transaction history
GDIP investment engine with TPIAs, GDC clusters, commodity backing, insured cycles, and statement/certificate surfaces
Sales agent and referral infrastructure with commission tracking, dashboards, approval logic, and payout pathways
Admin and operational tooling for products, users, orders, wallets, GDIP, reports, banners, credit requests, and security workflows
Multi-role platform design
The route structure covers customers, vendors, admins, agents, and GDIP participants. That makes the UX and system design meaningfully more complex than a single-audience commerce app.
Operational depth
The backend is organized around controllers, services, models, jobs, providers, and middleware, which suggests a platform built for ongoing operations rather than a one-off launch build.
Regional payment ambition
The documentation and service layer point to Nigeria-first commerce with broader West African payment and wallet considerations, including multi-provider payment support and financial workflow handling.
Role-based product design
Distinct surfaces for customers, admins, agents, and GDIP participants.
One of the strongest signals in the repo is that Glotrade is designed around multiple user roles with different jobs to do, not a single shopping interface.
Customer surface
The web app includes marketplace browsing, cart, checkout, wishlist, orders, wallet, notifications, support, and dashboard flows. This is a full customer product, not a thin storefront shell.
Admin surface
The admin area covers products, users, orders, wallets, withdrawals, banners, credit requests, reports, analytics, and dedicated GDIP management pages. It reads like a real operational console.
Agent surface
There are separate agent routes for referrals, commissions, and dashboards, which means the platform includes growth and distribution mechanics alongside core commerce.
Investor / GDIP surface
GDIP has its own dashboard, purchase flow, cycle pages, statements, certificates, and TPIA detail screens, giving the investment layer a first-class product experience.
Architecture
Monorepo architecture built for a growing platform, not a narrow storefront.
Turbo monorepo with separate `apps/web` and `apps/api` workspaces
Next.js frontend with App Router pages for marketplace, admin, wallet, GDIP, orders, agent flows, and profile areas
Express + TypeScript backend with versioned REST routes, role-aware middleware, and a large domain model set
Dedicated service layer for payments, wallets, GDIP, referrals, reporting, analytics, escrow, inventory, notifications, and storage
Technology stack
Next.js 15 App Router
React 19
TypeScript
Tailwind CSS
next-intl
Express
MongoDB
Mongoose
Redis rate limiting
WebSockets / realtime
Cloudflare R2
Paystack
Flutterwave
Korapay
node-cron
What makes it notable
Glotrade stands out because it tries to unify transactional commerce and financial participation in one system. That raises the bar for architecture, compliance thinking, internal tooling, and user education across the product.
System breakdown
The standout systems go well beyond standard marketplace requirements.
GDIP engine
The docs describe insured commodity-backed investment blocks, grouped into GDC clusters and processed through automated 37-day trade cycles. This adds a highly unusual financial-product layer to the platform.
Wallet architecture
The wallet design supports buyer and vendor wallets, transaction history, top-ups, payments, withdrawals, transfers, frozen balances, and admin fund controls, with NGN and token-aware thinking documented in the system design.
Vendor settlement
Vendor payout logic is tied to order delivery states, with automated grouping of line items by vendor and settlement into wallets. That creates a cleaner operational bridge between commerce events and money movement.
Growth loops
The sales agent and referral system adds commission logic, agent tiers, approval thresholds, dashboards, and payout pathways. That expands the platform beyond transactions into acquisition mechanics.
Repo evidence
Concrete signals from the codebase that support the case-study claims.
The API mounts more than thirty versioned route groups from `/api/v1/auth` and `/api/v1/market` to `/api/v1/wallets`, `/api/v1/gdip`, `/api/v1/referrals`, and `/api/v1/commissions`.
The frontend route tree includes dedicated areas for `/admin`, `/agent`, `/profile/wallet`, `/gdip`, `/checkout`, and seller storefront routes under `/s/[slug]`.
The wallet UI code shows transaction history, exports, top-up, withdrawal, credit request, commission widgets, and real-time wallet updates.
The GDIP dashboard code includes portfolio summaries, ROI calculations, available balance checks, statement generation, and TPIA-centric views.
Project readout
Why this project matters in the portfolio.
Glotrade shows NEXGEN operating at platform level. The repo suggests strong capability in designing systems where commerce, money movement, internal governance, and multi-role user experience all need to work together.
It also gives the portfolio a more ambitious story: not only building products that sell goods, but building ecosystems with wallets, payouts, referrals, insured investment mechanics, and regional growth intent.