Guides
SKU vs GTIN
SKUs organize products inside your operation; GTINs identify trade items across trading partners and retail systems.
Keep SKU logic internal
SKUs organize products inside your operation; GTINs identify trade items across trading partners and retail systems. SKUs are controlled by your business, so optimize them for stable internal operations rather than trying to make them look like UPCs or GTINs.
Use stable attributes only
Include only attributes needed to distinguish sellable or stockable variants, and avoid values that change frequently such as a temporary campaign or current storage location.
Design for uniqueness and scanning
Use a deterministic separator/abbreviation rule, preserve uniqueness across channels and keep the result short enough for warehouse staff to read or type when a scanner is unavailable.
Protect the product master
Store SKU, GTIN and supplier identifiers in separate fields. Combining them into one overloaded field makes marketplace imports, purchasing and later migrations harder to audit.
Test before bulk import
Generate a sample across several product families, check for collisions and confirm that ecommerce, POS and inventory systems preserve the exact SKU characters before processing the whole catalog.
Evidence to keep
Use this distinction when designing product-master fields for sku vs gtin. Store the original identifier as text, keep the barcode symbology in a separate field when needed, and record which system assigned or owns each internal value. That structure makes conversions and label generation easier to audit later.
Review the boundary conditions
Most errors around sku vs gtin appear at boundaries: zero demand, a missing leading digit, the maximum field length, a variable-length GS1 field followed by another AI, or a printer size that rounds badly to whole dots. Check those boundary conditions deliberately instead of testing only one typical record. A tool that works for the middle of the range can still fail exactly where production data is most fragile.
Operational scenario
When sku vs gtin is part of replenishment planning, store the date range used to compute averages. A daily-demand average from a promotion month should not silently become a permanent baseline, and a supplier lead time measured before a process change may no longer describe current performance.
Downstream hand-off
If the output of sku vs gtin is copied into another spreadsheet, mark the identifier column as text before paste/import. That is especially important for UPC, EAN, GTIN, GLN and SSCC values because spreadsheet numeric conversion can remove leading zeros or display long values in scientific notation.
Technical references
Sources used on this page
- How to create a GTIN — GS1
Official guidance on constructing a GTIN from a licensed GS1 Company Prefix, item reference and check digit.
QiiChain summarizes source material and applies it to the tool or workflow. The linked source remains authoritative for its own standard or product documentation.