Marketplace Database Responsibilities

Why This Exists

This document defines conceptual database responsibilities for the Marketplace Domain.

It does not define SQL implementation, final schemas, migrations, or storage technology.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear persistence responsibilities make marketplace listing, discovery, matching, request, and visibility workflows auditable and searchable.

Conceptual Tables Or Collections

Conceptual table or collection	Responsibility
marketplace_listings	Provider listings and display state.
marketplace_providers	Marketplace provider representation and source references.
provider_categories	Category catalogue and hierarchy.
marketplace_search_sessions	Search interactions and filters.
marketplace_search_results	Ranked search result records.
marketplace_matches	Match records and rationale.
listing_visibility	Visibility status and display rules.
verification_displays	Display records for source verification signals.
quote_requests	Quote request workflow state.
support_requests	Support request workflow state.
recommendation_displays	Display records for Intelligence recommendations.
marketplace_audit_log	Marketplace changes and workflow audit.

Indexing Considerations

Future implementation should consider indexes for listing ID, provider type, category, region, visibility status, OrganizationId, request status, match score, recommendation source, and created date.

Ownership Rule

Marketplace storage is canonical for marketplace workflow and display state. It must not become the canonical store for supplier performance, funding applications, organization profiles, contract state, or intelligence reasoning.