SKU vs UPC and EAN Barcodes: What's the Difference?
See how internal SKUs relate to UPC and EAN barcodes, why both may be useful, and how product records connect a scan to the right item.
A delivery arrives with UPC or EAN barcodes already printed on the products. As you organize the product records, you also have internal SKUs to account for. Do you need another number, another label, or simply a connection between the information you already have?
A SKU is your business's internal inventory reference. UPC and EAN are retail barcode types that carry a standardized product identifier called a GTIN. The practical difference is between the internal reference you use to manage stock and the retail product identifier represented on the package.
Those two identifiers can belong to the same product record. Understanding how they relate helps you fill the right fields, avoid unnecessary relabeling, and check why a scan finds—or fails to find—a product.
Where UPC and EAN fit in the barcode family
Barcode is the broad term for machine-readable symbols that carry data. UPC-A and EAN-13 are examples of specific barcode types within that family. They are familiar linear barcodes used on retail products.
A SKU belongs to a different layer: it is an identifier used inside a business. It is not a barcode type. A SKU can be represented in a suitable barcode when the barcode format, label software, and receiving system support that use.
For UPC and EAN retail barcodes, the identifier carried by the symbol is a GTIN, or Global Trade Item Number. Keep the two layers clear:
- The identifier: an internal SKU or, for the retail product-identification role discussed here, a GTIN.
- The symbol used to read it: a suitable barcode format. UPC and EAN are specific retail formats that carry GTINs.
This is why an internal SKU label and a UPC label may both have scannable bars while serving different purposes. The barcode is the reading format; you still need to know what value it represents and how the application uses that value.
How internal SKUs and retail identifiers differ
When comparing a SKU with a UPC or EAN barcode, the useful comparison is their role in your business. In the retail column below, the product identifier is the GTIN carried by the barcode.
| What you are comparing | Internal SKU | Retail identifier carried by UPC/EAN |
|---|---|---|
| Main job | Identify stock for internal tracking and sales reporting | Identify a trade item when exchanging product data with trading partners |
| Rules behind the value | Your business's SKU convention, subject to the systems using it | The applicable standardized identification requirements |
| How you use it | Refer to the intended product or variant in your own catalog | Associate the retail identifier with the correct product data in the receiving system |
| Relationship to a printed barcode | May be encoded in a suitable barcode for an internal workflow | Encoded in a UPC or EAN symbol appropriate to that product and workflow |
| What makes a scan useful | The application can match the captured value to the intended item | The receiving system has the product record associated with the captured GTIN |
For example, a store can keep its own SKU for a shirt while recording the retail identifier supplied with that shirt. Both values point to the same sellable variant. One supports the store's internal organization; the other supports the product-data exchange needed for its retail workflow.
Why keep a SKU when a product already has a retail barcode?
A SKU gives your team a reference designed around its own catalog for tracking inventory and reporting sales. A clear naming convention helps staff distinguish the variants they pick, count, and report on.
Suppose a shirt comes in blue medium and blue large. To track their stock separately, give each separately managed variant a distinct internal reference. You might use recognizable abbreviations or a numeric convention, provided the values work with the records and applications your team uses.
The SKU can therefore remain useful even when the package already has a UPC or EAN barcode. The retail identifier does not automatically reproduce the internal naming convention your team prefers.
Equally, an internally assigned SKU does not automatically become the standardized identifier a trading partner requires. Printing it as a barcode changes how it can be read; it does not change the rules under which the value was assigned.
Keeping both roles clear does not always require two different values or two labels. That depends on how your systems connect the identifiers.
Can your SKU match the number in a UPC or EAN barcode?
It may, if that value also meets your internal SKU rules and the requirements of your connected systems. Reusing a verified retail identifier as your SKU is a possible catalog choice; it is not a requirement for every business.
The direction of that decision matters. Using an existing product identifier as an internal reference is different from taking an arbitrary internal SKU and treating it as a valid retail GTIN. Copying a value between fields does not establish that it is the correct identifier for the product or that a trading partner will accept it.
This also answers “Can a SKU and barcode be the same?” A SKU is a value; a barcode is a symbol. What can match is the SKU and the value encoded in the symbol. The symbol itself is the means of reading that value.
Before reusing a value, check that it identifies the intended sellable variant, works in the internal applications that use the SKU, and satisfies the receiving channel's requirements. If separate values work better, link them to the same product record.
How to connect the identifiers in your product system
Start with the information you need to connect: the exact product or variant, its internal SKU, and the retail identifier used for scanning. Whether you manage these details in a product spreadsheet, an inventory application, or a checkout system, use that relationship to guide your review.
The worksheet below is a suggested way to organize those details. Field names and lookup features vary by system, so check how your own setup stores and connects them:
| Part of the setup | Intended information | What to check |
|---|---|---|
| Product or variant record | The exact item being stocked and sold | Confirm the intended size, color, or other option |
| Internal identifier (SKU) | Your internal inventory reference | Match the convention and workflow used by your team |
| Retail identifier, such as a GTIN | The identifier the receiving workflow expects | For a UPC/EAN workflow, verify the relevant product GTIN |
| Printed symbol | A barcode carrying the intended value | Confirm its type and captured data suit the workflow |
| Receiving product record | Product data linked to the captured identifier | Confirm the application retrieves the intended item |
A possible workflow is: scan the UPC or EAN → capture its GTIN → find the matching variant → use the SKU associated with that record for internal work. One scan can connect the retail identifier with your internal reference when the application supports that arrangement.
Before adding another label or changing identifiers in bulk, check which value is received and how the product lookup works. If you use a spreadsheet, keep the identifiers clearly associated with the same item; if you use software, check its actual search and import rules before relying on that association.
A successful scan still needs a matching product record
A scanner can read the barcode correctly while the application fails to find the product. The symbol may be readable, but the required data relationship may be missing.
GS1 US explains this handoff for retail: brand owners must send product, GTIN, and barcode data to their trading partners. The partner can then populate its database so a scanned GTIN retrieves the associated product information.
When checking a problem, separate three steps:
- Read the value. Compare the captured data with the identifier that should be encoded in the label.
- Find the item. Check which product or variant the application matches. If there is no result, inspect the stored identifier and lookup field.
- Complete the operation. Confirm that the intended stock, receiving, or checkout action happens for that item.
If the expected identifier reaches the application but no product appears, investigate the mapping before redesigning the barcode. If the wrong product appears, preserve both the captured value and the matched record so you can trace the mismatch.
Choose a setup that fits your inventory and sales channels
For internal stock management, establish consistent SKUs and confirm the identifier your inventory application expects. Use a suitable barcode if scanning is part of that process.
For retail partners, confirm the required product identifier and barcode format, then share the associated product data. Keep your internal SKU linked to the same item if it helps your own operations.
For products already carrying UPC or EAN barcodes, check whether your system can use the existing retail identifier to reach the right record before printing an additional label.
Test one item through the full workflow before expanding to the rest of the catalog. The goal is a dependable connection from the printed barcode to the correct product record, with the internal SKU and retail identifier each serving a clear purpose.