OTIF explained and how to avoid retailer fines
OTIF stands for on-time, in-full. It measures whether the right products arrive in the required quantities within the agreed delivery window. Wholesale distributors and direct store delivery (DSD) teams need to check each order against the retailer’s requirements and keep a reliable receiving record.
At the order level, OTIF is the percentage of eligible orders delivered both on time and in full. An order has to meet both conditions to count. If 88 of 100 eligible orders do, the OTIF score is 88%.
Catch shortages and timing problems before delivery, and keep the records needed to explain what happened if a retailer questions it. Retailer “fines” are generally compliance charges or payment deductions. The applicable supplier program sets the calculation and dispute rights.
How to calculate OTIF correctly
The order-level formula is:
OTIF percentage = Orders delivered on time AND in full ÷ Total eligible orders × 100
First, decide which orders belong in the calculation. An internal weekly scorecard should include orders due that week, with overdue, undelivered orders counted as failures. For retailer reporting, follow its required period, exclusions and measurement unit. Count each eligible order once, even if it takes multiple shipments to deliver it.
In this hypothetical example, a beverage distributor has 100 eligible store orders due this week. Each has one agreed delivery window, with the same requirements applied throughout.
| Delivery result | Orders | Passes OTIF |
|---|---|---|
| On time and complete | 88 | Yes |
| On time but short | 7 | No |
| Outside the window but complete | 3 | No |
| Outside the window and short | 2 | No |
| Total eligible orders | 100 | 88 pass |
OTIF is 88 ÷ 100 × 100 = 88%. Looking at the two conditions separately, 95% of orders arrived on time and 91% were complete. Multiplying those rates gives 86.45%, a different result from the 88% actually observed. Use the count of orders that met both conditions. The separate rates don’t tell you how many did.
The measurement unit matters, too. A hypothetical order for 100 cases with 90 correct cases delivered on time fails a strict whole-order test. A case-based method can credit those 90 cases. McKinsey’s research on retailer OTIF definitions describes these differences across order, line and case measures, along with differences in requested dates, promised dates and appointment windows. Its 2019 proposed standard explains the measurement choices; consult the retailer’s current rules for compliance.
Confirm the retailer rules before setting a target
Build a requirements sheet for each account. Target percentages and fine schedules vary by retailer. Use the current supplier agreement, routing guide and retailer portal, noting the effective date and who confirmed each rule.
| Rule to confirm | What your team needs to record |
|---|---|
| Measurement unit | Order, line, case or unit; eligible population; exclusions |
| Timing test | Required date or window, time zone, early allowance and accepted arrival event |
| Completeness test | Item identifiers, case packs, approved substitutions, split deliveries and rejected goods |
| Accountability | Supplier delivery versus retailer collection; which party owns each event |
| Charges and disputes | Reason codes, calculation basis, thresholds, evidence requirements and submission deadlines |
Check whether timestamps mean arrival at the gate, check-in, unloading or completed receipt. A driver’s arrival record and a warehouse’s receiving timestamp can both be accurate while describing different events. Keep both so your team can explain the difference.
Appointment changes also need a separate check against the purchase order. Kroger’s public logistics guidance, for example, tells suppliers of fresh meat, floral and produce to request a buyer date change before scheduling outside the due date. It also says grocery appointments cannot normally be made within 24 hours of delivery. That guidance explains how to schedule; it does not establish a universal OTIF target or penalty schedule.
For DSD accounts, check receiving hours and who can accept the delivery. A recorded store visit alone won’t show that the full order was accepted. Keep store-level requirements separate from distribution-center programs.
Prevent delivery failures before the truck leaves
Validate the order and every change
Check the ship-to location, product identifier, unit of measure and case pack against the purchase order. Twenty-four cases and 24 individual units are very different requests. Confirm stock availability before committing to a delivery window, and flag promotional quantities that exceed normal demand.
Put one person in charge of order revisions. Keep the original order and each approved change, then update the warehouse instructions and shipping records together. GS1 US order-change guidance emphasizes agreement between the purchase order, advance ship notice (ASN) and trading partners. The ASN describes the shipment before receipt. You’ll still need receiving evidence to establish what the buyer accepted.
Reconcile the pick and the load
Before dispatch, compare the ordered, picked and loaded quantities by SKU. Fix wrong pack sizes, missing cases and product condition issues while the goods are still at the warehouse. If a short shipment is unavoidable, get any required approval and retain the revised instruction. Lowering the order quantity without that approval would hide the shortage in the score.
For van sales, check how much loaded inventory is already committed to later stops. A truck can be full and still be short of the product one account needs. Your order fulfillment process should carry the same quantities from order entry through picking and delivery.
Plan for receiving time and escalate early
Build the route around receiving windows, unloading time and known access constraints. Allow time at each stop to check quantities and record acceptance. When a carrier handles the delivery, confirm the appointment has been accepted and the required shipping references are ready before pickup.
Dispatch needs a short list of orders at risk: appointments awaiting confirmation, picking that’s running close to departure, stock shortages and stops likely to miss their windows. Give each issue an owner and a next action. Contact the buyer through the required channel while there’s still time to act, and save the written response. Check it carefully: a new appointment alone doesn’t establish a change to the compliance due date.
Record acceptance at the stop
While the driver is still at the store, record the delivery time, receiver, quantities accepted and any exceptions. Capture shortages, rejected cases and substitutions by item. Add photos where they help explain condition or quantity, along with the signature or other acceptance evidence the account requires.
At low-signal locations, check that the records were saved and later synced before closing the route. Proof of delivery software can keep signatures, photos and check-in records with the order. Make sure the fields your team captures match the evidence the retailer accepts.
Investigate deductions with an order evidence file
Start by matching the deduction to the order and the rule it allegedly breached. Pricing, invoice, labeling and damage disputes can follow different processes, so check the reason code before treating a deduction as an OTIF failure.
A practical review follows the order from the original commitment through receipt:
- Record the retailer, facility, purchase order, invoice, reason code, amount, disputed quantity and submission deadline
- Gather the original order, approved revisions, delivery window and appointment confirmations
- Add the pick and load records, ASN where required, carrier references, arrival evidence and signed receiving documents
- Compare the records to establish whether there was a physical shortage or delay, a receipt mismatch, a unit conversion error or an approved exception
- Submit the evidence through the retailer’s designated process, save the case number and reconcile the final adjustment
Consider a hypothetical order for 40 cases. The retailer records 36 received, but the driver’s signed receipt lists 40. Include the item-level receipt, order and delivery reference in the dispute. If the receipt instead records four rejected cases, investigate why they were rejected. The signature alone won’t establish that all 40 cases qualified as accepted product.
Check the charge calculation just as closely. Under a hypothetical agreement that charges 2% of $5,000 in affected merchandise, the deduction is $100. Applying the same rate to a $20,000 invoice gives $400. Neither example represents a current retailer policy. Verify the percentage, the amount it applies to, any thresholds and whether charges can overlap under the actual program.
Use separate reason codes for operational failures and disputed data errors. Reviewing them by retailer, facility, SKU and route helps your team spot recurring problems, such as the same case-pack mistake appearing across several deliveries. Keep disputed, approved and recovered amounts separate as well. Filing a claim doesn’t mean the money has been recovered.
Make OTIF part of the daily delivery workflow
Start with one retailer and follow a small set of recent orders from the original commitment through receipt. Confirm that your calculation and evidence match the account’s requirements, then use those checks before dispatch and during route closeout. Work on the causes that keep recurring, and revisit the requirements whenever the retailer changes its program.
SimplyDepo’s direct store delivery software brings route building, mobile orders, van inventory visibility and delivery records into the field workflow. Its proof of delivery tools capture signatures, photos and GPS-stamped check-ins. Those records can help your team run deliveries more consistently. Your team still needs to manage retailer rules, required EDI messages and dispute submissions.
If route and delivery records are difficult to reconcile, book a SimplyDepo demo and use a real order with delivery exceptions to walk through the workflow.
Frequently asked questions
No. Fill rate measures how completely orders were fulfilled, at an order, line or unit level. OTIF adds the timing requirement. Before comparing the two, check that they cover the same orders and reporting period and use the same measurement unit.
Perfect order fulfillment also considers documentation accuracy and product condition, as set out in ASCM’s SCOR definition. An order can meet a narrowly defined OTIF measure and still fail a separate documentation or damage requirement.
Not automatically. A replacement can resolve the shortage after the original delivery window has been missed. Keep the original delivery records and apply the retailer’s rules for split deliveries, corrections and approved changes.
Follow the program’s eligibility rules, and keep the cancellation timestamp and approval. A valid cancellation before the cutoff can be treated differently from one made after the order was due. Don’t remove failed orders retroactively to raise the score.
Check orders at risk before dispatch and delivery exceptions during route closeout. Review recurring causes weekly, then reconcile the retailer’s official scorecard on its reporting schedule. Those daily checks give the team a chance to act even if the retailer scores monthly.
Yes, depending on the program. The retailer may control transportation while the supplier remains responsible for product availability, pickup readiness and documentation. Record when the order was ready and what happened at pickup, then apply the program’s accountability rules.
-
October 28, 2026 -
October 28, 2026
-
October 27, 2026
