Restaurant Delivery Order Handover Checklist: Right Bag, Right Rider
A pickup-counter control that prevents wrong-rider and partial-bag handoffs while preserving useful wait and dispute evidence.
Last verified: 2026-08-31
A restaurant delivery order handover checklist creates a clear custody point. The restaurant verifies the platform order, approved rider or pickup process, sealed bag count, drinks and special packages, then records the actual transfer time. The rider should not need to open food packaging to identify the order.
foodpanda's public partner page describes rider pickup after the restaurant prepares the order. The exact identity check, code and screen action can change, so follow the live platform and current partner instructions.
Handover gate
Point to each bag while counting. A label that says two bags is not proof that both crossed the counter.
Do not mark picked up before custody changes. Accurate times distinguish restaurant wait from later delivery events.
| Check | Confirm | Record |
|---|---|---|
| Order | Platform and full order ID | Ticket/label |
| Status | Actually complete and ready | Ready time |
| Package | Seal intact and bag count | 1 of 2, 2 of 2 |
| Extras | Drinks, sauces and separate cold bag | Count |
| Rider | Current platform-approved verification | Reference, not excess personal data |
| Transfer | All packages physically handed over | Pickup time/operator |
| Exception | Delay, refusal, mismatch or damage | Reason/support reference |
Design the pickup area
Separate waiting riders from food preparation and customer traffic. Stage orders by platform and stable order ID with drinks or cold packages visibly linked.
Restrict access so riders cannot self-select from many bags. A named employee should complete the verification and transfer.
Use the live platform verification
Follow the current rider identity, pickup code, scan or status action shown in the partner tool. Do not invent a parallel code in a notebook that bypasses the platform record.
If verification fails or a different rider arrives, hold the order safely and use partner support. Do not disclose customer contact details to resolve identity informally.
Sources for this section: foodpanda Bangladesh partner portal
Record ready, arrival and pickup separately
Avoid guessed timestamps added at day close. Capture the event when it happens or label it as estimated.
| Time | Meaning | Use |
|---|---|---|
| Accepted | Restaurant confirmed order | Start fulfilment |
| Ready | All sealed packages complete | Kitchen performance |
| Rider arrival | Verified rider at pickup point | Rider wait |
| Pickup | Custody transferred | Restaurant handoff complete |
| Exception close | Mismatch/delay resolved | Support evidence |
Handle partial or damaged packages
If a seal breaks, a drink leaks or one bag is missing, stop the handoff. Repack under the restaurant procedure, replace the seal and update bag count before transfer.
If the rider accepts only part of an order or leaves before verification, record the event and contact platform support immediately. Preserve the package and camera reference where lawfully available.
Wrong-rider prevention
- Use full order ID rather than a short name
- Keep platforms visually distinct
- One employee controls the shelf
- Count every bag aloud
- Use current platform verification
- Record pickup after transfer
- Escalate mismatches instead of improvising
Exception register
| Code | Exception | Evidence |
|---|---|---|
| RID | Rider verification mismatch | Platform/support reference |
| BAG | Bag missing/damaged | Repack record |
| WAIT-R | Rider waited after arrival | Arrival/ready/pickup times |
| WAIT-K | Order ready before rider | Ready/arrival times |
| REF | Rider refused package | Reason and support |
| WRG | Possible wrong pickup | Order/rider/time/camera reference |
Shift handover
List ready orders not collected, riders waiting, support cases, damaged/repacked orders, device issues and pickup-area exceptions. The next operator should verify physical bags against the list.
Weekly review
Measure wrong/partial handoff events, rider wait after arrival, restaurant wait for riders, seal failures and support cases. Use precise timestamps and sample checks before assigning blame.
How we calculated and verified this
The public partner page supports the prepare-then-rider-pickup sequence. The verification and custody fields are a restaurant-side template, not a claim about Foodpanda's private partner controls.
Use the current platform interface, agreement and support process for rider identity, pickup codes, cancellation and dispute evidence.
A delivery handoff is a custody event, not a bag placed on a shelf. Verify order, rider process, seal and bag count, then record actual transfer.
Use Rosuii for the restaurant-side order reference and the live marketplace tool for platform verification.
Related guides
- Restaurant Delivery Packaging Checklist
- Foodpanda Order Cancellation Log
- Restaurant Shift Handover Checklist
See this workflow in Rosuii: Track delivery orders and marketplace references in Rosuii
Sources checked
Last updated:
Frequently asked questions
What should be checked at rider pickup?
Should riders take bags from an open shelf?
Why record ready and pickup times separately?
What if rider verification fails?
What if a seal is broken before pickup?
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
