Glam n Go is a multi-vendor marketplace for women’s and kids’ clothing. I built the two dashboards behind it: one for merchants running their own shop, one for the platform team running everything.
Two dashboards, one platform
A marketplace has two operators with opposite needs. A merchant cares about their products, their orders and their payouts. The platform team cares about every merchant at once, and about the ones causing problems.
Building both meant a shared component set with different data scoped to each. Same tables, same forms, same behaviour, different permissions and different reach.
What I built
The merchant dashboard covers the day-to-day of selling. The admin dashboard covers the platform.
- Product and inventory management, with variants for size and colour that clothing needs and most catalogues handle badly.
- Order management through to fulfilment, so a merchant can see what is owed and what is late.
- Merchant onboarding and approval on the admin side, since who is allowed to sell is a platform decision.
- Catalogue oversight and reporting across all vendors.
Keeping it consistent
Data flows through Redux Toolkit Query, so panels reading overlapping data share one cached request instead of firing three. Typed API contracts mean a changed response shape breaks the build rather than a screen in production.
Four of us worked on it at once. The shared components and typed contracts did most of the coordinating: it was obvious when two people were about to solve the same problem, and cheap to reuse the answer when one of them already had.