One word, five cases, and only three of them end in money
Refund gets used for five different situations: the seller never shipped, the item never reached the warehouse, the item arrived and is being returned, the parcel never arrived, or the parcel arrived with damage. Two of those five are usually settled without money changing hands, because the fastest fix is a replacement, a re-send, or a correction to the parcel.
Naming the case before opening a request changes the outcome more than the wording of the message does. A damaged-item message that asks for money on the first line usually gets an assessment request back; the same message asking what the options are gets a decision tree back, and often one of the branches is faster than a refund.
- Seller never shipped: a purchase that has to be unwound, not a return.
- Item lost before intake: a warehouse-side question about a carrier, not about a seller.
- Item returned from the warehouse: a return decision with an evidence bar.
- Parcel lost after departure: a claim against the booking party of the freight.
- Damage found at delivery: an assessment, which may end in money or in a re-send.
Two of the five are decided by photographs. The third and the fifth both rest on what the intake set or the delivery set actually shows, which is why [reading QC photos](/steps/qc-photos/) is a skill that pays for itself before any dispute starts.
Risk list: probability against impact, from a first-time buyer view
The list below ranks the five cases by how likely they are to happen and how much they cost when they do. Probability is described in qualitative bands, because no verified frequency data exists for any of these outcomes and inventing percentages would be worse than leaving the band wide.
| Case | How often | Cost when it happens | Priority |
|---|---|---|---|
| Item returned from warehouse | Common | Item value plus return handling | High |
| Damage found at delivery | Occasional | Repair, replacement or partial value | High |
| Seller never shipped | Occasional | Item value, unwound in full | Medium |
| Parcel lost after departure | Less common | Item value plus freight | High |
| Item lost before intake | Less common | Item value, warehouse-side question | Medium |
Priority is deliberately not the same as how often a case happens. A lost parcel is rarer than a return, and it costs more and needs faster evidence, so it sits higher on the list of things to prepare for.
Priority one: build the evidence before you ask for anything
Two cases need evidence that expires. Damage found at delivery needs the outside of the box photographed before it is opened, because the packing record disappears the moment the parcel is unpacked. A lost parcel needs the freight invoice and the last posted scan, because those establish which party booked the route.
Everything else can be assembled later. That asymmetry is why a ten-minute habit at delivery prevents most of the arguments in this article: photograph the label and the box, then open it, then photograph the contents against the packing list.
A missed damage case runs into a second limit. Once the item has been used or washed, the condition that made it returnable is gone, and the photographs you take afterwards cannot restore it. Two rules cover the whole window: take the pictures before the box is opened, and open the item without removing tags or altering it, until you have decided whether you are keeping it. A third rule costs nothing at all: if the outer box looks crushed, photograph it before accepting the delivery, not after.
- Photograph the closed box and the label, with the date visible.
- Open, then photograph the contents as they were packed.
- Compare the contents with the packing list, item by item.
- Store all of it next to the freight invoice in one folder.
A photograph of a closed box cannot be taken after the box is opened. This is the only step in the whole chain that cannot be redone later at any price.
Priorities two and three: unwinding a purchase, and the return decision
Start with the seller-side unwind, because it is the only case in the list with nothing physical attached to it. The money has to travel back, and the two dates that matter are the day the purchase was placed and the day the reversal was confirmed. A case of this kind is usually over in one exchange, provided the request names the item reference in its first line instead of opening with an explanation of why you changed your mind.
The return decision is harder, because the item physically exists and someone has to decide who carries it. Two questions settle most of it: is the problem visible in the intake photographs, and does the item still have a destination worth sending it to? A return that costs more than the item is worth is a legitimate outcome, and saying so out loud shortens the discussion considerably compared with arguing about the principle of the thing.
| Situation | Better instrument | Why |
|---|---|---|
| Defect visible in the intake set | Return request with the photo cited | The evidence already exists |
| Problem only visible in hand | New photographs plus a written description | The record has to be extended first |
| Item still wanted, defect minor | Partial outcome or a keep decision | Avoids a full return cycle |
| Item not wanted at all | Return, then decide on freight | Two separate decisions, taken separately |
When a refund is the wrong instrument, and what to use instead
A refund moves money and leaves the stage where it was. If your item is sitting in the warehouse with a storage clock running, a refund discussion does not pause that clock, and neither does it extend a claim window. The clock keeps counting while messages go back and forth, which is the real cost of using money as the only tool.
- If the parcel is unpacked: ask whether the item can still be packed or split before arguing about money.
- If a return window is open: file inside it, because a refund request is not a substitute for a claim.
- If the problem is a wrong address: an address correction is the instrument, and only before freight is booked.
- If a parcel is already packed: a merge or split decision changes what ships, and money does not.
The [merge and packing stage](/steps/merge-parcel/) is where this matters most. Packing choices change what you pay for shipping and what arrives, and a refund cannot undo a packing choice that has already been made. The same logic applies to a split: asking for one item to be pulled out of a finished parcel is a physical operation with a new weight and a new label, not an edit to an existing one.
There is also a sequencing cost. A return request and a freight payment can both be open on the same item, and paying the freight while a return is pending is how people ship something they were trying to send back. Neither action blocks the other by itself, so the order in which you do them is entirely your responsibility.
The sequence that keeps both the money and the clock in view
Run the sequence below in order. Each step is written to preserve the next one, so a request made early does not close a door you still need.
- Write the case name first: shipped-never, lost-before-intake, returned, lost-after-departure, damaged.
- Check the stage and its closing dates before writing anything.
- Attach the evidence that belongs to that case, and only that.
- State what you want in one line, and ask for the next step in a second line.
- Diary the answer date, and follow up once, referencing the earlier message.
Damage cases have a fourth option that people forget: asking for a local assessment. A repair quote or a maker assessment can be cheaper for everyone than a return cycle, and it produces a document in writing, which is what a later dispute needs anyway.
Keep the numbers visible. Item value, freight paid, and any return cost are three separate figures, and a partial outcome only makes sense when those three are written down. The wider rules behind each case are collected under [returns and disputes](/table/returns/), and the questions that keep coming back are answered in [open doubts](/doubts/).
One closing distinction saves a lot of frustration. A refund is a payment outcome; a claim is a written request for a decision. Filing a claim does not commit you to wanting money, and asking for money does not create a claim. Write down which of the two you are doing before you send anything, because the counterparty reads the first line and acts on that.
Flow dependency: a refund returns money but not a stage, so any item whose clock has already started keeps running during the refund, which means the storage clock and the claim window continue while a refund is being discussed. (stated basis: Flow dependency)
This note explains the mechanics; the list is where the items are.