Café Pre-order Collection: Keep Promises and Handover Together

Start with the accepted order and its promise

Use a stable collection case reference linked to the original order. Record the outlet, collection location, service date, timezone, accepted order revision and each item code, description, unit and quantity. Keep protected references to the ordering system instead of copying guest contact details into the shared worksheet.

Write what was actually promised and when it was accepted. Ready by 12:30 is different from a booked handover at 12:30 or a collection window from 12:30 to 13:00. Name the promised event and retain its evidence. A desired time entered by the customer is not an accepted promise until the existing order process confirms it.

Before accepting, the responsible team checks the relevant capacity, service and operating arrangements through its existing process. This record does not establish those conditions or approve a promise. Changes need their own time, authority and communication reference; keep the original promise beside the revised one.

Check readiness against the current order

Use the current accepted revision to check each ordered line at the collection point. Record the item and quantity actually ready, the checking role, time and evidence. Refer to the operation’s existing packaging, identification and release controls; a count on this form does not establish suitability or safety.

Keep readiness separate from collection. A complete order waiting at the pass has not been handed over. If something is missing, substituted or changed, record the exception and refer it through the existing approval and customer-agreement process. Do not quietly change the order quantity to match what happens to be available.

Record notification without assuming receipt

Record what was communicated, through which approved channel, when, by which role and with what message reference. A submitted message, a confirmed send and an acknowledgement are different observations. Use only the state supported by the communication record.

The worksheet holds a protected message reference, not the customer’s address, phone number, collection secret or message contents containing personal information. If notification fails or its outcome is unknown, keep that visible and assign the next action under the existing process. Do not infer that the customer has seen a ready message simply because an order screen changed.

Worked example: PU-024 at Outlet North

In this fictional case, order ORD-024 revision 1 contains two sandwiches, item SW-01, and two bottled drinks, item DR-01. The accepted promise is ready by 12:30 IST on 8 November 2026 at Outlet North’s collection counter. A check records all four ordered units ready at 12:26, and a notification is confirmed sent at 12:27; no acknowledgement is recorded.

The collector arrives at 12:35. The team completes the existing order-and-collector verification, recording its protected check reference, then agrees a partial handover. At 12:38 two sandwiches and one drink are actually handed over. As of the 12:40 review, one drink remains unresolved in this collection case. The table keeps quantities by item rather than treating three units as a complete order.

Make the handover its own event

For each handover, record the actual event time, location, order revision, verification reference, responsible role and quantities by line. Use the existing authorised collection checks without putting secrets into the worksheet. A readiness notification is not evidence that the person at the counter may collect the order.

Record partial collection explicitly, including its agreement reference and the owner of anything remaining. In PU-024 the manually entered case status is Part collected at the 12:40 cutoff. Readiness was complete and a message was sent, but those facts do not remove the outstanding drink.

The later fictional handover of the remaining bottle at 12:45 is a new linked event. Retain the original 12:40 review and its unresolved quantity. After checking both handover records against the accepted lines, the reviewer can record a later fully collected status with its own time and evidence. Do not rewrite the earlier snapshot as if the bottle had already left.

Keep cancellations and corrections distinguishable

An item resolved through an authorised cancellation, substitution or refund process has not thereby been collected. Record that outcome and its reference separately from handover quantities. The responsible system and policy determine what changes are permitted; this form makes no financial decision and posts nothing.

If a handover entry is wrong, retain the original and add the correction, evidence, reviewer and record time. Prevent duplicate event references from counting the same handover twice. Reconcile each order line, including authorised revisions and unresolved quantities, before recording closure.

A collection record can show that a promise, notification or handover needs investigation, but it does not establish why a guest arrived later, why an item remained, or whether the café met every service expectation. Keep those questions separate from the event history.

Where the distinction comes from

Shopify’s pickup guidance distinguishes an order marked ready for pickup, with its notification, from an order marked picked up after collection. It also describes location-specific collection instructions and an expected processing time. Those general distinctions inform this original record. Shopify’s plans, screens, inventory transfers and automated behaviours are not applied to other systems, and no Keystonne feature is implied.