# 3.1 Vendor Management Requirements

## Core Goals
- Maintain a centralized vendor database capturing contact details, performance history, and competency attributes.
- Automate onboarding, qualification, and offboarding to ensure vendor lifecycle governance.
- Implement a vendor rating and feedback mechanism so procurement teams can score engagements.

## Functional Expectations
- Vendor profiles should consolidate identity, key contacts, certifications, and capability tags.
- Workflow-driven onboarding should validate documentation, approvals, and required checklists before activation.
- Offboarding must revoke access, archive records, and log reasons for deactivation.
- Feedback collection should allow scoring per engagement and aggregate historical performance metrics.

## Implementation Notes
- Align vendor metadata with the `vendors` schema and extend it where necessary for performance KPIs.
- Integrate workflow steps to transition vendors between onboarding, active, and offboarded states.
- Surface ratings in procurement selection flows to inform RFQ invitations.
- The dashboard **Vendor Management** modal now exposes tabs for contacts, addresses, capabilities, compliance documents, supporting evidence, and performance metrics. Use the prebuilt forms (`Vendor Contact`, `Vendor Address`, etc.) to capture these records and keep the lifecycle status, review timestamp, and rating fields up to date.
- Filters at the top of the modal let users switch between lifecycle stages or focus on a single vendor; once selected, every tab scopes its tables and pre-fills the add buttons so onboarding steps remain consistent.
