What on-time in-full delivery measures for an order
Delpack Logistics
October 26, 2026
10 min read
A pallet reaches its deadline with nineteen of twenty cases; test timing and complete quantity separately before the combined OTIF result.
A customer expects a pallet of twenty cases by Tuesday afternoon. The truck arrives within the agreed window, but the receiver counts nineteen cases. The timing condition is met and the quantity condition is not. What on-time in-full delivery measures , often shortened to OTIF, is whether the defined order or shipment satisfied both conditions together: the required goods arrived by the applicable deadline and the committed quantity was delivered. A timely vehicle arrival alone cannot make a short shipment “in full.”
The example is hypothetical. It shows why OTIF combines records from order fulfillment and transportation. The order states what was promised, the shipment records what left, and the receipt or delivery evidence shows what actually reached the customer and when. The exact measurement unit and tolerances depend on the agreement and report design. A useful OTIF result states those rules before judging a case.
Test timely arrival against the agreed window
Timely arrival requires a defined promise. The agreement may specify a date, a time window, or an appointment. A scheduled pickup is not the same as a promised delivery. A truck that departs its origin early can still miss the customer’s receiving window. For the pallet, suppose the applicable deadline is Tuesday at 4 p.m. and the receiver confirms delivery at 3:30 p.m. The time component passes under that example rule.
Before making that comparison, identify the evidence of arrival or completion the customer and supplier use. A gate check-in may differ from a signed receipt. A truck can reach the site before the deadline but wait to unload until afterward. Some agreements use arrival at a facility, others use completed delivery or proof of receipt. The metric must follow the agreed event. This article does not choose a universal rule for all carriers or customers.
Promise changes also need a record. If the customer requests a different date, the team should preserve the original and revised terms and note which governs the OTIF calculation. An updated estimated arrival from a carrier is useful operational information, but it does not automatically replace the customer’s commitment. Reporting against a movable estimate after the event would make performance look better without showing whether the original obligation was met.
A timing-only measure stops here. OTIF continues to ask whether the complete committed quantity was delivered. That is the distinction from the on-time delivery topic. One order can be on time under a timing report and fail OTIF because the load is short.
Check complete quantity against the commitment
The complete quantity test compares the delivered amount with the amount due for the measured order, line, or shipment. In the pallet example, the commitment is twenty cases and the receiver counts nineteen. If the agreement requires all twenty by Tuesday, the full-quantity component fails. The missing case might arrive Wednesday, but that later completion does not make the Tuesday delivery both on time and in full under the original deadline.
Quantity needs a unit of measure. Twenty cases are not twenty individual units if each case contains several items. A shipping document may list twenty cases while a receiver counts nineteen physical cases. The team should reconcile the product and packaging units before declaring a shortage. A damaged case rejected by the receiver may also affect accepted delivered quantity under the agreement, even if the truck physically carried twenty cases to the site.
DHL describes OTIF as a shipment arriving within the agreed lead time and in the total quantity promised. It notes that the industry does not use one universally aligned formula. That is a useful caution: the combined idea is stable, while the precise population, event, and tolerance rules must be stated for each report. This article uses the strict twenty-of-twenty example for clarity, not as a claim about every commercial contract.
Some agreements permit a defined quantity tolerance or an approved substitution. If so, the report should apply that documented rule. A team cannot silently treat nineteen as “full” because the shortage seems small. Nor should it reject an order that legitimately falls within an agreed tolerance. The numerator of an OTIF rate depends on these choices, so the choices belong in the metric definition.
Choose the eligible order unit
An eligible order might be a purchase order, order line, shipment, pallet, or delivery appointment. These units produce different outcomes. If one order contains several lines and one line is short, an order-level OTIF result may fail while the other lines pass when measured separately. The report should name its unit and keep it stable across the comparison period.
Take a two-line order. The customer expects twenty cases of one product and ten of another. The first line arrives complete by Tuesday; the second arrives with one case missing. An order-level strict OTIF test fails because the order as a whole is short. A line-level report could show one passing line and one failing line. Neither output is meaningful without its unit label. A single percent cannot tell a reviewer which version was used.
Split shipments add another question. A supplier may send the twenty cases in two deliveries, both due Tuesday. If twelve arrive in the morning and eight in the afternoon before the deadline, the full quantity can pass under a deadline-based order rule. If the second delivery arrives Wednesday, the order fails that rule even though the entire quantity eventually arrives. A report that counts only the first truck’s arrival would miss the remaining obligation.
The eligible population should also be defined. Orders canceled before release, customer-requested holds, and service types with different promises may require distinct handling. Exclusions should be documented before results are known. Removing a short order after it fails would inflate the rate; including an order that never became a delivery obligation could distort the denominator. A trustworthy report shows how many orders were eligible and how exceptions were treated.
Work the missing-case example step by step
Write down the agreement: twenty cases due Tuesday by 4 p.m. Record the observed handoff: the receiver signs or otherwise confirms nineteen accepted cases at 3:30 p.m. The time test passes. The in-full test fails because one required case is absent. The combined OTIF result fails. If the missing case is found later and delivered Wednesday, record that later completion separately. Do not overwrite the Tuesday result.
Now ask where the case went, but keep that investigation separate from the OTIF calculation. The warehouse may have picked nineteen, loaded twenty but failed to record one, or delivered twenty with a receiving count discrepancy. Each scenario needs evidence from pick, pack, load, and receipt records. The combined metric identifies a failed obligation under the chosen rule; it does not by itself identify the responsible stage.
A receiving document that lists twenty expected cases is not proof that twenty were accepted. A shipping manifest listing twenty planned cases is not proof all twenty reached the customer. The strongest evidence includes the actual physical count and the authorized receipt record. If the count is disputed, preserve both parties’ records and reconcile the case rather than awarding an OTIF pass from a planned document.
Suppose the missing case was left at the origin dock and delivered the next morning. That is a clear fulfillment or loading miss in the example, yet the OTIF verdict remains a combined failure on Tuesday. The team can repair the process once the cause is established. Changing the original deadline after a late second trip would erase the signal the metric was meant to provide.
Keep OTIF separate from order accuracy
OTIF usually focuses on timing and completeness of the committed goods. A broader order-accuracy measure can ask whether the right product variant, destination, and condition were received. The two can overlap in practice, because a wrong product may fail the “in full” obligation if the promised product is absent. A report should state whether it treats substitutions as incomplete or tracks them in a separate correctness measure.
In the pallet example, the product identity is assumed correct and the only discrepancy is one missing case. That isolates the quantity decision. A different example, a pallet of twenty cases delivered on time with one wrong variant, belongs to the order-accuracy question. Treating all errors as the same metric makes it hard to know whether a team needs better quantity control, item selection, or delivery timing.
Likewise, a route can deliver a complete order late. The in-full component passes, the on-time component fails, and OTIF fails. A combined score should retain the component results so the team can see which side of the obligation broke. Reporting only “fail” makes it harder to improve the right process.
Audit the rate from records
For each eligible unit, store the promised deadline, committed quantity, accepted delivered quantity by that deadline, actual handoff event, and component results. Then mark OTIF pass only when both components pass under the documented rules. If ninety of one hundred eligible orders satisfy both, the OTIF rate is 90 percent. A timing-only rate or a quantity-only rate for the same group could be higher. Those differences are useful because they show which condition caused the combined misses.
Check a sample of borderline cases. A delivery at the deadline may depend on whether the endpoint is inclusive. A partial receipt before the deadline followed by a final case after it should remain short at the deadline. A delivery record with no receiver count may need reconciliation. A changed order quantity needs an authorized change record. The rate should be reproducible from the saved promise and receipt evidence rather than a manually selected pass flag.
Trend reports should not compare unlike service populations without explanation. A week with many multi-line pallet orders may present more ways to fail an order-level strict OTIF test than a week of single-case orders. Show the denominator and, when useful, the mix of order types. A rate can change because execution improved or because the measured work changed.
Preserve partial receipts and later corrections
A receiver may initially report nineteen cases, then find the twentieth on the same trailer before the delivery window closes. In that situation, the final accepted quantity by the deadline may be twenty if the correction is verified under the receiving process. The original short count should remain in the event history, along with the recount and its time. A team can then see that the case was present by the deadline and why the first receipt record differed.
Another case has the same first count but a different outcome: the twentieth case is still at the origin and reaches the receiver the next day. A later record should add the second delivery rather than edit Tuesday’s accepted quantity to twenty. The distinction depends on physical handoff evidence, not a revised spreadsheet total. OTIF concerns what was delivered by the governing deadline.
Corrections can also change the promised quantity. If the customer approves a nineteen-case order before shipment, the obligation may be nineteen under the authorized change. The team should preserve when that approval occurred and which order line it affected. An after-the-fact reduction solely to turn a failure into a pass would not describe the original commitment. Keeping versioned order terms lets a reviewer distinguish a genuine amendment from a retroactive rewrite.
What a logistics worker can learn from OTIF
OTIF connects several parts of the operation. Order entry records the obligation. Warehouse staff pick and load the committed quantity. Transport staff move it to the agreed destination. Receiving or delivery staff confirm what arrived and when. A worker in any one stage should know which record they contribute to the final comparison and how to report a discrepancy rather than silently mark a task complete.
A job seeker can ask how the employer records short shipments, whether drivers verify case counts, and who reconciles a disputed receipt. The answers reveal whether the role is mainly picking, load control, carrier coordination, or final handoff. The delivery route performance metrics guide addresses other results of driver work; OTIF adds a combined customer obligation that cannot be inferred from route departure alone.
The Fort Wayne driver careers page lists Delpack’s current local opportunities. The posting and employer process determine whether a particular driver counts cases, verifies a load, or records a short delivery. This article does not assume Delpack uses OTIF as a contractual metric.
Require both parts to pass
What on-time in-full delivery measures is whether the defined customer obligation was met in time and in quantity. The pallet at 3:30 p.m. passes the time test and fails the twenty-case test because only nineteen arrive. Its combined OTIF outcome fails under the stated rule. Keeping the two component results, the promise, and the accepted receipt lets the operation explain the result and investigate the missing case without confusing timely arrival with complete fulfillment.
Continue with Delpack
Review the Fort Wayne career overview or contact Delpack with a question about the company.
Topics
Browse Topics
All Guides
346
Job Search, Applications & Offers
79
Role Types & Job Fit
83
Schedules, Policies & Work-Life
40
Route Operations & Performance
91
Logistics & Warehouse Operations
53
Delpack Logistics Delpack Logistics is an Amazon Delivery Service Partner and last-mile logistics company serving the Fort Wayne market. Explore Welcome Meet Delpack Fort Wayne Delivery Driver Careers Driver Resources Contact Delpack Delpack News Legal Terms of Service Privacy Policy SMS status Contact info@delpacklogistics.com 260-306-5806 View market and mailing address © 2026 Delpack Logistics . All rights reserved.