haat

byJAI
demo/loginAdmin Overview DashboardOnboard ShopanalyticsUsers & StaffAll ShopsActivity Logssubscriptionsownersettings/owner/shop-profile/owner/analytics/owner/settings/owner/staff/owner/products/owner/orders/:id/staff/ordersStaff
demo

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for haat

1. Introduction

1.1 MASTER BUILD PROMPT — HAAT / AI-Powered Local Commerce & Kirana Store Management Platform

You are acting as a Senior Product Designer, Principal Frontend Engineer, UI/UX Architect, PWA Specialist and Product Strategist.

Your task is to design and IMPLEMENT a premium, production-quality, fully responsive frontend for a startup product named HAAT.

Do not simply create a landing page or a collection of static dashboard screenshots. Build a complete, interactive, multi-role frontend prototype that can be demonstrated to real Indian kirana shop owners, their employees and customers.

The application must feel like a real commercial product developed by an experienced design and engineering team.

1.2 PRODUCT BACKGROUND

Product Name: HAAT

Tagline: Your Local Market, Digitally Connected.

Product Category: AI-powered Hyperlocal Commerce and Shop Operations Platform.

HAAT helps traditional neighbourhood shops digitise their ordering and preparation workflow.

Page 1 of 79

1.3 PRODUCT BACKGROUND / The real-world problem

In Indian kirana stores, customers generally place orders in three ways:

  1. They physically visit the shop and give a handwritten shopping list (parcha).

  2. They call the shopkeeper and dictate their shopping list.

  3. They send their shopping list through WhatsApp using text, voice notes or photographs.

The shopkeeper or employees then manually read the parcha, collect each product, calculate the price and hand the order to the customer.

Customers frequently have to wait 10–30 minutes, especially during busy hours. Other walk-in customers also experience delays.

HAAT aims to make this process organised and efficient.

1.4 FOUR CORE MODULES

1.5 MODULE 1 — SUPER ADMIN PANEL / E. Admin Interface Design

1.6 MODULE 2 — SHOP OWNER DASHBOARD / A. Owner Home Dashboard

Display a personalised greeting:

"Namaste, Sharma Ji 👋"

Show current store status:

Open / Closed / Temporarily Paused.

1.7 LANDING AND DEMO EXPERIENCE

Page 2 of 79

1.8 FINAL DELIVERABLES / FINAL PRODUCT VISION

HAAT is not just an online listing of local shops.

It is a digital operating system for neighbourhood commerce.

Our first objective is to help kirana shopkeepers manage physical parchas, WhatsApp orders, employee preparation and customer pickup through one simple mobile-first platform.

Product motto: Less Waiting. Better Shopping. Smarter Shops.

Project name is HAAT.

2. System Overview

2.1 FOUR CORE MODULES

HAAT must have four distinct modules:

  1. Super Admin.

  2. Shop Owner.

  3. Shop Staff.

  4. Buyer.

All modules must have a unified visual identity but different interfaces and permissions.

<!-- planning-notes:v1:start -->
Page 3 of 79

Planning notes

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

Added during planning

  • admin: Named in your document but missing from the generated catalog
  • /admin/shop-onboarding: Named in your document but missing from the generated catalog
  • /admin/users: Named in your document but missing from the generated catalog
  • /admin/analytics: Named in your document but missing from the generated catalog
  • /admin/settings: Named in your document but missing from the generated catalog
  • Shop Management: Named in your document but missing from the generated catalog
  • Overview: Named in your document but missing from the generated catalog
  • Order Detail Screen: Named in your document but missing from the generated catalog
  • Shop Detail: Named in your document but missing from the generated catalog
  • Order Creation: Named in your document but missing from the generated catalog

Name changes

  • /admin/shops: The generated catalog named this page 'admin'
<!-- planning-notes:v1:end -->
Page 4 of 79

3. Functional Requirements

3.1 DEVELOPMENT SCOPE

Instead:

  • Use realistic mock data.

  • Create simulated AI extraction results.

  • Make frontend interactions functional.

  • Persist demonstration data using localStorage.

  • Clearly label simulated integrations where necessary.

Page 5 of 79

3.2 FOUR CORE MODULES

Create a role-based demonstration entry point where users can choose which module to preview.

/buyer

/buyer/discover

/buyer/shop/:id

/buyer/create-order

/buyer/orders

/buyer/orders/:id

/login

Add appropriate protected-route-style demo navigation, while making clear that actual authentication is not implemented.

3.3 MODULE 1 — SUPER ADMIN PANEL

The Super Admin is the platform-level administrator.

Admin must be able to view and manage the entire HAAT platform.

This module should be desktop-first but responsive.

Page 6 of 79

3.4 MODULE 1 — SUPER ADMIN PANEL / A. Admin Overview Dashboard

Display:

  • Total registered shops.

  • Active shops.

  • Suspended shops.

  • Total orders today.

  • Total orders this month.

  • Active shop owners.

  • Total registered staff.

  • Platform-level order trends.

Create realistic charts:

  • Shop registration growth.

  • Monthly order volume.

  • Shop category distribution.

  • Active versus inactive shops.

  • Top-performing shops.

Add a recent activity feed.

Page 7 of 79

3.5 MODULE 1 — SUPER ADMIN PANEL / B. Shop Management

Display a comprehensive shop table containing:

  • Shop name.

  • Owner name.

  • Phone number.

  • Shop category.

  • Location.

  • Registration date.

  • Staff count.

  • Order count.

  • Subscription plan.

  • Current status.

Features:

  • Search shops.

  • Filter by category.

  • Filter by active/inactive status.

  • View shop details.

  • Edit shop profile.

  • Activate shop.

Page 8 of 79
  • Suspend shop.

  • View assigned staff.

  • View shop activity.

Page 9 of 79

3.6 MODULE 1 — SUPER ADMIN PANEL / C. One-Time Merchant Onboarding

This is especially important.

HAAT's internal onboarding team will initially set up merchants for them.

Create an elegant multi-step shop onboarding wizard.

Steps:

  1. Shop Information.

  2. Owner Information.

  3. Contact Information.

  4. Location and Address.

  5. Business Category.

  6. Operating Hours.

  7. Staff Details.

  8. Account Setup.

  9. Review and Confirm.

Fields should include:

Shop Name

Shop Category

Owner Name

Owner Phone Number

Shop Address

Page 10 of 79

City

Pincode

Opening Time

Closing Time

Number of Staff

Staff Names

Staff Phone Numbers

Add validations.

Show a polished onboarding success screen with the newly created shop profile.

The owner should not have to repeat this setup every time they log in.

3.7 MODULE 1 — SUPER ADMIN PANEL / D. Admin Staff and Subscription Management

Create:

  • Staff management.

  • User management.

  • Subscription overview.

  • Plan status.

  • Shop account status.

  • Platform configuration.

Page 11 of 79

3.8 MODULE 2 — SHOP OWNER DASHBOARD / Owner onboarding experience

The HAAT team will initially configure the shop profile.

The owner receives access to their shop dashboard.

Provide a simple dashboard entry action:

"Open My Dashboard"

The owner should be able to access the dashboard with minimum friction.

After first login, show a friendly welcome screen:

"Namaste, Sharma Ji!"

"Welcome to your HAAT Shop Dashboard."

Show the shop's name, category and status.

Do not force the owner through a long configuration flow.

Page 12 of 79

3.9 MODULE 2 — SHOP OWNER DASHBOARD / A. Owner Home Dashboard

This is the first screen.

Design for mobile before desktop.

Show four important metrics:

  1. Today's Orders.

  2. Preparing.

  3. Ready for Pickup.

  4. Completed.

Show:

  • Today's order count.

  • Today's estimated sales.

  • Pending orders.

  • Average preparation time.

  • Recent orders.

  • Busy-hour indicator.

  • Most demanded products.

Use clear numbers and simple descriptions.

Provide primary quick actions:

  • View New Orders.
Page 13 of 79
  • View All Orders.

  • Manage Staff.

  • View Analytics.

The most important action should be obvious.

Page 14 of 79

3.10 MODULE 2 — SHOP OWNER DASHBOARD / B. Live Order Management

This is a core feature.

Display a unified order inbox containing orders from:

  • WhatsApp.

  • Physical Parcha.

  • Phone Orders.

Each order card should include:

  • Order ID.

  • Customer name.

  • Source type.

  • Received time.

  • Requested pickup time.

  • Number of items.

  • Quantity summary.

  • Current status.

  • Assigned staff member.

Create filters:

All

New

Page 15 of 79

Accepted

Preparing

Ready

Picked Up

Cancelled

Support search by customer and order ID.

Page 16 of 79

3.11 MODULE 2 — SHOP OWNER DASHBOARD / C. Order Detail Screen

When the owner opens an order, display:

Customer Information

Order Number

Order Source

Received Time

Requested Pickup Time

Product List

Quantity

Unit

Item Availability

Staff Assignment

Preparation Status

Final Price

Pickup Code

Provide owner controls:

Accept Order

Provide owner controls:

Reject Order

Provide owner controls:

Page 17 of 79

Assign Staff

Provide owner controls:

Edit Quantity

Provide owner controls:

Mark Item Unavailable

Suggest Substitution

Enter Final Price

Mark Ready for Pickup

Require suitable confirmation for important actions.

Never automatically mark an order ready merely because the AI has extracted the items.

Only allow Ready status after preparation is complete and final pricing is entered.

Mark Picked Up

Require suitable confirmation for important actions.

3.12 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard

The owner must be able to understand how their business is performing.

Create an understandable analytics area.

Show:

Page 18 of 79

3.13 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard / Sales Analytics

  • Today's sales.

  • Weekly sales.

  • Monthly sales.

  • Previous-period comparison.

  • Sales trend chart.

3.14 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard / Order Analytics

  • Total orders.

  • WhatsApp orders.

  • Physical parcha orders.

  • Phone orders.

  • Completed orders.

  • Cancelled orders.

  • Average preparation time.

Page 19 of 79

3.15 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard / Product Demand Analytics

Show:

  • Most demanded items.

  • Most frequently ordered products.

  • Product quantity sold.

  • Weekly product demand.

  • Monthly product demand.

3.16 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard / Customer Analytics

Show:

  • Total customers.

  • Repeat customers.

  • New customers.

  • Frequently ordering customers.

Page 20 of 79

3.17 MODULE 2 — SHOP OWNER DASHBOARD / E. Staff Management

The owner should be able to:

  • Add an employee.

The owner should be able to:

  • Edit employee information.

The owner should be able to:

  • Activate or deactivate an employee.

The owner should be able to:

  • Assign roles.

Roles can include:

  • Store Manager.

The owner should be able to:

  • Assign orders.

The owner should be able to:

  • View employee activity.

The owner should be able to:

  • View completed orders per employee.

  • Order Operator.

  • Picking Staff.

Make permissions clear and easy to understand.

Page 21 of 79

3.18 MODULE 2 — SHOP OWNER DASHBOARD / F. Shop Profile

Show:

  • Shop name.

  • Shop category.

  • Shop logo/image.

  • Owner details.

  • Address.

  • Opening hours.

  • Contact details.

  • Shop status.

Provide editable profile details.

Page 22 of 79

3.19 MODULE 2 — SHOP OWNER DASHBOARD / G. Products

Create an optional lightweight product management interface.

Show:

  • Product name.

  • Brand.

  • Unit.

  • Category.

  • Price.

  • Availability.

  • Aliases.

Support adding, editing and searching products.

Page 23 of 79

3.20 MODULE 3 — SHOP STAFF DASHBOARD / A. Staff Home

Display:

"Good morning, Amit!"

Show:

  • Assigned orders.

  • New orders.

  • Orders in preparation.

  • Orders completed today.

Primary actions:

  • Scan Parcha.

  • View Assigned Orders.

  • Add Manual Order.

Page 24 of 79

3.21 MODULE 3 — SHOP STAFF DASHBOARD / B. Parcha Scanner

This is a critical demonstration feature.

Create a mobile-first scanning interface.

Include:

  • Camera capture.

  • Image upload.

  • Image preview.

  • Retake photo.

  • Use sample parcha.

  • Extracted product list.

Where browser camera permission is available, use the camera through the appropriate browser API. Provide upload as a fallback.

Do not make this interface dependent on actual AI APIs.

Simulate the extraction with realistic sample data and a convincing processing-state animation.

Example extracted result:

Aashirvaad Atta — 5 kg

Tata Salt — 2 packets

Amul Butter — 1 packet

Fortune Oil — 1 litre

Page 25 of 79

Arhar Dal — 2 kg

Each extracted item must be editable.

The staff member must be able to:

  • Change product name.

  • Change quantity.

  • Change unit.

  • Remove incorrect items.

  • Add missing items.

  • Confirm the list.

After confirmation, create a new order in the shared order queue.

Clearly label AI extraction as a demonstration simulation.

Page 26 of 79

3.22 MODULE 3 — SHOP STAFF DASHBOARD / C. Staff Picking Checklist

When staff opens an assigned order, display:

Order Number

Customer Name

Pickup Time

Product List

Quantity

Item Checkboxes

Availability Status

Special Instructions

Each item should have a clear checkbox.

As employees collect products, they can mark the items complete.

Show a visible preparation progress indicator.

When all items are collected, allow staff to submit the order as ready for owner confirmation or final pricing, depending on permissions.

Page 27 of 79

3.23 MODULE 3 — SHOP STAFF DASHBOARD / D. Manual Phone Order Entry

Provide a very simple form for orders received through phone calls.

Fields:

Customer Name

Phone Number

Product Name

Quantity

Unit

Customer Instructions

Add multiple line items.

Save the order to the same order queue.

3.24 MODULE 3 — SHOP STAFF DASHBOARD / E. Staff Activity

Show:

  • Orders handled today.

  • Orders completed.

  • Current assigned workload.

  • Recent activities.

Page 28 of 79

3.25 MODULE 4 — BUYER EXPERIENCE

However, create a lightweight mobile-first buyer experience so that we can demonstrate the complete future customer journey.

This should behave like a simple local-shopping PWA or public web storefront.

Page 29 of 79

3.26 MODULE 4 — BUYER EXPERIENCE / A. Discover Local Shops

Create a visually appealing discovery screen.

Display:

  • Search bar.

  • Shop categories.

  • Nearby shops (mock location data).

  • Featured shops.

  • Shop opening status.

  • Store information.

  • Available pickup options.

Initial demo categories:

Kirana

Dairy

Bakery

Fruits & Vegetables

General Store

Use realistic Indian shop names and product examples.

Page 30 of 79

3.27 MODULE 4 — BUYER EXPERIENCE / B. Shop Detail

Show:

  • Shop name.

  • Shop banner.

  • Contact details.

  • Address.

  • Opening hours.

  • Categories.

  • Popular products.

  • Shop pickup details.

Page 31 of 79

3.28 MODULE 4 — BUYER EXPERIENCE / C. Order Creation

Create a simple order-building experience.

Customers can:

  • Search products.

  • Add products.

  • Change quantities.

  • View order summary.

  • Add a special instruction.

  • Select a preferred pickup time.

  • Submit a simulated order request.

Display a confirmation screen with an order number.

For the frontend demonstration, simulate the order creation locally.

Add an explanation that WhatsApp messaging will be integrated in a future phase.

Page 32 of 79

3.29 MODULE 4 — BUYER EXPERIENCE / D. Order Tracking

Show:

Order Received

Confirmed

Preparing

Ready for Pickup

Picked Up

Create a clear tracking timeline.

Display:

  • Shop name.

  • Order ID.

  • Items.

  • Final amount.

  • Pickup code.

  • Pickup information.

Add a reorder interaction.

Page 33 of 79

3.30 CORE INTERACTIVE FEATURES

The prototype must have functional interactions.

This is not negotiable.

Implement:

  1. Role-based demo entry.

  2. Navigation between all modules.

  3. Search and filters.

  4. Interactive order cards.

  5. Order detail pages.

  6. Order status changes.

  7. Order acceptance and rejection.

  8. Staff assignments.

  9. Product checklists.

  10. Manual order creation.

  11. Parcha image upload and preview.

  12. Simulated AI extraction.

  13. Item editing and deletion.

  14. Final-price form.

  15. Ready-for-pickup action.

Page 34 of 79
  1. Pickup completion.

  2. Analytics date filters.

  3. Shop onboarding wizard.

  4. Staff creation.

  5. Shop profile editing.

  6. Buyer order creation.

  7. Buyer order tracking.

When an owner marks an order ready, the buyer's simulated order tracking screen should update.

  1. Role switching.

  2. Demo data reset.

Include a demo reset control.

  1. PWA installation guidance.

When staff completes an item, the order progress shown to the owner should update.

All modules should operate on shared demonstration data.

Use a central mock data service or context/store rather than keeping unrelated copies of order information in each screen.

Persist relevant changes using localStorage.

Page 35 of 79

3.31 ORDER DATA AND MOCK DATA

Order source types:

  • WHATSAPP

  • PHYSICAL_PARCHA

  • PHONE

Order statuses:

NEW

NEEDS_CLARIFICATION

AWAITING_ACCEPTANCE

ACCEPTED

PREPARING

AWAITING_CUSTOMER_APPROVAL

READY_FOR_PICKUP

PICKED_UP

CANCELLED

REJECTED

The same order must show the same price, items and status across all modules.

Page 36 of 79

3.32 LANDING AND DEMO EXPERIENCE

Primary CTA:

"Explore HAAT"

Secondary CTA:

"See How It Works"

Include:

  • Problem explanation.

  • How HAAT works.

  • Owner dashboard preview.

  • Staff parcha scanning preview.

  • Order preparation workflow.

  • Buyer experience preview.

  • Benefits for local shopkeepers.

  • Four module explanations.

A demo role selector should allow the presenter to instantly open:

Admin Demo

Shop Owner Demo

Staff Demo

Buyer Demo

Page 37 of 79

This is extremely important because I will demonstrate the prototype directly to local shopkeepers.

Provide convenient demo-account access rather than making a presenter fill a long registration form.

3.33 DESIGN QUALITY REQUIREMENTS

  • Thoughtful empty states.

  • Proper loading states.

  • Helpful success and error messages.

All important buttons must perform a meaningful frontend action.

Page 38 of 79

3.34 MOBILE UX ACCEPTANCE CRITERIA

A shop owner should be able to:

  1. Open their dashboard.

  2. See how many new orders arrived.

  3. Open a customer order.

  4. View all requested products and quantities.

  5. Assign an employee.

  6. Enter a final amount.

  7. Mark an order ready.

A shop owner should be able to:

  1. View daily and monthly analytics.

A staff member should be able to:

  1. Scan or upload a physical parcha.

  2. Review extracted products.

  3. Correct the list.

  4. Create the order.

A staff member should be able to:

  1. Open the staff dashboard.

A staff member should be able to:

Page 39 of 79
  1. Open assigned orders.

  2. Complete product checklist items.

  3. Update preparation progress.

3.35 IMPLEMENTATION INSTRUCTIONS

STEP 3:

Implement the shared routing, layouts and role-based demo entry.

STEP 4:

Implement the Shop Owner module first because it is our most important module.

STEP 5:

Implement the Staff module, including the parcha scanner and picking checklist.

STEP 6:

Implement the Admin module and shop onboarding wizard.

STEP 7:

Implement the Buyer storefront and order tracking experience.

STEP 8:

Connect all modules to a shared mock data layer.

Page 40 of 79

3.36 FINAL DELIVERABLES

  1. Desktop-ready admin and owner dashboards.

  2. Four fully navigable modules.

  3. Shared interactive demo data.

  4. Functional order management prototype.

  5. Staff parcha scanner demonstration.

  6. Analytics dashboards.

  7. Merchant onboarding wizard.

  8. Buyer storefront and tracking.

  9. App icons and PWA manifest.

  10. README with setup instructions.

  11. Demo credentials or one-click demo access.

  12. Known frontend-only limitations.

  13. Build and validation results.

The final application should run locally using the documented development command.

The prototype must be impressive enough to demonstrate to real kirana shop owners and buyers.

4. User Personas

Page 41 of 79

4.1 MODULE 2 — SHOP OWNER DASHBOARD

THIS IS THE MOST IMPORTANT MODULE.

The majority of HAAT's product value will be experienced here.

The shop owner will use an Android phone most of the time.

The owner should be able to open the application and understand the current situation immediately.

4.2 MODULE 3 — SHOP STAFF DASHBOARD

The staff module should be even simpler than the owner dashboard.

Staff members are generally busy collecting products and serving customers.

They must be able to operate the interface with one hand wherever possible.

Page 42 of 79

4.3 ORDER DATA AND MOCK DATA

Example shop:

Sharma Kirana & General Store

Owner: Rajesh Sharma

Staff:

  • Amit Kumar — Store Manager

  • Rahul Verma — Picking Staff

  • Suresh — Order Operator

Create several realistic demo customers:

  • Rahul

  • Priya

  • Amit

  • Neha

  • Ramesh

Page 43 of 79

5. Core User Flows

HAAT connects customers, shop owners, staff, and the internal onboarding team through a shared order workflow. The customer submits a shopping list; the order enters the shop’s digital queue; staff prepares the products; the shopkeeper confirms the final price; the customer receives a ready notification; and the customer visits the shop to collect the order. Orders may also enter the shared queue from WhatsApp, a physical parcha, or a phone order. The same order must show the same price, items, and status across all modules.

1. Internal team onboards a shop

  1. The HAAT onboarding team opens the role-based demonstration entry point and selects the super-admin module.
  2. The team starts the one-time shop onboarding wizard and completes Shop Information, Owner Information, Contact Information, Location and Address, Business Category, Operating Hours, Staff Details, Account Setup, and Review and Confirm.
  3. The team enters the required shop, owner, contact, address, city, pincode, operating hours, staff count, staff names, and staff phone numbers. Validations prevent invalid or incomplete submissions.
  4. On confirmation, HAAT creates the shop profile and shows a polished success screen with the newly created profile. The owner does not repeat this setup on later access.
Page 44 of 79

2. Owner opens the shop dashboard

  1. After HAAT configures the shop, the owner uses “Open My Dashboard” with minimum friction.
  2. On first access, HAAT shows a friendly welcome state such as “Namaste, Sharma Ji!” and “Welcome to your HAAT Shop Dashboard,” with the shop name, category, and status. The owner is not forced through a long configuration flow.
  3. The mobile-first home dashboard immediately presents Today’s Orders, Preparing, Ready for Pickup, and Completed, along with today’s order count, estimated sales, pending orders, average preparation time, recent orders, busy-hour indication, and most demanded products.
  4. The owner can continue to View New Orders, View All Orders, Manage Staff, or View Analytics. Desktop adapts for efficient order management rather than simply scaling the mobile layout.

3. Owner manages an incoming order

  1. The owner opens the unified order inbox, which includes WhatsApp, physical parcha, and phone orders. Each order card shows order ID, customer name, source type, received time, requested pickup time, and number of items.
  2. The owner searches by customer or order ID, or filters by All, New, Accepted, Preparing, Ready, Picked Up, or Cancelled.
  3. The owner opens an order to review customer information, order number, order source, items, requested pickup time, and order context.
  4. The owner accepts or rejects the order, assigns staff, edits quantities, marks unavailable items, suggests substitutions, and enters the final price as needed. Important actions require suitable confirmation.
  5. Assigned staff prepares the order. The owner may mark it Ready for Pickup only after preparation is complete and final pricing is entered; extracted items alone never trigger Ready status.
  6. The customer receives the ready notification and visits the shop. The owner confirms collection through Mark Picked Up, with suitable confirmation.
Page 45 of 79

4. Staff captures and verifies a physical parcha

  1. Staff opens the mobile-first staff dashboard, which shows assigned orders, new orders, orders in preparation, and orders completed today. Primary actions include Scan Parcha, View Assigned Orders, and Add Manual Order.
  2. Staff captures a parcha with the camera, uploads an image, or uses a sample parcha. The interface provides image preview and Retake Photo controls.
  3. HAAT presents the extracted product list. Staff verifies and edits every item: product name, quantity, and unit can be changed; incorrect items can be removed; missing items can be added.
  4. Staff confirms the corrected list. HAAT creates a new order in the shared order queue for owner or staff processing.

5. Staff prepares an assigned order

  1. Staff opens an assigned order and reviews the order number, customer name, pickup time, product list, quantities, item checkboxes, availability status, and special instructions.
  2. Staff collects products and checks each item as complete on the picking checklist. When staff completes an item, the order progress shown to the owner updates.
  3. When all items are collected, staff submits the order as ready for owner confirmation or final pricing, depending on permissions. The owner then completes the final-price and Ready for Pickup decision.

6. Staff records a phone order

  1. Staff opens the manual phone order form and enters Customer Name, Phone Number, Product Name, Quantity, Unit, and Customer Instructions.
  2. Staff adds multiple line items as needed and saves the order to the same shared order queue.
Page 46 of 79

7. Buyer discovers a shop and creates an order

  1. The buyer opens the mobile-first storefront and browses the discovery screen: search bar, shop categories (Kirana, Dairy, Bakery, Fruits & Vegetables, General Store), nearby shops on mock location data, featured shops, opening status, store information, and available pickup options.
  2. The buyer opens a shop detail page showing shop name, banner, contact details, address, opening hours, categories, popular products, and pickup details.
  3. The buyer searches products, adds products, changes quantities, reviews the order summary, adds a special instruction, and selects a preferred pickup time.
  4. The buyer submits a simulated order request. Order creation is simulated locally for the frontend demonstration, and a confirmation screen displays an order number.

8. Buyer tracks an order

  1. The buyer opens order tracking and sees a clear timeline: Order Received, Confirmed, Preparing, Ready for Pickup, Picked Up.
  2. The screen displays shop name, order ID, items, final amount, pickup code, and pickup information.
  3. When the owner marks the order ready, the buyer’s simulated tracking screen updates.
  4. The buyer can use the reorder interaction to rebuild a previous order.
Page 47 of 79

9. Owner maintains shop operations

  1. The owner opens Staff Management to add employees, edit employee information, activate or deactivate employees, assign orders, view employee activity, and view completed orders per employee.
  2. The owner maintains the shop profile, including name, category, logo/image, owner details, address, opening hours, contact details, and shop status.
  3. The owner manages products by adding, editing, and searching records containing brand, unit, category, price, availability, and aliases.
  4. The owner uses Analytics with date filters to understand business performance without interrupting live order handling.

The role-based entry point supports demonstration navigation across the super-admin, buyer, owner, and staff experiences, with one-click demo access rather than a long registration form. Protected-route-style navigation may be shown for the demo, while actual authentication is not implemented. Buyer routes include /buyer, /buyer/discover, /buyer/shop/:id, /buyer/create-order, /buyer/orders, and /buyer/orders/:id; the shared login route is /login.

5.1 PRODUCT BACKGROUND / The proposed experience

Customer sends a shopping list → Order enters the shop's digital queue → Staff prepares the products → Shopkeeper confirms the final price → Customer receives a ready notification → Customer visits and collects the order.

Page 48 of 79

5.2 MOBILE UX ACCEPTANCE CRITERIA

A buyer should be able to:

  1. Find a sample shop.

  2. Open the storefront.

  3. Create an order.

  4. View its tracking status.

An admin should be able to:

  1. View registered shops.

  2. Onboard a new merchant.

  3. Edit shop information.

  4. Manage shop status.

  5. View platform analytics.

6. Visuals Colors and Theme

[Design proposal; unspecified choices are defaults.]

Page 49 of 79

6.1 Visuals, Colours and Theme

HAAT is a warm, humane tool for Indian kirana retail — trustworthy, friendly, efficient, modern, approachable, professional and local-market inspired. The muse is Yves Béhar: serious technology softened by warm materials and a calm, everyday pace. Backgrounds stay predominantly light; green carries important actions and statuses; cards are not all filled with colour.

Colour tokens (light mode)

RoleToken
BackgroundWarm Ivory #F7F6F0
SurfacePure White #FFFFFF
Primary / actions & statusForest Green #176B4A
Deep green (pressed, emphasis)Dark Green #124B37
Accent (small warm signal only)Terracotta #D98660
Rare highlightSoft Lime #D9EE9B
Primary text#202C26
Secondary text#78827C
Border#E7E9E3
Success#28845A
Warning#D99734
Error#C94E4E
Page 50 of 79

Typography. Manrope for headings at 700–800 weight, tight tracking, short lines; DM Sans for interface text. Modular scale 1.25 — 56/44/32/24/18/16, hero clamp(40px, 8vw, 96px). Large but restrained page headings, readable labels, strong numerical hierarchy, comfortable line height, no unnecessarily tiny text.

Shape and spacing. Soft rounded blocks at 16–24px radii, capsule buttons, calm panels; thin warm borders replace heavy shadows. Consistent spacing, radius, typography and shadow tokens across all four modules (Super Admin, Shop Owner, Shop Staff, Buyer) under one unified identity.

Layout. Mobile-first single column with full-width order cards; desktop (1024/1280/1440px) uses a sidebar, top toolbar and three-column dashboard grid. Mobile and desktop are thoughtfully adapted, not scaled copies. Minimum 44px touch targets, no horizontal scrolling, no tiny data tables, safe-area respect, mobile-friendly sheets and dialogs.

Imagery. Warm natural-light photography of shop shelves, parcha paper and hands at work — used selectively at section openers, never behind text, never generic stock illustration.

Avoid. Generic AI dashboard aesthetics, excessive gradients, purple/blue gradients, glassmorphism, over-rounded card stacks, giant headings on operational screens, decorative elements that obstruct tasks, emoji as navigation icons.

Readable text and controls stay whole at 375px, 768px and 1280px — headlines, wordmarks, labels, numbers and controls wrap or scale to fit; imagery and decoration may bleed, rotate or overlap instead.

6.2 RECOMMENDED TECH STACK

Page 51 of 79

6.3 BRAND IDENTITY AND VISUAL DESIGN / Colour palette

Use a coherent design system.

Suggested palette:

Primary Forest Green: #176B4A

Dark Green: #124B37

Warm Ivory: #F7F6F0

Pure White: #FFFFFF

Soft Lime: #D9EE9B

Terracotta Accent: #D98660

Primary Text: #202C26

Secondary Text: #78827C

Border: #E7E9E3

Success: #28845A

Warning: #D99734

Error: #C94E4E

Keep backgrounds predominantly light.

Use green to communicate important actions and statuses.

Do not fill every card with coloured backgrounds.

Page 52 of 79

6.4 BRAND IDENTITY AND VISUAL DESIGN / Typography

Use Manrope for headings and DM Sans for interface text.

Make the hierarchy clear:

  • Large but restrained page headings.

  • Readable labels.

  • Strong numerical hierarchy.

  • Comfortable line height.

  • No unnecessarily tiny text.

Page 53 of 79

6.5 BRAND IDENTITY AND VISUAL DESIGN / Visual design rules

Avoid:

  • Generic AI dashboard aesthetics.

  • Excessive gradients.

  • Purple and blue gradient everywhere.

  • Excessive glassmorphism.

  • Overuse of rounded cards.

  • Unnecessary giant headings in operational screens.

  • Decorative elements that obstruct task completion.

  • Generic stock illustrations.

  • Emoji used as the main navigation icon.

Use meaningful product photography selectively, not randomly.

Build consistent spacing, border radius, typography and shadow tokens.

Page 54 of 79

6.6 MODULE 1 — SUPER ADMIN PANEL / E. Admin Interface Design

Design a professional sidebar with:

Overview

All Shops

Onboard Shop

Users & Staff

Analytics

Subscriptions

Activity Logs

Settings

Admin dashboard should look like a serious SaaS control centre.

6.7 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard / Customer Analytics

Use readable charts and concise explanations.

Do not overcrowd the mobile screen with charts.

Use Recharts.

6.8 ANIMATIONS AND 3D DESIGN

The UI should look premium and memorable without feeling artificial.

Page 55 of 79

6.9 DESIGN QUALITY REQUIREMENTS

The result should look like a professionally funded Indian technology startup product.

Use:

  • Carefully designed spacing.

  • Consistent visual hierarchy.

  • Strong responsive layouts.

  • Subtle shadows.

  • Excellent typography.

  • Meaningful illustrations.

  • High-quality product visuals.

  • Beautiful charts.

6.10 IMPLEMENTATION INSTRUCTIONS

STEP 2:

Create a coherent design system and HAAT brand identity.

Page 56 of 79

7. Signature Design Concept

[Design proposal; unspecified choices are defaults.]

Muse and headline. Yves Béhar's humane technology, expressed as "Your Shop. Smarter. Faster. Online." — the public entry's hero, with subline "Manage every parcha, prepare orders faster and serve customers without unnecessary waiting." and call to action "Open the Demo". Product motto: Less Waiting. Better Shopping. Smarter Shops.

Identity. An original HAAT wordmark with a simple custom SVG icon combining an abstract market/store or shopping-basket motif — no copied startup logos. The product should read as a carefully designed, professionally funded Indian retail technology startup.

Public entry composition. A split hero on warm ivory. Left: the stacked headline in forest green over a soft lime block, with the role selector pinned beneath it. Right: a layered order card carrying a parcha photo, tilting slightly on desktop via CSS 3D. This recomposes only accepted content and controls — no new behaviour or destination.

Signature moves.

  • Stacked headline over a soft lime block, role selector beneath.
  • Floating order card with parcha photo and CSS 3D tilt on desktop.
  • Status badges that breathe once when their state changes.
  • Picking checklist filling a green progress rail as staff tick items.
  • Rounded capsule buttons with short press-down feedback.
Page 57 of 79

Module expression. Super Admin reads as a serious SaaS control centre (sidebar: Overview, All Shops, Onboard Shop, Users & Staff, Analytics, Subscriptions, Activity Logs, Settings). Owner home is designed mobile-first with a low-friction "Open My Dashboard" entry. Staff is simpler still — one-handed, mobile-first, with the Parcha Scanner (camera capture, upload, preview, retake, sample parcha, extracted list) as the critical demonstration, clearly labelled as simulated. Buyer discovery shows search, categories (starting with Kirana), nearby mock shops, featured shops, opening status and pickup options. Simulated integrations are labelled; no dead buttons, Lorem Ipsum or fake success messages.

7.1 BRAND IDENTITY AND VISUAL DESIGN

Create a distinctive, premium identity for HAAT.

The product should feel like a carefully designed Indian retail technology startup.

7.2 BRAND IDENTITY AND VISUAL DESIGN / Brand attributes

  • Trustworthy.

  • Friendly.

  • Efficient.

  • Modern.

  • Approachable.

  • Professional.

  • Local-market inspired.

Page 58 of 79

7.3 BRAND IDENTITY AND VISUAL DESIGN / Logo

Create an original HAAT wordmark.

Develop a simple custom SVG icon combining an abstract market/store or shopping-basket motif.

Do not copy existing startup logos.

7.4 ANIMATIONS AND 3D DESIGN / 3D effects

7.5 LANDING AND DEMO EXPERIENCE

Create a premium public landing/demo entry page.

Hero headline:

"Your Shop. Smarter. Faster. Online."

Supporting copy:

"Manage every parcha, prepare orders faster and serve customers without unnecessary waiting."

Page 59 of 79

8. Interaction Model & Motion Direction

[Design proposal; unspecified choices are defaults.]

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: layered_2d

Landing Hero Motion Brief. Focal subject: the layered order card with its parcha photo, resting on warm ivory beside the stacked forest-green headline over soft lime. Thesis: the visitor selects a role beneath the headline → the order card settles and its status badge breathes once → the visitor understands HAAT's promise and opens the demo. Vocabulary: slow breathing easing, one-shot reveals, a slight CSS 3D tilt on desktop pointer movement, capsule press-down feedback. Composed first frame: headline and role selector fully legible at left, order card layered at right, nothing covering text or controls. Reduced-motion state: static split layout, card flat and untilted, badge at rest, all content readable.

Motion system. Framer Motion for meaningful interactions only: smooth page transitions, order-card entrance, animated status badges, subtle modal transitions, picking-checklist progress (animates once), analytics chart reveal (Recharts), sidebar transitions, interactive success confirmation, subtle button press feedback, and the parcha scanning processing-state animation. 3D is selective — brand introduction, subtle hero perspective, floating order card, depth on product visuals, subtle tilt on selected desktop cards — built with CSS 3D transforms where possible. No heavy Three.js scene in dashboards; prioritise performance on low-end Android phones. Avoid continuous animation that distracts shopkeepers. All motion stops under prefers-reduced-motion, which must still present a usable static arrangement.

8.1 ORDER DATA AND MOCK DATA

Page 60 of 79

8.2 ANIMATIONS AND 3D DESIGN

Use Framer Motion for meaningful interactions.

Examples:

  • Smooth page transitions.

  • Order card entrance animations.

  • Animated status badges.

  • Subtle modal transitions.

  • Picking checklist progress animation.

  • Analytics chart reveal.

  • Sidebar transitions.

  • Interactive success confirmation.

  • Subtle button press feedback.

  • Parcha scanning animation.

Page 61 of 79

8.3 ANIMATIONS AND 3D DESIGN / 3D effects

Use 3D effects selectively.

Possible applications:

  • A distinctive HAAT brand introduction.

  • Subtle perspective effect on the hero section.

  • A floating order-card visual.

  • Depth effects on product visuals.

  • A subtle tilt interaction on selected desktop cards.

Use CSS 3D transforms where possible.

Do not add a heavy Three.js scene to every dashboard screen.

Prioritise performance on low-end Android phones.

Respect prefers-reduced-motion.

Avoid continuous animations that distract shopkeepers from their tasks.

8.4 IMPLEMENTATION INSTRUCTIONS

STEP 10:

Add animations, polish, transitions and realistic empty/loading/error states.

9. Non-Functional Requirements

Page 62 of 79

9.1 PRODUCT BACKGROUND / Most important product principle

The users are traditional Indian shopkeepers and employees, not technology experts.

The UI must be simple enough that a shopkeeper can understand the dashboard within 30–60 seconds.

Never sacrifice usability for decorative design.

9.2 BRAND IDENTITY AND VISUAL DESIGN / Visual design rules

9.3 RESPONSIVE DESIGN STRATEGY

This is one of the highest-priority requirements.

Most of our target kirana shop owners use Android smartphones. Many will not have a laptop or desktop computer.

Therefore, mobile UX has priority.

Page 63 of 79

9.4 RESPONSIVE DESIGN STRATEGY / Mobile specification

Primary target viewport: 360px–430px width.

Support:

  • 360px Android devices.

  • 390px devices.

  • 412px devices.

  • Tablet layouts.

  • Desktop screens.

On mobile:

  • Bottom navigation for Owner and Staff.

  • Large, easy-to-tap buttons.

  • Minimum 44px touch targets.

  • Readable text without zooming.

  • Sticky primary actions where helpful.

  • Full-width order cards.

  • No horizontal scrolling.

  • No tiny data tables.

  • Use cards instead of compressed desktop tables.

  • Respect device safe areas.

Page 64 of 79
  • Use mobile-friendly sheets and dialogs.

9.5 RESPONSIVE DESIGN STRATEGY / Desktop specification

Support 1024px, 1280px and 1440px screens.

On desktop:

  • Sidebar navigation.

  • Top toolbar.

  • Multi-column dashboard layouts.

  • Proper data tables.

  • Spacious analytics.

  • Efficient order management.

The mobile and desktop interfaces must be thoughtfully adapted, not simply scaled versions of each other.

Page 65 of 79

9.6 RESPONSIVE DESIGN STRATEGY / PWA requirements

Make HAAT installable as a Progressive Web App.

Implement:

  • Web app manifest.

  • App name and short name.

  • App icons and favicon.

  • Theme colour.

  • Standalone display mode.

  • Service worker.

  • Offline fallback screen.

  • Install guidance.

  • Appropriate mobile viewport settings.

9.7 MOBILE UX ACCEPTANCE CRITERIA

Test the most important workflows at 360px, 390px and 412px viewport widths.

No horizontal overflow, clipped buttons or unreadable text.

Page 66 of 79

9.8 IMPLEMENTATION INSTRUCTIONS

STEP 9:

Implement responsive PWA functionality.

STEP 11:

Test navigation, form validation, shared data changes and all main user workflows.

STEP 12:

Run the production build and fix all TypeScript errors, compilation errors and broken interactions.

9.9 FINAL DELIVERABLES / FINAL PRODUCT VISION

Build HAAT with the quality of a serious startup product, not a hackathon-style temporary dashboard.

10. Tech Stack

10.1 DEVELOPMENT SCOPE

  • Create service abstractions so backend APIs can be integrated later.

The frontend must be architected so that real FastAPI, Supabase and WhatsApp integrations can be introduced without rewriting the entire application.

Page 67 of 79

10.2 RECOMMENDED TECH STACK

Inspect the existing repository before starting.

If the repository already has a working stack, preserve it unless there is a strong technical reason to change it.

If it is an empty repository, use:

  • React + TypeScript

  • Vite

  • React Router

  • Tailwind CSS

  • Framer Motion

  • Recharts

  • Lucide React

  • React Hook Form + Zod

  • vite-plugin-pwa

  • LocalStorage for demo persistence

Keep the application modular and maintainable.

Use TypeScript interfaces for all major data structures.

Avoid putting the entire application in App.tsx.

Suggested architecture:

src/

Page 68 of 79

app/

App.tsx

router.tsx

providers/

components/

common/

navigation/

dashboard/

charts/

orders/

forms/

feedback/

modules/

admin/

  pages/

  components/

modules/

owner/

  pages/

  components/

staff/
Page 69 of 79
  pages/

  components/

buyer/

layouts/

hooks/

services/

mock/

api/

data/

types/

utils/

styles/

assets/

You may improve this structure where appropriate.

Page 70 of 79

10.3 FOUR CORE MODULES

Suggested routes:

/demo

/admin

/admin/shops

/admin/shop-onboarding

/admin/users

/admin/analytics

/admin/settings

/owner

/owner/orders

/owner/orders/:id

/owner/analytics

/owner/staff

/owner/products

/owner/shop-profile

/owner/settings

/staff

/staff/orders

/staff/scan-parcha

Page 71 of 79

/staff/orders/:id

/staff/my-activity

11. Assumptions and Constraints

11.1 PRODUCT BACKGROUND / The proposed experience

HAAT is pickup-first.

We are NOT building a delivery-first business.

11.2 PRODUCT BACKGROUND / Most important product principle

Page 72 of 79

11.3 DEVELOPMENT SCOPE

IMPORTANT: This development phase is FRONTEND ONLY.

Build the complete frontend prototype with realistic mock data and functional interactions.

Do not implement:

  • Actual WhatsApp Cloud API integration.

  • Real AI model/API integration.

  • Real database/backend.

  • Real payment gateway.

  • Real OTP authentication.

  • Actual production subscriptions.

  • Actual OCR or speech recognition services.

Do not pretend simulated actions are live external integrations.

11.4 RESPONSIVE DESIGN STRATEGY / PWA requirements

Do not claim that real-time notifications or offline order synchronisation are available unless actually implemented.

11.5 MODULE 1 — SUPER ADMIN PANEL / D. Admin Staff and Subscription Management

Use mock data.

Page 73 of 79

11.6 MODULE 2 — SHOP OWNER DASHBOARD / D. Analytics Dashboard / Customer Analytics

All analytics must be based on consistent mock order data.

Distinguish estimated order revenue from actual collected payments.

11.7 MODULE 2 — SHOP OWNER DASHBOARD / G. Products

Do not make a large catalogue mandatory to use HAAT.

11.8 MODULE 3 — SHOP STAFF DASHBOARD / D. Manual Phone Order Entry

Do not create a separate phone-order management system.

11.9 MODULE 3 — SHOP STAFF DASHBOARD / E. Staff Activity

Avoid exposing owner-only financial analytics.

11.10 MODULE 4 — BUYER EXPERIENCE

A separate native buyer application is NOT required in V1.

11.11 MODULE 4 — BUYER EXPERIENCE / A. Discover Local Shops

Do not request actual device location in the demonstration.

11.12 MODULE 4 — BUYER EXPERIENCE / C. Order Creation

For the frontend demonstration, simulate the order creation locally.

Page 74 of 79

11.13 MODULE 4 — BUYER EXPERIENCE / D. Order Tracking

The buyer module must remain simple and must not distract from the main owner/staff experience.

11.14 CORE INTERACTIVE FEATURES

Page 75 of 79

11.15 ORDER DATA AND MOCK DATA

Seed the application with realistic Indian kirana shop data.

Use currency: INR (₹).

Use quantities and units relevant to Indian grocery stores:

kg, g, litre, ml, packet, piece, dozen, box.

Products:

  • Aashirvaad Atta.

  • Rice.

  • Sugar.

  • Tata Salt.

  • Amul Butter.

  • Milk.

  • Eggs.

  • Fortune Oil.

  • Arhar Dal.

  • Moong Dal.

  • Maggi.

  • Tea.

  • Biscuits.

Page 76 of 79

Create enough data to populate analytics meaningfully.

Use realistic historical dates and a consistent sample dataset.

11.16 LANDING AND DEMO EXPERIENCE

Avoid presenting unsupported sales improvements or making false productivity promises.

11.17 DESIGN QUALITY REQUIREMENTS

Do not:

  • Use Lorem Ipsum.

  • Use generic placeholder screens.

  • Add dead buttons.

  • Create non-functional navigation.

  • Use fake API-success messages.

  • Generate meaningless random charts.

  • Force the buyer module into the owner dashboard.

  • Display every feature on the mobile home screen.

  • Overcomplicate operational workflows.

11.18 MOBILE UX ACCEPTANCE CRITERIA

Page 77 of 79

11.19 IMPLEMENTATION INSTRUCTIONS

Follow this exact process:

STEP 1:

Inspect the repository, existing dependencies and project structure.

Do not stop after writing a plan or creating a landing page.

Actually implement the full working frontend.

Do not ask me to approve every screen or minor design decision. Make sensible professional decisions and proceed.

If some advanced functionality cannot be implemented without a backend, create an honest and polished frontend simulation.

11.20 FINAL DELIVERABLES

At completion, provide:

  1. Complete working HAAT frontend.

  2. Responsive mobile PWA.

Page 78 of 79

12. Glossary

TermDefinition
HAATThe product name: an AI-powered hyperlocal commerce and shop operations platform, taglined "Your Local Market, Digitally Connected." It helps traditional neighbourhood shops digitise their ordering and preparation workflow.
Hyperlocal commerceCommerce between buyers and nearby neighbourhood shops within the same local area, as opposed to distant or national retailers.
Shop Owner DashboardThe module through which a shop owner manages shop operations, including staff management (assigning roles and permissions).
Store ManagerA staff role assignable by the shop owner within the Shop Owner Dashboard.
Order OperatorA staff role assignable by the shop owner.
Picking StaffA staff role assignable by the shop owner.
Buyer ExperienceThe module in which buyers discover local shops and shop by category.
Shop categoriesThe classifications used for local shop discovery: Dairy, Bakery, Fruits & Vegetables, and General Store.
Order source typeThe channel through which an order enters the system: WHATSAPP, PHYSICAL_PARCHA, or PHONE.
ParchaA written physical order slip; a PHYSICAL_PARCHA order is one captured from such a slip.
Order statusThe lifecycle state of an order. Values: NEW, NEEDS_CLARIFICATION, AWAITING_ACCEPTANCE, ACCEPTED, PREPARING, AWAITING_CUSTOMER_APPROVAL, READY_FOR_PICKUP, PICKED_UP, CANCELLED, REJECTED.
Units of measureIndian grocery-relevant quantities and units used in orders: kg, g, litre, ml, packet, piece, dozen, box.
Mock dataRepresentative sample data used in the product, including realistic Indian shop names and product examples such as Aashirvaad Atta, Rice, Sugar, Tata Salt, Amul Butter, Milk, Eggs, Fortune Oil, Arhar Dal, Moong Dal, Maggi, Tea, and Biscuits.

Default: no additional terms are defined beyond those evidenced above.

Page 79 of 79
Live
demo design preview
Buyer demo selected
Demo access continued
Storefront opened
Browse or search shops
Shop selected
Shop detail opened
Start order
Products added
Pickup details set
Order submitted
Track order
Order ready for pickup
Reorder past order
Rebuilt order
demo: Select Buyer Demo
/login: Continue with demo account
buyer: Open buyer storefront
/buyer/discover: Browse nearby shops
/buyer/discover: Search shops by category
/buyer/shop/:id: View shop details
Shop Detail: Review popular products
/buyer/create-order: 1. Add products and quantities
Order Creation: 2. Set pickup time and instructions
/buyer/create-order: 3. Submit order request
/buyer/orders: 4. View order confirmation
/buyer/orders/:id: Track order timeline
/buyer/orders/:id: View pickup code
/buyer/orders: 5. Reorder previous order
Live
demo design preview
Buyer demo selected
Demo access continued
Storefront opened
Browse or search shops
Shop selected
Shop detail opened
Start order
Products added
Pickup details set
Order submitted
Track order
Order ready for pickup
Reorder past order
Rebuilt order
demo: Select Buyer Demo
/login: Continue with demo account
buyer: Open buyer storefront
/buyer/discover: Browse nearby shops
/buyer/discover: Search shops by category
/buyer/shop/:id: View shop details
Shop Detail: Review popular products
/buyer/create-order: 1. Add products and quantities
Order Creation: 2. Set pickup time and instructions
/buyer/create-order: 3. Submit order request
/buyer/orders: 4. View order confirmation
/buyer/orders/:id: Track order timeline
/buyer/orders/:id: View pickup code
/buyer/orders: 5. Reorder previous order