How to Calculate Vendor KPIs from Warehouse Receipt Data: Formulas, Weighted Score, and Worked Example

How to calculate vendor KPIs from warehouse receipt data means turning arrival records into four numbers: on-time delivery, quality acceptance, quantity accuracy, and the share of warning-free transactions. The four are combined into a weighted score and read through status bands of good, warning, or critical.

Supplier evaluation often rests on impressions: a vendor that feels late or problematic. The impression may be right, but it is hard to use in negotiation or in deciding who to keep. Warehouse receipt data holds more objective evidence because it is recorded when goods arrive. This article gives the formula for each metric, the weighted score formula, and a worked example with illustrative numbers.

The content describes general practice, not a standard and not a guarantee of results. The weights and thresholds in the example are illustrative only. To discuss vendor evaluation at your company, contact our team. The data comes from the receiving process, covered in barcode scanning for goods receiving.

What Is a Vendor KPI and How Do You Calculate Vendor KPIs from Receipt Data?

A vendor KPI is a supplier performance measure calculated periodically and compared with a target. Warehouse supplier evaluation is rating suppliers by what happens in the warehouse when goods are received, not by promises or impressions.

Receipt data is a good source because it is recorded at the time of the event by the person receiving the goods. Arrival date, quantity received, inspection result, and the warnings raised during scanning are all already on the receipt document. No extra entry is needed just for evaluation, so warehouse workload does not grow. The resulting numbers can also be traced back to the source document if a vendor questions them.

The prerequisite is a receipt document opened from a PO that holds the promised delivery date and the ordered quantity. Without a promised date, on-time delivery cannot be calculated. Without an ordered quantity, quantity accuracy has no reference. Make sure both are filled in on the PO before the KPI is used. For older POs that lack them, mark them as not assessable instead of guessing the date.

What Data Do You Need from Warehouse Receiving?

Each metric needs a few columns from the receipt document and the PO. The table below maps metrics to their data, so it is easy to check whether the system already stores everything. If a column is missing, complete the recording process first, because a KPI calculated from half-complete data will treat a vendor unfairly, for better or worse.

The meaning of each column must be agreed first, for example whether receipt date means the date the truck arrived or the date of the first scan. Different definitions produce different numbers for the same vendor. Write the definitions in one document that is also shared with vendors, so no debate arises over how the numbers are calculated.

What Is the Supplier On-Time Delivery Formula?

Supplier on-time delivery is the percentage of deliveries that arrive on or before the promised date, within an agreed tolerance. The formula: OTD (%) = number of on-time deliveries divided by the total number of deliveries in the period, times 100.

Example with illustrative numbers: of 20 deliveries in a period, 17 arrive on time, so OTD is 17 divided by 20, times 100, which is 85 percent. The counting unit can be deliveries, PO lines, or receipts; pick one and use it consistently.

Define the tolerance clearly. Some companies treat arrival on the promised day as on time, others allow a few days. That tolerance is policy, so keep it as adjustable configuration and record its version, so old numbers do not change meaning when policy changes. Partial deliveries need their own rule: are they judged per delivery or do they wait until the whole order is complete? Whichever you choose, write it down and apply it equally to all vendors.

How Do You Calculate the Quality Acceptance Rate?

The quality acceptance rate is the percentage of goods received that pass quality inspection compared with all goods received. The formula: QAR (%) = quantity passing inspection divided by quantity received, times 100.

Example with illustrative numbers: of 1,000 units received, 960 pass inspection and 40 are rejected, so QAR is 960 divided by 1,000, times 100, which is 96 percent. If units differ between lines, calculate per line in its own unit and then average, rather than adding up units that are not comparable.

Watch the denominator. If rejected goods are never recorded as received, QAR will always look like 100 percent. Record the quantity that physically arrived first, then the inspection result. Also record the rejection reason, because problem categories such as damaged packaging or wrong dimensions are more useful for improvement than the total figure. With uniform categories, meetings with vendors can address specific causes, not just a percentage.

How Do You Calculate Supplier Delivery Quantity Accuracy?

Supplier delivery quantity accuracy measures how close the quantity that arrived is to the quantity ordered, whether short or over. Per order line: accuracy = 1 minus the absolute difference between received and ordered quantity divided by ordered quantity. Values below zero are rounded to zero. Period accuracy is the average of all lines, times 100.

Example with illustrative numbers: an order of 100 units with 92 arriving gives line accuracy of 1 minus (8 divided by 100), which is 92 percent. An order of 100 units with 108 arriving is also 92 percent, because over-delivery and under-delivery both deviate from the order.

The formula treats excess and shortage equally. If shortage hurts the plant far more, use separate formulas or give them different weights. Explain the choice to vendors so the figures are not seen as one-sided. An order changed midway should be compared with the last approved quantity, not the original, so a vendor is not judged for changes the plant itself requested.

What Is Warning-Free Transactions as a Vendor Indicator?

Warning-free transactions is the percentage of receiving scans that raise no warning, for example for excess quantity. The formula: warning-free percentage = number of scans without warnings divided by the total number of scans, times 100.

This indicator catches small problems that never reach rejection: excess quantity, packaging that deviates from habit, or patterns that force operators to write a reason repeatedly. Warnings that appear often for a particular vendor are an early signal before the problem becomes a rejection. The reason an operator types when continuing past a warning also becomes concrete material for discussion with the vendor.

The concept of warnings and hard stops is covered in the barcode receiving scan article. Note that a hard stop rejects the scan, so it is not recorded as a valid transaction. This indicator therefore reads warnings, not rejections, and should be read together with the other three metrics. A vendor can have a high warning-free percentage simply because few of its goods were scanned; read the figure alongside the transaction count.

What Is the Weighted Score Formula and the Status Bands?

A weighted score combines several metrics into one number. The formula: score = sum of (metric weight times metric value), with total weight of 100 percent. Weights express which metric matters most to the company; a plant very sensitive to production schedules may give on-time delivery a larger weight.

Status bands (illustrative example, adjustable): a score of 90 or above is good, from 75 up to below 90 is warning, and below 75 is critical. The weights and thresholds above are only examples; each company sets its own numbers based on its policy and process sensitivity. Weights are best agreed with purchasing, quality, and production, so the score represents real interests. Keep weights and thresholds as configuration, not fixed numbers in the program, so adjustments do not need a code change.

What Does a Two-Vendor Score Calculation Look Like (Illustrative Numbers)?

Below are two fictional vendors with illustrative numbers, using the example weights above. The score is the sum of weight times value, and every value column is on a 0 to 100 scale so they can be added directly.

Vendor A: 0.30 times 85 equals 25.5; 0.30 times 96 equals 28.8; 0.25 times 92 equals 23.0; 0.15 times 90 equals 13.5. The total is 90.8. Vendor B: 21.0 plus 27.0 plus 22.0 plus 12.0 equals 82.0. All these numbers are fictional and only show how to calculate. Note that Vendor B has fairly good quality, but its score is pulled down by timeliness. By reading the components, purchasing knows that the conversation with Vendor B should start with delivery schedules, not goods quality.

How Is a Warning Dashboard Used Without Blocking Warehouse Work?

A score that sits only in an end-of-month report arrives too late to use. The dashboard should always show a warning when a vendor's score crosses a threshold, for example dropping from good to warning, so purchasing can act earlier.

These warnings are informational, not blocking. Receiving goods from a vendor in warning or critical status continues as usual; what changes is the attention of the purchasing and quality teams. Blocking receipt because of a score would hold back goods the production line may need. The decision to replace or limit a vendor stays with people, with the score as one input alongside other factors such as price and availability of alternatives.

Use the score to open a conversation, not to pass a verdict. Discuss the lowest component with the vendor, for example timeliness, then agree on an improvement step and the next review period. Periodic review, monthly or quarterly for instance, keeps the score relevant. A dashboard view across warehouse data is in the WMS BI dashboard article, and the supply chain context is in supply chain management software.

Case Study: Vendor KPIs in DAISHIN

Automata is building DAISHIN, a web-based warehouse and manufacturing system for PT Shinko Kogyo Indonesia, a manufacturing company. The system is in development and will replace a workflow based on Excel and VBA. No operational results are claimed here; what is described is behavior that has been implemented.

KPIs are computed per vendor from receipt data: on-time delivery, quality acceptance, quantity accuracy, and warning-free transactions. The four are combined into a weighted score with status bands of good, warning, and critical. The dashboard always shows a warning when the score crosses a threshold, without blocking the workflow. The weights and thresholds the client uses are not published; the numbers in this article are entirely illustrative. This describes the behavior of a system under construction, not usage results, and the rules can be adapted to each company's policy. Because the KPIs come from receipt data, KPI quality depends on the quality of scan recording in the warehouse.

10-Step Checklist for Calculating Vendor KPIs

1. Make sure the PO holds the promised delivery date and ordered quantity, since both are references for the metrics.
2. Agree on the definition of receipt date and the on-time tolerance, and write it down so it can be shared with vendors.
3. Record the physical quantity that arrived before the quality inspection result.
4. Record rejection reasons in uniform categories, such as packaging, dimensions, or documents, so they can be summarized.
5. Decide the counting unit (delivery, PO line, or receipt) and the rule for partial deliveries.
6. Calculate the four metrics with the same formula for all vendors, and document the formulas in one place.
7. Set the weights and status bands as adjustable configuration, together with purchasing, quality, and production.
8. Store the version of weights and tolerances, so old numbers stay meaningful.
9. Show a dashboard warning when a score crosses a threshold, without blocking goods receipt.
10. Review scores with vendors periodically, starting from the lowest component, and record the follow-up with the next review date.

Common Mistakes in Calculating Vendor KPIs

• Rejected quantity not counted as received. Quality acceptance looks perfect.
• No promised date on the PO. On-time delivery cannot be calculated.
• Definitions change without a record. Numbers across periods are not comparable.
• Too little data. One or two deliveries are not enough to conclude anything, so show the delivery count next to the score.
• One number replaces everything. The total score hides the component that has a problem.
• The score is used to block. Warehouse work stalls because of a number that may not be relevant to production needs at that moment.

These mistakes make a KPI look convincing but misleading. A simple, documented formula is more useful than a complicated one vendors do not understand. If a vendor can reproduce the numbers from the same data, the discussion shifts from disputing figures to fixing causes. Receiving results also relate to FIFO issuing per lot, because the lots received become the stock that is issued later.

Frequently Asked Questions

How do you calculate vendor KPIs from receipt data?

Calculate four metrics from the receipt document: on-time delivery, quality acceptance, quantity accuracy, and warning-free transactions. Combine them in a weighted score, which is the sum of weight times metric value, then read the result through status bands such as good, warning, and critical.

What is the supplier on-time delivery formula?

OTD (%) is the number of on-time deliveries divided by the total number of deliveries in the period, times 100. Set the date tolerance and counting unit (deliveries or PO lines) first, then use them consistently for all vendors.

What is the quality acceptance rate formula?

QAR (%) is the quantity of goods passing quality inspection divided by the quantity of goods received, times 100. Record the physical quantity that arrived first, including what is later rejected, so the figure does not always look like 100 percent.

How do you calculate supplier delivery quantity accuracy?

Per line, accuracy is 1 minus the absolute difference between received and ordered quantity, divided by ordered quantity, with a floor of zero. The average of all lines in the period, times 100, gives the quantity accuracy for that period.

Are the weights in this article used by your client?

No. The weights and status bands in this article are illustrative examples and adjustable. The client's own weights and thresholds are not published. DAISHIN itself is still in development, and this article claims no operational results.

Does a vendor score block goods receipt?

No. In the flow described here, the dashboard shows a warning when a score crosses a threshold, but receiving continues. The score is used as input for purchasing and quality follow-up. Contact our team for a demo.