OTIF, short for on-time in-full, is the share of orders that arrive both complete and within the agreed time frame. An order only counts when both are true at once: a late or incomplete order fails the test. OTIF is often treated as a warehouse number. The other half is carrier execution and the final delivery, and a delivery platform can measure that half of the score.

What OTIF measures, and its two halves

OTIF combines two questions into one pass-or-fail result.

On time asks whether the order arrived by the date you agreed with the customer. In full asks whether every line and the full quantity arrived, with nothing back-ordered or missing. An order scores as OTIF only when it satisfies both. This order-level test reflects what the customer actually received against the original promise.

You will also see DIFOT, delivered in full on time, used across transport and postal contexts. It usually describes the same customer-facing idea in reversed word order. Treat it as a near-synonym unless a trading partner defines it differently in a contract.

The two halves fail for different reasons and have different ownership areas: in-full misses trace back to stock availability and picking accuracy inside the warehouse, while on-time misses happen after dispatch, in carrier handoff, transit, and the final delivery attempt. Generally, we found that separating the two helps teams investigate the right causes.

How to calculate OTIF, and the mistake to avoid

A reliable formula counts orders directly:

OTIF (%) = (orders delivered both on time and in full ÷ total orders) × 100

Use the same population and unit of analysis throughout so the result can be compared reliably in carrier reviews and supplier scorecards.

A common shortcut gives you a different number. Many pages tell you to multiply your on-time rate by your in-full rate, but that only matches true OTIF when the two are statistically independent, which real orders rarely are.

Consider 1,000 orders: 920 arrive on time, 950 arrive in full, and 890 satisfy both. Counted directly, OTIF is 890 ÷ 1,000, or 89.0%. Multiply 92.0% by 95.0% instead and you get 87.4%. 

The shortcut understates real performance here, and in other months it will overstate it. Instead, count the orders that clear both conditions and you avoid the guesswork.

For diagnosis, keep the direct order-level score as your headline, then break failures down to the line level so you can see which SKUs, carriers, or lanes are behind a miss.

What is a good OTIF score?

A good score depends on the promise you have made and the sector you operate in. Your own baseline, measured consistently over time, is usually the most useful benchmark.

Many large retailers run OTIF compliance programs with targets of 95% or higher, and some hold suppliers to 98% or more with penalties for misses.

Those figures are buyer-set targets, not descriptions of what the average operation achieves. Regulated and high-criticality supply chains, from healthcare to automotive production lines, tend to hold tighter tolerances because a late or short order can stop something downstream.

Therefore, a generic figure found online may not reflect your operation: measure OTIF against the correct promised date, then review the trend by carrier and lane to identify where performance can improve.

Bottom line: Set the target from your customer commitments and contract terms.

Measured consistently over time, your own baseline is the most useful OTIF benchmark.

A generic figure found online rarely fits your own promises and contract terms

Freeze the scorecard before you benchmark

An OTIF result is only comparable when everyone scores it the same way. Before comparing carriers or quoting a figure to a customer, settle the policy questions that can materially change the result and document them.

Decision A safe default Why it changes the number
Which date counts as "on time" The original promised date, with any re-promise logged separately A silently updated date can make performance look better than the customer's experience
What proves delivery Accepted receipt or the completed promised slot, mapped from carrier events A "delivered" scan does not always mean the promise was met
What "in full" means Order level for the headline, line level for diagnosis Line-level detail shows which SKUs and carriers drive a miss
Back-orders and split shipments Exclude from "in full" unless the contract allows them Counting partials as complete inflates the score
Early delivery Define it, since window and appointment operations can count "too early" as off-time Early is not automatically on-promise in scheduled receiving

Once agreed, apply these rules across every carrier so you can explain and defend the benchmark when it is questioned.

OTIF, on-time delivery, fill rate and perfect order

These metrics overlap, and teams often use the terms loosely. Each metric below answers a narrower or wider question than OTIF.

Metric What it measures Relationship to OTIF
On-time delivery (OTD) Timeliness only, against the agreed date The time half of OTIF, without the completeness test
Fill rate Whether demand was filled, often at line or unit level Explains part of the in-full half, usually reads higher than OTIF
OTIF Orders both complete and on time The combined promise, pass or fail per order
Perfect order On time, complete, damage-free, and accurately documented Stricter than OTIF, adds condition and paperwork

Report these metrics together to avoid reading a strong result in one as evidence that the whole order process is performing well. When fill rate is healthy but OTIF is weaker, investigate the delivery leg.

In supply-chain reporting, OTIF covers more than fill rate and less than perfect order.

  • Fill rate measures whether demand was filled.

  • Perfect order adds damage-free delivery and accurate documentation.

  • OTIF asks whether the customer received the whole order when promised.

Bottom line: Use perfect order when contracts reward those additional conditions or when damage and invoice accuracy are active concerns, while keeping OTIF as the everyday measure of the delivery promise.

Why the on-time half is a carrier performance problem

Once an order is picked correctly and complete, its OTIF result depends on the delivery, and delivery problems remain common.

In the EU, Eurostat found that 35.4% of online shoppers encountered a problem in 2025, and the single most common issue was slower delivery than expected, reported by 19.9%.

In the UK, Ofcom research found that 68% of parcel recipients experienced a delivery issue in 2025, with delays among the most common.

Last-mile delivery research has put first-attempt failure rates as high as 20% in B2C, and a failed first attempt can still close as a carrier "delivered" event days later, after the promised window has passed.

35.4%

of EU online shoppers hit a problem in 2025

Eurostat, 2025

68%

of UK parcel recipients hit a delivery issue in 2025

Ofcom, 2025

Up to 20%

of first-attempt B2C deliveries can fail

Last-mile delivery research

Together, these findings point to reliability against the promise rather than raw speed. A delivery that arrives when expected supports the customer relationship, while a faster delivery on one order does not offset a missed promised window on another. Measuring performance against the promised date by lane shows which carriers consistently meet the commitment and which are lowering the score.

A failed first attempt can also create a measurement problem: a carrier scan that reads "delivered" is not automatic proof that the original promise was kept. The authoritative event depends on the operation: an accepted receiving advice at a B2B dock, or completion of the promised delivery slot for a consumer parcel. Define the qualifying event by service and lane so the OTIF calculation can be explained when a carrier challenges it.

Bottom line: A single universal transit target will not show these differences. Break aggregate OTIF down by carrier, service, lane, and destination. A carrier performance measurement approach scores each shipment against the SLA that applies to it, showing which carriers contribute most to on-time misses.

Where OTIF misses come from

OTIF misses have different causes and owners, and the response to the question above depends on both.

Use this breakdown to avoid treating the headline percentage as a single operational problem:

Failure Half affected Usual owner First move
Stock shortage or back-order In full Planning, procurement Reduce stockouts, review allocation by SKU and customer
Pick or pack error In full Warehouse Tighten scan verification, chase repeat SKU failures
Late order release or missed cut-off On time, before dispatch Order management, transport planning Firm up cut-off governance, watch release-to-handover times
Missed collection or wrong service On time, before dispatch Warehouse, transport Check handoff readiness, match service choice to the promise
Transit variance or failed first attempt On time, in transit Carrier, shared with shipper Track first-attempt success, reroute where failures persist
Inconsistent or late carrier events Measurement quality Carrier management, analytics Normalize status codes, flag missing events before the miss date

The in-full rows generally require warehouse action. The on-time rows require closer measurement of order release, carrier handoff and delivery performance.

How to improve OTIF

Improving the delivery side of OTIF starts with accurate measurement of the on-time half, including enough detail to act before the promised window is missed.

Protect the original promised date

If the committed date is silently rewritten mid-order, performance looks better than the customer's experience. Report against the original promise, and track any re-promise separately with a reason code.

Measure each shipment against the SLA for its lane and service

A carrier can clear a generous three-day window while missing the next-day promise on the same route every week. Segmenting by carrier, service, and lane keeps those apart.

 nShift Ship gives distribution teams that per-carrier view. Berggård Amundsen, which ships more than 1,200 parcels a day across Norway, uses it exactly this way. As Logistics Director Rolf Inge Danielsen puts it, "the amount of shipping history we have serves as an informative basis when we need to assess new carriers."

Normalize carrier events so results compare

Carriers use different status codes, and benchmarking requires consistent definitions. A common shipment record provides the basis for a trustworthy cross-carrier scorecard.

nShift Data Fabric unifies delivery data into a single model, allowing comparisons from one record rather than a stack of exports. Global fashion brand Superdry runs a multi-carrier operation across 100 countries on nShift Ship, with the real-time visibility that makes a like-for-like read across carriers possible.

Track first-attempt success and act on exceptions early 

Live delivery data is most useful while there is still time to intervene and keep the promise.

Golf apparel brand Galvin Green, which ships more than 30,000 parcels a year, works this way with nShift Track. "The value of nShift Track for me is that it helps us move from reacting to problems to seeing where we can still make a difference," says E-commerce Manager Gustav Höjelid. "If we know a shipment is at risk, we can contact the customer before they have to contact us."

Use visibility to protect the customer relationship around a miss

Clear, proactive updates give customers useful information even when a delivery runs late.

Activewear brand ICANIWILL cut delivery-related customer queries by 50% after taking control of tracking, which also gave it firmer visibility into the speed and success of its orders.

50%

fewer delivery-related customer queries after taking control of tracking

ICANIWILL, activewear brand

Route volume toward carriers that keep the promise

Once scores are consistent, use them in carrier selection and performance reviews. For industrial and freight movements, nShift TMS extends the same discipline to the wider transport operation. These steps can improve the on-time component and the quality of its measurement. They do not address inventory accuracy or picking, so they need to sit alongside warehouse work on the in-full half.

For a broader view of using delivery data to guide routing and reviews, see how teams optimize with delivery analytics.

Match the review cadence to the decision so the data stays current without creating busywork. Weekly checks catch exceptions and SLA breaches while there is still time to act, monthly reviews track trends and carrier mix, and quarterly sessions feed contract decisions with evidence.

Put a defensible number on the on-time half

The in-full half is usually owned by warehouse teams.

Carrier selection, execution and measurement shape much of the on-time half, yet that part is often tracked less consistently.

Score each shipment against the SLA that applies to it, preserve the original promised date, and act on exceptions before the window closes.

See how carrier performance measurement uses the shipment data you already collect to compare carriers fairly and strengthen the on-time half of OTIF.

FAQ

What does OTIF stand for?

OTIF stands for on-time in-full. It measures the percentage of orders that arrive both complete and within the agreed delivery time frame, scored pass or fail per order.

How is OTIF calculated?

Divide the number of orders delivered both on time and in full by the total number of orders, then multiply by 100. Counting orders directly is more reliable than multiplying a separate on-time rate by a separate in-full rate, because those two are rarely independent.

What is a good OTIF score?

Targets vary by sector and contract. Many retail programs set 95% or higher, and some require 98% or more. Treat those as goals set by the buyer, and manage against your own consistently measured baseline and promised dates.

What is the difference between OTIF and OTD?

On-time delivery (OTD) measures timeliness only. OTIF adds the completeness test, so an order has to arrive both on time and in full to count. OTIF is the stricter, more customer-accurate view.
Thomas Bailey

About the author

Thomas Bailey

Product Innovation Lead, nShift

Thomas plays a key role in shaping how new features and platform improvements deliver real value to customers. With a background spanning product, tech, and go-to-market strategy, he brings a pragmatic view of what innovation looks like in practice and how to make delivery experiences work harder for your business.
Read more from this author  →