Small-business outsourcing research
What share of pickup orders wait more than one day after the ready notice?
A protocol for measuring how many pickup orders remain uncollected more than one day after the customer is told they are ready.

Research question and scope
This protocol asks what share of pickup orders remain uncollected more than one business day after the ready notice is sent. The unit is one pickup order, not one customer and not one item. The study measures the share collected inside the window, the share collected late, and the orders that are never collected. It does not judge whether the customer had a good reason to delay.
Set the scope to one business, one pickup location, and one notice process. Record the ready-notice template, the pickup window, and the storage rule in force. If the policy changes during the window, keep the original rule for orders already ready and analyze later orders separately. A new notification channel can change pickup behavior without changing the underlying demand.
Define the population as every order that received a ready notice during the window, including orders that were later canceled or restocked. State any exclusion, such as a wholesale order collected at a loading dock, and apply it to every order. Test the definition on two weeks of completed pickups before collection begins. The reader should be able to rebuild the population from the order system and the message log.
Definitions that make the measure reproducible
Define the ready notice as the first message that tells the customer the specific order is ready and states where and when to collect it. A general marketing message is not a ready notice. Define the clock start as the send time of that notice, not the time the order was packed. Record both times when the system supports it.
Define collection as the time the order is released to the customer or an authorized proxy in the order record. A customer who says they will come is not a collection. Define the pickup window from the written policy and record whether it was stated in the notice. Use business days and state the time zone so the delay is reproducible.
Record whether the order was extended, canceled, restocked, donated, or disposed. Each outcome should have a date and an approver. A late collection that follows an approved extension is different from one that follows no contact. Keep those events in the same order record so the analysis can separate them.
Evidence standard and data dictionary
For each order, capture the order identifier, the customer segment, the ready time, the notice time, the channel, the pickup window, the collection time, and the outcome. Add the number of reminders, the last contact date, and the person who approved any extension. Record the storage fee or refund, if any. Keep the notice text linked to the order.
Capture the reason for a delay when it is documented: a customer travel conflict, a missing notice, a wrong phone number, a payment issue, or a store closure. Do not infer a reason from an empty field. If the reason is unknown, mark it unknown and report the count. A guessed reason hides the stage that actually needs repair.
Record whether the customer contacted the business before the window closed. A customer who asks for more time is a different finding from one who never responds. Note the date of the request and the reply. These details matter because the business may be able to fix a contact problem before the order ages.
Sampling and collection
Collect every order that received a ready notice in the window rather than a sample, because the pickup promise applies to each one. If the business has several locations or product lines, collect each separately and record the group. A combined rate can hide one location with a persistent notification problem. Report the number of orders and the value behind every percentage.
Draw times from the order system and the message log, not from a spreadsheet maintained after the fact. If the message log is incomplete, say so and reduce the claim. Record the export date, the filters, and any order that could not be matched to a notice. A missing notice record is itself a finding about the process.
Ask the store lead to identify weeks when a holiday, a sale, or a weather event changed pickup volume. Those weeks can produce delays that have nothing to do with the routine. Record the event and analyze those orders separately. The reader should be able to tell whether the rate reflects the rule or the calendar.
Analysis and reporting
Report the share collected within one business day, the share collected later, and the share never collected. Show the median and range of days from notice to collection. Present the results by location, product type, and notice channel. Use the same denominator for every rate.
Separate orders that waited because the customer did not come from orders that waited because the notice never arrived. A bounced message is a different finding from a customer who chose to delay. Report both because they lead to different fixes. A business may accept a customer delay but should not accept an undelivered notice without a documented fallback.
Inspect the oldest uncollected orders and describe which stage dominated without naming the customer. A wrong phone number, a missing reminder, and a storage decision each point to a different repair. Compare the delay with the pickup window and the reminder schedule. Report orders with incomplete timestamps rather than dropping them from the denominator.
Limits of the evidence
The order record can show when an order was released, but it cannot show why the customer delayed. A customer may have been traveling, ill, or simply forgot. The protocol also cannot capture a conversation at the counter that was never logged. State that limitation before presenting the rate.
A small business may have too few pickup orders to support a stable trend. Describe the order count and the product mix instead of ranking staff. If one person sends every notice, the result may reflect that person's availability more than the process design. Do not use the rate as a performance score without the context of seasonality and store hours.
Do not compare a business that holds orders for two weeks with one that restocks after two days. The two operate different storage rules even when the late-pickup rate looks similar. Report the window and the storage rule beside the rate. A target that can be met by canceling every uncollected order is not a good target.
What to change
Give the result to the owner and the store lead and ask them to choose one observable change. The change might be a required phone check at intake, a reminder at the midpoint, a clearer pickup window, or a weekly uncollected-order review. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions after the change.
If the on-time rate rises but the never-collected rate also rises, the business may be sending more notices without making pickup easier. If both fall but cancellations rise, the team may be closing orders before the customer has a fair chance. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.
Ask the store lead which order was hardest to close and why. A concrete answer often reveals a wrong number, a customer who moved, or a product that was too large to transport. Use that answer to improve the intake rather than to blame the customer. The next measurement should test whether the same delay shrank.
Sources
- U.S. Small Business Administration, marketing and sales, U.S. Small Business Administration; checked 2026-11-17
- Federal Trade Commission, mail, internet, or telephone order merchandise rule, Federal Trade Commission; checked 2026-11-17
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-17
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-17
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 customer referrals are rewarded within the stated window?
A protocol for measuring how many qualifying customer referrals receive their reward inside the window the business promised.
How often do failed subscription payments recover without manual contact?
A protocol for measuring how many failed subscription payments recover through the retry schedule before a person has to intervene.
What share of lost-package claims close inside the carrier claim window?
A protocol for measuring how many lost-package claims reach a final carrier decision before the claim window closes.