Scan-to-search and back-to-back receiving

We rebuilt the returns receiving workflow at facility NJ-01 around one device: the scanner. Scan-to-search now jumps straight to the matching parcel, scan-verified dispose confirms an item before it leaves the floor, back-to-back receiving keeps the line moving without leaving the screen, and every receive number is a guaranteed-unique sequence saved before the label prints. The primary benefit is simple: less time per parcel at the exact station where returns cycle time is won or lost.

If you run a returns operation, you already know receiving is the choke point. A parcel that sits unopened is a parcel that is not graded, not restocked, and not resold. This update is about removing the small frictions that quietly add seconds to every unit, then multiply across 180,000+ returns.

Why receiving is the bottleneck

Everything downstream depends on receiving being fast and correct. Grading, disposition, evidence, and restock all wait on the receive event. When receiving is slow or ambiguous, the delay compounds: a mismatched parcel triggers a manual lookup, a lookup interrupts the operator, and the interruption stalls the whole line behind them.

The old flow made operators do the reconciliation work in their heads and across screens. They keyed order numbers, switched tabs to find the expected return, then switched back to log condition. Each context switch is a few seconds and a chance to make a mistake. At volume, seconds and mistakes are the whole game. So we moved the reconciliation into the scanner and kept the operator's eyes on one screen.

What changed, feature by feature

Scan-to-search: jump straight to the matching parcel

Scan a label or a return barcode and the system resolves it directly to the expected return record. No typing, no tab switching, no guessing which of three lookalike orders is the right one. The match is made against the inbound manifest, so the operator sees the customer, the SKU, and the expected condition the instant the parcel is in hand. This is the core of the scanner-first idea: the operator scans, the screen answers, and work begins immediately. Match accuracy across the network sits at about 99.6%, and scan-to-search is a big part of why.

Scan-verified dispose: confirm the item before it leaves the floor

Some returns are destined for disposal rather than resale. The risk is disposing of the wrong unit, which destroys value and creates disputes. Scan-verified dispose closes that gap: before an item leaves the floor, the operator scans it and the system confirms it is the exact unit tied to that disposition decision. If the scan does not match, the item does not go. That check turns disposal from a trust exercise into a verified event, and it feeds the custody chain so the record shows precisely what left and when.

Back-to-back receiving: keep the line moving

The moment one parcel is received, the screen is ready for the next. No return to a menu, no reload, no hunting for the receive button. Back-to-back receiving is a small change that pays out on every single unit, because it removes the dead time between parcels that used to accumulate across a shift. The operator establishes a rhythm and holds it, which is exactly what you want on a receiving line.

Guaranteed-unique receive numbers, saved before the label prints

Every parcel gets a receive number from a guaranteed-unique sequence, and that number is committed to the database before the label prints. Order matters here. Saving first means a label never carries a number that does not exist in the system, and two parcels can never collide on the same identifier. That reliability is what lets the evidence bundle, the grade, and the disposition all hang off one clean key for the life of the return.

Feature to impact at a glance

How this feeds evidence and grading

Faster receiving is only half the point. The other half is that a clean, fast receive event makes everything downstream more trustworthy. Every parcel is photographed at receiving and gets an evidence bundle: photos, an A/B/C/R grade, a confidence score, and a custody chain. Because the receive number is committed before the label prints, each of those artifacts attaches to a stable key from the very first second the parcel exists in the system.

That key is what makes A/B/C/R condition grading auditable rather than anecdotal. A grade means more when you can trace it back to the exact photographed unit received under a verified identifier. When a partner questions a decision, there is a single record to point at, not a reconstruction after the fact.

The throughput and cycle-time payoff

Median cycle time across the network is about 48 hours, and receiving speed is the largest lever on that number. Shaving seconds per unit at the front of the flow means graded, restockable inventory moves back into the sellable pool sooner. That directly improves restock velocity, the metric that ties receiving speed to recovered revenue.

The economics follow. Every extra hour a return sits in processing is holding cost and depreciation on goods that could be resold. We break that down in the real cost of a return, and receiving is where the biggest chunk of that clock is either spent or saved. A scanner-first workflow is not a cosmetic change; it is the most direct way to compress the time between a parcel arriving and value being recovered.

If you want the full picture of how NJ-01 is built and instrumented, the node spec lays out the facility, the flow, and the numbers behind these features.

Frequently asked questions

What is scan-to-search in a returns receiving workflow?

Scan-to-search means scanning a parcel label or return barcode jumps the operator straight to the matching return record on the inbound manifest. There is no manual order lookup and no tab switching, so receiving starts the instant the parcel is in hand.

How does back-to-back receiving improve throughput?

Back-to-back receiving loads the next parcel the moment the current one is received, without returning to a menu or reloading the screen. It removes the dead time between units that accumulates across a shift, letting operators hold a steady rhythm and process more parcels per hour.

Why save the receive number before the label prints?

Committing a guaranteed-unique receive number to the database before printing guarantees the label never carries an identifier that does not exist in the system, and no two parcels can collide on the same number. That clean key anchors the evidence bundle, grade, and disposition for the life of the return.

What does scan-verified dispose prevent?

It prevents disposing of the wrong unit. Before an item leaves the floor, the operator scans it and the system confirms it is the exact unit tied to that disposition decision. A mismatched scan stops the disposal, and the verified event is recorded in the custody chain.

How does faster receiving affect cycle time?

Receiving is the largest lever on cycle time, which runs at a median of about 48 hours across the network. Cutting seconds per unit at receiving moves graded, restockable inventory back into the sellable pool sooner, improving restock velocity and recovered revenue.

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

Related reading: Returns Processing Product Updates: What We've Shipped and Why