Why every return should ship with proof

A photo taken the moment a box is opened ends most condition disputes before they start. That single frame, timestamped at receiving and paired with an AI condition grade, is the core of returns evidence: proof of what actually arrived, in what state, before anyone had a chance to argue about it. When every return ships with that proof attached, condition disputes stop being a debate between two memories and become a matter of looking at the record.

Most returns operations still run on trust and assertion. A customer says the item was defective, an agent says it looked used, a marketplace seller says it was never sent back at all. Without evidence captured at the point of receiving, each of those claims carries equal weight, and the party with the loudest escalation usually wins. Attaching a complete evidence bundle to every parcel flips that. The record speaks first.

What a complete evidence bundle contains

Evidence only resolves disputes if it is complete and captured consistently. A blurry phone photo taken three days later proves nothing. At areturnz, every returned parcel is photographed at receiving and assembled into a structured bundle in the dashboard, retrievable as signed JSON via the API. Each element answers a specific question a disputing party might raise.

• Outer label photo: confirms which parcel arrived and ties it to the original outbound order and RMA.
• Opened-parcel photo: shows the contents in the box as received, before anything is removed or handled.
• Item photo: the product itself, framed to show overall condition.
• Defect close-up: a detail shot of any damage, wear, or missing component the system detects.
• AI condition grade: an A/B/C/R grade with a confidence score and detected tags, so the state of the item is expressed as a value your rules can act on, not just an opinion.
• Custody chain: a record of who and what touched the parcel from scan-in to disposition.
• Timestamps: the moment-of-receiving time on every step, which is the anchor the whole bundle hangs on.

You can see all of this on a real, non-hypothetical record at our public evidence sample. It is worth opening before you read further, because the rest of this article is about what each of those elements does for you in practice.

Why the moment-of-receiving timestamp matters

The timestamp is what makes evidence defensible. A photo with no reliable time attached can always be challenged as staged, edited, or captured after damage occurred in your own facility. A photo bound to the moment the parcel was opened at receiving, inside a custody chain that records every subsequent handling, establishes a clear before: this is the condition the item was in when it reached us, prior to any processing on our side. That distinction is the difference between evidence that ends an argument and a picture that starts one. It is also why we grade and photograph at the point of receiving rather than at some later stage. The full story of that approach is in photo evidence on every parcel.

Which dispute each element prevents

Disputes are not generic. Each one turns on a specific factual claim, and each element of the bundle is aimed at a specific claim. The table below maps them.

The single most common and most expensive dispute, item not as described, collapses almost entirely when the item photo, defect close-up, and grade are on the record. We wrote a full breakdown of how that plays out in killing item not as described.

How customer service uses it

The operational win is that evidence lets your CS team stop adjudicating and start forwarding. When a customer disputes a condition decision, the agent does not need to relitigate the case or guess. They pull the bundle and forward it verbatim: here is the label we received, here is the item as it arrived, here is the grade and the time it was recorded. Most disputes end there, because there is nothing left to contest. The ones that continue are genuine edge cases worth a human, not the volume of he-said-she-said that normally clogs a queue.

This changes the economics of a return, not just its tone. Every dispute an agent resolves in one message instead of a three-round email thread is time returned to the team, and every unwarranted refund avoided is margin protected. For the wider math on what a single return actually costs, see the real cost of a return.

Chargeback defense and trust with end customers

Evidence works in two directions. Against chargebacks and marketplace claims, a timestamped bundle is exactly the documentation acquirers and platforms ask for: proof the return was received, proof of its condition, proof of custody. Representment backed by a photo record from the moment of receiving wins cases that a written assertion never would.

In the other direction, the same evidence builds trust with honest customers. When a shopper who genuinely returned a pristine item gets a correct grade and a fast refund because the record is unambiguous, that is a good experience. Evidence is not only a shield against bad actors; it is what lets you say yes quickly and confidently to the majority who are telling the truth.

How developers pull it as signed JSON

For engineering teams, the bundle is not a PDF someone screenshots. It is structured data. Every return exposes its evidence as signed JSON through the API, and lifecycle webhooks fire as the state changes: return.received, return.graded, return.dispositioned, return.restocked. That means your systems can attach evidence to a support ticket automatically, gate a refund on a grade, or file a chargeback response without a human copying anything by hand.

Because the payload is signed, the evidence is verifiable end to end: a downstream system, a partner, or an acquirer can confirm the record came from us and was not altered. The AI grade travels as a value with its confidence score and tags, so your disposition rules can consume it directly. The full contract, including grade semantics and the custody model, is documented in the node spec, and the grading scale itself is explained in how A/B/C/R AI condition grading works.

The standard: proof on every return, not on request

The reason to attach evidence to every return, rather than capturing it only when a dispute arises, is that you cannot photograph a moment that has already passed. By the time a claim comes in, the box is unpacked and the item is on a shelf or back in stock. Evidence has to be captured at receiving, for everything, or it is not available when you need it. Across 180K+ returns processed at a median cycle of roughly 48 hours, that consistency is what turns evidence from a nice-to-have into a dependable answer. Proof on every return is not overhead. It is the cheapest dispute you will ever avoid.

Frequently asked questions

What is returns evidence?

Returns evidence is the documented proof of a returned item's condition, identity, and handling, captured at the moment of receiving. A complete bundle includes photos of the label, the opened parcel, the item, and any defect, plus an AI condition grade with confidence and tags, a custody chain, and timestamps. Together they establish what arrived and in what state before any processing.

How does photo evidence stop condition disputes?

A photo taken when the parcel is opened, anchored to a receiving timestamp, removes the ambiguity that disputes feed on. Instead of one party's word against another's, there is a record of the item as it arrived. Most condition disputes end the moment that record is shared, because there is no longer anything factual to contest.

Can I use an evidence bundle to fight a chargeback?

Yes. A timestamped evidence bundle is the kind of documentation acquirers and marketplaces request for representment: proof of receipt, proof of condition, and a custody chain. Because the record is captured at receiving and delivered as signed JSON, it is verifiable, which is what makes it persuasive in a dispute.

How do developers access the evidence?

Every return exposes its evidence as signed JSON through the API, with webhooks (return.received, return.graded, return.dispositioned, return.restocked) firing as the state changes. Systems can pull the bundle, act on the grade, and attach proof to tickets or chargeback responses automatically. See the node spec for the full contract.

Where can I see a real evidence bundle?

A live, non-hypothetical bundle is published at the evidence sample page. It shows the actual photos, grade, confidence score, tags, custody chain, and timestamps exactly as they appear in the dashboard and API.