Securing Goods-In: Sample IMEI Checks on Supplier Deliveries
· TR Vertriebs GmbH
How well-designed goods-in sampling surfaces blocks, model mismatches, and label errors without checking every single device.
For larger deliveries of used devices, checking every single unit in full is often neither economical nor necessary. Quality assurance's answer is sampling: you check a deliberately chosen part of the delivery and infer the rest. Applied correctly, an IMEI sample at goods-in surfaces systematic problems — misdeclared models, clustered blocks, or swapped labels — before the goods enter stock and the error becomes expensive.
You should know what a sample can and cannot do. It is strong at detecting systematic or clustered defects: if a meaningful share of a delivery is affected, the problem will very likely show up in the sample. A single bad device in an otherwise clean batch, by contrast, often escapes it. Sampling therefore suits homogeneous lots best; with heavily mixed goods, the sample must be larger or the checking denser.
Several check points are worthwhile per drawn device. First, matching the IMEI on the device against the label and packing list — do the 15 digits actually agree? Then the blacklist status and the activation lock. Finally, the model and storage match via the TAC: does the actual model correspond to what was sold? Label errors and model mismatches are more common than open blocks, and can only be uncovered by reading the real IMEI on the device.
The sample's size and selection determine how meaningful it is. Devices should be drawn at random and across all boxes, not just from the top layer. For new or unproven suppliers, high goods value, or the first delivery of a model, a larger sample makes sense. For long-trusted sources and homogeneous goods, it can be smaller. The sample should fit the structure of the delivery, not a rigid fixed number.
A pre-defined escalation rule matters. At what share of flagged devices in the sample is the entire lot checked in full or rejected? This threshold should be fixed before the check, so it is not negotiated case by case. If the sample finds several blocked or misdeclared devices, that signals a systematic problem — and a full check of the affected lot is the right consequence, not the exception.
Over time, the findings build a picture of each supplier. Recording per supplier how many anomalies the samples reveal lets you tune checking intensity deliberately: denser for sources with frequent deviations, leaner for consistently clean goods. This feedback loop makes quality assurance learn across deliveries and, at the same time, provides a factual basis for conversations with the supplier should problems accumulate.
Sample IMEI checking at goods-in is a compromise between effort and certainty — but a considered one. It catches systematic errors early, aligns checking intensity with risk, and creates solid data about your own suppliers. By fixing size, selection, and escalation in advance, you turn a gut feeling while unpacking into a controlled, repeatable step.