Shopify variants now support multiple barcodes

Author

Felix

Published

September 21, 2026

What Shopify has changed

A product variant can now contain up to 20 barcodes.

Shopify supports the following types, among others

UPC
EAN
ISBN
GTIN
ASIN
Custom

If a standardized barcode type is specified, Shopify validates the value against the corresponding formatting rules. This allows issues such as incorrect lengths or invalid check digits to be detected as soon as the value is entered.

Codes can be added, scanned, and removed directly on the variant page in Shopify Admin. They can also be managed through the Shopify app, the bulk editor, and product CSV files.

What multiple barcodes solve

A product can have multiple real-world identities

A typical example is a retailer who sources the same product from multiple suppliers.

Supplier A uses

4001234567890

Supplier B used

012345678905

The dealer also has an internal code.

Until now, it was necessary to decide which of these would be stored in Shopify's standard barcode field.

The remaining identifiers often ended up in

Metafields
ERP systems
PIM systems
Tables
custom apps

Shopify can now store these identifiers directly on the same product variant.

The variant remains the same

Multiple barcodes do not create additional variants.

All stored codes continue to identify the same ProductVariant object.

That means, for example

Black sneaker, size 42

→ Manufacturer UPC

→ own EAN

→ Marketplace ID

→ internal warehouse code

All codes lead to the same variant.

What doesn't change

The first barcode remains particularly important

Shopify continues to treat the first barcode as the primary barcode.

Systems and sales channels that support only a single barcode will continue to receive this first value.

The order of the barcodes is therefore not merely cosmetic.

For example, if a marketplace requires a GTIN, you should carefully check which barcode appears first.

A useful rule can be

The first barcode is the identifier that should continue to be used as the primary code in existing external systems.

Existing barcodes do not need to be migrated

Existing barcodes will remain unchanged.

Shopify retains the existing barcode as the first entry. Merchants therefore do not need to migrate anything manually just because the new feature is available.

Not every sales channel automatically uses all barcodes

Having multiple codes in Shopify does not automatically mean that a marketplace or app will process all 20 codes.

Shopify explicitly notes that sales channels may continue to use the first barcode if only one barcode is expected.

This is particularly important for marketplace, feed, and ERP integrations.

Management in Shopify Admin

Open variant

In the Shopify admin, first open the desired product and then the relevant variant.

Multiple barcodes can be added to the variant there.

Select barcode type

The appropriate type should be used for standardized product identifiers.

For example

UPC

EAN

GTIN

ISBN

ASIN

Shopify validates typed codes against the corresponding format.

A custom code can be used for your own internal identifiers.

Deliberately set the primary barcode

The first barcode should be chosen carefully.

This remains relevant for systems that continue to use only the traditional single barcode field.

Therefore, before changing the order, it should be checked

which marketplaces are integrated
which ERP interfaces can read the barcode
which apps synchronize product data
which labeling systems are used
which feeds support only one barcode

Add more identifiers

After that, supplier or marketplace identifiers, for example, can be added.

One possible variant could then be structured like this

Primary

EAN

Secondary

UPC

ASIN

Internal Custom Code

Shopify manages all identifiers within the same variant.

Bulk Editing and CSV

For larger product ranges, processing each item individually would hardly be practical.

Shopify therefore also supports multiple barcodes in the bulk editor.

Additionally, the information can be processed via the product CSV import and export.

Shopify uses the following column for this

Variant Barcodes

This allows barcode sets to be imported or exported even for larger product catalogs.

For merchants with tens of thousands of variants, this is far more appealing than maintaining them manually in the admin panel.

Shopify POS can recognize all assigned barcodes

The change is particularly relevant when used with Shopify POS.

Since Shopify POS 11.14, staff have been able to search for or scan variants using any assigned barcode.

That means

A product has three barcodes.

Barcode A is located on the manufacturer's packaging.

Barcode B is located on the store's own label.

Barcode C comes from a different supplier.

When any of these codes is scanned, Shopify POS can still find the same product variant.

This reduces situations where store employees have to manually search for a product by SKU or name.

Typical retail use case

A retailer sells the same water bottle both online and in 30 stores.

The original manufacturer uses a UPC.

Later, the retailer switches suppliers. The new batch has an EAN.

Both products are commercially identical and should use the same Shopify inventory.

Previously, either the stored barcode had to be changed or a separate mapping had to be maintained outside of Shopify.

UPC and EAN can now be assigned to the same variant.

In the store, both versions of the packaging can be scanned and will lead to the same variant.

Multiple suppliers

The same problem can quickly arise in multi-supplier setups as well.

A retailer orders the same product from different distributors depending on availability.

Each distributor may use a different internal or external code.

However, the commerce system remains of interest

Which product is it?

Which variant is it?

Which inventory does it belong to?

Multiple barcodes make it possible to link different physical identifiers to the same commerce identity.

Private Label and Manufacturer Barcode

Another common case is private labeling.

For example, the manufacturer supplies the product with its own UPC.

The retailer sells it under its own brand and also uses its own EAN.

Both identifiers can now exist on the same variant.

The merchant no longer has to decide which identifier is technically lost entirely.

Marketplace-Setups

Marketplaces sometimes use their own or additional product identifiers.

Shopify explicitly lists ASIN as a supported barcode type.

A product can therefore, for example, simultaneously have

EAN

UPC

ASIN

For enterprise setups, however, it is crucial that not every channel automatically uses every identifier.

The first barcode remains relevant for systems that expect only one identifier.

Therefore, the function is no substitute for proper marketplace mapping logic.

ERP and PIM are becoming more important

For larger Shopify stores, the real challenge lies less in adding the second barcode.

What matters is which system is responsible for this data.

For example, a company may have the following architecture

PIM

→ Shopify

→ Online Store

→ POS

→ Marketplace

Parallel

ERP

→ Inventory and Fulfillment

If both the PIM and ERP systems can modify barcodes, it must be clear which system is the authoritative source.

Otherwise, for example, one sync might add an additional barcode, while another sync removes it again shortly afterward.

Meaningful data stewardship

For larger setups, documentation should be provided

Product Master Data

PIM

Commerce Product Model

Shopify

File

ERP or WMS

Barcode-Master

PIM or ERP

The specific breakdown that makes sense depends on the project.

The only important thing is that multiple systems do not independently overwrite the entire barcode list.

API Change for Apps and Integrations

The new admin feature also has a relevant technical aspect.

Shopify is introducing a new barcodes connection for ProductVariant in the GraphQL Admin API model. It can be used to retrieve the complete list of barcodes.

The feature is part of API version 2026-10.

As of September 21, 2026, this API version is still in release candidate status and will become stable on October 1, 2026. Shopify recommends release candidates for development and testing, not for production use.

This is important for existing integrations.

The existing barcode field will be deprecated

Until now, many apps have read only this field

ProductVariant.barcode

Shopify has since marked this field as deprecated. It still works for now.

When scanned, it still returns the first barcode of the variant.

An existing integration may therefore continue to work initially, even though a variant now has, for example, five barcodes.

However, that is precisely where a risk also lies.

The Risk of Silent Data Loss

Suppose a variant has

EAN A

UPC B

ASIN C

A legacy ERP integration still reads only the classic barcode field.

She then only receives

EAN A

Technically, no error occurs.

However, the integration is also unaware that there are two additional barcodes.

In its developer documentation, Shopify explicitly describes this issue as potentially causing silent data truncation. Apps that pass barcodes on to ERP systems, marketplaces, POS systems, or supplier feeds, for example, should therefore be prepared for the new barcodes structure.

Writing barcodes via the API

The logic also changes when writing.

The complete list of barcodes can be managed, among other ways, using the corresponding variant mutations.

There is one important distinction, however.

If the new barcodes input is used, Shopify replaces the complete barcode list for the relevant variant.

Therefore, an integration should not only send the new barcode.

It must also include all existing barcodes that are to be retained.

Simplified

Existing

EAN A

UPC B

New integration would like to

Add ASIN C

Only the following would be incorrect in terms of meaning

Send ASIN C

If the complete barcodes list is replaced, it must instead contain all the desired values.

EAN A

UPC B

ASIN C

This is an important distinction for synchronization architectures.

Do not write to the legacy and new fields at the same time

Shopify also documents that a single variant input cannot set both barcode and barcodes at the same time.

Integrations should therefore have a clear migration path.

For the time being, either the traditional field or the new multi-barcode structure will be used.

Mixing modes within the same change is not supported.

Barcode search is becoming more powerful

The product search using the barcode filter can now take into account any identifier assigned to a variant.

This enables an important enterprise use case.

An external system only knows a supplier's barcode.

Shopify only has the same barcode as a secondary identifier.

A search can still find the right variant.

This can simplify integrations that first need to match products based on incoming identifiers.

Barcode is not the same as SKU

Even with multiple barcodes, the roles of the different identifiers should remain clearly separated.

An SKU is often an internal commercial identifier.

A barcode is primarily a machine-readable form of product identification.

Although both can be used to find a variant, they serve different functions.

A sensible structure could be, for example

SKU

SHOE-BLK-42

EAN

4001234567890

UPC

012345678905

ASIN

B0EXAMPLE

The advantage of the new feature is that these various external product identifiers no longer need to be artificially squeezed into a single field.

When the feature is particularly useful

Retailers with physical stores

Retail is probably the most obvious use case.

If different packaging or suppliers use different codes, store staff can still scan the same variant.

Merchant with multiple suppliers

Products can use the same Shopify product record regardless of the supplier.

Marketplace seller

Additional product identifiers can be managed more centrally in Shopify.

It is still necessary to check which identifier each channel actually uses.

Retailers with PIM or ERP

Companies can align their product data model more closely with reality and synchronize multiple identifiers for each variant.

Companies with catalogs that have evolved over time

Over the years, different barcode schemes may have emerged.

The new model enables gradual consolidation without necessarily having to remove old code immediately.

When multiple barcodes aren't the solution

Different products should not be merged

Just because two products look similar, their barcodes should not be assigned to the same variant.

Multiple barcodes are intended for multiple identifiers of the same product.

Not for multiple different products.

Barcodes do not replace variants

Size 42 and size 43 remain separate variants.

Therefore, your barcodes should also be assigned to the corresponding variants.

Barcodes are no substitute for product data governance

Twenty possible barcodes do not mean that twenty codes should be stored without any structure.

It should be understandable

where a barcode comes from
which standard it complies with
which barcode is primary
which system maintains it
which systems use it

Common Mistakes

Ignore the order of the barcodes

The first barcode remains relevant for older systems and certain channels.

Accidentally reordering items can therefore affect existing integrations.

Automatically consider all apps compatible

Just because Shopify supports multiple barcodes doesn't mean that every installed app can already handle the new structure.

Apps can still only read the first barcode.

ERP Sync overwrites the entire list

If an integration uses the new barcodes input, the entire list can be replaced.

The sync must therefore take existing values into account.

Change primary barcode without tests

Before changing the primary barcode, marketplaces, feeds, POS, ERP, and other product integrations should be tested.

Incorrectly save custom identifiers as a standardized type

An internal code should not be referred to as an EAN or GTIN if it does not comply with the relevant standard.

Shopify validates typed barcodes against its rules.

Moving Primates Perspective
Multiple barcodes may initially seem like a minor improvement in the product admin. In enterprise projects, however, the greater impact lies in the integrations. For years, many existing ERP, PIM, and marketplace interfaces have assumed that each Shopify variant has exactly one barcode. These systems will continue to work at first, but may only recognize the primary value. That is precisely what makes the change easy to overlook. Before rolling it out widely, it is therefore important to determine which system is responsible for barcode data, which interfaces support multiple values, and which code must remain in the first position. Only then should the product catalog be expanded systematically.

Technical Implications for Larger Stores

The product model is becoming more realistic

Until now, the simplified structure often looked like this

Product

→ Variant

→ a barcode

Now it can look like this

Product

→ Variant

→ primary barcode

→ Supplier barcode

→ Marketplace-ID

→ internal barcode

This models physical product processes much more realistically.

Integrations must understand lists instead of individual values

This is probably the most important technical change.

Off

barcode

is becoming conceptual

barcodes[]

An integration must therefore decide

Does it only read the primary barcode?
Does it read all barcodes?
what types does she need
Is she allowed to modify the list?
How does it prevent other people's codes from being deleted?

API version 2026-10 should be prepared

The complete new GraphQL structure is currently available in API version 2026-10.

This will remain a release candidate until October 1, 2026.

Development teams can already test the integration and prepare for the stable release.

According to Shopify, the latest stable API version should continue to be used for production applications.

Legacy field requires a migration plan

The classic ProductVariant.barcode field is deprecated but continues to work.

As a result, there is no immediate need to migrate.

For apps that will be maintained over the long term, there should still be a plan for supporting the complete list of barcodes.

Shopify has not yet announced a final removal date and says it will communicate this separately with sufficient advance notice for the API.

POS should be part of the test

Shopify POS 11.14 can already use any associated barcode to find the variant.

Retailers should therefore not only test the admin interface.

A realistic test should include actual scanners, packaging, and a variety of in-store scenarios.

Pre-Go-Live Checklist

Has it been defined which system manages the barcode master data?
Has it been decided which barcode should appear first for each variant?
Have ERP and PIM integrations been tested with multiple barcodes?
Have marketplace feeds been checked for their barcode logic?
Have installed apps been checked for compatibility?
Are standardized barcode types being used correctly?
Have CSV imports with multiple barcodes been tested?
Has Shopify POS been tested with all relevant codes?
Has it been verified whether existing integrations only read the old barcode field?
Has a migration plan been prepared for the new GraphQL structure?

Summary

Since September 8, 2026, Shopify has supported up to 20 barcodes per product variant.
Supported types include, but are not limited to, UPC, EAN, ISBN, GTIN, and ASIN.
Standardized barcodes are validated against their formatting rules.
Custom internal codes can also be saved.
The first barcode remains the primary value for systems that support only one barcode.
Existing barcodes will remain valid and do not need to be migrated.
Bulk Editor and product CSV support the new structure.
Shopify POS 11.14 can find variants using any of their assigned barcodes.
With version 2026-10, the GraphQL Admin API will receive a complete barcodes structure.
API version 2026-10 is currently still in release candidate status.
The existing single barcode field is deprecated but continues to work.
Before using enterprise shops, businesses should primarily evaluate ERP, PIM, marketplace, and POS integrations.

Frequently Asked Questions

How many barcodes can a Shopify variant have?

A product variant supports up to 20 barcodes. Each barcode can also have a barcode type.

Which barcode types does Shopify support?

Shopify supports UPC, EAN, ISBN, GTIN, and ASIN, among others. Custom values can also be used for non-standardized internal identifiers.

Which barcode do distribution channels use?

If a sales channel expects only a single barcode, Shopify will continue to use the variant's first barcode. Therefore, its position should be managed carefully.

Can Shopify POS scan any barcode?

Starting with version 11.14, Shopify POS can find a variant using any of its assigned barcodes. The additional codes must first be added to the variant.

Do existing barcodes need to be migrated?

No. Existing barcode values are retained and will continue to be used as the primary barcode.

Do custom apps need to be adapted?

Not immediately. The existing ProductVariant.barcode field will continue to work, but it only returns the primary barcode. Apps that need the complete list of barcodes should plan to use the new GraphQL structure introduced in API version 2026-10.