magic-meta

byNaresh Gangwar
demo/admin/shop-onboardingadmin/admin/analytics/admin/settings/admin/users
demo

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for magic-meta

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.

1.3 RECOMMENDED TECH STACK

Page 1 of 81

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

1.5 MOBILE UX ACCEPTANCE CRITERIA

1.6 FINAL DELIVERABLES / FINAL PRODUCT VISION

HAAT is not just an online listing of local shops.

It is a digital operating system for neighbourhood commerce.

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

The chosen project name is magic-meta.

2. System Overview

2.1 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.

Page 2 of 81

2.2 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.

2.3 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.

2.4 FINAL DELIVERABLES / FINAL PRODUCT VISION

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

3. Functional Requirements

Page 3 of 81

3.1 DEVELOPMENT SCOPE

  • Actual OCR or speech recognition services.

Instead:

  • Use realistic mock data.

  • Create simulated AI extraction results.

  • Make frontend interactions functional.

  • Persist demonstration data using localStorage.

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

  • Clearly label simulated integrations where necessary.

Do not pretend simulated actions are live external integrations.

Page 4 of 81

3.2 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.

Page 5 of 81

3.3 FOUR CORE MODULES

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

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

Page 6 of 81

/staff/scan-parcha

/staff/orders/:id

/staff/my-activity

/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.4 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 7 of 81

3.5 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 8 of 81

3.6 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 9 of 81
  • Suspend shop.

  • View assigned staff.

  • View shop activity.

Page 10 of 81

3.7 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 11 of 81

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.8 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 12 of 81

3.9 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 13 of 81

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

This is the first screen.

Design for mobile before desktop.

Display a personalised greeting:

"Namaste, Sharma Ji 👋"

Show current store status:

Open / Closed / Temporarily Paused.

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.

Page 14 of 81
  • Most demanded products.

Use clear numbers and simple descriptions.

Provide primary quick actions:

  • View New Orders.

  • View All Orders.

  • Manage Staff.

  • View Analytics.

The most important action should be obvious.

Page 15 of 81

3.11 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 16 of 81

Accepted

Preparing

Ready

Picked Up

Cancelled

Support search by customer and order ID.

Page 17 of 81

3.12 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

Reject Order

Assign Staff

Edit Quantity

Page 18 of 81

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.13 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:

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

  • Today's sales.

  • Weekly sales.

  • Monthly sales.

  • Previous-period comparison.

  • Sales trend chart.

Page 19 of 81

3.15 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.

3.16 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.

Page 20 of 81

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

Show:

  • Total customers.

  • Repeat customers.

  • New customers.

  • Frequently ordering customers.

Use readable charts and concise explanations.

Do not overcrowd the mobile screen with charts.

Use Recharts.

All analytics must be based on consistent mock order data.

Distinguish estimated order revenue from actual collected payments.

Page 21 of 81

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

The owner should be able to:

  • Add an employee.

  • Edit employee information.

  • Activate or deactivate an employee.

  • Assign roles.

  • Assign orders.

  • View employee activity.

  • View completed orders per employee.

Roles can include:

  • Store Manager.

  • Order Operator.

  • Picking Staff.

Make permissions clear and easy to understand.

Page 22 of 81

3.19 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 23 of 81

3.20 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 24 of 81

3.21 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 25 of 81

3.22 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 26 of 81

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 27 of 81

3.23 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 28 of 81

3.24 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.25 MODULE 3 — SHOP STAFF DASHBOARD / E. Staff Activity

Show:

  • Orders handled today.

  • Orders completed.

  • Current assigned workload.

  • Recent activities.

Page 29 of 81

3.26 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 30 of 81

3.27 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 31 of 81

3.28 MODULE 4 — BUYER EXPERIENCE / B. Shop Detail

Show:

  • Shop name.

  • Shop banner.

  • Contact details.

  • Address.

  • Opening hours.

  • Categories.

  • Popular products.

  • Shop pickup details.

Page 32 of 81

3.29 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 33 of 81

3.30 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 34 of 81

3.31 CORE INTERACTIVE FEATURES

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.

  16. Pickup completion.

  17. Analytics date filters.

Page 35 of 81
  1. Shop onboarding wizard.

  2. Staff creation.

  3. Shop profile editing.

  4. Buyer order creation.

  5. 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.

3.32 ORDER DATA AND MOCK DATA

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

3.33 ANIMATIONS AND 3D DESIGN / 3D effects

Page 36 of 81

3.34 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."

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.

Page 37 of 81

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

Admin Demo

Shop Owner Demo

Staff Demo

Buyer Demo

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.35 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 81

3.36 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.

  8. View daily and monthly analytics.

A staff member should be able to:

  1. Open the staff dashboard.

  2. Scan or upload a physical parcha.

  3. Review extracted products.

  4. Correct the list.

  5. Create the order.

  6. Open assigned orders.

  7. Complete product checklist items.

  8. Update preparation progress.

Page 39 of 81

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.

Page 40 of 81

3.37 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 9:

Implement responsive PWA functionality.

STEP 11:

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

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

Page 41 of 81

3.38 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 42 of 81

4.1 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

5. Core User Flows

Page 43 of 81

5.1 Customer places an order and collects it

Actors: Customer, shop owner, shop staff.

Trigger: The customer needs groceries and sends a shopping list by WhatsApp (text, voice note or photograph), by phone, or in person as a handwritten parcha.

  1. The customer submits the list through one of the three accepted channels.
  2. The order enters the shop's digital queue and appears in the owner's unified order inbox, labelled with its source type (WhatsApp, Physical Parcha, Phone).
  3. The owner opens the order detail, reviews the items, and accepts or rejects it; on acceptance the owner assigns a staff member.
  4. Staff open the assigned order and see order number, customer name, pickup time, product list, quantity, item checkboxes, availability status and special instructions. As they collect products they tick each item; a visible preparation progress indicator updates, and the progress shown to the owner updates with each completed item.
  5. When all items are collected, staff submit the order as ready for owner confirmation or final pricing, depending on permissions.
  6. The owner enters the final price. Only after preparation is complete and final pricing is entered can the owner mark the order Ready for Pickup; AI extraction alone never advances an order to Ready.
  7. The customer receives a ready notification and visits the shop to collect the order.
  8. The owner marks the order Picked Up after handover.
Page 44 of 81

Branches and recovery: Rejected orders leave the queue as Cancelled. Unavailable items are resolved through quantity edits or substitutions before pricing. Important status changes (Ready, Picked Up) require confirmation. Orders can be searched by customer or order ID and filtered by All, New, Accepted, Preparing, Ready, Picked Up, Cancelled. Statuses follow the defined set: NEW, NEEDS_CLARIFICATION, AWAITING_ACCEPTANCE, ACCEPTED, PREPARING, AWAITING_CUSTOMER_APPROVAL, READY_FOR_PICKUP, PICKED_UP, CANCELLED, REJECTED.

Result: The customer collects a prepared, priced order without the 10–30 minute in-store wait; the order closes as Completed.

5.2 Staff digitises a handwritten parcha

Actors: Shop staff, shop owner (downstream).

Trigger: A parcha arrives at the shop and must enter the digital queue.

  1. Staff open the mobile-first Parcha Scanner from the staff home.
  2. Staff capture a photo with the camera, upload an image, or use a sample parcha; they preview and may retake the photo.
  3. The scanner returns an extracted product list, clearly labelled as a demonstration simulation of AI extraction.
  4. Staff edit each extracted item: change product name, quantity or unit; remove incorrect items; add missing items.
  5. Staff confirm the list.

Result: A new order is created in the shared order queue, where it follows journey 1 from acceptance onward.

Page 45 of 81

5.3 Staff records a phone order manually

Actors: Shop staff, shop owner (downstream).

Trigger: A customer places an order by phone call.

  1. Staff open the simple manual order form and enter customer name, phone number, product name, quantity, unit and customer instructions.
  2. Staff add multiple line items as needed.
  3. Staff save the order.

Result: The order is saved to the same shared order queue and follows journey 1 from acceptance onward.

5.4 Staff reviews their workload

Actors: Shop staff.

Trigger: Staff want to see their current work.

  1. Staff open the staff dashboard and view orders handled today, orders completed, current assigned workload and recent activities.
  2. Staff open an assigned order to continue preparation (journey 1, step 4).

Result: Staff know what remains to be prepared and pick up assigned orders directly.

Page 46 of 81

5.5 Super Admin onboards a merchant

Actors: HAAT internal onboarding team (Super Admin), shop owner (recipient).

Trigger: A new kirana shop joins the platform.

  1. The Super Admin opens the multi-step shop onboarding wizard.
  2. They complete the nine steps: Shop Information, Owner Information, Contact Information, Location and Address (including pincode), Business Category, Operating Hours (opening and closing time), Staff Details (number of staff, staff names, staff phone numbers), Account Setup, and Review and Confirm, with validations applied.
  3. On confirmation, a polished success screen shows the newly created shop profile.

Result: The shop and its owner account exist once; the owner does not repeat this setup at each login.

Page 47 of 81

5.6 Shop owner enters the dashboard for the first time

Actors: Shop owner.

Trigger: The owner receives access after HAAT configures the shop profile.

  1. The owner logs in and uses the single entry action Open My Dashboard.
  2. A friendly welcome screen greets them ("Namaste, Sharma Ji!", "Welcome to your HAAT Shop Dashboard") and shows the shop's name, category and status.

Result: The owner reaches the home dashboard with minimum friction; no long configuration flow is forced. The home screen shows store status (Open / Closed / Temporarily Paused), the four metrics (Today's Orders, Preparing, Ready for Pickup, Completed), today's order count, estimated sales, pending orders, average preparation time, recent orders, busy-hour indicator and most demanded products, with quick actions to View New Orders, View All Orders, Manage Staff and View Analytics.

Page 48 of 81

5.7 Shop owner manages staff

Actors: Shop owner, staff member.

Trigger: The owner needs to add or adjust shop employees.

  1. The owner adds an employee or edits employee information.
  2. The owner assigns a role (roles can include Store Manager) and activates or deactivates the employee.
  3. The owner assigns orders and later views employee activity and completed orders per employee.

Result: Staff are available for order assignment in journey 1 and their activity is traceable.

5.8 Shop owner reviews business performance

Actors: Shop owner.

Trigger: The owner wants to understand how the business is performing.

  1. The owner opens the analytics area.
  2. They review sales analytics (today's, weekly and monthly sales, previous-period comparison, sales trend chart), order analytics (total, WhatsApp, physical parcha, phone, completed and cancelled orders, average preparation time) and product demand analytics (most demanded items, most frequently ordered products, quantity sold, weekly and monthly demand).

Result: The owner has an understandable view of sales, order mix and demand to guide stocking and staffing.

Page 49 of 81

5.9 Shop owner maintains products and shop profile

Actors: Shop owner.

Trigger: Product details or shop details change.

  1. The owner adds, edits or searches products, keeping brand, unit, category, price, availability and aliases current.
  2. The owner updates editable shop profile details.

Result: The catalogue and profile stay accurate for order preparation and customer discovery.

5.10 Super Admin governs shops and the platform

Actors: Super Admin.

Trigger: Routine platform administration.

  1. The Super Admin searches shops and filters by category and active/inactive status.
  2. They view shop details, edit a shop profile, activate or suspend a shop, and view assigned staff and shop activity.
  3. They manage staff, users, subscription overview, plan status, shop account status and platform configuration.

Result: Shops remain correctly provisioned and their subscription and account status reflect current standing.

Page 50 of 81

5.11 Buyer discovers a shop and creates an order

Actors: Buyer, shop owner/staff (fulfilment).

Trigger: The buyer wants to order from a nearby shop through the lightweight mobile-first storefront.

  1. The buyer opens the discovery screen and uses the search bar, shop categories, nearby shops (mock location data), featured shops, opening status, store information and available pickup options; initial demo category is Kirana.
  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, views the order summary, adds a special instruction and selects a preferred pickup time.
  4. The buyer submits a simulated order request; creation is simulated locally in the frontend.
  5. A confirmation screen displays the order number.

Result: The order proceeds through the shop's queue as in journey 1.

Page 51 of 81

5.12 Buyer tracks an order

Actors: Buyer, shop owner (status changes).

Trigger: The buyer wants to know the state of a placed order.

  1. The buyer opens the order tracking screen and follows the timeline: Order Received, Confirmed, Preparing, Ready for Pickup, Picked Up.
  2. The screen shows 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 may use the reorder interaction to build a new order (journey 11, step 3).

Result: The buyer knows when and how to collect the order and can repeat a past order.

5.13 Presenter opens a role demo

Actors: Presenter (demonstrating to shopkeepers), demo roles.

Trigger: The presenter wants to show the prototype without registration.

  1. From the landing experience (primary CTA "Explore HAAT", secondary "See How It Works"), the presenter uses the demo role selector.
  2. The selector instantly opens Admin Demo, Shop Owner Demo, Staff Demo or Buyer Demo via convenient demo-account access rather than a long registration form.

Result: Each module is reachable in one step for live demonstration; navigation between all modules and shared demo data keep changes visible across roles.

Page 52 of 81

5.14 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.

6. Visuals Colors and Theme

[Design proposal; unspecified choices are defaults.]

Page 53 of 81

6.1 Visuals, Colours and Theme

HAAT reads as a carefully designed Indian retail technology startup: trustworthy, friendly, efficient, modern, approachable, professional and local-market inspired. The muse is Aaron Draplin — bold, honest shop craft. Thick-line badges, workwear colours and plain talk suit kirana shopkeepers, their staff and local buyers who need a 30-second read on a phone. Usability is never sacrificed for decoration.

Colour tokens (light mode, authoritative):

RoleToken
Background#F7F6F0 warm ivory
Surface#FFFFFF
Primary text#202C26
Secondary text#78827C
Primary (actions, status)#176B4A forest green
Dark green#124B37
Accent (single hot accent)#D98660 terracotta
Badge fill#D9EE9B soft lime
Border#E7E9E3
Success#28845A
Warning#D99734
Error#C94E4E

Backgrounds stay predominantly light; green communicates important actions and statuses; cards are not all filled with colour. Soft lime fills small badges only.

Page 54 of 81

Typography: Manrope for headings at 700–800 weight with tight tracking on large numbers; DM Sans for interface text. Modular 1.25 scale: 44/34/26/20/16/14. Hero headline clamp(38px, 7vw, 84px). All-caps DM Sans labels at 11px with 0.12em tracking. Large but restrained page headings, readable labels, strong numerical hierarchy, comfortable line height, no body copy below 14px.

Shape and spacing: hard 8px and 12px radii on panels, 2px ink borders, chunky badge stamps and ruled dividers — no soft blobs. Consistent spacing, radius, typography and shadow tokens; subtle shadows only.

Imagery: thick-line SVG icons of baskets, sacks and weighing scales; halftone photographs of Indian shop shelves used once per section, never randomly and never generic stock illustration.

Responsive: mobile-first for the owner dashboard — bottom navigation for Owner and Staff, minimum 44px touch targets, full-width order cards, no horizontal scrolling, no tiny data tables, cards instead of compressed tables, safe-area respect, mobile-friendly sheets and dialogs, sticky primary actions where helpful. Desktop at 1024/1280/1440px uses sidebar navigation, top toolbar, multi-column dashboards, real data tables and spacious analytics. The two are thoughtfully adapted, not scaled copies.

Avoid: purple/blue gradients on white, glassmorphism, soft blobs, emoji as navigation icons, grids of identical hover-lift cards, tiny text, decorative art covering a button or label, generic AI dashboard aesthetics, excessive gradients, overuse of rounded cards, giant headings in operational screens.

Readable text and controls stay whole at 375px, 768px and 1280px; imagery and decoration may bleed, rotate or overlap freely.

Page 55 of 81

6.2 BRAND IDENTITY AND VISUAL DESIGN / Brand attributes

  • Trustworthy.

  • Friendly.

  • Efficient.

  • Modern.

  • Approachable.

  • Professional.

  • Local-market inspired.

Page 56 of 81

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 57 of 81

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 58 of 81

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 59 of 81

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 ANIMATIONS AND 3D DESIGN

The UI should look premium and memorable without feeling artificial.

6.8 LANDING AND DEMO EXPERIENCE

Page 60 of 81

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 61 of 81

7. Signature Design Concept

[Design proposal; unspecified choices are defaults.]

HAAT wordmark and icon. An original HAAT wordmark in Manrope 800, paired with a simple custom SVG icon combining an abstract market/store or shopping-basket motif. No existing startup logos are copied.

Poster-like layout. Blocks on a 12-column grid. A forest-green headline block spans the viewport edge to edge on the landing page. A terracotta circular badge with the HAAT basket icon is stamped at a slight angle on each section opener. A thick ruled divider with an all-caps label separates every dashboard section.

Order cards. 2px ink border with a left status stripe that changes colour by order state — the recurring operational object across Owner, Staff and Buyer surfaces.

Parcha scan panel. A moving ink-line sweep with a stamped 'Extracted' mark on completion; extraction is simulated with realistic sample data and a convincing processing state, never dependent on live AI APIs.

Public entry hero. A full-bleed warm-ivory poster: a giant forest-green headline block fills the left two thirds with "Your Shop. Smarter. Faster. Online."; a terracotta badge stamp with the basket icon sits at the top right; the subline "Manage every parcha, prepare orders faster and serve customers without unnecessary waiting." sits under the headline; the primary CTA "Explore HAAT" is a solid green bar pinned beneath it, with secondary "See How It Works". The page continues into problem explanation, how HAAT works, owner dashboard preview, staff parcha scanning preview, order preparation workflow, buyer experience preview, benefits for local shopkeepers and the four module explanations.

Page 62 of 81

Admin control centre. A professional sidebar — Overview, All Shops, Onboard Shop, Users & Staff, Analytics, Subscriptions, Activity Logs, Settings — reading as a serious SaaS control centre, with realistic charts for shop registration growth, monthly order volume, category distribution, active versus inactive shops and top-performing shops. The multi-step merchant onboarding wizard ends on a polished success screen showing the newly created shop profile.

Owner welcome. After first login, a friendly screen: "Namaste, Sharma Ji!" / "Welcome to your HAAT Shop Dashboard." with shop name, category and status — no forced long configuration flow. The home dashboard leads with the personalised greeting, store status (Open / Closed / Temporarily Paused) and four metrics: Today's Orders, Preparing, Ready for Pickup, Completed, with the most important action obvious.

Buyer discovery. Search bar, categories (Kirana, Dairy, Bakery, Fruits & Vegetables, General Store), nearby shops on mock location data, featured shops, opening status, store information and pickup options, using realistic Indian shop names and products.

Quality bar. Thoughtful empty states, proper loading states, helpful success and error messages, beautiful Recharts analytics on consistent mock order data that distinguish estimated order revenue from actual collected payments, and a demo reset control. Every important button performs a meaningful frontend action; no dead buttons, non-functional navigation, fake API-success messages or meaningless random charts.

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.

Page 63 of 81

7.2 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.

Page 64 of 81

8. Interaction Model & Motion Direction

[Design proposal; unspecified choices are defaults.]

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

Landing Hero Motion Brief. Focal subject: the forest-green headline block and the terracotta basket badge stamp. Input → transformation → outcome: the visitor lands on the warm-ivory poster; the badge stamps in at a slight angle and the green CTA bar snaps into place; the visitor reads the promise and presses "Explore HAAT". Motion vocabulary: snap-in entrances and stamp effects at 160ms, no continuous loops. Composed first frame: headline block left two thirds, badge top right, subline and green CTA bar beneath — fully legible before any motion runs. Reduced-motion state: the same composition rendered static, with no stamp or snap animation.

Framer Motion, meaningful only: 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 and the parcha scanning animation.

3D, selective and CSS-first: a distinctive HAAT brand introduction, a subtle perspective effect on the hero section, a floating order-card visual, depth effects on product visuals and a subtle tilt interaction on selected desktop cards. Use CSS 3D transforms where possible, prioritise performance on low-end Android phones, and never add a heavy Three.js scene to every dashboard screen. Avoid continuous animations that distract shopkeepers from their tasks.

Page 65 of 81

Reduced motion: all motion stops under prefers-reduced-motion, leaving a usable static arrangement.

8.1 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 66 of 81

8.2 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.

Prioritise performance on low-end Android phones.

Respect prefers-reduced-motion.

8.3 IMPLEMENTATION INSTRUCTIONS

STEP 10:

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

9. Non-Functional Requirements

Page 67 of 81

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 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 68 of 81

9.3 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 69 of 81
  • Use mobile-friendly sheets and dialogs.

9.4 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.

9.5 RESPONSIVE DESIGN STRATEGY / PWA requirements

9.6 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 70 of 81

9.7 MODULE 4 — BUYER EXPERIENCE / D. Order Tracking

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

9.8 CORE INTERACTIVE FEATURES

The prototype must have functional interactions.

This is not negotiable.

9.9 ANIMATIONS AND 3D DESIGN / 3D effects

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

Avoid continuous animations that distract shopkeepers from their tasks.

9.10 DESIGN QUALITY REQUIREMENTS

9.11 MOBILE UX ACCEPTANCE CRITERIA

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

No horizontal overflow, clipped buttons or unreadable text.

9.12 IMPLEMENTATION INSTRUCTIONS

STEP 12:

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

Page 71 of 81

9.13 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 72 of 81

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 73 of 81

app/

App.tsx

router.tsx

providers/

components/

common/

navigation/

dashboard/

charts/

orders/

forms/

feedback/

modules/

admin/

  pages/

  components/

modules/

owner/

  pages/

  components/

staff/
Page 74 of 81
  pages/

  components/

buyer/

layouts/

hooks/

services/

mock/

api/

data/

types/

utils/

styles/

assets/

You may improve this structure where appropriate.

10.3 IMPLEMENTATION INSTRUCTIONS

STEP 8:

Connect all modules to a shared mock data layer.

11. Assumptions and Constraints

Page 75 of 81

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

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.

11.4 RESPONSIVE DESIGN STRATEGY / PWA requirements

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

Page 76 of 81

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

Use mock data.

11.6 MODULE 2 — SHOP OWNER DASHBOARD / G. Products

Do not make a large catalogue mandatory to use HAAT.

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

Do not create a separate phone-order management system.

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

Avoid exposing owner-only financial analytics.

11.9 MODULE 4 — BUYER EXPERIENCE

A separate native buyer application is NOT required in V1.

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

Do not request actual device location in the demonstration.

11.11 MODULE 4 — BUYER EXPERIENCE / C. Order Creation

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

Page 77 of 81

11.12 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 78 of 81

Create enough data to populate analytics meaningfully.

Use realistic historical dates and a consistent sample dataset.

11.13 LANDING AND DEMO EXPERIENCE

Avoid presenting unsupported sales improvements or making false productivity promises.

11.14 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.

Page 79 of 81

11.15 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.

11.16 FINAL DELIVERABLES

At completion, provide:

  1. Complete working HAAT frontend.

  2. Responsive mobile PWA.

12. Glossary

Page 80 of 81

12.1 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

Page 81 of 81
Live
demo design preview
buyer demo selected
signed in
browse shops
narrow results
shop selected
shop selected
view storefront
begin order
build basket
items added
pickup chosen
order simulated
view orders
order opened
order ready
order collected
repeat order
rebuild basket
demo: Open Buyer Demo
/login: Sign in as buyer
buyer: Enter storefront home
/buyer/discover: Search nearby shops
/buyer/discover: Filter by category
/buyer/shop/:id: Open shop storefront
Shop Detail: Review products and pickup
/buyer/create-order: Start new order
Order Creation: 1. Add products and quantities
Order Creation: 2. Set pickup time
Order Creation: 3. Submit order request
Order Creation: 4. View order confirmation
/buyer/orders: 5. Open my orders
/buyer/orders/:id: 6. Track order status
/buyer/orders/:id: View pickup code
/buyer/orders/:id: 7. Reorder past order
/buyer/orders/:id: Confirm order picked up
Live
demo design preview
buyer demo selected
signed in
browse shops
narrow results
shop selected
shop selected
view storefront
begin order
build basket
items added
pickup chosen
order simulated
view orders
order opened
order ready
order collected
repeat order
rebuild basket
demo: Open Buyer Demo
/login: Sign in as buyer
buyer: Enter storefront home
/buyer/discover: Search nearby shops
/buyer/discover: Filter by category
/buyer/shop/:id: Open shop storefront
Shop Detail: Review products and pickup
/buyer/create-order: Start new order
Order Creation: 1. Add products and quantities
Order Creation: 2. Set pickup time
Order Creation: 3. Submit order request
Order Creation: 4. View order confirmation
/buyer/orders: 5. Open my orders
/buyer/orders/:id: 6. Track order status
/buyer/orders/:id: View pickup code
/buyer/orders/:id: 7. Reorder past order
/buyer/orders/:id: Confirm order picked up