vendor-negotiation

Run the scorecard subcommand with a vendor ID and optional period, for example vendor scorecard --vendor VEN001 --period 2026-08. The output combines on-time delivery, quality, fill rate, price competitiveness, and rebate metrics into a weighted score with a rating tier.

Use the contract-expiry subcommand with a day threshold, such as vendor expiring-contracts --days 90. It returns expiring contracts, auto-renewal warnings, and negotiation talking points so you can act before notice deadlines pass.

The default weights are on-time delivery 30%, quality acceptance 25%, fill rate 20%, price competitiveness 15%, and rebate accrual 10%. These weights and the rating tier thresholds are configurable in the scorecard.yaml scoring section.

Scorecards should use the most recent 3 to 6 months of data. Annual averages mask recent performance deterioration, and data older than 6 months is explicitly discouraged because it hides current trends.

Comparing vendors across vastly different categories or volumes produces unfair scores. Benchmark vendors only against peers with similar categories and spend volumes, and flag any single vendor exceeding 30% of category spend as a concentration risk.