Library · Chargebacks · Guide
Refused / RTS vs not-received — claim map
GuideRefused / RTS vs not-received — claim mapBack to article
Return-to-sender and refused delivery vs not-received fight. Filter the claim. Distinct from WISMO and damaged-in-transit. We invent no attempt-count chip.
| Claim | Reality | Do | Do not |
|---|---|---|---|
| Refused / RTS scan means fight as not-received | No. The parcel did not complete a clean delivery | Refund or reship; watch for the return scan | Paste an RTS scan into an NR representment |
| Undeliverable address = fight NR with 3DS | No. No delivered scan. 3DS does not fix a bad address | Fix the address book; refund or reship | Send auth logs into undeliverable |
| Delivered scan + “never got it” is this map | No. That is the WISMO scan checklist | N/A — open wismo-tracking | Skip the delivery scan because attempts failed last week |
| Duty refusal is only this map | Related. Who owes the border sits on DDP vs DDU | N/A — open ddp-vs-ddu for Incoterm; handle RTS cash here | Ignore Incoterm when duties caused the refuse |
| Attempt count before refund is a universal chip | No. We invent none. Write this brand’s attempt rule | Named max-attempt / hold policy in CS | Promise a forum “3 attempts then auto-refund” |
| Amazon A-to-z is my DTC RTS policy | No. A-to-z is Amazon’s door. This is your carrier outcome | N/A — open amazon-a-to-z for marketplace claims | Paste Seller Central onto a DTC RTS ticket |
Filter the claim. Refused and RTS are carrier outcomes. Not-received with a delivery scan is a different fight. We invent no attempt-count chip.
Pairing procedure: Refused or RTS is not a not-received fight. Topic: Chargebacks.
Work with us — We run this job on your accounts. Services