WEIMI INSIGHTS / PICKUP OPERATIONS
A practical collection-window policy for food retailers using chilled lockers after hours.
SET THE WINDOW
State when collection starts and ends.
CONTROL ACCESS
Define what an expired code should do.
CLOSE THE LOOP
Assign the food decision to a trained person.
A locker holds an order; it does not decide how long that order remains suitable for sale or who should contact the customer.
01 / BUYER NOTES
A refrigerated pickup locker can extend collection beyond counter hours, but “collect anytime” is rarely a complete policy. Decide how long each product may remain in the locker under your food-safety procedures, then offer a collection window that your staff can actually support. Different products may need different windows.
Show the deadline before payment and repeat it in the collection message. Explain how customers should report a delay, whether rescheduling is possible, and what happens after the deadline. Avoid hiding these details in a message that arrives only once the order is packed.
02 / BUYER NOTES
A reminder and an access code serve different purposes. The reminder tells the customer that time is running out; the code authorises a specific compartment to open. Ask your supplier whether expiry, reminder timing and order status can be configured separately, and which functions require another ordering system.
Test a late arrival, an incorrect code and a customer who requests a new collection time. Extending a code should not silently extend the food holding period. If staff approve an extension, record who approved it and check the product against the operating procedure first.
03 / BUYER NOTES
Start the next shift with a list of uncollected orders, their loading times and any temperature exceptions. A compartment that appears occupied is not proof that the correct order is still inside. Staff should reconcile the order record with the physical contents before releasing that space for a new customer.
Define separate actions for a customer who is still coming, an order cancelled under your terms and food that must be removed. Do not automatically relist returned or uncollected food. Its disposition depends on traceability, condition, time and temperature, and applicable local requirements.
04 / BUYER NOTES
Power loss, a stuck door or an unreadable message can make a missed collection the operator’s responsibility rather than the customer’s. Give support staff enough information to distinguish these cases. They need the order reference, compartment, timeline and system events—not a customer’s full payment-card details.
Agree who may issue a refund or replacement, how the decision reaches the ordering system and when access must be cancelled. A documented exception process helps the team resolve a real problem without leaving a valid code attached to a compartment that has already been reassigned.
Retail team: Check the order, holding limit and assigned compartment.
System: Show the correct collection window and contact route.
Retail team: Review late requests and product condition.
System: Apply the agreed code-expiry rule and flag the order.
Retail team: Remove or resolve the order before reassignment.
System: Preserve the audit trail and cancel obsolete access.
PRACTICAL ANSWERS
Only if your product-specific procedure allows it and staff approve the order. Refrigeration alone does not establish a safe holding period.
That depends on the sales terms and integration. Agree the policy first, then test whether refunds and order status stay consistent across the connected systems.
Treat this as an access incident. Check the event history and physical compartment, then arrange a supported collection, replacement or refund as appropriate.
YOUR NEXT STEP
Share your product range, collection hours and ordering workflow when discussing a locker project. Start with the locker versus dispensing comparison if you are still choosing the format.
Explore equipment →Discuss your requirements →