Small-business outsourcing research
What share of open purchase orders age past the promised delivery week?
A protocol for measuring how many open purchase orders remain unreceived past the delivery week the supplier promised.

Research question and scope
This protocol asks what share of open purchase orders remain unreceived past the delivery week the supplier promised. The unit is one purchase order line, not one order and not one supplier. The study measures the share received inside the promised week, the share still open after it, and the lines that were cancelled without a delivery. It does not judge whether the supplier gave a realistic promise.
Set the scope to one shop, one purchasing process, and one promise rule. Record how the promised week is captured, the receiving method, and the date the rule took effect. If the shop changes its order system during the study, keep the original promise for lines already placed and analyze later lines separately. A new system can change the record without changing the supplier schedule.
Define the population as every purchase order line placed during the window, including lines that were cancelled, split, or backordered. State any exclusion, such as a service contract with no delivery date, and apply it to every line. Test the definition on ten closed lines before collection begins. The reader should be able to rebuild the population from the order list and the receiving notes.
Definitions that make the measure reproducible
Define the promised week as the week the supplier confirmed for the specific line, not the week the shop hoped for. Record whether the promise came in writing and on what date. Define the clock start as the order date and the clock stop as the receiving date on the first complete delivery. A line received in parts is not closed until the final part arrives.
Define age as the number of days between the end of the promised week and the receiving date or the review date. Keep the age in whole days and record the date of the calculation. Treat a line cancelled before delivery as a separate outcome with its own date. A definition that measures from the order date alone will mix fast and slow promises.
Evidence standard and data dictionary
For each line, capture the order number, supplier, item, quantity, order date, promised week, confirmation date, receiving date, quantity received, and current status. Add the buyer, the receiver, and any backorder note. Keep the purchase order and the receiving note linked to the entry. Record any change to the promised week and the message that stated it.
Capture the reason for an aged line when it is documented: a supplier backorder, a missed shipment, a quality hold, or a shop request to delay. Do not infer a reason from an empty field. Mark unknown reasons as unknown and report the count. A guessed reason hides the step that actually needs repair.
Sampling and collection
Collect every purchase order line in the window rather than a sample, because the promise applies to each line. If the shop runs several departments or supplier groups, collect each separately and record the group. A combined rate can hide one department that never confirms a week. Report the number of lines and the value behind every percentage.
Draw data from the order system and the receiving record, not from a spreadsheet kept after the fact. If either record is incomplete, say so and reduce the claim. Record the export date, the filters, and any line that could not be matched to a receiving note. A missing receiving note is itself a finding about the routine.
Analysis and reporting
Report the share received inside the promised week, the share still open after it, and the share cancelled. Show the median and range of days past the promised week for the open lines. Present the results by supplier, department, and order value. Use the same denominator for every rate.
Separate a line that aged because the supplier missed a shipment from one that aged because the shop never confirmed a week. A supplier miss is a different finding from an unconfirmed promise. Report both because they lead to different fixes. A shop may accept a supplier backorder but should not accept an order with no promise at all.
Limits of the evidence
The order and receiving records can show when goods arrived, but they cannot show whether they arrived when the shop needed them. A delivery inside the promised week can still be too late for a customer. The protocol also cannot capture a purchase made by phone and never entered in the system. State that limitation before presenting the rate.
A small shop may have too few lines to support a stable trend. Describe the line count and the supplier mix instead of ranking buyers. Do not compare a shop that orders daily with one that orders monthly. Report the promise rule and the review cadence beside the rate.
What to change
Give the result to the owner and the purchasing lead and ask them to choose one observable change. The change might be a required written promise at order time, a weekly aging list, a named owner per supplier, or a follow-up date inside the promised week. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions.
If the on-time rate rises but cancelled lines also rise, the shop may be closing orders instead of receiving them. If both fall but backorders grow, the team may be promising weeks it cannot meet. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.
Sources
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-20
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-20
- Internal Revenue Service, Publication 583, starting a business and keeping records, Internal Revenue Service; checked 2026-11-20
- U.S. Small Business Administration, marketing and sales, U.S. Small Business Administration; checked 2026-11-20
Frequently asked questions
Does a favorable sample prove the routine caused the result?
No. The design is observational and supports a bounded operating decision, not a universal causal claim.
What should an owner review first?
Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.
Related research
What share of supplier invoices match the purchase order and receipt on first check?
A protocol for measuring how many supplier invoices agree with the purchase order and the receiving record on the first check.
How long do customer returns take to reach a refund or exchange decision?
A protocol for measuring the wait between a customer return and a recorded refund, exchange, or store credit decision.
How often are same-day pickup orders ready before the promised time?
A protocol for measuring how often an order is staged and checked before the pickup time the customer was given.