Small-business outsourcing research

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.

How often are same-day pickup orders ready before the promised time?

Research question and scope

This protocol asks how often a same-day pickup order is fully staged and checked before the pickup time the customer was given. The unit is one pickup order, not one customer and not one item. The study measures the share ready before the promised time, the share ready late, and the orders that were never completed that day. It does not judge whether the customer arrived on time.

Set the scope to one shop, one pickup point, and one promise rule. Record the promise window, the staging area, and the date the rule took effect. If the shop changes its order system during the study, keep the original rule for orders already promised and analyze later orders separately. A new system can change the record without changing the work at the counter.

Define the population as every order promised for same-day pickup during the window, including orders that were cancelled or never collected. State any exclusion, such as an in-stock item handed over immediately at the counter, and apply it to every order. Test the definition on ten completed orders before collection begins. The reader should be able to rebuild the population from the order list.

Definitions that make the measure reproducible

Define ready as every item on the order checked, staged at the pickup point, and marked with the order number. Define the promised time as the time the shop told the customer, in writing or by a recorded message. A target printed only in an internal system is not a promise. Record both the promise time and the ready time.

Define early and late as separate outcomes, because an order staged long before pickup can hold limited counter space. Treat a customer-requested reschedule as a new promise with its own time. Record the time zone and whether the promise crosses noon or midnight. A definition that counts a customer delay as a shop delay will distort the result.

Evidence standard and data dictionary

For each order, capture the order identifier, customer, item count, promise time, staging time, ready check time, checker, and pickup time. Add whether the ready notice was sent and whether the order was complete at pickup. Keep the order record and the ready notice linked. Record any item that was missing or substituted at the check.

Capture the reason for a late order when it is documented: a missing item, a supplier delay, an equipment fault, or a staffing gap at the counter. 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 same-day order in the window rather than a sample, because the promise applies to each order. If the shop runs several pickup points or item types, collect each separately and record the group. A combined rate can hide one item type that is never ready on time. Report the number of orders and the value behind every percentage.

Draw times from the order system and the ready check, not from a spreadsheet maintained after the fact. If either record is incomplete, say so and reduce the claim. Record the export date, the filters, and any order that could not be matched to a ready check. A missing check is itself a finding about the routine.

Analysis and reporting

Report the share ready before the promise, the share ready late, and the share never completed that day. Show the median and range of minutes early or late. Present the results by item type, day of week, and staff shift. Use the same denominator for every rate.

Separate an order that was late because an item was missing from one that was ready but never marked. A supply gap is a different finding from a counter that forgot to stage. Report both because they lead to different fixes. A shop may accept a supplier delay but should not accept an order that sits ready and unlabelled.

Limits of the evidence

The order record can show when the order was marked ready, but it cannot prove the mark was accurate. A staged order is not a verified order. The protocol also cannot capture an order promised verbally and never entered in the system. State that limitation before presenting the rate.

A small shop may have too few same-day orders to support a stable trend. Describe the order count and the item mix instead of ranking staff. Do not compare a shop with a two-hour promise with one that promises by closing time. Report the promise rule and the staging space beside the rate.

What to change

Give the result to the owner and the counter lead and ask them to choose one observable change. The change might be a ready check before the notice, a fixed staging shelf, a named order owner, or a late-order message sent before the promise passes. 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 ready rate rises but pickup no-shows also rise, the shop may be staging orders earlier than customers expect. If both fall but cancellations shrink, the team may be promising fewer orders than it could serve. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Sources

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