Skip to main content

Profile & Settings PRD for Marketplace Features

Date: March 2026 Author: Product Team Status: Draft Version: 1.0 Related: Marketplace Strategy Analysis v2

Executive Summary

This PRD defines the Profile and Settings features required to support Avala’s data marketplace. Based on comprehensive analysis of the existing codebase, ~60% of the foundation exists but critical marketplace-specific features are missing.

Key Gaps Identified

Implementation Scope

  • Backend: 12 new models, 8 new API endpoint groups
  • Frontend: 6 new pages, 15+ new components
  • Estimated Effort: 8-12 weeks (2 senior engineers)

Part 1: Current State Analysis

1.1 Existing Profile Infrastructure

Backend Models (Django)

Frontend Pages (Flutter)

1.2 Existing Organization Infrastructure

Backend Models

Frontend Pages

URL Design: Uses GitHub-style root-level slugs. Both organizations and users share the /{slug}/... namespace. Reserved system routes (/settings, /admin, /api, /search, etc.) are protected.

Part 2: Gap Analysis by Feature Area

2.1 Creator Profile Features

Required for: Marketplace sellers to showcase their work and build trust

What’s Missing

Required Models


2.2 Payment Integration (Stripe Connect)

Required for: Creators to receive earnings from dataset sales

What’s Missing

Required Models


2.3 Reputation & Rating System

Required for: Building trust and quality signals in the marketplace

What’s Missing

Required Models


2.4 Creator Analytics Dashboard

Required for: Creators to understand their performance and optimize

What’s Missing

Required Models

Required API Endpoints


2.5 Notification Preferences

Required for: Users to control how they receive updates

What’s Missing

Required Models


2.6 Enhanced API Key Management

Required for: SDK users to manage access with granular permissions

What’s Missing

Required Model Updates


2.7 Privacy & Visibility Settings

Required for: Users to control their public presence

What’s Missing

Required Model Updates


Part 3: Frontend Requirements

3.1 New Pages Required

3.2 New Components Required

3.3 State Management (Cubits/BLoCs)


Part 4: API Endpoints Required

4.1 Creator Profile & Analytics

4.2 Payment Integration

4.3 Reviews & Ratings

4.4 Notifications

4.5 Privacy & Blocking


Part 5: Implementation Roadmap

Phase 1: Creator Foundation (Weeks 1-3)

Goal: Enable creators to set up profiles and connect payments Deliverables:
  • Creator can add display name, bio, social links
  • Creator can connect Stripe account
  • Creator can see basic earnings overview

Phase 2: Reputation & Reviews (Weeks 4-6)

Goal: Build trust signals through ratings and reviews Deliverables:
  • Users can rate/review purchased datasets
  • Creators have aggregated reputation scores
  • Verification and achievement badges display

Phase 3: Analytics Dashboard (Weeks 7-9)

Goal: Give creators insights into their performance Deliverables:
  • Creators see revenue, downloads, views over time
  • Top performing datasets highlighted
  • Analytics exportable as CSV

Phase 4: Settings & Privacy (Weeks 10-12)

Goal: Complete user control over their experience Deliverables:
  • Users control notification delivery
  • Users control profile/data visibility
  • API keys show usage and have granular scopes

Part 6: Success Metrics


Part 7: Open Questions

  1. Commission structure: Is 12% platform commission final? Need to confirm for transaction model.
  2. Tax handling: Do we collect W-9 ourselves or use Stripe’s tax form collection?
  3. Review moderation: Auto-approve all reviews or require moderation queue?
  4. Badge criteria: What are the specific thresholds for each badge type?
  5. Analytics retention: How long do we keep daily analytics data? (Suggest: 2 years)
  6. Notification channels: Do we support SMS notifications or just email + in-app?

Appendix A: Database Migration Plan

New Tables

  • account_creator_payment_profile
  • marketplace_transaction
  • marketplace_dataset_review
  • marketplace_creator_reputation
  • marketplace_badge
  • analytics_dataset_engagement
  • analytics_creator_earnings
  • notifications_preference
  • apikey_usage_log
  • account_user_block

Modified Tables

  • account_user - Add creator fields, privacy settings
  • apikey_apikey - Add rate limits, usage tracking

Migration Order

  1. Core user fields (no dependencies)
  2. Payment profile (depends on user)
  3. Transaction/review models (depends on user + dataset)
  4. Analytics tables (depends on user + dataset)
  5. Notification preferences (depends on user)

Appendix B: Third-Party Integrations


Last Updated: March 2026