Modern Atelier: one marketplace, three very different users
A multi-vendor marketplace is really three products wearing one domain: a storefront for customers, a back office for vendors, and a control room for admins. Modern Atelier ships all three as separate portals over a shared catalog and order pipeline.
- Type
- E-commerce · multi-vendor marketplace
- Stack
- Next.js · Multi-portal architecture
- Portals
- Customer · Vendor · Admin
- Status
- Live at modern-atelier.vercel.app
The problem
Single-seller shops are a solved problem; marketplaces are not. The moment multiple vendors sell through one storefront, every concern splits three ways: who owns a product listing, who fulfils which slice of a mixed-vendor order, who resolves disputes, and what each role is allowed to see. Building that as one tangled app is how marketplaces become unmaintainable.
Three portals, one source of truth
Customers browse a unified catalog and check out across vendors in one flow. Vendors get their own portal to manage listings, inventory, and incoming orders — seeing only their own slice. Admins oversee the whole marketplace: vendor onboarding, catalog moderation, and order oversight. Each portal has its own navigation, permissions, and workflows, but all three read and write the same underlying catalog and order data, so nothing drifts.
Build notes
Built with Next.js as a portal-separated architecture rather than one role-switched UI — the cleanest way to keep three permission models from leaking into each other. Live at modern-atelier.vercel.app.