Traceability for second hand products: following a used unit from source to buyer and back

A used unit gets its identity from a combination of its original markings and the seller's own identifier. Original model and batch codes, where legible, should be recorded, and where they are missing or damaged, that fact should be recorded too, rather than guessed. The seller's own identifier, such as a sequential unit number, then becomes the key linking the unit to its inspection, repairs, listing, and buyer.

That identifier should be physically attached to the unit or its packaging, and should appear in every record concerning the unit. An identifier that lives only in a spreadsheet, without a physical counterpart, will be lost when the unit moves, and a physical label without a record counterpart is equally useless. The pair, physical and recorded, is what makes traceability real.

Source logging should record where the unit came from, when it arrived, in what stated condition, and from whom, where that information is available. A batch of units from one trade source, a collection from a house clearance, or a single unit from a walk in seller each carry different implications for pattern risk. A fault found in several units from one source suggests a source problem, while a fault in units from many sources suggests a model problem, and only source logging lets the seller tell the difference.

Source information also matters for recalls and supplier questions. A reseller who can tell a supplier or an authority exactly which units came from which source, and when, can answer questions precisely and can warn the right downstream buyers. Illustration: a reseller of used power tools traces a faulty batch of drills to a single trade in source and contacts only those buyers, rather than alarming every drill buyer.

Buyer linkage is the sales record done properly: unit identifier, buyer contact, sale date, and listing or label version at sale. That record lets the seller contact the buyer if a later fault emerges in similar units, and lets a buyer complaint be matched to the unit's inspection and repair history. Without it, a complaint about a used product becomes an anecdote about a model, rather than a case about a unit.

Privacy matters here too. Buyer contact details should be kept securely, used only for safety and service purposes, and retained for a sensible period. A seller who keeps buyer details carelessly, or uses them for unrelated marketing without permission, undermines the trust that makes buyers willing to be contacted about safety in the first place.

When a complaint arrives, tracing runs backwards: from the buyer's unit identifier to its inspection record, its repair record, its source, and its sibling units from the same source or with the same repair. That backward run answers the key question: is this an isolated unit fault, or a pattern? A pattern answer triggers wider action, such as checking sibling units still in stock or contacting other buyers, while an isolated answer supports a single unit remedy.

The tracing should be documented, with the units checked and the conclusions drawn, even where the conclusion is that no pattern exists. A documented no pattern finding protects the seller against a later claim that a pattern was ignored, and it gives the team a record to revisit if a second similar complaint arrives.

Gaps usually appear at handover points: units arriving without labels, repairs done without recording the unit, listings created from stock photographs rather than unit photographs, and sales recorded by model rather than by unit. Each gap breaks the chain at a different point, and each needs a specific fix: label on arrival, record repair by unit, photograph the actual unit, record the sale by unit identifier.

A periodic trace test reveals gaps before a real complaint does. Pick a sold unit at random, and try to trace it back to source and forward to buyer, using only the records. Where the trace breaks, fix the stage that broke it. That test, run occasionally, keeps the system honest in a way that a written procedure alone cannot.

A trace system can be very simple: a log with columns for unit identifier, source, arrival date, inspection result, repairs, sale date, and buyer contact, kept consistently for every unit. Simplicity is a virtue, because a complex system that staff abandon is worse than a simple system they actually use. The system should fit the volume: a market stall needs a notebook or a sheet, while a large refurbishment centre may need a database, but both need the same columns.

Consistency beats sophistication. A simple log kept for every unit, without exception, will trace better than a sophisticated system used for most units but skipped for rush sales. The rule should therefore be absolute: no unit moves to sale without a log entry, and no log entry is created after sale from memory. That discipline is the whole system, in one sentence.