Evidence packets
One file that says what came back
A packet is the return, closed and legible to somebody who was not there. It is generated in one click as a PDF and a ZIP, it is versioned, and once generated it does not change.
What is inside
- A numbered evidence index. Every photograph has a number, an item it belongs to and a category. A reader can point at one and be understood.
- Expected versus received. What the order line said should come back, next to the graded condition of what did.
- A full timeline. When the return was received, who inspected it, when they graded it, what they uploaded and when it was closed.
- The return identifiers. The identifier the return was received against, so the packet can be tied back to the order it came from.
Immutable and versioned
Generating a packet writes a version. Generating another one writes a new version and leaves the previous one exactly as it was. That is the point: a record that can be revised silently is not evidence, it is a draft.
PDF and ZIP
The PDF is the readable document — index, comparison, timeline, images in order. The ZIP carries the original image files alongside it, so nothing depends on a downscaled copy embedded in a page.
What a packet is not
ReturnSignal does not file claims and does not handle money. A packet is a record you hold. Nothing about generating one submits anything anywhere, and nothing about it is sent to Amazon by ReturnSignal.
Preparing a packet does not guarantee a SAFE-T reimbursement or any outcome.
If you are assembling a packet with a SAFE-T claim in mind, read the SAFE-T claims guide first — the distinction it draws between a SAFE-T reimbursement and a customer refund changes what is worth documenting.
Be told when it opens
One email, once. No newsletters and no marketing sequences.