Lead with the conclusion: supplier inbound performance is judged at the receiving dock, not in the contract. A supplier can look excellent on paper and still jam the dock every week. A usable scorecard tracks only four numbers: on-time delivery rate, ASN timeliness rate, ASN accuracy rate and inbound pass rate. All four come from the WMS and the ERP. They never come from the supplier's own report or from a receiver's gut feeling. The method below gives receiving teams the formulas, tiering rules and fix process.
Why must receiving own the numbers? Because the number a supplier reports and the number the dock feels are often two different things. In 2023, at a third-party warehouse in East China where I led the go-live, one food supplier rated itself above 95% on time, every month, while the receiving lead complained daily that the dock was blocked. Pulling WMS data settled it: the supplier counted a shipment as on time when the truck left its plant, while receiving counted it as on time only when the truck checked in inside its appointment window. Change the definition and the real on-time rate was 71%. Get the definition wrong and every tier and deduction discussion built on it is empty talk. I have seen this pitfall three times, and the root cause is always the same: nobody froze the definitions before go-live.
How to Calculate the Four Numbers of Supplier Inbound Performance
Freeze the four definitions first, write them into the receiving work instruction, then pull WMS numbers on exactly those definitions.
On-time delivery (OTD): the denominator is total appointment deliveries in the month, and the numerator is trucks that check in inside their appointment window. A delivery outside the window counts as late, whether it arrives early or late. Early arrivals lose points too, for a reason covered later.
ASN timeliness rate: the denominator is total deliveries in the month, and the numerator is deliveries whose ASN arrived before the agreed lead time. Write the lead time into the supplier manual, for example 24 hours before arrival, and set it per supplier rather than forcing one number on the whole warehouse.
ASN accuracy rate: this is the number worth the most. Compare line by line: item, quantity, batch and pallet count on the ASN against what was actually received. One wrong line makes the whole delivery inaccurate. Do not use a value-based accuracy rate. A delivery can match on total value and still be wrong on every detail, which leaves receivers opening cartons to find out what really arrived.
Inbound pass rate: the denominator is total units or lines received, and the numerator is the quantity that passed inspection without rework or replacement. Damage, wrong items, expired stock and unscannable labels all count as failures.
The data pull is detailed on purpose: vague steps produce vague numbers. Step 1: export the month's receipts from the WMS, with supplier, appointment time, actual check-in time, ASN number and ASN send time at minimum. Step 2: export the matching purchase order lines from the ERP and join them on order number. Step 3: flag every delivery against the four definitions, 1 for pass and 0 for fail, with ASN accuracy flagged line by line. Step 4: roll the flags up by supplier and build the scorecard. Never hand-edit a number. Log an odd delivery, then work through it line by line at the review meeting.
How to Tier Supplier Inbound Performance and Run the Quarterly Review
Tiering works best with four grades, thresholds set to what the warehouse can absorb. The starting scale I use most often: grade A means all four rates at 95% or above; grade B means 90% to 95%; grade C means 80% to 90%; grade D means any single rate below 80%. Grade A suppliers go into priority scheduling with wider appointment windows. Grade D suppliers go onto a watch list and must improve the next quarter.
The quarterly review runs one hour with a fixed agenda of four items. Start with the trend charts for the four rates and name which suppliers dropped and by how much. Then work through the exception deliveries for grades C and D, with the supplier explaining each one on the spot. Next, set next quarter's improvement targets as numbers, for example lifting ASN accuracy from 78% to 90%. Close by confirming consequences: priority scheduling for grade A, a formal fix process for grade D. Every item ends with a number and a date.
Now the cost of a wrong ASN in plain arithmetic: a warehouse receiving 200 deliveries a month at 70% ASN accuracy leaves 60 deliveries needing manual carton-by-carton checks. At 40 extra minutes per delivery, that is 2,400 minutes, or 40 working hours, in one month. If those 60 deliveries had accurate ASNs, checking would take about 8 minutes each, or 8 hours in total. The 32-hour gap is labor eaten directly by bad ASNs, before counting dock overtime and rework when the wrong goods reach a customer. Show that arithmetic to a supplier and it beats ten reminder calls.
| Situation | Check time per delivery | Monthly time for 60 deliveries | Dock effect |
|---|---|---|---|
| Accurate ASN | About 8 minutes | About 8 hours | Flows inside the appointment window |
| Inaccurate ASN | About 40 minutes | About 40 hours | Frequently overruns the window |
How to Fix a Low-Scoring Supplier
The fix process has four steps, each leaving a paper trail. Step 1: send a written improvement notice with the scorecard and the exception delivery list attached, naming exactly which deliveries failed and which lines were wrong. Step 2: require the supplier to return an improvement plan within two weeks, with cause, action, owner and due date; a plan missing any one of those four items goes straight back. Step 3: run a one-quarter observation period, sending that supplier's four rates weekly, and escalate if two consecutive weeks show no improvement. Step 4: split on the result. A supplier back to grade C or above keeps its volume. A supplier still at grade D loses order share, and two consecutive quarters at grade D starts the replacement process.
Replacement is not a one-line decision: keep the evidence chain complete: scorecards, review minutes, improvement notices, supplier replies and observation-period data, all filed. With that chain, purchasing can defend a replacement and the supplier cannot claim receiving acted on impressions. Deductions follow the same rule: deduct only on terms written into the contract and numbers on the scorecard, never invent a penalty standard inside the scorecard itself. Specific deduction amounts and retailer thresholds should follow the contract and each retailer's latest compliance guide.
Where Scorecards Usually Break
One counterintuitive point first: earlier is not always better. A delivery two days early occupies dock doors and storage, wrecks the schedule, and forces on-time trucks to wait. The scorecard measures inside the window, not earliest arrival. Reward early arrivals without penalizing them and the dock will eventually choke on goods that arrived ahead of plan.
A second break point: tracking on-time rate while ignoring ASN accuracy. The truck arrives on time, the ASN is a mess, receivers still open cartons, and the dock still jams. On time and complete must be scored together. That is the whole meaning of OTIF: only on time and in full counts as a pass. A scorecard that measures half the job will rate the most disruptive supplier as a good one.
A third break point belongs on the night-before-go-live checklist: definition sign-off. Before go-live, confirm in writing: how the appointment window is measured, the ASN lead time, whether accuracy is scored by line or delivery, the tier thresholds, and which system supplies the data. If any one of those five items is unconfirmed, the first month's data cannot be trusted and the scorecard never gets off the ground. Get supplier, purchasing and receiving to sign the definitions; do not leave them in chat messages nobody can find later.
The honest point to close on: a scorecard exists to put receiving's real cost on the table. When the numbers are clean, good suppliers earn priority scheduling, weak suppliers get a clear path to improve, and the dock keeps moving.
By Lin Xiao, WMS Implementation Consultant









