Build a complete, scalable, modern, multi-vendor e-commerce marketplace platform inspired by Amazon, Flipkart, and Meesho.
The objective is to create a production-oriented, feature-rich e-commerce ecosystem with a responsive web interface, reusable components, well-defined user journeys, and scalable backend architecture.
Use Amazon, Flipkart, and Meesho as functional and design references, but create an original and consistent UI/UX rather than copying their branding.
Follow these instructions strictly while generating the project:
Start by analyzing the complete requirements.
Generate a detailed Software Requirements Specification (SRS).
Identify all modules, submodules, and functional dependencies.
Generate detailed user stories and acceptance criteria.
Create a complete sitemap covering all customer, seller, and admin pages.
Generate user flow diagrams for all major functionalities.
The final project should include:
Complete Software Requirements Specification.
Functional and Non-Functional Requirements.
Complete Sitemap.
User Flow Diagrams.
Complete UI/UX Designs for Every Page.
Deliver a complete, scalable, production-oriented, multi-vendor e-commerce marketplace that provides a seamless shopping experience for customers, powerful business management capabilities for sellers, and complete operational control for administrators.
Project name: heroic-requirement.
Create a centralized administration portal with role-based access and advanced management capabilities.
Audit Logs
System Settings
Generate the following architecture diagrams:
High-Level System Architecture.
Frontend and Backend Architecture.
Database Entity Relationship Diagram (ERD).
Authentication and Authorization Flow.
Customer Shopping Journey.
Seller Onboarding Flow.
Product Management Flow.
Order Processing Flow.
Payment Processing Flow.
Shipping and Delivery Flow.
Return and Refund Flow.
Admin Management Flow.
API Integration Architecture.
Deployment Architecture.
Clearly explain the responsibilities and interactions of each component.
Design the complete database schema and ER diagrams.
Generate the High-Level Architecture and Low-Level Architecture.
The application should be architected and designed as one integrated ecosystem rather than three separate disconnected applications.
The platform should allow customers to browse products, search and filter items, add products to their cart, place orders, make payments, track shipments, submit reviews, and manage their accounts.
The platform must also support multiple sellers who can register, manage their stores, upload products, manage inventory, process orders, track sales, and receive payments.
Additionally, provide a comprehensive Admin Panel that allows administrators to manage the entire marketplace, including customers, sellers, products, orders, payments, commissions, promotions, inventory, returns, refunds, and platform configurations.
Implement role-based access control (RBAC) with the following user roles:
Register and log in using email, mobile number, or social authentication.
Manage personal profile and addresses.
Browse and search products.
Add products to wishlist and cart.
Place orders and complete payments.
Track orders and shipments.
Cancel orders and request returns or refunds.
Submit product ratings and reviews.
View order history and download invoices.
Browse and search products.
Add products to wishlist and cart.
Place orders and complete payments.
Track orders and shipments.
Cancel orders and request returns or refunds.
Submit product ratings and reviews.
View order history and download invoices.
Manage notifications and communication preferences.
Register as a seller and complete business verification.
Create and manage a seller store.
Manage seller profile and store settings.
Add, edit, delete, and publish products.
Manage product categories, variants, pricing, and inventory.
Upload product images and descriptions.
Manage incoming orders.
Update order processing and shipment statuses.
Handle customer return and refund requests.
View sales analytics and revenue reports.
Track commissions, settlements, and payouts.
Access a centralized admin dashboard.
Manage customers and seller accounts.
Approve, reject, suspend, or deactivate sellers.
Manage products, categories, and attributes.
Monitor and manage all marketplace orders.
Configure commissions and seller payouts.
Manage payments, refunds, and disputes.
Manage promotional campaigns and discount coupons.
Manage banners, homepage content, and featured products.
Configure shipping providers and delivery rules.
Generate business reports and analytics.
Manage system settings, permissions, and audit logs.
Generate all the following pages with fully connected navigation and functional user flows.
Login Page
Customer Registration Page
OTP Verification Page
Forgot Password Page
Reset Password Page
Social Login Integration Flow
Homepage
Product Listing Page
Product Category Page
Product Subcategory Page
Product Search Results Page
Product Details Page
Product Comparison Page
Wishlist Page
Shopping Cart Page
Checkout Page
Address Selection and Management Page
Payment Method Selection Page
Order Confirmation Page
Order Tracking Page
Order History Page
Order Details Page
Return and Refund Request Page
Product Reviews and Ratings Page
My Account Dashboard
Personal Information Page
Address Book Page
Saved Payment Methods Page
My Wishlist Page
My Orders Page
Notifications Page
Help and Support Page
Contact Us Page
FAQ Page
About Us
Privacy Policy
Terms and Conditions
Return and Refund Policy
Shipping Policy
Generate a separate seller portal with a professional dashboard layout.
Seller Registration
Seller Login
Business Verification
Seller Dashboard
Store Profile Management
Product Listing Management
Add New Product
Edit Product
Product Category Management
Product Variant Management
Inventory Management
Bulk Product Upload
Order Management
Order Details
Shipment Management
Return and Refund Management
Customer Queries
Sales Analytics
Revenue Reports
Commission Details
Payment and Settlement Management
Seller Notifications
Seller Support
Seller Account Settings
Admin Login
Admin Dashboard
Sales Analytics
Revenue Analytics
Customer Analytics
Seller Performance Analytics
Product Performance Analytics
Customer Management
Customer Details
Seller Management
Seller Approval and Verification
Seller Details
Seller Performance Monitoring
Admin User and Role Management
Product Management
Product Approval
Product Details
Category Management
Subcategory Management
Brand Management
Product Attributes Management
Order Management
Order Details
Payment Management
Refund Management
Commission Configuration
Seller Payout Management
Transaction History
Invoice Management
Coupon Management
Discount Management
Promotional Campaign Management
Banner Management
Homepage Content Management
Shipping Provider Management
Delivery Configuration
Return and Replacement Management
Customer Support Management
Notification Management
General Settings
Payment Gateway Configuration
Tax Configuration
Shipping Configuration
Security and Access Management
Audit Logs
Reports and Data Export
Implement the following business functionalities across the entire platform:
Multiple product images and image galleries.
Product variants such as size, color, and material.
SKU and barcode management.
Product pricing and discounted pricing.
Product specifications and descriptions.
Stock availability and low-stock alerts.
Product ratings and reviews.
Related and recommended products.
Search products by name, keyword, SKU, and brand.
Search suggestions and autocomplete.
Advanced filtering by category, price, brand, rating, availability, and attributes.
Sorting by price, popularity, newest arrivals, and ratings.
Recently viewed products.
Personalized product recommendations.
Add and remove products from cart.
Update product quantities.
Apply coupon codes.
Calculate taxes, discounts, and shipping charges.
Select delivery addresses.
Select payment methods.
Validate product stock before order placement.
Support guest checkout and registered customer checkout.
Design a payment abstraction layer supporting:
UPI.
Credit and debit cards.
Net banking.
Digital wallets.
Cash on Delivery.
Payment gateways such as Razorpay and Stripe.
Include payment verification, transaction tracking, refunds, and payment failure handling.
Implement a complete order lifecycle:
Pending → Confirmed → Processing → Packed → Shipped → Out for Delivery → Delivered.
Also support:
Cancelled orders.
Failed payments.
Return requests.
Replacement requests.
Refund processing.
Partial refunds.
Order status notifications.
Shipping provider integration.
Shipment creation.
Tracking ID generation.
Delivery status synchronization.
Shipping cost calculation.
Estimated delivery dates.
Multiple shipping addresses.
Delivery serviceability checks.
Percentage-based discounts.
Fixed-value discounts.
Category-based offers.
Product-specific offers.
First-order discounts.
Minimum-cart-value discounts.
Coupon expiration and usage restrictions.
Recently viewed products.
Responsive product listing grids.
Easy-to-use filters and sorting.
KPI cards.
Interactive analytics charts.
Data tables with pagination, sorting, and filtering.
Forms with proper validation.
Clear status indicators.
Action menus and confirmation dialogs.
Order Items
Payments
Transactions
Refunds
Shipments
Shipment Tracking
Coupons
Promotions
Ensure that orders preserve historical product prices, descriptions, and seller information even if the original product changes later.
Returns and Refunds
Notifications
Analytics and Reporting
Admin Configuration
Requirements:
RESTful APIs with consistent response structures.
Input validation and error handling.
JWT-based authentication with secure token management.
Role-based and resource-level authorization.
Database transaction handling.
Background jobs for notifications and asynchronous processing.
File and image upload management.
Generate backend modules and API endpoints.
Implement database models and relationships.
Integrate authentication and authorization.
Connect all frontend pages with the backend APIs.
Implement the complete business logic.
Add proper validation, error handling, and loading states.
Implement responsive layouts.
Generate test cases for all major functionalities.
Generate the entire application, including customer, seller, and admin interfaces.
Maintain consistency across all pages and modules.
Ensure that every screen has a clear purpose and is connected to the relevant user journey.
Do not use placeholder pages for required functionality.
Do not generate disconnected static designs.
Ensure that all navigation links, buttons, forms, and actions have defined behaviors.
Do not assume that a feature is complete merely because its UI has been generated.
Ensure the project can be extended with additional modules in the future.
Generate realistic sample data for development and testing.
The marketplace serves three human roles under role-based access control (RBAC). Payment, shipping and notification services support these roles but are not personas.
| Role | Responsibilities and goals | Inputs | Decisions | Observable success | Access |
|---|---|---|---|---|---|
| Customer | Browse and search products; build a wishlist and cart; place orders and complete payments; track orders and shipments; cancel orders and request returns or refunds; submit ratings and reviews; view order history and download invoices; manage notifications and communication preferences | Product listings, search and filter results, order and shipment status, invoices | What to buy, whether to cancel, return or refund, what to review, which notifications to receive | Completed orders, tracked shipments, resolved returns/refunds, submitted reviews, downloaded invoices | Customer-facing storefront and own account |
| Seller | Register and complete business verification; create and manage a store, profile and store settings; add, edit, delete and publish products with categories, variants, pricing, inventory, images and descriptions; manage incoming orders and update processing and shipment statuses; handle customer return and refund requests; view sales analytics and revenue reports; track commissions, settlements and payouts | Verification documents, product data, incoming orders, return/refund requests, sales and payout reports | What to publish and price, how to process and ship orders, how to respond to returns and refunds | Approved verification, live store and listings, orders processed and shipped, returns handled, payouts tracked | Seller dashboard scoped to own store |
| Administrator | Operate the marketplace from a centralized admin dashboard: manage customer and seller accounts; approve, reject, suspend or deactivate sellers; manage products, categories and attributes; monitor and manage all orders; configure commissions and seller payouts; manage payments, refunds and disputes; manage promotional campaigns and discount coupons; manage banners, homepage content and featured products; configure shipping providers and delivery rules; generate business reports and analytics; manage system settings, permissions and audit logs | Seller applications, order and payment data, dispute and support cases, analytics, platform configuration | Seller approval or suspension, commission and payout settings, refund and dispute outcomes, campaign and content choices, shipping and delivery rules | Managed seller base, monitored orders, configured payouts, resolved disputes, running campaigns, generated reports and audit logs | Admin panel governed by RBAC |
Customer journey: registration, login, homepage, product search, product details, add to cart, checkout, payment, order confirmation, shipment tracking, delivery, review. Guest checkout is supported alongside registered customer checkout, and the storefront provides recently viewed products, responsive product listing grids, and easy-to-use filters and sorting.
Seller journey: seller registration, business verification, store creation, product listing, inventory management, order received, order processing, shipment, payment settlement.
Administrator journey: admin login, dashboard, seller approval, product approval, order monitoring, payment monitoring, commission management, reports and analytics. System configuration covers general settings, payment gateway configuration, tax configuration, shipping configuration, and security and access management.
Trigger: customer opens the storefront (homepage, category, subcategory, or search results page).
Branch: no matching products — the listing/search page shows an empty result state and the customer can broaden filters or return to categories. Loading states and skeleton screens cover slow responses.
Trigger: customer decides to buy from the cart.
Branch: payment fails or is abandoned — the order is recorded as a failed payment and the customer remains at payment selection to retry or choose another method. Branch: address missing — customer adds a new address before continuing. Branch: stock unavailable at validation — customer is prompted to adjust the cart.
Trigger: customer opens order tracking or order history.
Trigger: customer decides to cancel or is dissatisfied after delivery.
Trigger: customer has received a product.
Trigger: customer opens the account area.
Trigger: customer has a question or problem.
Trigger: a business wants to sell on the marketplace.
Branch: rejected or suspended — the seller cannot publish products until the administrator reinstates the account.
Trigger: seller needs to list or update catalog items.
Trigger: a new order includes the seller's products.
Trigger: customer submits a return or refund request.
Trigger: seller reviews performance or settlement.
Trigger: seller receives a customer query or needs to adjust account details.
Trigger: administrator signs in to the centralized admin dashboard.
These journeys are independent entry points; customers, sellers, and administrators may start any of them without a fixed sequence, subject to the access rules in the detailed requirements. Every screen in these journeys is connected to the backend APIs and implements its business logic; navigation links, buttons, forms, and actions have defined behaviors, and no required screen is a placeholder or disconnected static design.
Generate detailed end-to-end user journeys for:
Registration → Login → Homepage → Product Search → Product Details → Add to Cart → Checkout → Payment → Order Confirmation → Shipment Tracking → Delivery → Review.
Seller Registration → Business Verification → Store Creation → Product Listing → Inventory Management → Order Received → Order Processing → Shipment → Payment Settlement.
Admin Login → Dashboard → Seller Approval → Product Approval → Order Monitoring → Payment Monitoring → Commission Management → Reports and Analytics.
[Design proposal; unspecified choices are defaults.]
The visual system follows Rasmus Andersson: systematic product craft with a point of view—warm paper, graphite ink, and a scarce tangerine signal. Customer surfaces use page ground #F6F3EE, white surfaces #FFFFFF, graphite text and primary actions #17181A, muted metadata #6E6A63, hairline borders #E4DFD6, and tangerine accent #E4572E. Teal #1F7A6B marks in-stock/success only and amber #C98A00 warnings only; blue or indigo is never a functional colour. Seller and admin chrome uses #141517 ground, #1C1D20 surfaces, #F2EFE9 text, and the same tangerine signal.
Headings use Space Grotesk at 500–700 weight with -0.02em to -0.03em tracking, sentence case except 11px uppercase micro-labels at 0.08em. Body and dense interface copy use Inter Tight. Prices, ratings, order totals, and dashboard KPIs use tabular Space Grotesk figures so columns align. Type scale: display clamp(40px, 6vw, 88px), H1 clamp(30px, 4vw, 48px), H2 clamp(24px, 3vw, 32px), H3 22px, body 16px/1.55, dense table and card metadata 14px, labels 13px, captions 12px, micro-labels 11px.
Use an 8-point spacing rhythm, a 12-column grid, 24px gutters, a 1280px maximum content width, and 32px side padding (16px at 375px). Buttons and inputs use 6px radius, product cards and panels 10px, modals and the hero promo block 14px. Prefer precise 1px hairlines over shadows; reserve 0 1px 2px rgba(23,24,26,.06) for dropdowns and sticky headers. Avoid pills except status chips, gradients, glass, blobs, oversized shadows, and decorative stock imagery.
The responsive customer entry uses a sticky black utility bar (delivery pin, account, wishlist, cart count), a white search header with category mega-menu, a 4-up category rail, a 2:1 promotional banner, and dense product rails at 4/2/1.5 cards for 1280/768/375. Seller and admin portals share a 248px dark sidebar with grouped nav and 11px section labels, a 56px header with search, notifications and avatar, and a paper content canvas. Product cards use 1:1 or 4:5 product photography with a 1px inner border, seller name in 12px muted, 18px tabular price, struck-through MRP, tangerine discount chip, 5-star glyph row with review count, and a hairline footer with wishlist and quick-add. Product detail splits gallery left and buy-box right with price, rating, seller, delivery estimate, and one tangerine CTA. Imagery is optimized and lazy-loaded; readable text and controls stay whole within the viewport at 375px, 768px, and 1280px.
Create a modern, professional, responsive, and user-friendly design.
Use a clean and modern e-commerce visual language.
Create a consistent design system across customer, seller, and admin portals.
Use a professional color palette with a clear primary and secondary color.
Maintain consistent typography, spacing, buttons, cards, tables, and form elements.
Use intuitive navigation and well-defined information hierarchy.
Implement responsive layouts for desktop, tablet, and mobile devices.
Avoid unnecessary UI elements and visual clutter.
Use product cards with high-quality images, prices, discounts, ratings, and wishlist actions.
Professional homepage with promotional banners.
Category navigation.
Featured products and deals.
Best-selling products.
Recommended products.
Sidebar navigation.
Header with search, profile, and notifications.
Establish a consistent design system.
Ensure all pages follow the same design language.
Generate the UI/UX design for every page.
[Design proposal; unspecified choices are defaults.]
Signature concept: The Commerce Instrument Panel. One precise design language connects shoppers, sellers, and administrators without making their workflows feel identical. Warm paper establishes trust; graphite provides structure and authority; one tangerine signal marks meaningful action, discount, focus, or active navigation.
The public entry is an editorial 12-column hero rather than a centred SaaS stack. The left seven columns carry the oversized two-line headline “Everything you need. Every seller you trust.”, a 16px muted subline, a black search field with a tangerine Search action, and three hairline-divided tabular figures: 12k sellers, 4M products, 48h delivery. The right five columns bleed a graphite #17181A block to the viewport edge holding one large 4:5 product photograph, a tangerine discount badge, tabular price, and a small white Shop the deal action. Beneath the band, a full-width hairline ticker of category names scrolls slowly left, leading into category navigation, featured products, deals, best sellers, and recommendations. At 768px the graphite block drops below the type at 16:9; at 375px it stacks under the search with the headline wrapping to three lines and no element cropped.
The same grammar scales into operational surfaces: KPI strips use 40px tabular numerals; tables use sticky headers, zebra-free hairline rows, right-aligned numbers, and inline status chips; sidebar navigation uses 11px grouped labels and a hairline active-rail marker. Loading, empty, error, and success states are first-class components: paper-tone skeletons replace content during loading, while schematic line diagrams and one clear black retry/action button replace blank screens. Confirmation dialogs, validation messages, action menus, wishlist controls, ratings, prices, discounts, and cart actions stay consistent across responsive customer, seller, and admin interfaces.
[Design proposal; unspecified choices are defaults.]
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
cubic-bezier(.2,0,0,1) for focus, hover, tabs, drawers, and navigation; a 1.4s linear paper-tone skeleton shimmer for loading; a 160ms slide-in for cart badges and toasts. No bounce, parallax, scroll-jacking, or decorative motion.prefers-reduced-motion makes state changes instant, stops the ticker, replaces animated skeleton shimmer with a static skeleton, and preserves category/product rows as wrapped or horizontally scrollable content so every item can be brought fully into view.Include loading states, skeleton screens, empty states, error states, and success messages.
Provide clear validation messages and confirmation dialogs.
Define:
Primary and foreign keys.
One-to-one, one-to-many, and many-to-many relationships.
Unique constraints.
Database indexes.
Appropriate timestamps.
Soft deletion where necessary.
Data validation and integrity rules.
Create a modular and maintainable backend architecture.
Caching for frequently accessed data.
Structured logging and monitoring.
Rate limiting and security protections.
Implement:
Secure password hashing.
OTP verification.
Access and refresh token management.
Role-based authorization.
Protection against SQL injection and XSS.
CSRF protection where applicable.
Secure file upload validation.
API rate limiting.
Payment webhook signature verification.
Secure handling of sensitive information.
Database backups.
Error monitoring.
Pagination for large datasets.
Optimized database queries.
Image optimization and lazy loading.
Prioritize functionality, scalability, maintainability, security, responsive UI/UX, and consistency across the entire system.
Design a normalized, scalable relational database.
Include appropriate entities and relationships for:
Users
Roles
Permissions
Customer Profiles
Seller Profiles
Seller Stores
Addresses
Products
Product Images
Categories
Brands
Separate the system into logical modules:
Authentication and Authorization
User Management
Seller Management
Product Catalog
Category Management
Inventory Management
Search and Discovery
Shopping Cart
Checkout
Order Management
Payment Management
Shipping Management
Promotions and Coupons
Reviews and Ratings
API documentation using Swagger/OpenAPI.
Use the following stack unless the existing project environment requires alternatives:
Frontend:
React.js or Next.js.
TypeScript.
Tailwind CSS.
Reusable component architecture.
React Query or an equivalent server-state management solution.
Backend:
Python Django and Django REST Framework or Node.js with NestJS.
REST APIs.
Background job processing.
Database:
PostgreSQL.
Redis for caching and background processing.
Storage:
Integrations:
Shipping provider APIs.
Email and SMS notification services.
Infrastructure:
Docker and Docker Compose.
Nginx.
CI/CD pipeline.
Cloud deployment architecture.
Database Schema and ER Diagrams.
High-Level Architecture Diagram.
Low-Level Architecture Diagram.
Complete Frontend Application.
Complete Backend Application.
API Documentation.
Authentication and Authorization System.
Payment and Shipping Integration Structure.
Admin Dashboard.
Seller Dashboard.
Deployment Documentation.
Ensure that all journeys are connected and that navigation between screens works correctly.
Do not skip any requested module, page, or workflow.
Do not generate only a homepage or a few sample screens.
Clearly distinguish between implemented features, mock integrations, and integrations requiring external credentials.
Product Variants
Product Attributes
Inventory
Carts
Cart Items
Wishlists
Wishlist Items
Orders
Reviews
Ratings
Returns
Replacements
Seller Commissions
Seller Settlements
Notifications
Support Tickets
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!