SKU vs. barcode on Shopify: what is the difference?
Understand what Shopify SKUs and barcodes identify, when each field is used, and why one value should not automatically be copied into the other.
A SKU and a barcode can appear beside each other on a Shopify variant, but they solve different identification problems. The SKU belongs to the store's internal inventory system. The barcode usually carries a standardized product identifier that scanners, retailers, and sales channels can recognize.
A Shopify SKU is an internal inventory code
A stock keeping unit is a code the business creates to distinguish the items it buys, stores, reports on, and fulfills. Shopify stores the SKU at variant level, so a blue medium shirt and a blue large shirt can have separate internal codes. The format can reflect the attributes staff use when picking an order, as long as it remains stable and unique.
Shopify describes the SKU as optional, while recommending unique values for inventory tracking, reporting, fulfillment, and third-party integrations. A warehouse or ERP may make the field operationally required even when Shopify itself allows it to be blank. See Shopify's current guidance onusing SKUs to manage inventory.
A barcode identifies a trade item for scanning and distribution
The Shopify barcode field commonly contains a GTIN such as a UPC, EAN, or ISBN. These values are assigned outside an individual retailer so the same packaged item can be recognized across stores and systems. The number is printed below a scannable barcode symbol, but the stored identifier and the printed symbol are not the same thing.
Barcodes become important when products pass through POS, wholesale, a warehouse, or a marketplace. Shopify'sbarcode guiderecommends a distinct barcode for each variant that needs identification in the supply chain.
SKU answers “which item is this in our operation?” Barcode answers “which assigned trade item is this across scanners and external systems?” A store can need either field, both fields, or neither one.
Do not copy one value into both fields by default
An internal SKU is not automatically a valid GTIN. Copying it into the barcode field can create an identifier that has the wrong length or check digit and was never assigned to the product. The reverse also removes useful separation: if the business later changes its internal naming convention, a manufacturer GTIN should not change with it.
If the same value is deliberately used by a closed internal workflow, document which system owns it and confirm that no sales channel interprets it as an assigned GTIN. For products sold through Google, review the currentGoogle & YouTube channel identifier requirementsbefore filling the field.
Audit each field against its real consumer
Review SKUs for uniqueness, consistency, invisible whitespace, and exact matches with the warehouse or inventory system. Review barcodes for assignment to the correct variant, supported GTIN structure, check digits, and duplicates. A value can be valid in one field and still be wrong for the workflow consuming it.
If the catalog already contains years of mixed identifier data, begin with afull SKU and barcode auditbefore imposing a new format. The first goal is to understand what each existing value does, not to make every row look identical.