Foodpanda Order Cancellation Log for Restaurants: Track Cause, Waste and Settlement
A copy-ready log that connects each cancelled marketplace order to acceptance timing, kitchen loss, support evidence and the eventual settlement line.
Last verified: 2026-08-30
A Foodpanda order cancellation log helps a restaurant answer four different questions: what happened to the customer order, whether the kitchen had started, what stock or labour was lost, and how the event appeared in the marketplace settlement. Treating all cancellations as one number hides whether the cause was availability, delayed acceptance, customer change, rider capacity, address trouble, restaurant rejection or a platform/support decision.
The public foodpanda Bangladesh customer terms distinguish cancellation before and after vendor acceptance, but a partner's financial treatment comes from the current agreement, Partner Portal and support decision. Therefore this template records facts and evidence first. It never assumes a reimbursement or fee.
Copy-ready cancellation log
Capture timestamps from the system rather than memory. If a field is unknown, mark it unknown; do not invent a time that makes the restaurant look faster. Save the order status and relevant support screen before it disappears from the active queue.
Do not put customer phone numbers or addresses in an unrestricted spreadsheet. Use the order ID for traceability and limit personal data to the system that needs it.
| Field group | Fields to capture |
|---|---|
| Order | Marketplace order ID, restaurant order ID, branch, date and channel |
| Timing | Received, accepted, kitchen-start, ready, cancellation and rider-arrival times |
| Decision | Who cancelled, displayed reason, restaurant reason and status screenshot |
| Food impact | Items started, reusable stock, discarded quantity, cost estimate and wastage entry |
| Customer/support | Customer contact outcome, support case ID, messages and attachments |
| Settlement | Expected treatment, statement line, difference, dispute status and resolution |
| Prevention | Root cause, owner, action, due date and repeat check |
Separate cancellation stage from cancellation cause
Stage describes where the order was: not accepted, accepted but not started, preparing, ready, handed over or disputed after delivery. Cause describes why it stopped. Keeping both fields prevents an early customer cancellation from being grouped with a restaurant stock-out after cooking began.
Use a controlled cause list with an optional note: item unavailable, restaurant closed, duplicate order, customer request, address/contact issue, delayed preparation, rider unavailable/delayed, payment issue, suspected fraud, platform action or other. The displayed platform reason and the restaurant's root-cause finding should be separate.
Sources for this section: foodpanda Bangladesh customer terms and cancellation policy
Record acceptance and preparation evidence
Public customer terms say cancellation rights differ depending on whether the vendor has accepted the order. For the restaurant, acceptance time is therefore a key factual field, but it does not by itself decide partner compensation. Also record when the KOT reached the kitchen and when preparation actually started.
If an item was already made, link the cancellation to a wastage or recovery record. Record cost using the restaurant's approved recipe or inventory method, not menu selling price. If stock can safely return to inventory under the restaurant's food-safety process, record the quantity and approver rather than counting the full item as waste.
Sources for this section: foodpanda Bangladesh customer terms and cancellation policy
Build a complete support case pack
Use the current Partner Portal route and deadline shown for the case. The public sign-up page does not publish every partner dispute rule, and contract terms can change. Store the exact submission and response instead of relying on a manager's recollection.
One person may prepare the case, but a second person should review the amount and evidence for material disputes. Close the case only when the settlement or final decision is posted.
- Marketplace and restaurant order IDs
- Status timeline and screenshots
- Accepted and preparation timestamps
- Customer or rider communication available through approved channels
- Item availability and menu-status evidence
- KOT, ready-time and handover evidence
- Claimed amount and calculation basis
- Support case number, submission date and latest response
Sources for this section: foodpanda Bangladesh partner portal
Reconcile the cancellation to the payout
Do not net cancellations invisibly into total marketplace revenue. Match each material cancellation or grouped statement line to the payout reconciliation. If the platform statement groups several orders, preserve the supporting export or case mapping.
Operational wastage and settlement difference are separate. A restaurant may lose ingredients even when a statement credit appears, or may have no food loss but still need to explain a payment adjustment.
| Reconciliation line | Entry |
|---|---|
| Order gross | Original marketplace order value |
| Customer outcome | Cancelled, refunded, partially resolved or other displayed outcome |
| Restaurant expectation | Amount expected under current agreement/support case |
| Statement treatment | Actual credit, deduction or no line on settlement |
| Difference | Expected minus statement treatment |
| Resolution | Accepted, disputed, corrected or written off with approval |
Review cancellation rates without a fake benchmark
Calculate cancellation rate as cancelled orders divided by received marketplace orders for the same branch and period. Also show post-acceptance cancellation rate and prepared-order waste rate. Do not compare branches unless opening hours, order volume and menu availability are comparable.
There is no universal good rate in this article. Build a baseline from the restaurant's own clean weeks, then investigate a material change. A low rate achieved by rejecting difficult orders quickly is not automatically better than a slightly higher rate with stronger acceptance and revenue.
Fix the process behind repeat causes
Assign one corrective action per confirmed root cause and check whether the pattern falls. Avoid solving every cancellation with staff warnings. Stock data, menu status, device alerts and unrealistic preparation times are management-system issues.
| Pattern | Control to test |
|---|---|
| Item unavailable | Menu availability, stock threshold and sold-out update ownership |
| Slow acceptance | Device alerts, staffing, opening-hours status and backup owner |
| Late preparation | Prep-time settings, KOT routing, station load and menu complexity |
| Rider wait | Ready-time accuracy, pickup area and handover confirmation |
| Address/contact | Order-detail review and approved support escalation |
| Statement mismatch | Evidence pack quality, case tracking and payout reconciliation |
Weekly cancellation review agenda
Keep the meeting focused on preventable patterns and unresolved money. A cancellation log is useful only when the restaurant closes cases, corrects menu availability and changes the workflow that produced repeat loss.
- Orders and value cancelled by stage and cause
- Prepared items and recorded wastage cost
- Open support cases and oldest unresolved item
- Statement differences awaiting the next payout
- Repeat items, hours, stations and branches
- Actions completed and whether the pattern improved
How we calculated and verified this
The log is an operator control template, not a reproduction of a private foodpanda partner contract. Public customer terms are cited only to show that acceptance timing can affect the customer cancellation and refund path. A restaurant must use its current Partner Portal, support case and signed agreement for the actual commercial outcome.
No commission, cancellation fee, reimbursement percentage, dispute deadline or payout promise is stated. The template separates operational loss, customer outcome and settlement outcome because those three amounts can differ.
A cancellation has an order story, a kitchen story and a settlement story. Logging all three gives the restaurant evidence for support, a clean payout reconciliation and a fair view of operational waste.
Start with order ID, acceptance time, preparation stage, cause and statement outcome. Use the current partner agreement and portal for commercial rules, then use weekly patterns to prevent the next cancellation.
Related guides
- Foodpanda Payout Reconciliation for Restaurants
- Foodpanda Commission Rate in Bangladesh
- Foodpanda Menu Optimisation
- Manage Foodpanda and Pathao Orders
See this workflow in Rosuii: Track marketplace orders, order status and restaurant reports in Rosuii
Sources checked
Last updated:
Frequently asked questions
What should a Foodpanda cancellation log include?
Does cancellation after acceptance guarantee restaurant payment?
Should cancelled food be valued at menu price?
How is restaurant cancellation rate calculated?
How often should cancellations be reviewed?
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
