Returns bench · kit completeness

$340

The refund waits for what's actually in the box.

For a returns lead at a store that ships multi-item kits, ReturnWitness counts what comes out of the box, checks it against the packing slip and the return policy, and holds the refund until a person approves it.

Run the Instant Demo Return a box yourself How it works

RMA-20418 · Creator Kit · $340

Diagram of the seeded return, not model output. The Instant Demo replays the recorded run and labels every result.[Seeded merchant order & RMA fixture]

The problem: In this scenario, a “received” scan would release the refund, not what was in the box, so an incomplete kit refunds in full.
The solution: SAM 3.1 tracks each item, app code counts what settles in the tray against the packing slip, and the refund holds until a person approves.
Why it matters: The missing $109 zoom lens is caught at the bench, with a timestamped record, not at a restock count later.
How it’s used: Pick the RMA, unbox one item at a time into the tray, read the lines, then approve or keep the hold.

The problem

Rita's afternoon at Bench 2.

Rita Calder runs returns at Brindlewood Camera Co., an online camera store. The Creator Kit is a camera body, a zoom lens and a battery with charger: $340 together.

Illustrative workload, not measured

60–80 returned boxes on her bench each afternoon
about 40 seconds per box for the person opening it

A picture of the job for this scenario, not a count from a real store.

Picture a full bench of returned boxes every afternoon and little time for each. The customer on RMA-20418 says “everything's in there.” She lifts out the camera and the battery, a wad of kraft paper, and the box looks empty enough.

In this scenario, the return system marks the RMA “received” on the scan, and that scan would release the $340 refund on its own that night. The lens was never in the box. Someone finds out at a restock count a week later, and by then nobody can show whether it went missing at the bench or on the shelf.

Why it matters. The store absorbs the $109 lens, or the whole kit if the rest can't be resold, and it has no record to dispute with. The person at the bench has no time and no evidence. The gap is that the refund follows a scan, not the contents.

The solution · how it's used

Count, reconcile, hold, approve, refund.

The camera watches. Code counts. Models read and draft. A person decides. The product is the workflow around the refund, not a picture of a box.

Step 1: Film and segment
The overhead camera films the unboxing. SAM 3.1 segments each item and keeps following it from frame to frame.
Step 2: Count in code
An item counts once, when it settles in the inspected tray. That rule lives in app code, built not to add a count for hands, kraft paper or re-issued track IDs; it passes the synthetic stress sweep, and in the reported run it counted every item right (g1 with a merged-mask hold); the registered gate is incomplete, g2–g8 not filmed.
Step 3: Reconcile and hold
App code reconciles the counts against the packing slip and the policy. When enabled, Muse Spark 1.3 reads the same evidence and can only add a hold, never clear one.
Step 4: Draft, approve, refund
Muse Wonder 1.0 drafts the decision and cites the policy clause. A person approves. Then a Stripe test-mode refund runs.

Read the full pipeline Set up a bench

The held return

RMA-20418: the lens was not observed.

The card is the packing-slip rule as a diagram: two lines seen, one missing, so the whole $340 is held and the policy clause that applies is quoted next to it.

The Instant Demo replays the recorded filmed run of this return. There the lens was not observed, and the camera line was held too, on a false stand-in flag:

Loss misread: the prop is a real compact film camera, not a toy (it stands in for the kit's interchangeable-lens body); a false stand-in flag

The Instant Demo plays a recorded result. It does not make a live Meta call, and the label on the card says so. The merchant, the customer and the RMA are seeded data.

The packing-slip rule, as a diagram (not the recorded run)

RMA-20418 · Creator Kit

Brindlewood Camera Co. · Bench 2 · order ORD-58213

HELD

Expected versus seen settling in the tray, per packing-slip line
Packing-slip line	Seen / expected	Result
Camera body CK-BODY-01 · $199	1/1	OK
Zoom lens CK-LENS-24105 · $109	0/1	MISSING
Battery + charger CK-BATT-CHG · $32	1/1	OK

Refund requested ($340)$340 held

CLAUSE 4.2 · COMPLETE KITS

“A kit is refunded in full only when every component listed on the packing slip is returned.”

RECORDED FIXTURE · synthetic scene, not a live Meta call[Seeded merchant order & RMA fixture]

What a HELD shows, and what it doesn't

What the record shows

No accepted arrival of that item in the tray during this clip, or something the camera couldn't resolve: two items merged into one, a label it couldn't read. A hold is a question for a person, not proof the customer kept anything.

What it doesn't show

That the customer kept the item, that an item it did see is genuine, or that there is no hidden damage. A brick the shape of a lens is out of scope, and so is anything inside a sealed box.

So it never denies

It holds the refund, attaches timestamped evidence and the policy clause, and a person decides. Under clause 5.1 a hold is not a denial.

Proposed pricing

Proposed pricing: $2 per high-risk return inspected.

The merchant chooses which returns go to the bench. Clean, low-value returns never touch it.

Break-even illustration, before other costs

If the $109 lens really is missing, catching it once equals the fee on 54 inspections. This is arithmetic, not measured savings.

See the arithmetic

Proposed, per inspection

Watch a $340 refund get held.

One click opens RMA-20418 at the bench and walks the count, the hold and the approval. Test mode only; no real funds move.

Run the Instant Demo