Parcel Sorting Hardware: Read Rates and Reject Lanes

A sorting hub reads items moving at speed, in any orientation, with labels that have already been through a network. That combination is why sortation hardware differs from anything at a counter or in a warehouse aisle.

Items move; the reader does not

The defining difference from handheld scanning.

On a sortation line, parcels pass a fixed reading point on a conveyor. Nobody presents anything, nobody aims, and nothing waits. If the read fails, the item goes to a reject lane and becomes manual work.

Three consequences.

Read rate is the metric that matters, not read capability. A scanner that reads 98 percent of items at speed is meaningfully different from one that reads 99.5 percent, because the gap is manual handling.

Orientation cannot be controlled. Parcels arrive on any face, so labels present at any angle. Omnidirectional reading is a requirement rather than a feature.

Motion tolerance matters more than optics breadth. The item is moving, so the reader has a short window.

Where multiple faces must be covered, that is a multi-scanner arrangement rather than a better single scanner.

Labels arrive damaged

By the time a parcel reaches a sorting hub it has been handled, stacked, moved and possibly rained on.

Labels are creased, scuffed, partly torn, wet, or covered by tape someone applied over the top.

Two consequences.

2D codes with error correction tolerate this where linear codes fail. A damaged Data Matrix frequently still decodes because the redundancy is built in — our symbologies guide covers why.

Linear codes remain unavoidable, because carrier and trading partner formats specify them. GS1-128 carries structured shipment data and is what partners mandate — our compliance guide covers what those specifications contain.

So the reader must handle both, and handle them badly printed and badly treated.

Print quality upstream decides read rate downstream

The point most worth acting on, because it is cheaper than better scanners.

A hub’s reject rate is largely determined by the quality of labels applied by other people — shippers, merchants, other depots. You cannot control that entirely, but where you produce labels yourself, the same principle applies internally.

Three things drive it.

Quiet zones. A code crowded against the label edge will not decode however well it is printed, and this is one of the most common causes of unreadable labels. Our label design guide covers it.

Print darkness. Too low gives insufficient contrast; too high causes bars to bleed and widen, failing element width accuracy. Set it to the lowest value producing a clean verifiable code.

Printhead condition. A single failed element produces a continuous line through every code, and it degrades gradually rather than failing outright. Our printhead guide covers spotting it early.

Verification rather than scanning is what catches these before they reach a sorter — our verification guide covers the difference.

Label media for the journey

Where labels are produced in the hub, two failures recur.

Fading. Direct thermal fades under heat and light. For same-day and next-day it is adequate; for parcels sitting in a hot vehicle or a yard for longer, thermal transfer is safer.

Adhesive failure. Recycled corrugate is rougher than people expect, and cold or damp packaging needs appropriate adhesive. Standard adhesive lifts, and a label on the floor is a parcel with no identity. Our media guide covers selection.

The reject lane is where the work is

Every sortation operation has one, and how it is equipped determines how expensive it is.

Items arrive there because the code did not read, the label is missing, or the destination is unresolvable.

What that station needs.

A forgiving handheld imager to attempt a manual read on a damaged label — frequently succeeding where a fixed reader at speed did not, because the operator can angle it and hold still.

A label printer to relabel at the point of resolution rather than in a batch afterwards. A batch printed later has to be matched back to items, reintroducing the error.

A device that displays information, since resolving a destination means looking something up rather than only capturing a code — a mobile computer requirement.

Our returns processing guide covers a similar station, and the reasoning transfers directly.

Downtime is expensive here

A hub runs to a departure schedule. A sorter stopped for twenty minutes is not twenty minutes of lost throughput — it is a backlog that has to be cleared before a fixed cut-off.

Two consequences for spares.

Hold spares on site, not centrally with next-day delivery. Fixed scanners, a handheld, a printer, and printheads matching each printer resolution.

Consumables against peak consumption. Label and ribbon usage at peak can be several times normal, and suppliers are busier too. Our consumables guide covers setting reorder points from consumption and lead time rather than round numbers.

Our peak guide covers the wider preparation, including why printhead and cutter failures cluster exactly when you can least afford them.

Specifying a sorting operation

What read rate is required, and what does each rejected item cost to handle. What faces must be read, which determines scanner count. What symbologies arrive, and are they all enabled. How damaged are inbound labels typically. Where are labels produced, and are they verified. And what happens when a fixed reader fails mid-shift.

That last question usually determines the on-site spares holding.

Common questions

Tell us your read rate requirement and how many faces need covering, and we will specify the line and the reject station together.