snowy-topaz

bySupash R
No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for snowy-topaz

Page 1 of 38

1. Introduction

Act as a senior full-stack developer, UI/UX designer and e-commerce specialist.

Build a fully functional, premium-looking online thrift clothing store named VintageThriftHum, located in Belgaum (Belagavi), Karnataka, India.

The website should take inspiration from the design and shopping experience of thriftacular.com, but have its own unique branding, layout and identity.

IMPORTANT: This must be a fully functional e-commerce website, not just a static frontend demo.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. BRAND IDENTITY & DESIGN

Brand Name: VintageThriftHum

Location: Belgaum, Karnataka, India.

Brand Category: Online Thrift Clothing Store.

Design Philosophy:

  • Minimalistic

  • Premium

  • Modern

  • Clean

  • Youth-oriented

Page 2 of 38

The project name is snowy-topaz.

2. System Overview

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Build the complete application with a premium user interface, functional backend, secure admin dashboard and working WhatsApp ordering system.

<!-- planning-notes:v1:start -->

Planning notes

Planning resolved these page and owner names itself instead of stopping. Review them before building.

Name changes

  • admin: Listed both as a page and as a sign-in surface; kept the sign-in surface
<!-- planning-notes:v1:end -->
Page 3 of 38

3. Functional Requirements

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. HOMEPAGE

Create a beautiful homepage containing:

A. Navigation Bar:

  • VintageThriftHum logo.

  • Home.

  • Shop All.

  • New Arrivals.

  • Categories.

  • About Us.

  • Shopping Cart icon.

C. Featured Categories:

  • Oversized T-Shirts

  • Shirts

  • Sweatshirts

  • Hoodies

  • Jeans

  • Cargo Pants

Page 4 of 38
  • Trousers

  • Jackets

  • Other Accessories

D. New Arrivals:

Display the latest products added by the admin.

E. Trending Products:

Display popular products.

F. Why VintageThriftHum?

  • Affordable Fashion

  • Unique Thrift Finds

  • Carefully Selected Pieces

  • Easy WhatsApp Ordering

G. Footer:

  • About Us

  • Contact Information

  • Instagram link

  • WhatsApp contact

  • Location: Belgaum, Karnataka

  • Privacy Policy

  • Terms and Conditions

Page 5 of 38

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. PRODUCT CATALOGUE

Create a fully functional shopping catalogue.

Every product card should display:

  • Product image.

  • Product name.

  • Selling price in ₹.

  • Original price (optional).

  • Discount percentage (optional).

  • Product availability.

  • Product category.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. PRODUCT CATALOGUE

Create a fully functional shopping catalogue.

When a customer clicks a product, open a detailed product page.

Product detail page must include:

  • Multiple product images.

  • Product name.

  • Price.

  • Description.

Page 6 of 38
  • Available sizes.

  • Product condition (New / Like New / Good).

  • Measurements, if provided.

  • Stock availability.

  • Add to Cart button.

Since this is a thrift store, each product may have limited or single-piece inventory.

Automatically display SOLD OUT when inventory reaches zero.

Prevent customers from ordering unavailable products.

Add:

  • Search functionality.

  • Category filters.

  • Price sorting.

  • Newest arrivals sorting.

  • Availability filtering.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. SHOPPING CART

Implement a fully working shopping cart.

Customers should be able to:

  • Add products to cart.
Page 7 of 38
  • Remove products.

  • Increase or decrease quantities.

  • View product images.

  • View individual prices.

  • View total cart value.

  • Continue shopping.

  • Proceed to checkout.

Display:

Subtotal

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. SHOPPING CART

Implement a fully working shopping cart.

The cart should persist even if the customer refreshes the website.

Delivery Charges (if applicable)

Total Amount

  1. WHATSAPP CHECKOUT SYSTEM

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

THIS IS THE MOST IMPORTANT FEATURE.

All orders must be placed through WhatsApp.

STEP 3:

Page 8 of 38

Display a simple checkout form asking for:

  • Customer Name

  • WhatsApp/Mobile Number

  • Delivery Address

  • City

  • PIN Code

  • Additional Instructions (optional)

STEP 4:

Display the complete order summary.

STEP 5:

Add a prominent button:

"PLACE ORDER ON WHATSAPP"

STEP 6:

When the customer clicks the button:

  1. Save the complete order in the website database.

  2. Generate a unique Order ID.

  3. Generate a formatted WhatsApp message containing all order details.

The WhatsApp message should look professional.

Example:

Hello VintageThriftHum!

Page 9 of 38

I would like to place an order.

ORDER ID: #VTH1001

CUSTOMER DETAILS:

Name: [Customer Name]

Phone: [Customer Phone]

Address: [Delivery Address]

ORDER ITEMS:

  1. Oversized Vintage T-Shirt

  2. Open WhatsApp using the official wa.me click-to-chat link.

  3. Redirect the customer to the shop's WhatsApp number with the message prefilled.

The customer should only need to press SEND in WhatsApp.

Size: L

Quantity: 1

Price: ₹399

  1. Cargo Pants

    Size: 32

    Price: ₹599

Subtotal: ₹998

Delivery: To be confirmed

Total: ₹998

Page 10 of 38

Please confirm my order and share the payment details.

Thank you!

IMPORTANT TECHNICAL REQUIREMENTS:

  • Store every order in Supabase before opening WhatsApp.

IMPORTANT TECHNICAL REQUIREMENTS:

  • Use a configurable WhatsApp business number.

  • Never hardcode the WhatsApp number in multiple components.

  • Properly URL-encode WhatsApp messages.

  • Display a message explaining that the customer must press SEND in WhatsApp.

  • Do not claim an order is confirmed until the shop owner confirms it.

  • Do not automatically mark an order as paid.

  • Keep the order status as Pending until the admin updates it.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. ADMIN LOGIN PANEL

Create a separate, secure admin dashboard.

Customers must never see the admin dashboard or its login credentials.

Admin login URL:

/admin

Initial Admin Username:

supash

Page 11 of 38

Initial Password:

Use the password I supplied during project setup. Configure it securely through Supabase authentication or server-side secrets.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. ADMIN DASHBOARD

Create a professional admin dashboard with a clean sidebar.

Sidebar:

  1. Dashboard

  2. Orders

  3. Products

  4. Add New Product

  5. Inventory

  6. Categories

  7. Store Settings

  8. Logout

DASHBOARD OVERVIEW:

Display:

  • Total Orders.

  • New Orders.

  • Pending Orders.

Page 12 of 38
  • Confirmed Orders.

  • Completed Orders.

  • Total Products.

  • Products Out of Stock.

  • Total Sales (based on orders marked as paid).

Display recent orders and inventory alerts.

  1. ORDER MANAGEMENT

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Create a complete order management system.

Display:

  • Order ID.

  • Customer Name.

  • Customer Phone Number.

  • Products Ordered.

  • Product Sizes.

  • Quantities.

  • Total Amount.

  • Delivery Address.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. ORDER MANAGEMENT
Page 13 of 38

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Create a complete order management system.

Whenever a customer submits an order through WhatsApp checkout, save it in the database.

  1. ORDER MANAGEMENT

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Create a complete order management system.

The admin should be able to see all orders placed since their previous visit.

  • Order Date and Time.

  • Order Status.

  • Payment Status.

Order statuses:

  • New

  • Pending Confirmation

  • Confirmed

  • Processing

  • Shipped

  • Delivered

  • Cancelled

Add buttons:

Page 14 of 38
  • View Order

  • Open Customer WhatsApp Chat

  • Confirm Order

  • Mark as Processing

  • Mark as Shipped

  • Mark as Delivered

  • Cancel Order

IMPORTANT:

Create a New Orders notification/badge in the admin sidebar.

When the admin opens the dashboard, highlight orders received since the last admin visit.

Persist the last-visited timestamp in the database.

Allow the admin to search orders by Order ID, customer name or phone number.

Provide filters for date, order status and payment status.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. PRODUCT & INVENTORY MANAGEMENT

The admin must have complete control over the products.

Create an Add Product form containing:

  • Product Name

  • Product Description

Page 15 of 38
  • Category

  • Selling Price

  • Original Price (optional)

  • Product Images

  • Available Sizes

  • Stock Quantity

  • Product Condition

  • Product Tags

  • Featured Product toggle

  • New Arrival toggle

  • Product Availability

IMAGE MANAGEMENT:

  • Upload multiple images.

  • Preview uploaded images.

  • Delete images.

  • Change the main product image.

  • Store images in Supabase Storage.

INVENTORY MANAGEMENT:

  • Increase stock.

  • Decrease stock.

Page 16 of 38
  • Edit stock quantity.

  • Automatically update product availability.

  • Display low-stock alerts.

  • Display sold-out products.

  • Prevent overselling.

Each product should have a unique product ID.

Allow the admin to edit or delete existing products.

  1. STORE SETTINGS

Create a settings section where the admin can update:

  • Store Name.

  • WhatsApp Business Number.

  • Instagram Profile Link.

  • Store Contact Number.

  • Store Address.

  • Delivery Charges.

  • Free Delivery Threshold.

  • Store Announcement.

  • Homepage Banner.

  • Store Logo.

All settings should update dynamically without requiring code changes.

Page 17 of 38
  • Real-time order updates.

  • Secure admin-only operations.

  • Persistent cart functionality.

  • Proper error handling.

  • Input validation.

Make sure orders are stored even if the customer closes WhatsApp without sending the message.

Clearly distinguish between:

  • Order submitted to the website.

  • WhatsApp message sent by customer.

  • Order confirmed by admin.

Do not falsely assume that a prefilled WhatsApp message has been sent. If automatic WhatsApp message delivery or delivery-status tracking is required in the future, it will need an approved WhatsApp Business API integration.

  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Build this as a real, working e-commerce application.

Do not leave buttons non-functional.

Do not use fake product data after setup.

The complete customer journey should be:

VISIT WEBSITE

Page 18 of 38
   ↓

BROWSE CLOTHES

SELECT PRODUCT

  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do not leave buttons non-functional.

ADD TO CART

PROCEED TO CHECKOUT

ENTER CUSTOMER DETAILS

PLACE ORDER ON WHATSAPP

ORDER SAVED IN DATABASE

WHATSAPP OPENS WITH ORDER SUMMARY

CUSTOMER PRESSES SEND

ADD / EDIT / DELETE PRODUCTS

4. User Personas

RoleResponsibilitiesInputsDecisions / GoalsAccess
Customer (shopper)Browses the catalogue, adds clothing items to the cart, proceeds to checkout, enters customer details, places the order via WhatsAppProduct listings (including the latest products added by the admin), cart contents, own contact and delivery detailsWhich items to buy; whether to complete checkout; success = order placed on WhatsApp and confirmed by the shop ownerPublic storefront only; no registration or login required; must never see the admin dashboard or its credentials
Administrator (shop owner)Signs in to the admin dashboard, reviews orders placed since the previous visit, contacts customers, confirms orders, manages inventory and has complete control over productsNew orders, customer contact details, product and stock dataOrder status progression (confirm, processing, shipped, delivered, cancel); inventory and product changes; success = orders confirmed and inventory kept currentAuthenticated admin only, via /admin; all admin routes protected; credentials never exposed in frontend code or browser JavaScript
Page 19 of 38

4.1 Customer journey

  1. Arrives on the storefront, typically from an Instagram link on a mobile browser.
  2. Browses products, including the latest products added by the admin.
  3. Adds clothing items to the shopping cart.
  4. Clicks Proceed to Checkout.
  5. Enters customer details.
  6. Places the order on WhatsApp.
  7. The shop owner confirms the order.

4.2 Administrator journey

  1. Admin login at /admin.
  2. Dashboard.
  3. View new orders (all orders placed since the previous visit).
  4. Contact customers (including opening the customer WhatsApp chat).
  5. Confirm orders, then move them through processing, shipped and delivered, or cancel.
  6. Manage inventory and products.

Default (not specified in evidence): the customer is assumed to be a single shopper role regardless of device; no separate guest or returning-customer personas are distinguished.

5. Core User Flows

Page 20 of 38

5.1 Browse and Discover Products

Actor: Customer (no account required). Trigger: Visiting the storefront.

  1. Customer lands on the homepage and sees the navigation bar (Home, Shop All, New Arrivals, Categories, About Us, Shopping Cart icon), the hero banner with the tagline "GOOD STYLE. BETTER FINDS." and the "SHOP NOW" CTA.
  2. Customer explores Featured Categories (Oversized T-Shirts, Shirts, Sweatshirts, Hoodies, Jeans, Cargo Pants, Trousers, Jackets, Other Accessories), Latest Products, Trending Products, and the "Why VintageThriftHum?" section.
  3. Customer opens the catalogue and narrows results using search, category filters, price sorting, newest-arrivals sorting, and availability filtering.
  4. Customer opens a product detail page showing multiple images, name, price, description, available sizes, condition (New / Like New / Good), measurements if provided, and stock availability.

Result: Customer identifies items of interest. Branch: Products with zero inventory display SOLD OUT and cannot be ordered.

Page 21 of 38

5.2 Manage the Shopping Cart

Actor: Customer. Trigger: Selecting "Add to Cart" on a product.

  1. Customer adds a product (with chosen size) to the cart.
  2. Customer reviews the cart: product images, individual prices, quantities, and total cart value (subtotal).
  3. Customer increases or decreases quantities, removes products, or continues shopping.
  4. Cart persists across sessions.

Result: A ready-to-checkout cart. Branch: Unavailable products are blocked from being added or ordered.

Page 22 of 38

5.3 Place an Order via WhatsApp Checkout

Actor: Customer; supporting actors: website backend (Supabase) and WhatsApp.

  1. Customer clicks "Proceed to Checkout."
  2. Customer completes the simple checkout form: Customer Name, WhatsApp/Mobile Number, Delivery Address, City, PIN Code, and optional Additional Instructions.
  3. Customer reviews the complete order summary.
  4. Customer clicks the order button. The system then:
    • Saves the complete order in the Supabase database before opening WhatsApp.
    • Generates a unique Order ID (e.g., #VTH1001).
    • Builds a formatted, URL-encoded WhatsApp message containing customer details, order items (size, quantity, price), subtotal, delivery (to be confirmed), total, and a request to confirm and share payment details.
    • Opens WhatsApp via the official wa.me click-to-chat link to the shop's number with the message prefilled.
  5. The page explains that the customer must press SEND in WhatsApp; the customer presses SEND.

Result: Order is recorded on the website and a WhatsApp message is sent to the shop. Branch: If the customer closes WhatsApp without sending, the order remains stored. The system clearly distinguishes order submitted to the website, WhatsApp message sent by customer, and order confirmed by admin. No payment gateway is involved; payment is discussed on WhatsApp, after which the order is processed.

Page 23 of 38

5.4 Admin Signs In

Actor: Administrator. Trigger: Navigating to /admin.

  1. Admin authenticates with the initial username supash and the setup-supplied password, configured securely via Supabase authentication or server-side secrets.
  2. All admin routes are protected; only authenticated administrators reach admin functions.

Result: Access to the admin dashboard. Branch: Unauthenticated visitors never see the dashboard or credentials; passwords are never stored in frontend code or exposed in browser JavaScript.

Page 24 of 38

5.5 Admin Reviews and Manages Orders

Actor: Administrator. Trigger: Opening the dashboard.

  1. Admin views dashboard overview metrics: Total Orders, New Orders, Pending Orders, Confirmed Orders, Completed Orders, Total Products, Products Out of Stock, and Total Sales (orders marked as paid), plus recent orders and inventory alerts.
  2. A New Orders badge in the sidebar highlights orders received since the last admin visit, using a last-visited timestamp persisted in the database.
  3. Admin searches orders by Order ID, customer name, or phone number, and filters by date, order status, and payment status.
  4. Admin opens an order to view Order ID, customer name, phone, products ordered, sizes, quantities, total amount, and delivery address.
  5. Admin contacts the customer, confirms the order, and advances it through Confirm Order, Mark as Processing, Mark as Shipped, Mark as Delivered, or Cancel Order, and can open the customer's WhatsApp chat directly.

Result: Order status reflects the real fulfillment state. Branch: Cancelled orders are recorded as such; real-time order updates keep the list current.

Page 25 of 38

5.6 Admin Manages Products and Inventory

Actor: Administrator. Trigger: Adding or maintaining catalogue items.

  1. Admin opens Add New Product and enters Product Name, Description, Category, Selling Price, Original Price (optional), Images, Available Sizes, Stock Quantity, Condition, Tags, Featured toggle, New Arrival toggle, and Availability.
  2. Admin uploads multiple images to Supabase Storage, previews them, deletes images, and sets the main image.
  3. Admin edits or deletes existing products.
  4. Admin adjusts inventory (increase, decrease, edit stock); availability updates automatically, low-stock and sold-out alerts display, and overselling is prevented.

Result: Catalogue stays accurate and current. Branch: Stock reaching zero automatically marks the product SOLD OUT.

5.7 Admin Configures Store Settings

Actor: Administrator. Trigger: Updating store-wide configuration.

  1. Admin edits Store Name, WhatsApp Business Number, Instagram Profile Link, Store Contact Number, Store Address, Delivery Charges, Free Delivery Threshold, Store Announcement, Homepage Banner, and Store Logo.

Result: Storefront reflects updated settings. Branch: Changes propagate to the homepage and checkout messaging.

Page 26 of 38

5.8 End-to-End Journey

VISIT WEBSITE → BROWSE CLOTHES → SELECT PRODUCT → ADD TO CART → PROCEED TO CHECKOUT → ENTER CUSTOMER DETAILS → PLACE ORDER ON WHATSAPP → WHATSAPP OPENS WITH ORDER SUMMARY → CUSTOMER PRESSES SEND → PAYMENT DISCUSSED ON WHATSAPP → SHOP OWNER CONFIRMS ORDER → ORDER PROCESSED.

Checkout workflow:

STEP 1:

Customer adds clothing items to the shopping cart.

STEP 2:

Customer clicks "Proceed to Checkout".

   ↓

SHOP OWNER CONFIRMS ORDER

   ↓

PAYMENT DISCUSSED ON WHATSAPP

   ↓

ORDER PROCESSED

The admin journey should be:

ADMIN LOGIN

   ↓

DASHBOARD

VIEW NEW ORDERS

Page 27 of 38

CONTACT CUSTOMERS

CONFIRM ORDERS

MANAGE INVENTORY

6. Visuals Colors and Theme

[Design proposal; unspecified choices are defaults.]

Muse: Kenya Hara — “Emptiness as Content”

VintageThriftHum is a premium, youth-oriented online thrift clothing store in Belgaum (Belagavi), Karnataka, India, inspired by thriftacular.com's shopping experience but with its own branding, layout and identity. The visual language is minimal, modern, clean and quiet: each one-of-one garment is a still-life object in generous space rather than a crowded catalogue.

Page 28 of 38
  • Light-mode palette: background #FAF8F4; surface #F1EDE6; text and primary action #141414; accent #8C6A4A; muted text #8A857D; hairline borders #DDD6CB. Ink black carries typography and the “Place Order on WhatsApp” action; beige and wood brown are reserved for surfaces, rules and sold-out labels. One accent colour only.
  • Typography: Zen Kaku Gothic New, weights 300–400, for headings and labels; Zen Maru Gothic for body copy. 1.25 modular scale: 44/34/26/18/15px, hero heading clamped from 44px on mobile to 96px on desktop with 0.02em tracking. Sentence case for copy; small labels in wide-tracked capitals.
  • Shape and layout: square product imagery, sharp corners or 2px radius, 1px rules, no blobs, stickers, gradients, glass panels or card shadows. Wide page margins and generous whitespace. Product grids: four columns at 1280px, two at 768px, one at 375px. Every headline, wordmark, label, number, card text and control stays wholly inside the viewport and its container at 375px, 768px and 1280px, wrapping or scaling to fit; imagery and decoration may bleed or crop but never cover readable text or controls.
  • Imagery: one garment per frame on a plain paper or linen ground, soft natural light, visible fabric texture and stitching in close crops. Product cards use a square image, hairline #DDD6CB border and a wood-brown “One of one” tag.
  • Public entry copy: label “VintageThriftHum · Belgaum”; headline “Good Style. Better Finds.”; subline “Discover unique thrift pieces. Upgrade your wardrobe without upgrading your budget.”; CTA “Shop Now”.
  • Persistent commerce emphasis: cart and checkout keep a fixed thin bottom bar with the clearly visible “Place Order on WhatsApp” button. Fast loading, optimised images, responsive grids and smooth scrolling support the mobile-first storefront across smartphones, tablets, laptops and desktops.

Visual Design:

  • Pure white or off-white background.
Page 29 of 38
  • Black typography.

  • Minimal grey borders.

  • Clean product cards.

  • Large, high-quality clothing images.

  • Smooth animations and transitions.

  • Modern typography.

  • Generous white space.

  • Responsive layout.

Avoid:

  • Too many colours.

  • Unnecessary gradients.

  • Cluttered layouts.

  • Excessive animations.

B. Hero Section:

Large fashion-focused banner with the heading:

"GOOD STYLE. BETTER FINDS."

Subheading:

"Discover unique thrift pieces. Upgrade your wardrobe without upgrading your budget."

CTA Button:

Page 30 of 38

"SHOP NOW"

The final result should look and feel like a professionally developed Indian online thrift fashion store.

7. Signature Design Concept

[Design proposal; unspecified choices are defaults.]

Signature Design Concept — The One-of-One Still Life

The public entry is a centred, single-column fashion composition: a small wide-tracked “VintageThriftHum · Belgaum” label, the thin black hero headline and subline, then one near-full-bleed still-life image of a vintage garment on a beige ground taking about 60% of the first screen. A small wood-brown rule and the “Shop Now” text CTA sit beneath the headline; no new destination or behaviour is introduced.

The same calm system carries into featured categories, new arrivals, product listing and product detail views: section openers use one thin rule, a small-caps label and substantial empty space above the title; clean cards expose large high-quality imagery and complete item information while making limited, single-piece inventory legible. The ink-black fixed checkout bar anchors the WhatsApp ordering journey and keeps “Place Order on WhatsApp” prominent.

The result must feel like a professionally developed Indian online thrift fashion store, not a static demo: navigation stays simple and product discovery uncluttered. The secure admin dashboard keeps a clean sidebar (Dashboard, Orders, and the remaining management sections) and may reuse the palette, type and rules, but avoids dense storefront-style promotional treatment.

The website should feel like a premium fashion brand.

Page 31 of 38

8. Interaction Model & Motion Direction

[Design proposal; unspecified choices are defaults.]

Interaction Model: Static (direction) Motion Tempo: still Hero Dimensionality: flat

Page 32 of 38

8.1 Landing Hero Motion Brief

  • Focal subject: one vintage garment photographed on a beige paper or linen ground, with visible texture and stitching.
  • Input → transformation → outcome: the visitor selects “Shop Now” → the storefront moves through the existing catalogue navigation into browsable clothing items → the visitor inspects one-of-one products, adds an available item to the cart and continues toward the WhatsApp checkout flow.
  • Motion vocabulary: composed stillness, slow fades only, restrained opacity transitions. Product images may crossfade between accepted image states on hover. No bounce, spring, marquee, parallax or excessive animation.
  • First frame: full-width still-life image below the centred label, headline and subline; the ink-black “Shop Now” CTA and small wood-brown rule stay wholly readable, never covered by imagery.
  • Reduced-motion state: remove fades and image crossfades; retain the same static image, readable text, simple navigation, usable controls and fixed WhatsApp checkout bar. Any moving or scrollable content remains available as a readable row or horizontally scrollable arrangement.

The interaction model prioritises easy navigation, fast perceived loading and smooth scrolling while avoiding complicated navigation and visual clutter.

  • Easy to navigate

  • Complicated navigation.

Page 33 of 38

9. Non-Functional Requirements

SECURITY REQUIREMENTS:

  • Never store passwords in frontend code.

  • Never expose admin credentials in browser JavaScript.

  • Use secure authentication.

  • Store password hashes securely.

  • Protect all admin routes.

  • Only authenticated administrators can access admin functions.

  • Implement proper database permissions using Supabase Row Level Security.

Implement:

  • Secure authentication.

  • Row Level Security.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. RESPONSIVE DESIGN

The entire website must work perfectly on:

  • Android smartphones.

  • iPhones.

  • Tablets.

  • Laptops.

Page 34 of 38
  • Desktop computers.

Prioritise mobile-first design because most customers will visit through Instagram links and mobile browsers.

Ensure:

  • Fast loading.

  • Optimised product images.

  • Smooth scrolling.

  • Proper navigation.

  • Responsive product grids.

  • Easy-to-use shopping cart.

  • Clearly visible WhatsApp checkout button.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Page 35 of 38

10. Tech Stack

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1. DATABASE & BACKEND

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Use Supabase for the backend.

Create the following database tables:

  1. products

  2. categories

  3. orders

  4. order_items

  5. admin_users

  6. store_settings

  7. admin_activity

Use Supabase Storage for product images.

  • Database relationships.
Page 36 of 38

11. Assumptions and Constraints

IMPORTANT:

Do not implement customer registration or customer login.

Anyone should be able to browse and shop without creating an account.

Do not integrate Razorpay, Stripe, UPI payment gateways or any online payment gateway.

  • Never store passwords in frontend code.

  • Never expose admin credentials in browser JavaScript.

  • Store password hashes securely.

There should be no customer login or customer registration system.

IMPORTANT:

For thrift products, stock quantities may be as low as one.

Do not falsely assume that a prefilled WhatsApp message has been sent. If automatic WhatsApp message delivery or delivery-status tracking is required in the future, it will need an approved WhatsApp Business API integration.

  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do not use fake product data after setup.

  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do not create a customer login system.

Page 37 of 38
  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do not integrate any payment gateway.

  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do not expose admin credentials.

  1. FINAL REQUIREMENTS

━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Do not use a complicated checkout process.

12. Glossary

Payment statuses:

  • Unpaid

  • Payment Pending

  • Paid

  • Refunded

Page 38 of 38

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Rendering diagram...

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Rendering diagram...