How would you prevent wrong items in deliveries?

Behavioral / Product-Process Scenario

Imagine you are on a food delivery platform. Some customers get the wrong items—the restaurant packed the order incorrectly, the courier grabbed the wrong bag, labels were missing, and so on.

Prompt

Explain how you would drive the largest possible reduction in wrong-order incidents. Address:

• How you would identify root causes across restaurant, courier, and app flow
• Which process and/or technical changes you would put in place
• How you would track success and handle trade-offs such as pickup time, cost, and merchant friction
• How you would deploy changes safely Overview: The question tests systems thinking, root-cause analysis, metrics-driven decisions, and cross-functional leadership within operational product-process settings. Solution

1) Structure the answer (demonstrates leadership)

Use a clear structure:

1. Define the problem and metric
2. Find root causes using data plus qualitative input
3. Generate mitigations across process, product, and engineering
4. Prioritize by impact versus effort and stakeholder friction
5. Pilot, measure, and iterate

---

2) Define metrics and scope

Primary metric (pick one and define it precisely):

• Wrong-order rate = wrong-item reports divided by completed deliveries
• Or cost rate = refunds plus credits from wrong items divided by GMV Guardrail metrics:
• Pickup time / courier wait time
• Merchant acceptance / churn
• Customer satisfaction (CSAT) and re-order rate
• Fraud rate (false claims) Break metrics down by:
• Merchant, merchant size, and cuisine
• Courier experience tier
• Order complexity (number of items, modifiers)
• Packaging type (sealed versus unsealed)

---

3) Diagnose root causes

Use a mix of:

• Customer support tags (wrong item, missing item, wrong order, tampered seal)
• Courier app events (arrived, picked up, photo, barcode scan)
• Merchant POS/integration signals (order acknowledged, printed, packed) Build a simple attribution taxonomy:
• Merchant packing error (wrong or missing items)
• Courier pickup mix-up (picked the wrong bag)
• Handoff labeling issue (missing label, unreadable label)
• Customer misreport / fraud Then use Pareto analysis to find the top contributors—for example, the top 5% of merchants may cause 40% of incidents.

---

4) Intervention ideas (process + product)

4.1 Low-cost process controls (quickest wins)

• Standardized packing checklist in the merchant tablet or POS, especially for modifiers.
• Prominent order label showing customer name, order ID, and item count.
• Sealed packaging requirement plus guidance on seal integrity.

4.2 Pickup verification (the “extra check” mechanism, applied thoughtfully)

Goal: verify without creating too much friction.

• Scan-based verification: the courier scans a barcode or QR code on the bag label.
  • The app checks that it matches the order ID.
  • This works best when the platform prints the labels or supplies the QR code.
• If scanning is not feasible, use photo confirmation at pickup with the bag label visible for high-risk merchants or orders.
• Two-person confirmation at the merchant for high-incident locations, as an operational playbook rather than everywhere. Trade-off: it adds pickup time. Mitigation: enforce it only on high-risk segments based on merchant or order score.

4.3 Reduce merchant packing errors

• UI improvements in the merchant app:
  • Highlight modifiers such as “no onions”
  • Group items by station, such as hot or cold
  • Add a “mark item packed” flow for complex orders
• For integrated merchants, send structured item and modifier data and make sure printer formatting is clear.

4.4 Courier-side improvements

• Improve pickup UX by showing the expected bag count and store pickup notes.
• Provide training and nudges for new couriers, plus coaching for repeat offenders.

4.5 Fraud/false-claim controls (handle carefully)

• Require photo evidence for certain claim types.
• Use anomaly detection to flag repeated claim patterns, while avoiding penalties for legitimate users.

---

5) Prioritization and rollout

Prioritize using Impact × Confidence / Effort.

• Start with the merchants that have the most incidents, using a targeted rollout.
• A/B test verification flows—scan versus photo versus none—with guardrails on pickup time.
• Roll out gradually from 1 city to 10 cities with monitoring.

---

6) Measurement plan

Success means:

• Wrong-order rate falls overall and in targeted segments
• Refund cost falls
• No meaningful regression in pickup time or courier churn
• Merchant satisfaction remains acceptable Also watch for substitution effects:
• Wrong-item reports may decline while missing-item reports rise, since the packing checklist partially helps both.

---

7) Close with stakeholder alignment

Emphasize that this is cross-functional:

• Merchant ops for training and compliance
• Courier ops for workflow
• Product/eng for labeling, scanning, and telemetry
• Support for taxonomy and the feedback loop A strong interview answer explicitly balances customer trust, operational friction, and scalability of the solution.