Failed delivery / reattempt gate
Control the failed delivery before it becomes a dispute.
Use this when receiver is unavailable, refuses, OTP fails, shop closes, gate blocks entry, or the address cannot receive goods.
1
Failed
8
Checks
0
Plans
Current status
Plan failed delivery reattempt only. No refund, penalty, payout, ledger, or settlement.
1. Failed handover queue
Only failed receiver proof enters this gate.
2. Custody subject
Carrier, goods, receiver failure, and condition.
CRH-DEMO-FAILED-ORDER
Verified Mohallah Rider
Ali Sabzi Wala / local shop to Mohallah family doorstep
Receiver issue
Receiver did not answer. OTP not completed. Rider stayed at safe lane checkpoint.
Packages
4 bags / packets
Goods condition
Goods still with carrier. Fresh items need quick second attempt.
Destination
Customer lane / safe checkpoint, exact private address hidden
3. Reattempt decision
Second attempt, hold, return, or escalate.
4. Reattempt record
Plan safe next movement.
5. Reattempt checks
Confirm no finance mutation.
Runtime locks
Failed delivery is not refund or penalty.
Failed delivery / reattempt gate controls the next movement plan only.
It must not mark delivery complete, customer accepted, GRN created, inventory received, or seller settled.
Refund, penalty, rider earning, payout, ledger, settlement, and payment changes remain blocked.
Fresh, medicine, cold-chain, fragile, and high-value goods must carry condition risk into the next review.
Repeated failure must go to FAEDA Team escalation, not silent cancellation.
The next locked step after reattempt planning is a new controlled attempt or exception review, not settlement.
Recent plans
Local failed-delivery packets.
Next locked step
Damage / Shortage / Dispute Gate.
Variance, damage, refusal, or repeated failed attempt needs dispute handling before completion or settlement.