Without a standard response to lost parcels, customs holds or bad addresses, support improvises and the same issue is handled differently each time. Writing an exception card with type, first action, required evidence and escalation condition is SOP work the operations team can own.
The card needs a trace column: when detected, which rule was applied, whether it escalated and what happened. Refunds and money movements always pass a human gate and are never auto-released; customer wording is reviewed by people, and this site makes no compliance or compensation judgement.
This article makes no compensation decision and does not score a team by one exception spike; it only requires that similar cases follow one traceable path.