Attributes, variants, SKUs, and barcodes: distinguishing similar products

A shirt can have a size and colour. A cable can have a diameter and length. A component can have a capacity or material grade. These characteristics may distinguish products that share a family name but are not interchangeable.

An attribute describes a characteristic. A variant represents a particular combination that matters to the business. A SKU or barcode identifies the relevant record for commercial or operational use.

When a characteristic needs a variant

The decision depends on whether the characteristic changes what is stocked, ordered, priced, or supplied. If medium and large shirts must be counted separately, size is operationally important. A descriptive note that does not change fulfilment may not need the same treatment.

DNA supports attribute definitions with several data types, including text, number, date, boolean, and controlled selections. Category relationships can make attributes available to related items. Variant generation uses selected dropdown values to produce combinations.

A practical combination

An item has two colours and three sizes. Generating every combination produces six possible variants. If the supplier sells only four of those combinations, the business should not assume all six represent a genuine stocked offering.

This is a general design principle: a mathematically possible combination is not automatically a valid commercial product. The actual product range and stock responsibilities determine the useful variants.

DNA's variant information can include SKU, barcode, and pricing. The matrix representation helps understand combinations. The reviewed form checks duplicate barcodes within the current variants and against loaded item rows; that frontend check alone does not prove uniqueness across every server record.

Why identification matters in transactions

A correct family with the wrong variant is still the wrong supply. Purchase, receipt, transfer, and sales records need to refer to the version actually involved. Otherwise, one variant can appear available while another is physically on the shelf.

The barcode should therefore correspond to the intended item or variant identity. A duplicate or reused code can undermine scanning and later investigation even when the product descriptions look clear.

Changes after use begins

Adding another characteristic to an established product family deserves care. Existing stock and transaction history already refer to the earlier identities. The business needs a coherent explanation of which new combinations apply and how existing goods remain identifiable.

Attributes should improve understanding rather than create unnecessary complexity. A small set of meaningful characteristics is more useful than a large set of inconsistently completed fields.

The outcome is precise product identity: the buyer, warehouse, and customer can all refer to the same version, and the system can preserve its quantity and history separately where required.