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.
- Procurement
- Features
- Supplier performance
Supplier performance
Supplier performance brings the delivery and purchasing record into the next sourcing discussion. A scorecard combines the period’s accepted evidence with the reasons behind exclusions. Buyer can compare quality, delivery reliability and price context without treating them as interchangeable measures.
OverviewSupplier Performance Quarterly×
Procurement · Supplier performance
New
Supplier Performance Quarterly
Supplier performance
| Scorecard number | Supplier | Period | PO count | Lines received | Excluded lines | |
|---|---|---|---|---|---|---|
| SP-75571 | Blue Quay Audio Devices | January 2026 | 18 | 70 | 480 | |
| SP-12049 | Tern Ridge Fabrication | February 2026 | 24 | 130 | 130 | |
| SP-14985 | Marshlight Workspaces | March 2026 | 10 | 170 | 510 | |
| SP-18729 | North Vale Computing | April 2026 | 15 | 220 | 240 | |
| SP-23889 | Crestline Industrial Supply | May 2026 | 39 | 30 | 490 |
6 of 6 records
January 2026Supplier performance · SP-75571
DraftSupplierBlue Quay Audio Devices
PO count18
Lines received70
Excluded lines480
On time delivery pct70
What you can do
Read the measures separately
| Measure | Evidence and interpretation |
|---|---|
| On time delivery pct | Completed eligible order lines compared with the first-issued need-by date |
| Quality score | Quality-defective quantity within the eligible inspected sample; lateness-only rejection excluded |
| Price competitiveness score | Comparable order and award prices against documented contract and RFQ benchmarks |
| PO count and lines received | Order activity and completed eligible lines; partial arrivals do not inflate completion count |
| Total spend | Net accepted value at receipt price snapshots, after accepted returns and corrections |
| Excluded lines | Receipt lines deliberately excluded, with their reasons |
| Overall score | Combined view of the delivery, quality and price components |
The quantity basis matters. Gross arrivals, accepted fulfilment and rejected quantities serve different purposes. A rejected delivery can contribute inspection evidence while leaving the order outstanding. Returns and corrections must reconcile to their original receipt so the same event does not improve or worsen a score twice.
Prepare and publish
The configured reporting period can be monthly or quarterly. Supplier performance holds the calculated draft and its supporting receipt, order and benchmark evidence. Procurement Manager reviews missing inputs, exclusions and unusual movements before publication. A draft is working material; only published results supply the sourcing comparison and supplier-facing scorecard.
The Supplier Performance Quarterly view puts the component scores alongside activity and exclusion counts. Small or unusual samples need that context: a single rejection and a sustained pattern should remain distinguishable in the underlying records. Missing observations use the documented neutral no history basis, with coverage showing which components lack observed evidence. Rescheduled dates preserve the first-issued promise for performance review.
Quality in the RFQ comparison
Bid comparison scores use the supplier’s latest published quality score with usable quality observations for the RFQ’s quality component. That score is based on quality-defective quantity within a reviewed comparable sample. Late delivery affects on time delivery pct and the broader supplier review; lateness alone does not lower the reject-based RFQ quality score.
The RFQ also compares the bidder’s quoted lead time as a separate weighted component. A short quoted lead time and a strong history of delivery punctuality are different facts. Buyer reviews the delivery history alongside the calculated recommendation and records the reason when choosing another offer.
Exclusions and corrections
Procurement Manager can exclude a receipt line when supported evidence shows that the recorded lateness or rejection should not count against the supplier. The line retains the exclusion flag and reason, and the scorecard retains the count. A Buyer request or supplier dispute does not itself remove the evidence.
Corrections follow the recorded receipt or return workflow before recalculation. Draft workings can be reviewed again with the changed inputs. Published history and the sourcing decision that used it remain traceable; a later correction must not silently change an earlier award’s recorded basis.
Use the results in purchasing
Buyer reads supplier performance before direct sourcing and during bid review. Procurement Manager uses the component trends, rejection reasons and expediting history in supplier reviews and renewal decisions. A score does not itself activate, suspend or block a supplier; those remain separate recorded status decisions.
PO On-Time Delivery provides the delivery detail. Spend by Supplier shows purchasing concentration and contract coverage. RFQ Award Cycle shows response rates, award timing and departures from the recommendation. These reports answer different questions and should retain their own source basis.
Supplier access and scope
Supplier sees its own published scorecard and the receipt evidence permitted for its account. Controller can review scorecards with the financial context. Viewer receives published aggregate scores without individual prices, spend details or approval decisions. The same restrictions apply to configured exports and connected access.
Financial health, sanctions screening, insurance and broader vendor risk remain in the vendor management layer. A configured connection can share procurement performance with that service; this scorecard does not claim to perform those assessments.
What it keeps track of
Data model- Supplier performance
- Period scorecard per supplier: on-time delivery, quality, price competitiveness. Computed from receipts and expediting at period end, published by the Procurement Manager, and read by bid comparison scores and the supplier’s portal seat.
- Receipts
- Physical arrival or service acceptance against a PO. Supplier ASN is untrusted advance evidence until an authorised receiver verifies it. A Posted receipt is immutable; correction is a linked reversal followed, if needed, by a replacement. Historical baseline receipts retain evidence but never repeat quantity or outbound effects.
- Receipt line items
- Per-line received quantity against a PO line. The grain accounts payable reads for the three-way match and the scorecard reads for on-time and quality.
- Supplier returns
- Controlled return of rejected arrivals or previously accepted goods, with original line, disposition and quantity evidence. Only shipped returns of previously accepted goods reduce PO accepted fulfilment; returning already rejected goods has no second quantity effect.
- Expediting
- The expediting worklist: open PO lines that are past need by date or inside the warning window. Written daily by the expediting-reminder workflow.
- Bid comparison scores
- Computed score per response: normalised price, normalised lead time and the supplier’s quality score, weighted by the RFQ’s weights. Drives the award recommendation.
- Purchase orders
- Supplier order with immutable approved revisions. Spend approvals record its authority separately from lifecycle; an RFQ award is selection evidence only. Prior requisition or agreement authority may be reused only within its approved scope and remaining capacity. Otherwise full matrix approval or the explicitly configured Buyer-limit exception is required before issuance.
- PO line items
- Per-item lines on a PO. The level at which receipts and the invoice match reconcile, and where the contract price check is recorded.
- Contract rates
- Negotiated prices: a Supplier × Item price valid for a date window, sometimes above a minimum quantity, tied to a master agreement when one exists. The contract-pricing-validation workflow reads this to guardrail buyer-entered prices.
- RFQ responses
- A supplier response revision to an RFQ. Only complete comparable Submitted responses enter scoring. Submission freezes header and line content; withdrawal and resubmission before the deadline creates a new revision, retains the previous version, and invalidates its scores and recommendation.
Who uses it
Permissions- Procurement Manager
- Reviews exclusions and publishes scorecards.
- Buyer
- Uses delivery and quality evidence in sourcing.
- Supplier
- Reviews its own published result.
- Controller
- Reads scorecards with commitment context.
- Viewer
- Reads the permitted published aggregates.
Set up Procurement your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.