Resolving Sneaker Size Variants in a Style-Code Barcode Lookup

A style code is not a sellable-unit identifier

The confusion starts when a sourcing sheet has one style code and an import tool wants one barcode. A style code groups a model and colorway, while a barcode, usually a GTIN, identifies one sellable unit. Each product variation needs its own GTIN: each size, each colour, and each combination of size and colour. That means one style code can legitimately map to many barcodes, and collapsing them into a single inventory row is the source of wrong-size attachments. See SKU Lookup vs Barcode Lookup for Resellers for the jobs each identifier performs.

What a style-code lookup returns

Use a style-code lookup when you need to enumerate the barcodes tied to a model and colorway. The lookup response can return multiple barcode records for the same style code, and each record carries its own size metadata plus a barcode type and value. Some responses also indicate whether a barcode record is verified rather than inferred. When a size-run view is requested, the response groups records by numeric size and orders them, so you can see which sizes have a barcode and where a size is missing. Missing does not mean the size does not exist; it means the catalog does not currently hold that barcode.

Resolve the exact variant before writing inventory

Treat the style code as the parent and the barcode as the child. When you import, store style code, size, colorway if present, and the barcode value as separate fields. Do not assign the first barcode in a style-code response to every size. Instead, match the size on the incoming unit to the size field on the barcode record. If you need to compare or store identifiers across systems, normalize GTIN widths first; a GTIN converter helps prevent a 12-digit and 13-digit form being treated as different products. Validate each barcode before relying on it, as covered in How to Validate a Barcode.

1. Start with the style code and request a size run when the lookup supports it.
2. Read each returned barcode record's size value and verification marker.
3. Match the unit's size to that size value instead of taking the first row.
4. If two records describe the same size, prefer the verified record.
5. If no size matches, flag the row for review rather than guessing.

Colorway and size need separate identity

Variant identity does not stop at size. If the same model comes in multiple colors, each color is a separate variation and needs its own GTIN. Product feeds likewise need a unique GTIN for each variant. In a sneaker context, that means a style-code lookup that returns many barcode rows may be giving you the size run for one colorway, while a different colorway needs a different set of rows. Use the colorway field on the product record to confirm which variant set you are resolving; do not assume every row under a style code belongs to the colorway you are holding.

A practical resolution workflow

This keeps one-to-many mappings from becoming many-to-one mistakes. It also makes later audits possible: if a barcode turns out to be missing, you can see whether the import guessed or whether the catalog simply lacked that variant. Barcode data confirms product identity; it does not prove authenticity, and a missing size row is a coverage gap, not evidence that the shoe is fake.

• Store style code, size, colorway, and barcode in separate columns.
• Keep the lookup response's size value attached to the barcode value.
• Do not overwrite one size's barcode with another size's barcode.
• Normalize GTIN width before matching across systems.
• Validate the final barcode before syncing to inventory.