robo-hub Feature Specification

Status: Living Document Last Updated: January 2026 Related: ARCHITECTURE.md (Technical Structure)

---

Purpose

This document defines robo-hub features with acceptance criteria. No feature ships without criteria defined here.

Target Market: EV Fleets (beachhead strategy) Expansion Path: EV Fleets → Autonomous EV Fleets → Full Robotaxi Revenue: $10,000/year per user

---

1. Zone Directory

1.1 Browse Zones

User Story: As a fleet operator, I can browse service zones to understand where suppliers operate.

URL: ?view=ZONE_DIRECTORY

Requirements:

• Grid of zone cards with elegant styling

• Each card shows: Zone name, city, supplier count, service categories

• Click card → expands to zone detail

• Filter by: City, service category

• Search by zone name

Acceptance Criteria:

• Loads in <2 seconds

• Mobile responsive (single column on mobile)

• Minimum 10 zones displayed

• Cards use gold/copper accent styling (#bb9375)

Status: COMPLETE - UI implemented

---

1.2 Zone Detail View

User Story: As a fleet operator, I can see all suppliers operating in a specific zone.

Requirements:

• Zone header with name, description, map preview

• List of suppliers in this zone

• Filter suppliers by service type

• "View Supplier" button on each supplier card

Status: PARTIAL - Basic view exists, map preview not implemented

---

2. Supplier Directory

2.1 Browse Suppliers

User Story: As a fleet operator, I can browse all suppliers to find service providers for my fleet.

URL: ?view=SUPPLIER_DIRECTORY

Requirements:

• Grid of supplier cards with elegant styling

• Each card shows: Company name, logo, service categories, zones covered, rating

• Click card → opens ContractViewSlider

• Filter by: Service category, zone, rating

• Search by company name

• Sort by: Rating, name, recently added

Acceptance Criteria:

• Loads in <2 seconds

• Mobile responsive

• Pagination or infinite scroll for large lists

• Cards use elegant dark theme with gold accents

Status: COMPLETE - UI implemented with ContractViewSlider

---

2.2 Supplier Profile Card

User Story: As a fleet operator, I can see key info about a supplier at a glance.

Card Contents:

• Company logo (or placeholder)

• Company name

• Service categories (badges)

• Zones covered (count or list)

• Rating (stars)

• "View Details" button

Status: COMPLETE

---

3. ContractViewSlider

3.1 Slider Panel

User Story: As a fleet operator, I can view detailed supplier info in a sliding side panel without leaving the directory.

Requirements:

• Slides in from right on supplier click

• Full supplier profile info

• Service offerings with pricing tiers

• Zones covered (map or list)

• Reviews/ratings

• Contact information

• Close button (X) and click-outside-to-close

Acceptance Criteria:

• Smooth slide animation (300ms)

• Backdrop blur on background

• Scrollable content if long

• Mobile: Full-screen overlay

Status: COMPLETE - UI implemented

---

3.2 Request Quote Action

User Story: As a fleet operator, I can request a quote from a supplier directly from their profile.

Flow:

1. User clicks "Request Quote" in ContractViewSlider

2. Modal opens with RFQ form

3. User fills: Service type, vehicle count, frequency, notes

4. User submits

5. RFQ sent to supplier (via FleetOS integration)

6. Confirmation shown to user

Acceptance Criteria:

• Form validates required fields

• Submission creates record in database (service_requests table)

• Supplier notified (email via edge function)

• User sees confirmation with success message

• RFQ appears in user's "My Requests" section

Implementation:

• RequestQuoteModal.tsx - Form component with validation

• Creates record in service_requests table

• Sends email notification via Supabase edge function

• Toast notification on success/error

Status: COMPLETE - Core functionality implemented (Jan 2026)

---

3.3 Add to Fleet Action

User Story: As a fleet operator, I can add a supplier to my fleet's supplier list for quick access.

Flow:

1. User clicks "Add to Fleet" in ContractViewSlider

2. If not logged in → prompt to login/signup

3. Supplier added to user's fleet supplier list

4. Confirmation shown

5. Supplier now appears in FleetOS supplier dropdown

Acceptance Criteria:

• Requires authentication (currently uses anonymous-fleet placeholder)

• Creates relationship record in database (relationships table)

• Shows success toast notification

• Tracks which suppliers have been added (local state)

• Syncs with FleetOS supplier list

Implementation:

• SupplierDirectoryPage.tsx - handleAddToFleet function

• Creates record in relationships table with status='active'

• Toast notification on success/error

• Tracks added suppliers in local Set state

Status: COMPLETE - Core functionality implemented (Jan 2026)

---

4. Supplier Onboarding

4.1 Become a Supplier Flow

User Story: As a service provider, I can register as a supplier to be listed in the directory.

URL: Linked from FleetOS "Become a Supplier" CTA

Flow:

1. User clicks "Become a Supplier" (from FleetOS or robo-hub)

2. Registration form with:

   • Company name

   • Email

   • Phone

   • Service categories (multi-select)

   • Zones served (multi-select)

   • Description

   • Logo upload

3. Email verification

4. Profile created (pending approval)

5. Admin reviews and approves

6. Supplier appears in directory

Acceptance Criteria:

• Form validates all required fields

• Logo upload to Supabase Storage

• Email verification required

• Admin approval workflow

• Pre-fill from FleetOS context if available

Status: PARTIAL - Form exists, approval workflow not implemented

---

4.2 Supplier Dashboard

User Story: As a supplier, I can manage my profile and view incoming RFQs.

URL: ?view=SUPPLIER_DASHBOARD (after login)

Sections:

• Profile overview (edit button)

• Incoming RFQs (from fleets)

• Active contracts

• Analytics (views, RFQs, conversions)

Status: NOT STARTED

---

5. Fleet Dashboard

5.1 Fleet Overview

User Story: As a fleet operator, I can see my supplier relationships and activity.

URL: ?view=FLEET_DASHBOARD (after login)

Sections:

• My Suppliers (added via "Add to Fleet")

• My RFQs (sent quotes)

• Active Contracts

• Spend analytics

Status: NOT STARTED

---

6. Authentication

6.1 Sign Up

User Story: As a new user, I can create an account to access fleet/supplier features.

Requirements:

• Email/password registration (Supabase Auth)

• Role selection: Fleet Operator or Supplier

• Email verification

• Company information collection

Status: PARTIAL - Supabase auth exists, role selection needs work

---

6.2 Sign In

User Story: As a returning user, I can sign in to access my dashboard.

Requirements:

• Email/password login

• "Forgot password" flow

• Redirect to appropriate dashboard based on role

Status: PARTIAL - Basic auth works, role-based redirect needs work

---

7. AI Contract Negotiation (Future)

7.1 AI Agent Overview

User Story: As a fleet operator, I can use an AI agent to help negotiate better rates with suppliers.

Note: This is a FUTURE feature. Do not implement until core features are complete.

Concept:

• AI analyzes market rates for services in a zone

• Compares supplier quotes against market average

• Suggests counter-offers

• Human always makes final decision

Status: FUTURE - Not in current scope

---

8. Cross-App Integration

8.1 FleetOS → robo-hub ("Become a Supplier")

Trigger: FleetOS user clicks "Become a Supplier"

Data Passed (URL params or session):

• email - User's email from FleetOS

• company - Company name from org

• source=fleetos - Attribution

Acceptance Criteria:

• Pre-fills registration form (userId, email, name)

• Tracks conversion source (onboarded_from: 'fleetos')

• Seamless UX (multi-step wizard)

Implementation:

• SupplierOnboardingPage.tsx - Multi-step onboarding form

• CTA added to FleetOS CleanLanding.tsx

• Creates user_profiles record with role='supplier', product='robo-hub'

• 3-step flow: Intro → Business Info → Services

Status: COMPLETE - Core flow implemented (Jan 2026)

---

8.2 robo-hub → FleetOS ("Add to Fleet")

Trigger: robo-hub user clicks "Add to Fleet"

Data Shared:

• Supplier ID

• Service types offered

• Contact info

Acceptance Criteria:

• Creates relationship in shared database

• Supplier appears in FleetOS supplier dropdown

• Can send requests via FleetOS

Status: NOT STARTED

---

Feature Status Summary

Feature	Status	Priority
Zone Directory	COMPLETE	-
Supplier Directory	COMPLETE	-
ContractViewSlider UI	COMPLETE	-
Request Quote Action	COMPLETE	-
Add to Fleet Action	COMPLETE	-
Supplier Onboarding	COMPLETE	-
FleetOS → robo-hub CTA	COMPLETE	-
Fleet Dashboard	NOT STARTED	HIGH
Supplier Dashboard	NOT STARTED	HIGH
Authentication	PARTIAL	MEDIUM
AI Negotiation	FUTURE	LOW

---

Design Guidelines

Theme: Elegant dark with gold/copper accents

Element	Style
Background	#1a1a1a (dark grey)
Cards	Soft glassmorphism, subtle shadows
Accent	#bb9375 (gold/copper)
Buttons	Brushed metal gradient
Text	White primary, grey secondary

Fonts: System fonts (no Orbitron - that's FleetOS only)

---

End of robo-hub Feature Spec