Skip to main content

Supplier scorecard definitions

This page defines every dimension on the Supplier Scorecard: the figure behind it, the dates that drive it, and how partial deliveries and short-closed or closed purchase orders (POs) count. For how to open the scorecard and change its weights, see Find slipping suppliers with Supplier Analytics.

Which POs the scorecard looks at​

The scorecard on a supplier's Performance tab covers the current period of the comparison you pick at the top of Supplier Analytics (YoY is the last 12 complete months).

  • It counts the supplier's POs whose Order Date falls in that period. Draft POs never count.
  • If the supplier has fewer POs in the period than Minimum POs required to compute a scorecard (3 unless you change it), the card reads Not rated with "Insufficient data — N of M POs in this period." instead of a score.
  • Lead-Time Reliability and Cost Competitiveness ignore the period. Their own windows are described below.

Several dimensions depend on the date a PO became fully received. That's the received date of the receipt that brought the last line up to its ordered quantity. When something other than a receipt completes the PO, such as short-closing its last open line, it's the date and time of that action. The Fully Received column on the Purchase Orders list shows it.

The dimensions​

The scorecard shows these dimensions in this order. Hover the score beside a dimension to see its raw figure, its 1–5 score, and its weight.

DimensionWhat it measuresBetter when
On-Time DeliveryShare of POs fully received on or before their ETAHigher
Lead-Time ReliabilityShare of closed POs, per product, fully received on or before their ETA over the last 12 monthsHigher
Fill RateUnits received ÷ units ordered on fully received POsHigher
Defect / RTV RateUnits returned to the supplier ÷ units receivedLower
Cost CompetitivenessThis supplier's price list against other suppliers of the same productsHigher
Price StabilityHow often the unit price went up between orders of the same productFewer increases
Customer Repair RateRepairs blamed on the supplier ÷ units sold from its stockLower
Warranty Cost per Unit SoldWarranty repair cost on its units ÷ units sold from its stockLower

On-Time Delivery​

Formula: on-time POs ÷ scored POs.

  • Dates used: the PO's ETA (expected delivery date) and the date it became fully received.
  • A scored PO is a PO in the period that has an ETA and either is fully received or is still not fully received with an ETA before today.
  • On time means fully received on or before the ETA.
  • Not scored: POs with no ETA, POs not yet due (ETA today or later), and POs whose submission status is Canceled or Voided.
  • Overdue POs count as late. An open PO past its ETA counts as late now, whenever it arrives. So a period's figure can drop as days pass.
  • Split deliveries: the PO counts once, as one PO, judged by the receipt that completed it. A PO that arrived in three shipments is on time only if the last shipment arrived by the ETA. Early partial receipts don't count on their own.

Lead-Time Reliability​

Formula: for each product you buy from the supplier, on-time POs ÷ all qualifying POs that carry it. The supplier's figure is the plain average of those product percentages.

  • Qualifying POs: POs from this supplier with an ETA, that were submitted, are Closed, and became fully received within the last 12 months.
  • On time means fully received on or before the ETA, as for On-Time Delivery.
  • Window: the last 12 months, by full-receipt date, whatever period you pick. SKU.io recalculates it every night.
  • Split deliveries: judged by the receipt that completed the PO, as above.
  • A PO with several products counts once for each product it carries.
It measures timing against the ETA, not against the quoted lead time

The dimension's tooltip describes consistency against the supplier's quoted lead time. The figure itself is an on-time rate against each PO's ETA, over closed POs. The product drill-down on the Performance tab shows lead times in days: Lead Time is the quoted lead time on the supplier's product, and Actual Lead Time is the average number of days from Order Date to full receipt.

Fill Rate​

Formula: total units received ÷ total units ordered, summed over every line of the fully received POs in the period, capped at 100%.

  • Dates used: Order Date, to place the PO in the period. Only POs that are fully received count.
  • Split deliveries: every receipt against a line adds to its received quantity, so three shipments of 40, 40, and 20 against a line of 100 count as 100 received.
  • A short line keeps the whole PO out. A PO with any line still short isn't fully received, so it doesn't count toward Fill Rate in either direction until it's resolved.

Defect / RTV Rate​

Formula: units shipped back to the supplier ÷ units received from the supplier, both in the period.

  • Dates used: the receipt's received date for units received, and the return shipment's date for units returned. Order Date doesn't matter here.
  • Returned units are units on vendor return shipments that aren't void, plus units shipped back against a vendor credit. A unit recorded on both counts once. Customer returns don't count.
  • Split deliveries: every receipt counts on its own received date.
  • The score uses 100 minus the rate, so a 2% rate scores as 98.

Cost Competitiveness​

Formula: for each product that other suppliers also sell you, this supplier's price-list price ÷ the average price-list price of the other suppliers. SKU.io averages those ratios and turns the result into an index from 0 to 100: 100 means at or below the other suppliers' average, 50 means 50% more expensive, and 0 means twice the price or more.

  • Data used: the prices on your supplier price lists today. It doesn't look at POs or the period.
  • When none of the supplier's products has another supplier, it reads No benchmark and doesn't count toward the overall score.

Price Stability​

Formula: price increases ÷ price comparisons, shown as "N% increases".

  • Data used: the unit price on each PO line in the period. For each product ordered more than once, SKU.io compares each order's unit price with the order before it, by Order Date.
  • It counts how often the price went up, not by how much.
  • The score uses 100 minus the rate.

Customer Repair Rate and Warranty Cost per Unit Sold​

These two come from repairs. Customer Repair Rate is repair lines whose fault is put on the supplier ÷ units sold out of stock you received from that supplier. Warranty Cost per Unit Sold is the warranty-borne repair cost on those units ÷ the same units sold. Both use the period, and both start at a weight of 0. See Two repair dimensions on the supplier scorecard.

How closing and short-closing a PO affects each dimension​

See Close, reopen, and short-close a purchase order for the actions themselves.

ActionOn-Time DeliveryLead-Time ReliabilityFill Rate
Short-close the last open lineThe PO becomes fully received at the moment you short-close. It's on time only if you short-close on or before the ETA.Counts once the PO is Closed, judged by the short-close date.Doesn't count against it. The line's ordered quantity drops to what arrived, so the PO counts as 100% filled for that line.
Short-close a line while others are still shortNo change until the PO is fully received. Past its ETA, the PO counts as late.Not counted yet.Not counted yet.
Close with units still outstandingNever fully received. Once the ETA passes, it counts as late.Never counted.Never counted.
Close with Receiving Discrepancy (Received For Less)Never fully received. Once the ETA passes, it counts as late.Never counted.Never counted.
Submission status Canceled or VoidedNot counted while not fully received.Never counted unless fully received and closed.Never counted unless fully received.
Short-closing hides a shortfall from Fill Rate

Fill Rate compares received units with the ordered quantity as it stands now. Short-closing lowers the ordered quantity, so the units the supplier never shipped don't appear as a shortfall. To see shortfalls a supplier caused, check the PO's short-close history rather than Fill Rate.

How the overall score is built​

  1. SKU.io turns each dimension's figure into a value from 0 to 100. Higher-is-better figures use the percentage itself. Lower-is-better figures use 100 minus the rate. Warranty Cost per Unit Sold uses 100 minus the warranty cost as a share of what those units cost.

  2. Score Thresholds in Scorecard settings map that value to a score from 1 to 5: the score of the highest band whose minimum it reaches.

  3. The overall score is the weighted average of the dimension scores, using Dimension Weights, rounded to one decimal. A dimension with nothing to measure reads No data in its tooltip and is left out of the average.

  4. The band comes from the overall score:

    Overall scoreBand
    4.5 or moreExcellent
    4.0 to 4.4Good
    3.0 to 3.9Needs attention
    Below 3.0Poor
    Too few POsNot rated

Only administrators can change weights, thresholds, and the minimum PO count. Everyone else sees Scorecard settings read-only.

Next steps​

Last verified: