The physical order-to-delivery process is only half the job. Reliable execution also requires controls that detect exceptions early, protect the customer promise and measure whether the order was delivered completely, accurately and on time.
Key Control Points
| Stage | Control | Typical Exception |
|---|---|---|
| Order entry | Price, address, item, quantity and requested-date validation | Invalid order or commercial mismatch |
| Allocation | ATP/inventory and customer-priority check | Short stock or backorder |
| Picking | Scan and quantity verification | Wrong SKU or quantity |
| Packing | Packaging, labels and document check | Damage or compliance error |
| Dispatch | Carrier, route, cut-off and load confirmation | Missed departure |
| Delivery | POD and discrepancy capture | Late, partial or damaged delivery |
Core KPI Formulas
OTIF % = Orders delivered on time and in full ÷ Total orders due × 100
APQC defines OTIF as the percentage of sales orders delivered complete and within the agreed time frame. It is important to define the promised date consistently: customer-requested date, confirmed date or contract date.
Perfect Order % = On-time % × Complete % × Damage-free % × Accurate-documentation %
Perfect order is stricter than OTIF because a shipment can arrive on time and complete but still fail through damage, wrong documentation or invoicing errors.
Order Cycle Time = Delivery timestamp − Valid order-entry timestamp
Backorder Rate % = Order lines not available at promise point ÷ Total order lines × 100
Worked KPI Example
Assume 500 orders were due this month. 455 arrived on time and in full. OTIF = 455 ÷ 500 × 100 = 91.0%.
Suppose the wider performance measures are 94% on time, 97% complete, 99% damage-free and 98% document-accurate. Perfect Order = 0.94 × 0.97 × 0.99 × 0.98 × 100 = 88.5% approximately. This shows why a business can have a reasonable delivery score while still losing performance through documentation, shortages or damage.
Exception Management
Every major exception should have four things: an owner, a customer-impact assessment, a recovery date and an escalation rule. Useful triggers include inventory shortages, late supplier receipts, missed carrier cut-offs, customs holds, rejected deliveries and missing POD.
| Exception | Immediate Action | Root-Cause Follow-up |
|---|---|---|
| Short stock | Allocate, split, substitute or revise promise | Forecast, safety stock, supplier or inventory accuracy |
| Missed dispatch | Rebook transport and notify customer | Cut-off, picking capacity or carrier reliability |
| Damaged delivery | Record POD exception and arrange replacement/claim | Packaging, handling or carrier controls |
| Wrong documentation | Correct document and prevent release delay | Master data, workflow or document ownership |
Customer Communication Standard
- Notify the customer before the missed promise becomes visible to them.
- State what changed, what is affected and the revised ETA.
- Offer partial delivery, substitute product or alternate delivery option where commercially appropriate.
- Close the loop after delivery and POD.
Useful Management Dashboard
- OTIF %
- Perfect Order %
- Order cycle time
- Backorder rate
- Pick/ship accuracy
- Damage/claims rate
- POD turnaround
- Customer-notified-before-failure %
- Top 5 exception root causes
Interview Question
Question: What is the difference between OTIF and Perfect Order?
Strong answer: OTIF measures whether the order was delivered complete and on time. Perfect Order is broader because it also considers whether the delivery was damage-free and supported by accurate documentation. I would use both because OTIF shows service reliability while Perfect Order captures the wider quality of fulfilment.
Related SCMANA Guides
References
Download the Practical Workbook
Use the SCMANA OTIF & Perfect Order KPI Calculator to calculate service performance from order-level results.
Comments 1