Investigate a Barcode Mismatch Before Receiving Stock Against the Wrong Product

A barcode scan that does not match the expected product record should stop the ordinary goods-in process, not invite a guess. Warehouse staff may have received the correct item in new packaging, a different variant under a familiar supplier code, or a case label where the system expected an individual retail unit. These circumstances can look alike on a scanner but require different decisions. Mapping the unfamiliar code to the nearest SKU simply to finish the receipt can spread an identity error into stock allocation, customer listings, picking, invoicing and returns. A controlled barcode-mismatch check protects the physical identity of goods while the business establishes what actually arrived.

This guide addresses UK trading SMEs receiving electronics, accessories and other identified products. GS1 provides international trade-item identification and packaging standards, but it cannot independently confirm that a particular shipment contains what a supplier claims. Staff therefore need both standards-based mapping and evidence from the real purchase order, labels, supplier documentation and physical inspection. A mismatch is an unresolved exception, not automatically fraud, a quality defect or a valid product change.

Capture what was scanned, where and when

Record the literal barcode characters, symbology if relevant, scanned physical object and receipt reference before any master-data edit. Photograph the visible label where workplace rules allow it, ensuring the image includes enough context to distinguish a case from an individual product. Note the supplier, delivery, internal purchase order, quantity, product reference and location. A code printed on shrink-wrap or a shipping case may not describe a consumer item inside it.

Preserve the expected identifier from the accepted purchase order alongside the observed code. Staff need to see what differs, not only that a scan failed. If a scanner reads part of the code because a label is damaged, a second verified reading may resolve the issue without a product-data change. If several cartons show the same unfamiliar code, capture the pattern but do not assume the contents match without a suitable sample inspection.

A scanner error and a trade-item identity mismatch are not the same. Verify whether the device is configured to interpret the intended barcode, including leading zeros or data separators when relevant. Avoid trimming characters merely to obtain a match. A barcode value is an identifier, not an invitation to adjust digits until the computer accepts it.

Distinguish the item from its packaging level

GS1's Global Trade Item Number guidance explains identification of defined trade items, and its Global Data Model distinguishes base units, packs, cases and pallets. A unit, an inner multipack and an outer case can have separate identities and different quantities. If goods-in expects the barcode for a single accessory but scans an outer carton, the mismatch may reflect the wrong scanning level rather than an incorrect delivery.

Write out the conversion from the actual package specification. If a case contains four inner packs of six eaches, a case represents twenty-four individual units only when those pack relationships are verified. That is an illustrative calculation, not a claimed supplier fact. A case code mapped to one individual unit would understate stock; a single-unit code treated as a case could overstate it. Both errors can create false customer promises.

Check mixed cartons separately. An assortment containing several colours or models cannot be mapped to the quantity of one variant because the outer box carries a general label. Record each approved component quantity and the relationship to the outer trade item. Where the company sells the case as a distinct retail or trade offer, also check that the customer-facing description matches its actual contents.

Compare supplier references and physical characteristics

Check the supplier's product number, manufacturer model, variant, revision and any serial or lot information needed for identification. If those agree with the order but the GTIN differs, ask whether packaging, allocation or a product change occurred. If the product reference also differs, consider the possibility of a wrong item or unauthorised substitution. Do not jump from either observation to a definitive diagnosis.

Inspect relevant physical characteristics: connector, dimensions, colour, included accessories, model marking and instructions. For electronics, superficially identical connectors can have different power or data capabilities. A warehouse employee should record the observable difference rather than certify technical compatibility beyond their authority. Material questions belong with a competent product reviewer and supplier documentation.

Use the GS1 GTIN Management Standard when evaluating whether the relevant product or packaging change warrants a different identifier. The rules require scenario-specific interpretation. A changed box design does not always imply a new trade item, while a meaningful change in quantity or product characteristics may require different identification. Do not invent a new GTIN to resolve a local mismatch.

Quarantine stock without losing its physical count

Place unresolved goods in the appropriate restricted state. This does not mean they disappear from the warehouse: staff should know how many units exist, where they are and which receipt owns the exception. The restriction prevents an unidentified variant from being picked or allocated to a customer before its identity is confirmed.

Keep a named owner and a next review date. A pallet put aside without an exception reference can become invisible inventory. Where safe and appropriate, other correctly identified items in the same shipment may proceed independently, but do not release a mixed carton whose composition remains uncertain. The actual scope of restriction should follow the available evidence.

If damaged labels are the sole issue and an approved alternative identifier permits reliable verification, record how that conclusion was reached. If the goods themselves differ from the order, the matter may require a commercial decision, not just a barcode correction. Warehouse availability and supplier settlement remain distinct tracks.

Ask suppliers precise, answerable questions

Send the purchase-order line, supplier reference, expected code, observed code, photographs and affected packaging level. Ask whether the physical goods are the ordered product, whether a new trade-item identifier was assigned, what changed, and from which production or dispatch date the change applies. Request supporting specifications or packing information when relevant. A reply saying 'it is the same' may not explain a changed case quantity or component.

Record written confirmation and its applicability. A supplier might have introduced a new code for future production while old and new stock coexist. Map both as appropriate with effective dates rather than overwriting every historical receipt. If a confirmed replacement model was shipped in error, purchasing must determine whether the business accepts it under the actual agreement.

Do not treat the supplier's ability to provide a label as proof that a product is safe or suitable for sale. Barcode validity, technical conformity and commercial acceptance answer different questions. Escalate any product-safety concern through the relevant process.

Update authoritative records, then dependent systems

Once the identity is resolved, decide whether to add an alias barcode to an existing item, correct a pack-level mapping, create or activate a separate product identity, or process a wrong-product return. Record who approved the change and which evidence it follows. Avoid using an undocumented alias that allows several materially different products to scan as one SKU.

Propagate legitimate changes to receiving, inventory, purchasing, picking, ecommerce and customer support as needed. If the pack count changed, check purchase price units and available stock quantities. If the model changed, review product images and compatibility text. A successful product-master edit is not evidence that a marketplace or warehouse scanner has received the same revision.

Preserve historic identity. Earlier customers may own the predecessor item and need the correct manual or return route. Stock received before the change may still carry the older label. An audit trail helps staff differentiate a valid transition from an accidental overwrite.

Test the scan and stock movement before releasing goods

Run a controlled goods-in transaction using the corrected identity. Confirm the item and expected pack quantity, then check the resulting stock record and pick instruction. Include at least one old and new package where both may circulate. A scan returning a green screen is insufficient if the system posts the wrong unit count or chooses the wrong variant.

Check duplicate receipt protection. If the first transaction was partially saved before the mismatch was noticed, reprocessing the entire delivery may double-stock it. Review existing events and reconcile exact quantities before retrying. Where the system has no safe reversal, escalate to the authorised stock-control owner instead of disguising the difference with another unverified barcode mapping.

Close the exception only once the physical goods, product identity, supplier explanation and resulting ledger agree. If one element remains unresolved, record its owner rather than marking the entire case completed for reporting convenience.

Use repeated mismatches to improve onboarding

Review confirmed mismatch reasons by supplier, product family and packaging revision. Repeated carton-code problems may indicate missing pack hierarchy fields; repeated replacement-model confusion may indicate weak supplier change notices. Scanner configuration issues are an internal training or technical concern. Avoid attributing every mismatch to poor supplier performance.

Use a small onboarding checklist for new items: assigned identifiers, expected unit and case labels, pack conversion, product version and an approved source document. First-delivery verification should check that the real cartons match the stated data. A supplier may still make legitimate changes later; the process should make them traceable, not forbid change.

Goods-in barcode control is successful when staff can answer which physical trade item arrived, what quantity it represents and why the system should recognise it. Preserve the observed code, verify the package level and product, then approve the mapping before moving goods into unrestricted stock. That sequence prevents a small scanning exception from becoming a customer-facing identity error.