On-Time In-Full (OTIF) is a composite supply chain key performance indicator that measures a supplier's ability to deliver the exact quantity of goods ordered by the originally committed delivery date. It is calculated as the percentage of purchase order lines delivered completely, without shortages or overages, and received on or before the scheduled due date.
Glossary
On-Time In-Full (OTIF)

What is On-Time In-Full (OTIF)?
A critical metric measuring perfect order fulfillment, evaluating both delivery timeliness and quantity accuracy against the original purchase order.
OTIF serves as a rigorous measure of perfect order fulfillment, penalizing both late deliveries and incomplete shipments. A failure in either dimension—a shipment arriving on time but short, or a complete shipment arriving late—results in an OTIF miss, making it a demanding benchmark for supplier reliability and supply chain precision.
Key Characteristics of OTIF
On-Time In-Full (OTIF) is a composite supply chain metric that measures delivery performance across two critical dimensions: timeliness and quantity accuracy. A line item is considered OTIF-compliant only if it arrives by the originally committed date and in the exact quantity ordered.
The Two-Dimensional Nature of OTIF
OTIF is a logical AND gate, not an average. A delivery fails the metric if it is late but complete, or on-time but short-shipped. This strict binary evaluation prevents suppliers from masking poor performance in one dimension with excellence in the other.
- On-Time: Delivery occurs on or before the original requested date, not a renegotiated date.
- In-Full: The quantity received exactly matches the quantity ordered; partial shipments are failures.
- Composite Rate: Calculated as (Number of OTIF-Compliant Lines / Total Lines Ordered) × 100.
Original Commit Date vs. Customer Request Date
A critical distinction in OTIF calculation is the anchor date. High-maturity supply chains measure against the customer's original request date, while less mature ones measure against the supplier's acknowledged date.
- Customer Request Date: The date the buyer initially wanted delivery. Measuring against this exposes the full capability gap.
- Supplier Commit Date: The date the supplier promised after order acceptance. This allows suppliers to negotiate away poor performance.
- Best Practice: World-class organizations use the unadjusted customer request date to drive genuine lead time compression.
OTIF vs. Traditional Fill Rate
Traditional fill rate metrics often obscure true performance by allowing backorders or partial shipments to be counted as fulfilled. OTIF eliminates these loopholes.
- Fill Rate: Measures the percentage of demand met from available stock, often allowing late deliveries to count positively.
- OTIF: Imposes a strict time window; a perfect fill delivered one day late is a failure.
- Line-Level vs. Order-Level: OTIF is typically measured at the line-item level. Order-level OTIF, where every line on a purchase order must be perfect, is a more stringent variant used for critical assemblies.
Calculation and Data Requirements
Accurate OTIF measurement requires clean, synchronized data from both the buyer's procurement system and the supplier's shipping documentation.
- Required Data Fields: Purchase order line number, ordered quantity, original request date, actual receipt date, and actual receipt quantity.
- Data Quality Challenges: Discrepancies in goods receipt posting times, time zone mismatches, and unrecorded partial deliveries corrupt the metric.
- Automation: Leading organizations integrate ERP systems with supplier portals to capture real-time ASN data, eliminating manual data entry errors.
OTIF as a Supplier Segmentation Tool
Procurement organizations use rolling OTIF scores to classify suppliers into performance tiers, which directly informs sourcing decisions and inventory strategies.
- Strategic Partners: >95% OTIF — eligible for long-term contracts and reduced oversight.
- Core Suppliers: 85-95% OTIF — require collaborative improvement plans.
- Transactional/At-Risk: <85% OTIF — trigger formal corrective action requests and potential resourcing.
- Dynamic Safety Stock: Suppliers with high OTIF variability force buyers to hold larger buffer inventories, directly increasing carrying costs.
Relationship to Predictive Lead Time Analytics
OTIF is a lagging indicator of historical performance. Predictive lead time analytics transforms this reactive metric into a forward-looking operational capability.
- Lead Time Prediction: Machine learning models forecast the probability of an OTIF failure for each open purchase order before the delivery date.
- Prescriptive Intervention: When a model predicts a high risk of failure, the system can trigger expediting actions or re-route inventory from alternative nodes.
- Root Cause Analysis: Correlating OTIF failures with external variables—such as port congestion or supplier financial distress—enables proactive risk mitigation rather than post-mortem reporting.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the On-Time In-Full metric, its calculation, and its role in modern supply chain intelligence.
On-Time In-Full (OTIF) is a composite supply chain key performance indicator (KPI) that measures a supplier's ability to deliver the exact quantity of goods ordered by the originally committed delivery date. It is calculated as the percentage of order lines or orders that meet both conditions simultaneously. The formula is: OTIF % = (Number of On-Time and In-Full Deliveries / Total Deliveries) * 100. A delivery is considered On-Time only if it arrives by the customer's originally requested date—not a revised or acknowledged date—and In-Full only if the delivered quantity matches the ordered quantity exactly, with no short shipments or partial fills. This strict dual-condition logic makes OTIF a far more rigorous measure of reliability than simple fill rate or average lateness, directly quantifying the customer experience and supplier precision.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Mastering OTIF requires understanding the predictive models, statistical techniques, and complementary metrics that quantify delivery precision and drive continuous improvement.
Lead Time Prediction
The application of machine learning models to forecast the total elapsed time from purchase order issuance to goods receipt. Unlike static lead times in ERP systems, these models dynamically account for:
- Supplier processing variability
- Manufacturing cycle times
- Transit duration and port congestion
- Seasonal demand patterns
Accurate lead time prediction is the foundational input for setting realistic delivery dates and improving OTIF scores.
Supplier Reliability Score
A composite quantitative metric that ranks suppliers based on historical delivery precision, lead time stability, and responsiveness. Key components include:
- On-Time Percentage: Frequency of meeting committed dates
- In-Full Percentage: Frequency of delivering complete quantities
- Lead Time Variance: Consistency of delivery cycles
- Recovery Rate: Speed of resolving disruptions
These scores enable procurement teams to segment suppliers by risk tier and trigger corrective action plans for chronic underperformers.
Prediction Intervals
A range of values within which a future delivery date is expected to fall with a specified probability (e.g., 90%). Unlike a single point estimate, prediction intervals quantify uncertainty and enable:
- Dynamic buffer time calculations for safety stock
- Risk-adjusted order promising to customers
- Proactive exception alerts when confidence drops
Prediction intervals transform OTIF from a reactive lagging indicator into a forward-looking risk management tool.
Dynamic Buffer Time
An algorithmically adjusted time cushion added to a deterministic lead time forecast based on real-time risk factors:
- Current port congestion indices
- Supplier production backlog signals
- Weather disruption probabilities
- Geopolitical risk scores
Dynamic buffers replace static safety lead times, absorbing variability precisely when and where it is needed to protect OTIF performance without inflating inventory costs across the board.
Mean Absolute Percentage Error (MAPE)
A scale-independent accuracy metric measuring the average absolute percentage difference between forecasted and actual lead times. While widely used for benchmarking model performance, MAPE has limitations:
- Asymmetric penalty: underestimates are penalized differently than overestimates
- Undefined when actual values are zero
- Sensitive to outliers in sparse delivery data
Supply chain data scientists often complement MAPE with pinball loss functions and prediction interval coverage probability for a more complete accuracy assessment.
Explainable AI (XAI) for OTIF
A set of methods and techniques that make complex machine learning predictions understandable to supply chain planners. When a model predicts a delivery will miss OTIF targets, XAI reveals the key drivers:
- SHAP Values: Quantify each feature's contribution to a specific delay prediction
- Counterfactual Explanations: Show what would need to change to achieve on-time delivery
- Feature Importance Rankings: Identify systemic issues like a specific carrier lane or product category
This transparency builds planner trust and enables targeted corrective actions rather than black-box alerts.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us