Supplier Database Responsibilities¶
Why This Exists¶
This document defines conceptual database responsibilities for the Supplier 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 supplier relationships, quotes, performance, ratings, reviews, and trust auditable and reusable.
Conceptual Tables Or Collections¶
| Conceptual table or collection | Responsibility |
|---|---|
| supplier_profiles | Supplier-specific profile state. |
| supplier_contacts | Supplier contacts. |
| supplier_capabilities | Supplier offerings, categories, regions. |
| supplier_relationships | Customer-supplier relationship state. |
| supplier_quotes | Quote requests, responses, validity, status. |
| supplier_performance_records | Performance records from delivery or interactions. |
| supplier_ratings | Structured supplier ratings. |
| supplier_reviews | Supplier reviews. |
| supplier_response_times | Response time records. |
| supplier_previous_contracts | Previous contract references. |
| preferred_suppliers | Preferred supplier relationship records. |
| supplier_trust_assessments | Trust state and evidence. |
| supplier_audit_log | Supplier changes and decisions. |
Indexing Considerations¶
Future implementation should consider indexes for SupplierProfileId, OrganizationId, category, region, relationship status, preferred status, quote status, trust level, rating score, response time, and contract reference.
Ownership Rule¶
Supplier storage is canonical for supplier-specific state. It must not become the canonical store for customer organization profiles, marketplace listings, contract delivery, or intelligence recommendations.