OTIF only means something when everyone uses the same promise
For Logistics heads, warehouse leads and distribution managers · Understand the problem
TL;DR — what you’ll learn
- Define the unit of measurement and the customer commitment before calculating OTIF.
- Count a qualifying order only when it meets both the on-time and in-full rules.
- Keep late changes, partial deliveries and missing receipt evidence visible.
- Analyse failure reasons rather than treating the headline percentage as the explanation.
Sales reports 95% service because most quantities shipped. Logistics reports 90% because most vehicles arrived on time. The customer reports 80% because several orders were either late or incomplete. Before debating the numbers, establish which promise each report is measuring.
How should a food distributor calculate on-time in-full delivery?
OTIF is the percentage of eligible orders or other defined units that satisfy both the agreed on-time and in-full conditions. The business must state the denominator, commitment basis, receipt event and quantity rules. Without those definitions, two correct calculations can describe different service performance.
- 01Define eligible ordersCommitment and measurement rules
- 02Link receipt evidenceTime and accepted quantity
- 03Check both conditionsOn time and in fullDoes the order satisfy both rules?YesReport the intersectionNoCount the supported failure or mark missing evidence unresolved.
- 04Report the intersectionCounts, rate and failure causes
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
Write the definition in a sentence
An example definition is: the percentage of eligible customer orders due in the period that were accepted within the confirmed receiving window and in the full agreed quantity. That is one possible business definition, not a universal contract standard. A customer may use line-level measurement or different rules, which should be documented separately.
Specify the period, exclusions, commitment timestamp, unit of measure and source of receipt evidence. Define whether early arrival qualifies and how agreed changes are treated. These decisions should be settled with the relevant commercial and operations owners before the dashboard is built.
Calculate the intersection
Suppose an illustrative period contains 100 eligible orders. Ninety are on time, eighty-five are in full and eighty satisfy both conditions. Order-level OTIF is 80 divided by 100, or 80%. It is not the average of 90% and 85%, and multiplying those two rates would not recover the observed intersection.
The example contains ten orders that are on time but short, five that are complete but late and five that are both late and short. Those groups explain the service failures without double counting an order in the headline denominator.
| Outcome | Orders |
|---|---|
| On time and in full | 80 |
| On time, not in full | 10 |
| In full, not on time | 5 |
| Neither | 5 |
| Eligible total | 100 |
| OTIF | 80% |
Preserve the promise that was measured
Keep the original request and the confirmed commitment, with later changes and their authorisation. If the delivery date is overwritten after a delay, the report can make a missed promise disappear. A revised agreement may deserve its own measure, but it should not silently replace the historical commitment.
Define how split deliveries affect the result. If an order requires all quantities by one window, a partial first delivery does not make the order complete. If the commercial agreement genuinely contains separate scheduled lines, use the corresponding agreed measurement unit. The data model should follow the promise rather than whichever transaction is easiest to count.
Use the right event as evidence
A dispatch timestamp proves that goods left the warehouse, not that the customer received them. A carrier arrival can differ from the customer's acceptance time. Choose the event that supports the stated definition and retain its source. Missing evidence should appear as unresolved rather than automatically on time or late without a disclosed rule.
Frappe's Delivery Note documentation illustrates the dispatch record and its related transactions. That is a useful starting relationship, but an OTIF calculation based on customer receipt needs the corresponding receipt evidence as well. Connect those records at the line or order level used by the metric.
Source: Frappe / ERPNext · Dispatch records and related transactions. Reference details
Turn failures into operational questions
Break the non-qualifying orders into causes supported by evidence: stock unavailable, production late, dispatch delayed, route disruption, receiving delay or unresolved quantity dispute. Preserve a separate unknown category. Forcing every failure into a convenient reason can create a confident but misleading improvement plan.
Compare periods and customers only when the definitions and mix are comparable. A small customer with a few orders can show a large percentage swing from one event. Display the numerator and denominator beside the rate so readers can judge its scale.
Start by manually reconciling a sample of complete and failed orders against source documents. Once the definition survives that review, automate the calculation and retain an exception queue for missing or contradictory evidence. The percentage should be the final result of the account, not the place where uncertainty is hidden.
Summary
OTIF measures the intersection of two promises under a stated definition. Preserve the commitment, use the correct receipt evidence and show the underlying counts. The metric becomes useful when failed orders lead to explainable operating causes rather than arguments about competing percentages.
What to do next
- Agree the order or line-level definition with sales, logistics and customer service.
- Recalculate one period using the original commitments and receipt evidence.
- Review failed and unresolved orders before setting an improvement target.
Recognise this problem in your operation?
Tell us where the records or handovers break down. We can discuss the process, data and software questions worth examining first.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Delivery NoteFrappe / ERPNext · Online product documentation, accessed October 2026
Reference for delivery records and related returns. Proof of receipt, customer acceptance and financial settlement remain distinct events in the proposed workflow.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
