Separating a Product Barcode From an Individual Asset Identity
Avoid assigning one product barcode to multiple asset records by distinguishing model identifiers, serial numbers and the organisation's permanent asset ID.
Can a supplier barcode be used as the unique asset identifier?
Only after confirming what the barcode identifies and whether it is unique to that individual item. A product or model code can legitimately appear on many units. Capture supplier codes in separate fields, test uniqueness across the population and use a controlled permanent asset identifier where the existing code does not identify one specific asset.
A field team scans the barcode on a monitor carton and assumes the resulting number identifies the monitor. The next carton produces the same value. The scanner has worked correctly, but the team has captured a product-level code. Recognising this distinction prevents duplicate register keys and incorrect matching during bulk equipment deliveries.
Identify what each printed code means
Inspect the label layout and available supplier documentation before configuring the capture form. Equipment can carry a product barcode, serial barcode, service reference and an internal asset label at the same time. Record the meaning of each field. Do not infer that a long number must be unique or that the largest barcode is the serial.
GS1's serialisation guidance distinguishes base product identification from individual instances and identifies keys for specific assets. That distinction is useful background when designing capture fields, but it does not prove what an unlabelled supplier barcode contains. Where necessary, ask the supplier to identify the code and confirm whether its uniqueness applies within a model, manufacturer or wider namespace.
Test the assumption on real units
Scan several units of the same model and compare their captured values. Include items from different deliveries if the scheme will be used across the organisation. If values repeat, determine whether the code is intentionally product-level or whether data was copied incorrectly. Keep the original scan result alongside the interpretation during the pilot.
Check packaging and equipment separately. A carton code may identify a package or shipment, while the equipment has its own serial. Avoid retaining packaging identifiers as permanent asset keys unless their role and lifecycle have been deliberately accepted. Once packaging is discarded, staff still need to identify the actual controlled item.
Design the form to prevent repeated confusion
Give the capture fields explicit names such as organisation asset ID, manufacturer serial and product code. Show operators which label to scan for each field using approved examples from the actual equipment. Validate the organisation's unique identifier at submission, but allow legitimate repetition in a product-code field.
When earlier records used a product code as the asset key, create a reviewed correction plan. Preserve the original code as a product attribute, assign individual identities and reconnect purchase, custody and maintenance evidence. Do not overwrite the repeated number without keeping a mapping, because older documents may still use it to describe the delivery population.
Practical Example
Illustrative example: a college receives twelve identical monitors. Their cartons show one repeated product barcode, while each monitor carries a different manufacturer serial. The team records the common product code, captures the individual serials and applies controlled asset tags. The purchase line remains linked to all twelve records without becoming their unique identity.
Action Checklist
- 1.Identify the purpose of each barcode using label context and supplier information.
- 2.Scan several units of the same model to test the claimed uniqueness.
- 3.Capture packaging references separately from identifiers attached to the equipment.
- 4.Use distinct fields for product code, manufacturer serial and organisation asset ID.
- 5.Preserve a correction mapping where historical records confused these identifiers.
Set capture rules that distinguish products from individual assets through Asset Verification Services.