A supplier promises Friday. The truck arrives Monday. Half the order is there, the ASN shows the full quantity, and procurement still marks the PO “received.” Finance sees a freight premium. Operations sees a stockout. The supplier sees one late delivery and asks what the fuss is about.
That mess is why a supplier OTIF scorecard has to be built from transaction evidence, not buyer memory. OTIF—on time, in full—should answer one blunt question: did the supplier deliver the quantity you ordered inside the window you agreed to? If the definition changes by buyer, facility or month, the score is decoration.
The point is not to punish suppliers. The point is to expose which failure created the shortage, premium freight, dock disruption or working-capital drag, then put an owner and due date on the correction.
Define the OTIF pass before you calculate the score
Start with the denominator. Score supplier OTIF at the purchase-order line level when one late or short SKU can stop production, miss a customer promise or force an emergency buy. Order-level scoring can hide a damaging line inside an otherwise clean PO. Shipment-level scoring is even easier to game because a supplier can split one order into several convenient shipments.
APQC defines supplier on-time delivery against the agreed delivery time. Its separate OTIF measure requires an order to be both complete and inside the agreed time frame. Those are useful anchors, but your operating rule still must settle the arguments before the first score is published.
| Decision | Rule to lock | Common failure |
|---|---|---|
| On-time date | Original requested date, confirmed date or appointment window | The baseline gets changed after the miss |
| In-full quantity | Ordered units, approved revision and tolerance | Partial receipts are counted as complete |
| Receipt event | Gate-in, dock arrival, first scan or accepted receipt | Every facility uses a different clock |
| Early delivery | Allowed window and storage consequences | Early freight is called “good” while it consumes space |
| Exclusions | Buyer changes, force majeure and documented holds | Exceptions become a back door for score manipulation |
Do not blend quality, damage, labeling and invoice accuracy into the OTIF calculation. Track them beside OTIF. One composite mystery number makes it impossible to see whether a supplier has a production problem, a shipping problem or a documentation problem.
Build one evidence chain from PO release to accepted receipt
A defensible supplier scorecard needs five linked records: the released PO, the supplier acknowledgement, the ASN, the delivery or appointment event, and the accepted receipt. Each record needs a timestamp, stable identifier and revision history. Screenshots and inbox archaeology are not a data model.
- Release: freeze the PO line, requested date, quantity, location and terms sent to the supplier.
- Acknowledge: capture the supplier’s confirmed quantity and date without silently overwriting the original request.
- Notify: require an ASN that identifies what actually shipped, how it is packed and when it will arrive.
- Receive: record the physical event and accepted quantity at the agreed measurement point.
- Reconcile: compare request, confirmation, ASN and receipt; then assign a reason code to every miss.
GS1 US maps the 850 purchase order, 855 acknowledgement and 856 advance ship notice as distinct transactions. That separation matters. A supplier confirmation should not erase what the buyer originally requested, and an ASN should describe the shipment—not rewrite the order.
Your supplier routing guide should define the shipping rules and evidence requirements. The advance shipping notice workflow should deliver the pre-arrival record. OTIF uses those controls as evidence; it does not replace them.
Where manual supplier scorecards break
Most manual scorecards do not fail because the spreadsheet formula is hard. They fail because the source events are inconsistent and the exceptions arrive faster than someone can clean them.
- Date drift: the buyer moves the requested date after the supplier says it will be late, making the miss disappear.
- Quantity drift: an unapproved short ship becomes the new expected quantity.
- Receipt noise: split receipts, reversals and duplicate scans create false failures or false passes.
- Wrong owner: a carrier delay is assigned to the supplier even when the buyer controlled transportation.
- Closed too early: a line is scored when freight reaches the gate, before shortage, damage or identity problems are known.
- Denominator games: canceled, changed and open lines enter or leave the report without a documented rule.
The cure is not a bigger spreadsheet. Preserve each source event, calculate against a versioned ruleset and keep an exception log that explains every override. If procurement can change a failed line to a pass, require the evidence, approver and timestamp.
Automate the calculation; keep humans on disputed exceptions
The repeatable work should run without a buyer touching it. Pull released PO lines from the ERP, supplier confirmations from EDI or a portal, ASNs from the supplier feed, appointments from the yard system and accepted receipts from the WMS. Normalize units of measure and time zones. Join on PO, line, shipment and handling-unit identifiers. Then calculate on-time, in-full and OTIF as separate pass/fail fields.
This is exactly where logistics and API automation consulting earns its keep. The automation should create the candidate score, expose the evidence and open an exception only when data conflicts or a contractual judgment is required. It should not invent a reason code or approve a debit because a confidence score looks impressive.
Humans should handle disputed timestamps, buyer-caused changes, damaged freight, approved substitutions, constrained allocations and commercial remedies. Give each exception an owner, due date, root-cause code and disposition. “Supplier contacted” is not a disposition.
If receiving is outsourced, define the same evidence inside your 3PL warehousing and fulfillment operation. A supplier score is only as trustworthy as the receiving scan, shortage code and quarantine process feeding it.
Turn the supplier OTIF scorecard into procurement action
A scorecard without a decision cadence becomes monthly theater. Review the largest misses by business cost and repeat cause, not alphabetically by supplier. Separate controllable supplier failures from buyer, carrier and facility failures. Then choose the action: correct the master data, repair the routing rule, change the order cadence, demand a supplier corrective-action plan, recover an agreed cost or re-source the risk.
ASCM describes OTIF as receiving the full order by the desired date. That sounds simple. Operationally, it means a line that is early but short is not a pass, and a line that is complete but late is not a pass. Keep the two component measures visible so a supplier can see which behavior must change.
Illustrative example — run your own numbers. A buyer receives 500 PO lines in a month. Forty fail OTIF. Twenty-five require 20 minutes of buyer or receiving work, at an internal burdened rate of $48 per hour. Eight trigger $350 of premium freight, and three create $1,800 of downtime or lost-margin exposure. The visible monthly cost is $8,400: $400 of handling, $2,800 of premium freight and $5,400 of operating impact. The percentages matter, but the cost-ranked cause list tells procurement where to start.
Use the same discipline as a freight carrier scorecard: metric definition, evidence source, review owner, corrective action and volume decision. Do not auto-charge a supplier from one questionable scan. Material consequences need the PO rule, event evidence, documented impact and a human approval.
Who should not use a standard OTIF scorecard
Here is the damaging admission: a standard OTIF scorecard is a bad fit for highly engineered, project-based or custom-fabricated purchases where milestone acceptance matters more than a single delivery date. It can also punish suppliers unfairly when buyers constantly revise demand, approve partials informally or control the late carrier. In those environments, use a milestone and constraint scorecard first. Fix buyer discipline before pretending the supplier owns every miss.
For repeat inbound flow, though, the thesis holds. Define the promise, preserve the transaction trail, automate the clean matches and make people resolve the exceptions. A useful supplier OTIF scorecard does not create another dashboard. It gives procurement, logistics and warehouse teams one version of the miss—and one next action.
Want to map your supplier performance workflow? Share a redacted PO, supplier acknowledgement, ASN and receiving record. Easy Logistics can identify the broken handoffs, define the scorecard rules and show where transportation, warehousing or API automation can remove the manual work. Request a supplier OTIF workflow review below.