Introducing photo evidence on every parcel

Photo evidence now ships on every return. As of today, every parcel that lands at our East Hanover node (NJ-01) is photographed at receiving, and those photos are attached to the return alongside the AI condition grade, confidence score, detected tags, and custody chain. This is live for every account with no toggle to flip and no plan tier to upgrade. When a customer disputes what came back, or finance questions a refund, or a partner wants to audit a decision, the proof is already sitting on the record.

We built this because returns run on trust, and trust that cannot be shown gets argued about. A grade on its own is an assertion. A grade with four timestamped photos behind it is a fact you can forward. This post covers what shipped, how it works on the floor, how to pull the evidence bundle from the dashboard and the API, and why it prevents disputes before they start.

What shipped

Every returned parcel is now captured at four points during receiving. Each photo is stored with the return, tied to the same custody chain that tracks the item from the moment its label is scanned. The full package, photos plus grade plus metadata, is what we call the evidence bundle. You can see a real one on our public evidence sample page.

The bundle includes:

• Photos from four capture points (below)
• The AI condition grade on our A/B/C/R scale
• A confidence score for that grade
• Detected tags (open box, missing accessory, visible defect, seal broken, and similar)
• The custody chain: who handled the parcel, when, and at which station

None of this is a separate product. It is the default shape of a return at areturnz now, applied across the 180K plus returns we have processed and every one that arrives next.

The four capture points and what each proves

Photography is not a single snapshot. A single image of an item tells you nothing about the parcel it arrived in or the label it traveled under. To close the gaps that disputes exploit, we capture at four distinct moments, each answering a specific question.

Read together, the four points form a chain of narrative. The label ties the parcel to the order, the opened view records the contents untouched, the item shot grounds the grade, and the defect shot documents the exception. There is no point in that sequence where a customer can credibly claim the wrong item was inspected or the box arrived empty, because the record already answers it.

How it works on the floor

Capture is folded into the receiving flow rather than bolted onto it. When a parcel is scanned in, the station prompts the operator through each capture point in order, and the images are bound to the return record immediately. The same scan-driven rhythm we describe in scan to search, back to back receiving keeps this fast: median cycle time across the node stays around 48 hours, and our match accuracy holds near 99.6 percent.

Once photos are attached, the grading model reads the item and defect images to assign the condition grade and confidence. If you want the detail on how those grades are produced, see how A/B/C/R AI condition grading works and the way we surface confidence scores on the line. The photos and the grade are two halves of the same record: the grade is the decision, the photos are the reason.

How to access the evidence bundle

The bundle reaches two audiences in two ways, and both are live now.

In the dashboard, for CS and finance

Every return in the dashboard now carries its photos, grade, confidence, tags, and custody chain on the record. Your CS team can open a return and forward the bundle to a customer verbatim, exactly as captured, with no editing and no screenshots. When a shopper insists the jacket came back unworn, the agent sends the item and defect photos and the conversation ends. Finance gets the same view for refund and chargeback decisions, so a disputed credit is backed by images rather than a note that says "agent inspected."

Via the API, for developers

Developers can pull the same bundle programmatically as signed JSON, so authenticity is verifiable rather than assumed. The lifecycle webhooks fire at each stage:

• return.received when the parcel is scanned and captured
• return.graded when the condition grade and confidence are set
• return.dispositioned when a disposition decision is made
• return.restocked when the item re-enters sellable stock

That lets you attach evidence to your own order records, trigger downstream logic, or archive the signed bundle for audit. The full contract, endpoints, payloads, and event shapes, lives in the node spec.

Why this prevents disputes

Most returns disputes are not really disagreements about policy. They are disagreements about facts that neither side can prove. The shopper says the item was defective; the brand says it came back worn. Without a record, whoever argues hardest wins, and the cost lands on the merchant either way.

Photo evidence removes the ambiguity. The most common and most expensive class of dispute, "item not as described," collapses when the opened parcel and item photos are already on file. We wrote about that specific pattern in killing item not as described. The broader principle, that a returns operation should put proof on every return, is now the default behavior of the network rather than a premium add-on.

The downstream effect is faster closes and fewer write-offs. CS resolves in one message instead of a back and forth. Finance approves or denies with images in hand. Partners auditing a batch of decisions can see the reasoning behind every grade instead of trusting a summary.

Who benefits

• CS teams close disputes in a single forwarded bundle instead of escalating
• Finance ties every refund and chargeback to timestamped images
• Developers ingest signed JSON and drive automation off the webhooks
• Brands and partners get an auditable record behind every disposition decision

What is next

Photo evidence is the foundation, not the finish line. We are extending detected-tag coverage, tightening the link between defect photos and disposition rules so that a graded exception can route automatically, and expanding the signed-bundle format so more of the custody chain travels with the JSON. As the node network grows, the same capture standard applies at every facility, so evidence is consistent no matter where a parcel lands.

If you want to see the capability before you touch your own account, open the public evidence sample. It is a real bundle, four capture points, grade, confidence, tags, and custody chain, exactly what your customers and your developers will see.

Frequently asked questions

Is photo evidence available on my account?

Yes. It is live for every account with no setting to enable and no upgrade required. Every parcel received at NJ-01 from today forward is photographed at the four capture points, and the photos are attached to the return automatically.

How do I send the evidence to a customer?

Open the return in the dashboard and forward the bundle verbatim. Your CS agent does not edit or reconstruct anything; the photos, grade, confidence, and tags go to the customer exactly as captured, which is usually enough to end the dispute in one message.

Can developers pull the evidence programmatically?

Yes. The full evidence bundle is available as signed JSON through the API, and lifecycle webhooks (return.received, return.graded, return.dispositioned, return.restocked) let you attach evidence to your own records and drive automation. See the node spec for the contract.

What exactly is in the evidence bundle?

Photos from four capture points (outer label, opened parcel, item, and any defect), the A/B/C/R condition grade, a confidence score, detected tags, and the custody chain that records who handled the parcel and when.

Does photographing every parcel slow down processing?

No. Capture is built into the scan-driven receiving flow, so median cycle time stays around 48 hours and match accuracy holds near 99.6 percent across the more than 180,000 returns processed to date.

Related reading: Shipped: AI Content and Quantity Verification on Receiving