Purchase Order Promise-Date Reliability

A supplier confirms that goods will arrive on a particular date, and procurement builds production or customer plans around that commitment. Purchase order promise-date reliability checks whether the supplier's confirmed dates remain credible, using a defined comparison with actual receipts or documented revisions.

Define the promise carefully, since the date requested by the buyer may differ from the date accepted by the supplier, so use the supplier-confirmed date for this measure and report request-date performance separately. Capture the first confirmed date, because if it is overwritten by a newer promise the supplier can appear perfectly reliable after repeatedly pushing delivery back.

Choose a comparison rule, since on-time-or-early and within a narrow delivery window are different and early arrivals can be costly when storage or site readiness is constrained. Specify whether time means dispatch or receipt, because a promised ship date is not a promised arrival date and freight transit can be outside the supplier's control under some terms.

Use a unit of count, since a purchase order with many lines and partial deliveries can be measured by line, schedule, quantity or whole order and the counts should be kept aligned. Handle partial receipts: if 90% arrives on the promised date and 10% later, a whole-order pass rule may fail while a quantity-weighted view tells a different story.

Set a reasonable tolerance and state it rather than silently applying one, because a one-day grace period may suit some supplies but not a just-in-time component. Use receipt evidence, since goods received in the system may be posted after the physical arrival, so check timestamps before blaming a supplier for a posting delay.

Separate buyer changes, because a buyer-requested postponement should not automatically count as the supplier missing its original commitment, so preserve the change history and reason. Track supplier revisions too, since later confirmed dates can help current planning even when the initial promise was missed, and report current-promise accuracy separately from original-promise stability.

Treat unconfirmed orders as a confirmation gap, not a date-reliability success or failure under this denominator. Check holiday and time zone, since a cross-border shipment can cross a calendar boundary, and specify the receiving site's calendar and agreed terms.

Distinguish delivery performance, because APQC measures supplier orders received by the original buyer-requested date, which is valuable but not identical to keeping the supplier's own first confirmed promise. Check quality holds, as goods may arrive on time but fail inspection, so date reliability and acceptable-goods delivery should be shown separately, and measure dispersion, since a single average days-late figure can conceal many small misses and one severe disruption.

Watch early shipping, which may occupy scarce storage or trigger costs, track dependent production by estimating the effect of a missed component date separately from the punctuality metric, and avoid gaming, because suppliers may promise deliberately late dates to score well, so pair the metric with lead time and performance against the buyer's requested date. Review order changes (a change to quantity or specification may create a new agreed promise, so label the baseline), consider carrier responsibility under contract handoff terms, reconcile duplicate receipts so one delivery cannot create several on-time wins, segment standard replenishment from custom manufacturing, save supplier confirmations and delivery records as evidence, and use reliability to plan buffers, remembering that no percentage guarantees an individual delivery and critical items deserve direct review.