Multi-vendor fashion marketplace

Fashion marketplaces carry problems a single-brand store does not:

• Vendor quality: labels upload inconsistent photos, sizes and descriptions, each with its own size chart.
• Returns: size-related returns are common in fashion, so payouts cannot be released the day an order ships.
• Shipping from many places: every vendor has its own pickup address and packing habits.
• Money flows: the operator collects payment, deducts commission and fees, handles tax collected at source under GST for e-commerce operators, and settles each vendor correctly.
• Discovery: shoppers expect instant filters by size, colour, fabric and occasion.

• Storefront: a Next.js site with fast category and collection pages, filters, label-specific size charts with fit notes, wishlists and prepaid or COD checkout.
• Vendor portal: onboarding with GSTIN, PAN and bank account verification, bulk product upload by CSV with image and size-chart checks, order management and shipping labels.
• Operations dashboard: catalogue moderation, vendor approvals, commission rules by category or vendor, and returns and dispute handling.
• Shipping: a courier aggregator such as Shiprocket for multi-pickup shipping, tracking, reverse pickups and non-delivery reports.
• Payouts: a ledger per order line holds vendor earnings until the return window closes, then settles them on a schedule.

• Storefront: Next.js with incremental static regeneration for catalogue pages, and images resized and served through a CDN.
• API: NestJS on PostgreSQL, with each order split into vendor sub-orders at checkout.
• Search: PostgreSQL full-text search at launch, with a move to a dedicated search engine planned once catalogue size and filter load justify it.
• Redis: caching, carts and job queues for catalogue imports and payout runs.
• Payments: Razorpay, with split settlements through Razorpay Route or bank payouts driven by the ledger.
• Hosting: Docker containers on AWS.