Complaint Handling for Delivery Issues
A useful complaint process resolves the customer’s immediate problem, protects staff from improvised promises and produces evidence that can improve delivery operations.
A useful complaint process resolves the customer’s immediate problem, protects staff from improvised promises and produces evidence that can improve delivery operations.
Start with the outcome, not a defensive explanation
Acknowledge what the customer says happened, confirm the order and establish what outcome they need now. Do not begin by blaming a driver, marketplace or busy kitchen. The customer should not have to understand the supplier chain before the business takes ownership of the next step.
Classify the problem accurately
| Complaint | What to verify | Typical operational owner |
|---|---|---|
| Late delivery | Accepted time, promised window, ready time, dispatch and arrival | Kitchen and dispatch |
| Cold or damaged food | Packing time, waiting time, bag use, journey and handover | Packing and delivery |
| Missing or wrong item | Order record, modifiers, kitchen ticket and packing check | Kitchen and pass |
| No delivery | Address, contact attempts, tracking and proof of handover | Dispatch |
| Allergen concern | Recipe data, order notes, preparation and handover; escalate immediately | Named food-safety lead |
Use calm, specific language
Helpful language is factual: “I can see the order was dispatched at 19:42 and arrived after the promised window. I am checking whether we can remake it safely or process a refund.” Avoid scripted phrases that deny the experience, such as “our system says delivered”, when the evidence is incomplete.
Match the remedy to the whole failure
- Replace only the affected item when the rest of the order remains useful.
- Offer a full remake only when the customer wants it and the revised time is realistic.
- Use a refund where the service cannot be recovered credibly.
- Do not substitute a future voucher for a remedy that is due now unless the customer freely chooses it.
- For marketplace orders, explain which part the restaurant can complete and which part requires platform processing.
Set authority before the shift
Give front-line staff clear limits for small partial refunds or replacements, with an escalation path for larger or safety-related cases. Record who approved the remedy and why. This reduces inconsistent treatment without forcing every complaint through the owner.
Close the loop
After the immediate issue is resolved, tag the root cause separately from the customer’s wording. “Cold food” may trace back to excessive kitchen-to-dispatch waiting, an oversized route group or a failed insulated bag. Review repeated causes by shift and zone, not only the total complaint count.
Complaint checklist
- Confirm the order and the customer’s preferred outcome.
- Check the order timeline and relevant evidence.
- Choose a lawful and proportionate remedy.
- Explain the next action and expected processing route.
- Record the root cause, remedy and owner.
- Review repeat failures in the weekly operations meeting.
Escalate safety and allergen complaints immediately
Reports involving a suspected allergen error, contamination, injury, threatening behaviour or unsafe delivery condition require a separate escalation route. Front-line staff should preserve the order record, avoid making unsupported medical or legal statements and pass the case to the named responsible person. A replacement meal is not an adequate automatic response to a suspected allergen failure.
Coordinate direct and marketplace records
For a marketplace order, the customer may contact both the platform and the restaurant. Staff should check whether a refund, credit or redelivery has already been authorised before issuing another remedy. Record the platform case reference, the restaurant action and the final financial result separately. This prevents duplicate compensation and makes later reconciliation possible.
Review fairness and consistency
Use the same decision principles across channels and customers. A repeat customer may deserve recognition, but basic remedies should not depend on customer lifetime value, social-media pressure or which employee answered the phone. Sample resolved cases monthly to check whether similar failures receive reasonably consistent outcomes.
| Case type | Immediate owner | Do not do |
|---|---|---|
| Late delivery | Shift lead or customer-support owner | Promise a refund before checking the route and platform process |
| Missing item | Order-resolution owner | Remake the whole order without asking what the customer needs |
| Suspected allergen error | Named food-safety escalation | Treat it as an ordinary quality complaint |
| Driver conduct or safety | Duty manager | Ask the customer and driver to argue directly |
Related guides
- Delivery Management — the main guide for the wider topic.
- Failed Deliveries and Problem Handling — the broader guide that frames this implementation.
- Redelivery and Refund Policies — a closely related operational control to review alongside this page.
- How to Reduce Failed Deliveries — a closely related operational control to review alongside this page.
Sources and recheck points
Guidance checked: 24 July 2026. Recheck official guidance and supplier documentation before changing a live process.
Operational, legal and platform requirements can change. Recheck official guidance and supplier documentation before altering a live service.
Related practical guides
Delivery ManagementDriver Communication SystemsA driver communication system should reduce ambiguity without demanding constant conversation. The best design uses structured status for routine…Read guide →Delivery ManagementDelivery Bags and EquipmentChoose delivery bags and equipment for the routes, food types and handling conditions of the business, then manage them as safety-critical operat…Read guide →Delivery ManagementSetting Up Delivery for the First TimeThe safest first delivery service is deliberately limited. Start with a small menu, a compact area and a controlled number of orders. The purpose…Read guide →
Delivery ManagementRestaurant Delivery Operations GuideDelivery should be designed as an operational channel with its own capacity, costs, risks and recovery procedures. This guide provides a practica…Read guide →
POS and Kitchen SystemsHow to Choose a Receipt PrinterChoose a printer by the job, environment and supported connection—not by speed claims alone. A customer receipt, kitchen ticket, packing slip and…Read guide →
Restaurant AppsApp Administration FeaturesThe administration system is where the business keeps the customer promise truthful. It deserves the same scrutiny as the public app.Read guide →Connect customer ordering with operations and profit
Use the wider guide library to check the menu, kitchen, fulfilment, payment and financial implications of each decision.
Browse all practical guides