twc-rumeo

byfree followers

Build a complete, functional, production-quality **mobile-first multi-vendor web app** called **RUMEO**, powered by **TWC WebCore**. ## PRODUCT RUMEO is a local commerce marketplace based on **BOPIS (Buy Online, Pick Up In Store)**. **Tagline:** Discover Local. Shop Online. Pick Up Nearby. Core flow: **Discover Store → Browse Catalogue → Order → Vendor Prepares → Customer Picks Up → Verify Code → Complete** RUMEO is NOT a delivery platform. Customers purchase online and collect orders directly from physical stores. Build a genuinely functional application with frontend, backend, database, authentication, authorization, CRUD, validation and persistent data. Do NOT create a static mockup. --- ## BRAND Primary brand: **RUMEO** Technology brand: **TWC WebCore** Parent brand: **TWC Group of Services** Use RUMEO prominently. Use "Powered by TWC WebCore" subtly in the footer and platform/vendor areas. Brand personality: * Modern * Friendly * Local * Trustworthy * Youthful * Indian startup feel Design a polished, premium but simple light UI. Avoid generic AI aesthetics, excessive gradients, glassmorphism, huge rounded cards and unnecessary animations. **Mobile-first is mandatory.** --- # USER ROLES ### CUSTOMER Discover stores, search products, browse catalogues, add to cart, checkout, choose pickup time, select payment method, track orders, view pickup code and order history. ### VENDOR Register business, manage store, categories, products, inventory and hours; receive/accept/reject orders; prepare orders; mark ready; verify pickup codes; view analytics; pause orders. ### ADMIN Approve/reject/suspend vendors, manage vendors/customers/orders, view platform analytics and settings. Implement secure role-based access and protected routes. --- # CUSTOMER MARKETPLACE ## Homepage Create a polished marketplace homepage. Hero: **Discover Local. Shop Online. Pick Up Nearby.** Supporting text: "Shop from stores around you, order online and collect your purchase directly from the shop." CTAs: **Explore Stores** **Become a Vendor** Include: * Search * Nearby stores * Popular stores * Popular categories * Recently added stores * How RUMEO Works * Vendor CTA * Trust section * Footer ## Store Discovery Create `/stores`. Features: * Search stores/products * Category filter * Location discovery * Open/closed status * Sorting Store cards: * Logo * Name * Category * Location * Open/closed * Preparation time * Product count * View Store --- # PUBLIC STORE Every approved vendor gets a storefront: `/store/[store-slug]` Display: * Logo * Cover image * Store name * Category * Description * Address * Phone * Hours * Open/closed status * Preparation time * Pickup instructions * Categories Products: * Image * Name * Description * Price * Availability * Stock * Quantity selector * Add to Cart Customers can browse without logging in but must authenticate at checkout. --- # CART A cart can contain products from **only one store**. If another store's product is added, show: "You already have items from another store." Options: **Clear Cart & Continue** **Keep Current Cart** Cart supports: * Quantity update * Remove item * Subtotal * Total * Store information --- # CHECKOUT Collect: * Name * Phone * Email * Pickup date * Pickup time/window Payment: * Pay Online * Pay At Store For MVP, **simulate payment only**. Do not integrate Razorpay yet, but structure payment logic for future integration. After checkout create: * Order ID * Unique pickup code, e.g. `RUMEO-4821` * Store details * Pickup time * Items * Total * Payment status * Order status Make the pickup code highly visible. --- # ORDER SYSTEM Statuses: **PLACED → ACCEPTED → PREPARING → READY FOR PICKUP → PICKED UP → COMPLETED** Also support **CANCELLED**. Prevent invalid state transitions. Customer `/orders`: * Active orders * Completed orders * Cancelled orders * Status timeline * Order details * Pickup code Internal notifications: * Order placed * Accepted * Preparing * Ready * Completed --- # PICKUP VERIFICATION Create `/vendor/pickup`. Vendor enters pickup code. Validate: * Code exists * Correct vendor * Order is ready * Not already collected If valid, show customer, order, items, total and payment status. Button: **Confirm Pickup** Then order becomes **PICKED UP → COMPLETED**. Prevent duplicate pickup verification. --- # VENDOR ONBOARDING Fields: * Owner name * Business name * Phone * Email * Category * Address * City * Pincode * Description * Logo * Cover image * Opening hours * Pickup instructions * Preparation time New vendors start as **PENDING APPROVAL**. Only approved vendors become public. --- # VENDOR DASHBOARD Create `/vendor/dashboard`. Show: * Today's orders * Pending orders * Ready for pickup * Today's sales * Products * Low stock Quick actions: Add Product | Orders | Catalogue | Inventory | Store Settings | Pickup ## Orders Tabs: New | Accepted | Preparing | Ready | Completed | Cancelled Actions: Accept | Reject | Start Preparing | Mark Ready | Verify Pickup ## Products Full CRUD. Fields: Name, description, category, price, compare-at price, image, SKU, stock, low-stock threshold, availability. Availability: Available | Low Stock | Out of Stock | Hidden ## Categories Create, edit, delete and reorder. ## Inventory Prevent overselling. Reserve inventory when an order is placed. Release inventory if cancelled. Finalize deduction when picked up. Show low-stock warnings. ## Store Settings Manage: Name, logo, cover, description, address, phone, hours, pickup instructions, preparation time and active/inactive status. Include **Pause New Orders**. --- # ADMIN DASHBOARD Create `/admin`. Metrics: * Total vendors * Approved vendors * Pending vendors * Customers * Orders * Orders today * Platform GMV * Estimated commission * Active stores Admin can: * Approve/reject vendors * Suspend/reactivate vendors * Search/filter vendors * View customers * View all orders * Filter orders by vendor/status/date * View analytics --- # DATABASE Use a proper relational database. Tables/entities: `users` `profiles` `vendors` `stores` `store_hours` `categories` `products` `inventory` `customers` `orders` `order_items` `payments` `pickup_codes` `notifications` Critical architecture: **ONE PLATFORM → MANY VENDORS → EACH VENDOR HAS ITS OWN STORE, CATALOGUE, INVENTORY AND ORDERS** Vendors must NEVER access another vendor's data. Customers can only access their own orders. Admins have platform-wide access. Implement server-side authorization and ownership checks. --- # AUTHENTICATION Implement: * Customer signup/login * Vendor signup/login * Admin login * Logout * Protected routes * Role-based redirects Do not rely only on client-side role checks. --- # MOBILE EXPERIENCE Mobile-first design. Bottom navigation: **Home | Stores | Orders | Cart | Profile** Requirements: * Touch-friendly controls * Sticky cart CTA where useful * Compact product cards * Easy checkout * No horizontal scrolling * Responsive dashboards * Tables become mobile-friendly cards * Fast navigation Desktop should enhance the mobile experience. --- # DEMO DATA Populate realistic Indian demo data. Create 5 stores: 1. Local Fashion Store 2. Gift & Accessories Store 3. Stationery Store 4. Mobile Accessories Store 5. Local Grocery Store Each needs logo, cover, categories, products, prices, inventory and hours. Also create sample customers/orders so dashboards look functional. --- # ROUTES Customer: `/` `/stores` `/store/[slug]` `/cart` `/checkout` `/orders` `/orders/[id]` `/profile` Vendor: `/vendor/onboarding` `/vendor/dashboard` `/vendor/orders` `/vendor/products` `/vendor/categories` `/vendor/inventory` `/vendor/pickup` `/vendor/store` `/vendor/settings` Admin: `/admin` `/admin/vendors` `/admin/customers` `/admin/orders` `/admin/analytics` --- # UI STATES Every major screen needs loading, empty, error and success states. Examples: * No stores found * No products * No orders * Vendor awaiting approval * Product unavailable * Invalid pickup code Use toast notifications for important actions. --- # FOOTER **RUMEO** Discover Local. Shop Online. Pick Up Nearby. Links: About | How RUMEO Works | For Vendors | Contact | Privacy | Terms Attribution: **Powered by TWC WebCore** **A TWC Group of Services product** --- # DO NOT BUILD YET Do not implement: * Delivery drivers * Delivery tracking * Live GPS * Real payment gateway * GST/accounting * Vendor subscriptions * Loyalty * Advanced coupons * AI chatbot * Recommendation engine * Multi-city logistics * Complex commission settlement Keep architecture extensible for future versions. --- # ACCEPTANCE TEST The following MUST work using the actual backend/database: 1. Vendor registers. 2. Admin approves vendor. 3. Vendor creates category. 4. Vendor adds product/inventory. 5. Product appears publicly. 6. Customer discovers store. 7. Customer adds product. 8. Customer checks out. 9. Order is saved to database. 10. Pickup code is generated. 11. Vendor receives order. 12. Vendor accepts. 13. Vendor prepares. 14. Vendor marks Ready. 15. Customer sees updated status. 16. Vendor enters pickup code. 17. System validates it. 18. Vendor confirms pickup. 19. Order becomes Completed. 20. Inventory updates. 21. Customer history updates. 22. Vendor analytics update. If something only looks functional but isn't connected to the backend/database, implement the real functionality. Build **RUMEO as a real multi-vendor SaaS web application powered by TWC WebCore**, not a static landing page.