Photograph the return where the return is

The workflow, step by step

1. A processor opens the return on the desktop and displays its QR code. The code belongs to that return, not to the account in general.
2. They scan it with their phone. The camera opens on the return already identified — no typing an order number on a phone keyboard at a loading dock.
3. They photograph what they can see: the outer carton, the packing, the item, the specific discrepancy, the label. Each photo is added to the set for that return.
4. The photos are held on the device while they work. Nothing is uploaded one at a time, so a weak signal in a warehouse does not interrupt the inspection.
5. They press Done. The set uploads together and appears on the return record, in order, ready to be assigned to an item and a category.

Why holding the photos on the device matters

Warehouse connectivity is the reason. A capture flow that uploads on every shutter press fails halfway through an inspection and leaves a return with three photos of an eight-photo problem. Holding the set until the processor says they are finished makes the upload one event that either happened or did not.

Grading and photographing are separate acts

Condition is graded against what the order expected, and then the photographs are taken. Doing it in that order means the images are taken to show something specific rather than as a general record of a box, and the evidence is legible to somebody who was not there.

An inspection interrupted mid-way saves as a draft, so a processor pulled onto something else does not have to start the return again.

Desktop capture is still there

Not every photograph is taken at the dock. Evidence can be uploaded from a desktop, sorted into categories and reordered, and it lands in the same record as anything captured on a phone. Every image is assigned to an item and a category either way.