Returns Processing Hardware: Scanning, Evidence, Relabelling
Returns arrive without the structure that outbound shipments have. Items come back in mixed condition, sometimes without paperwork, frequently with damaged labels, and the decision about what happens next has to be made per item.
Why returns are harder than receiving
Goods-in handles predictable deliveries from suppliers who label consistently. Returns do not.
Labels are damaged or missing. Items have travelled twice, been repackaged by customers, and had labels removed or covered.
Identification is uncertain. Without a readable code, the item has to be identified by appearance, which is slow and error-prone.
Condition varies per item. Each one needs assessing rather than counting, and the assessment determines whether it goes back to stock, to repair, to clearance or to disposal.
Evidence matters. Damage claims, warranty positions and customer disputes all depend on what was recorded at the point of receipt.
That last point is why returns hardware differs from receiving hardware.
Scanning what arrives
Two hardware implications follow from damaged labels.
2D imagers rather than lasers. Torn, creased and scuffed labels are the norm here. 2D codes carry error correction, so a damaged Data Matrix frequently still reads where a scratched linear code fails. Our symbologies guide covers why.
A wide range of symbologies enabled. Returns include items originally labelled by you, by suppliers, and by carriers. Several symbologies are disabled by default on scanners — our configuration guide covers enabling what you actually see.
Where no code is readable, the fallback is identification against the original order — which needs a device that can display order details rather than only capture codes.
Capturing condition
The step that determines whether a claim can be defended.
Photographs at receipt record what arrived, in what state, before anyone handles it further. That evidence supports supplier claims, carrier damage claims and customer disputes, and it is unrecoverable if not taken at the time.
Camera quality matters more than people assume, particularly in the poor lighting typical of a returns bay.
Structured condition grading rather than free text, so decisions downstream are consistent. The operator selects from defined options rather than describing.
Both of these mean returns is a mobile computer rather than a scanner. The scan is a small part of the work; seeing order details, capturing images and recording an assessment is most of it.
Relabelling is the core printing requirement
Items returning to stock need a label your systems can read, and the original frequently cannot be relied on.
Print at the point of assessment rather than in a batch afterwards. A batch printed later has to be matched back to items, which reintroduces the error you were avoiding.
Media follows the destination. Items going back to general stock need whatever your standard is; items going to chilled storage need adhesive that bonds cold, and standard adhesive fails silently. Our media guide covers selection.
Volume decides the printer class. A returns bay processing steadily through a shift is an industrial application — and if it processes a few dozen items a day, a desktop unit is correct and industrial construction buys nothing. Our printer class guide covers where the line falls.
Where items are dispositioned to different destinations, printing a clear destination label at assessment prevents the sorting error that otherwise happens later.
Where returns hardware differs from outbound
Three practical differences worth specifying for.
Bench work rather than movement. Returns assessment happens at a station, which favours a device that can sit in a stand or a presentation scanner, rather than a device carried all day.
Lighting is frequently poor. Returns areas are often in the least attractive part of the building, which affects both photograph quality and scanning of marginal labels.
Throughput is uneven. Returns arrive in waves after peak trading periods, so the area needs to handle a multiple of its normal volume for short periods. Our peak preparation guide covers planning for that, and note that a returns surge usually follows the sales peak rather than coinciding with it.
Specifying a returns area
What symbologies arrive, and are they all enabled. How often are labels unreadable, which determines how much the device needs to display. Is photographic evidence required, and in what lighting. Where do items go after assessment, which determines relabelling media. And what is peak returns volume, which is frequently a multiple of the average.
Send us those answers and we will specify the station together. See also our goods-in guide, which covers the inbound side.
Common questions
Why does returns need different hardware from receiving?
Because items arrive without structure — damaged or missing labels, uncertain identification, and condition that varies per item. Each one needs assessing rather than counting, and evidence captured at receipt is what supports claims later.
What handles damaged labels best?
2D imagers rather than lasers. 2D codes carry error correction, so a damaged Data Matrix frequently still reads where a scratched linear code fails. Also enable the full range of symbologies, since returns include labels from several sources.
Why photograph items at receipt?
Because that evidence supports supplier claims, carrier damage claims and customer disputes, and it is unrecoverable if not taken before the item is handled further. Camera quality matters in the poor lighting typical of returns areas.
Should relabelling happen in batches?
No. Print at the point of assessment, because a batch printed later has to be matched back to items, which reintroduces exactly the error the relabelling was meant to remove.
How should I size a returns area?
Against peak rather than average, since returns arrive in waves — and note that the returns surge typically follows the sales peak rather than coinciding with it, so the two do not overlap in planning.
Tell us your peak returns volume and what evidence you need to capture, and we will specify the station together.
