These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Vendor Management System
- Features
- Supplier performance
Supplier performance
Review published supplier delivery, quality and price results with their evidence.
OverviewPreferred Active Vendors×
Vendor Management System · Supplier performance
New
Preferred Active Vendors
Vendors
| Vendor code | Name | Preferred vendor | Status | Default payment terms | |
|---|---|---|---|---|---|
| VC-218 | Vendor 962 | Yes | Active | Net 15 | |
| VC-577 | Vendor 760 | Yes | Active | Net 30 | |
| VC-557 | Vendor 372 | Yes | Active | Net 45 | |
| VC-925 | Vendor 905 | Yes | Active | Net 60 | |
| VC-894 | Vendor 743 | Yes | Active | 2/10 Net 30 |
6 of 6 records
VC-218Vendors · VND-53478
YesNameVendor 962
StatusActive
Default payment termsNet 15
What you can do
Give the next sourcing choice context
A scorecard records the supplier, period, published status and the components behind an overall result. Delivery punctuality uses completed eligible order lines against the original need-by date. Quality uses the inspected quantity and quality-defective quantity; a late shipment by itself is a delivery issue. Price competitiveness is a separate component. Activity counts, spend and coverage help the Buyer interpret whether the sample is representative.
Procurement Manager reviews the draft calculation and decides publication. Published scorecards carry the publication time and person. A bid comparison can then use the latest published quality result for a later RFQ; its quality basis says whether comparable history exists. Supplier sees its own published evidence, while Controller can read it with purchasing context.
How the work is organized
- Delivery facts. Order lines retain original need-by dates, and receipt lines retain arrival, acceptance and rejection evidence. Partial deliveries remain visible until the line is fulfilled.
- Quality facts. Receipt lines record rejection reason and quality-defect quantity. An approved exclusion has a named reviewer and reason so a correction stays reviewable.
- Published period. The scorecard keeps delivery, quality and price components plus coverage, excluded lines and publication identity. The published result is what sourcing uses as historical context.
What to agree during setup
Choose the reporting period and which receipt evidence is eligible. Assign who may approve an exclusion and require a reason. Define which prices are comparable for the price component, including contract and RFQ benchmarks. Decide how the team handles a vendor with no relevant quality observations. Give Supplier access only to its own published result and permitted receipt evidence; Viewer reads aggregate published information without individual commercial terms.
Check the handoff on an actual case
Choose an order with one on-time accepted delivery and one later delivery with a quality rejection. Inspect the original promise dates, acceptance quantities and rejection reason before reading the calculated scorecard. Procurement Manager checks the sample size, exclusions and coverage, then publishes the period. Buyer starts a new RFQ and sees the published quality basis in the comparison. Revisit an excluded receipt line and confirm the recorded reviewer and reason explain why its evidence was left out.
Use a second vendor with no comparable published quality history. The RFQ comparison should retain a no-history quality basis rather than presenting an observed quality result. Procurement Manager can still read the vendor’s current qualification and terms before deciding an award.
What your team sees
- Published Vendor Scorecards — Period results with delivery, quality, price and coverage context.
- Vendor Directory — Supplier status and preferred designation beside the performance discussion.
Follow the work through
Use performance review before the next sourcing decision.
What it keeps track of
Data model- Scorecards
- Period scorecard per supplier: on-time delivery, quality, price competitiveness.
- Vendors
- Supplier master: legal vendor identity ordered from and paid through accounts payable.
- Purchase orders
- Supplier order with immutable approved revisions.
- PO line items
- Per-item lines on a PO, the level at which receipts and invoice match reconcile.
- Receipts
- Physical arrival or service acceptance against a PO.
- Receipt line items
- Per-line received quantity against a PO line.
- Bid comparison scores
- Computed score per response: normalised price, lead time and quality weighted by RFQ weights.
- RF qs
- Request-for-quote header for sourced spend that needs a competitive bid.
- Expediting
- The expediting worklist: open PO lines past Need By Date or inside the warning window.
Who uses it
Permissions- Procurement Manager
- Reviews exclusions and publishes period results.
- Buyer
- Uses the evidence in sourcing.
- Controller
- Reviews it with commitments.
- Supplier
- Sees its own published result; Viewer sees scoped aggregate results.
Set up Vendor Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.