On time
Delivered by the agreed customer promise date and time, using the same tolerance window and event timestamp in every period.
A perfect order is one order that meets every rule in scope: it is on time, complete, damage free, and supported by accurate documentation. When order-level outcomes are available, calculate perfect orders ÷ total orders × 100. For a KPI scorecard, the four-component Perfect Order Index is on-time rate × complete rate × damage-free rate × documentation-accuracy rate × 100.
All eligible orders in the reporting period.
Orders that passed every condition for that same order.
Orders delivered within your promised-date rule.
Orders supplied with every required item and quantity.
Orders accepted in the condition your policy requires.
Accurate, complete, on-time invoices and shipping documents.
The result will show the rate this component needs to reach the target.
Set your own comparable internal target; this is not a universal benchmark.
Check the highlighted input.
—
Method 1 — measured perfect order rate: Actual perfect orders ÷ total eligible orders × 100
Method 2 — four-component Perfect Order Index: On-time rate × complete rate × damage-free rate × documentation-accuracy rate × 100
Method 1 is the most defensible result when transaction data can identify whether every criterion passed for the same order. Method 2 follows the component-rate approach used by APQC. It multiplies marginal rates, so it is best labeled an index or estimate when the data does not establish how the component successes overlap order by order.
Do not infer intersections from separate counts. Knowing that 960 orders were on time, 980 were complete, and 990 were damage free does not tell you how many individual orders passed all three tests. Multiplying those rates produces an index, not 931 observed perfect orders.
Delivered by the agreed customer promise date and time, using the same tolerance window and event timestamp in every period.
Every required item and quantity is supplied. Decide whether a split shipment can pass and whether the basis is the whole order or each order line.
The order arrives without unacceptable physical damage and meets configuration, specification, installation, and acceptance rules where applicable.
Invoices, packing slips, bills of lading, labels, and other required documents are accurate, complete, and available on time.
Document the promised-date rule, tolerance window, order-versus-line basis, damage threshold, cancellation treatment, and reporting period. These are company-policy choices unless a customer contract or reporting standard specifies them; consistency matters more than choosing a generous rule.
A warehouse reviews 1,000 eligible orders and finds that 912 of those same orders passed all four criteria.
912 ÷ 1,000 = 0.9120.912 × 100 = 91.2%This is a measured rate: 912 perfect and 88 non-perfect orders.
The scorecard reports 96% on time, 98% complete, 99% damage free, and 97% documentation accurate.
96% = 0.96, 98% = 0.98, 99% = 0.99, 97% = 0.970.96 × 0.98 × 0.99 × 0.97 = 0.9034502490.345024% → 90.35%This is an index estimate unless the underlying records establish the overlap.
Why the answers can differ: separate counts of 960 on-time, 980 complete, and 990 damage-free orders could overlap in many ways. At most 960 orders could pass all three; as few as 930 must pass all three by the inclusion–exclusion lower bound, and adding documentation can reduce the intersection further. Neither the component counts nor their product proves the observed perfect-order count.
A measured result tells you how many actual orders passed every test. A component-rate index summarizes several marginal KPIs but may not equal the observed intersection. Label the method in reports, show the eligible order count, and trend the same definition over time.
The weakest component is a useful investigation starting point, not proof of root cause. Break failures down by customer, facility, carrier, product, promise type, and failure reason before assigning action. Also track the count and severity of failures: one late order and one completely lost order both count as non-perfect, although their business impact differs.
APQC cross-industry median: 88.0%. The live APQC Perfect order performance measure (ID 101741) displayed a median of 88.0% and a total sample size of 13,590 when checked on 14 July 2026. APQC defines this measure as on-time delivery × complete orders × damage-free delivery × accurate documentation × 100.
Publication note: APQC’s live measure page does not show a publication date, so the access/verification date above identifies this benchmark snapshot. Recheck the source before publishing a long-lived target.
Compare like with like. Results vary with industry, order complexity, service promise, geography, customer mix, reporting period, and whether documentation accuracy is included. A cross-industry component index is not directly comparable with an order-level observed rate or a three-component internal KPI.
Use the calculator’s target field to quantify the gap. With actual counts, it shows how many additional orders must pass every condition. With the component index, select one component to see the required rate while holding the others constant. A requirement above 100% means one component cannot close the gap; improve multiple components or revise the target and assumptions.
A perfect order passes every rule in scope for the same order: on time, complete or in full, damage free, and documentation accurate. A failure in any required component makes that order non-perfect.
Perfect order rate (POR) combines the full set of order-level requirements. OTIF covers on-time and in-full delivery. Fill rate measures how much demand was filled, often by units or lines. Order accuracy checks whether the right items and quantities were supplied; it may not cover timing, damage, or documents.
Use the basis specified by your measurement standard and keep it consistent. For an order-level POR, every required line and component must pass before the order passes. A line-level result answers a different question and should be labeled separately.
Yes for the standard four-component APQC Perfect Order Index and the ASCM SCOR definition. A company may publish a three-component internal KPI, but it should disclose that documentation accuracy is excluded.
Monthly reporting is common, with weekly monitoring where order volume supports a stable rate. Use a fixed reporting period, compare similar seasons, and show the order count so readers can judge volatility.
Separate counts can be converted to marginal rates and multiplied only as a Perfect Order Index estimate. They do not prove how many of the same individual orders passed every condition because the overlap is unknown.
Write the policy before measuring. Typically, partial deliveries fail in-full, split shipments pass only if the promise permits them, cancellations are included or excluded by a consistent reason rule, and returns fail when caused by fulfillment damage or error. Apply the same policy in every period.
Yes. All calculations run locally in your browser; values are only added to the URL if you choose Share.
Methodology: The calculator separates observed order-level performance from the component-rate index. It uses unrounded inputs for calculations and rounds displayed rates to two decimals. The target scenario holds all non-selected inputs constant. Definitions set by APQC or ASCM are labeled as standards; tolerance windows, exclusions, and other internal rules are company policy.
Author and review: Starlight Tools editorial staff. Reviewed by the Starlight Tools Supply Chain Analytics Editorial Team for KPI definition, calculation logic, and operations-reporting context. Last updated 14 July 2026.
Authoritative references: APQC Perfect order performance, measure 101741 (four-component index and benchmark; accessed 14 July 2026) and ASCM SCOR RL.1.1 Perfect Customer Order Fulfillment (order-level formula and component definitions; accessed 14 July 2026).