Multiple barcodes per variant on Shopify

On stores with an ERP behind them, barcodes cause a quiet kind of mess. The manufacturer's UPC lives in Shopify. The private-label EAN lives in the ERP. The marketplace ASIN lives in someone's spreadsheet. Scanning the wrong one at a till or in the warehouse finds nothing.

Shopify has fixed the root of that. Product variants can now hold up to 20 barcodes, each with a type and format validation, and any of them identifies the product. The first barcode stays the default wherever only one is expected, so labels, feeds and apps keep working. For most stores it's an opportunity to tidy up, not a forced change.

What changed?

Shopify announced the update in its changelog on the 8th of September 2026. Until now, a variant held one barcode. Items that arrived with several identifiers meant choosing one and tracking the rest elsewhere.

Now you can do the following.

• Store up to 20 barcodes on each variant.
• Give each one a type, such as UPC, EAN, ISBN, GTIN, ASIN or Custom. Shopify checks the format.
• Add, scan and remove barcodes on the variant page or in the mobile app.
• Update many variants at once in the bulk editor.
• Import and export them through a new Variant Barcodes CSV column.
• Scan and search variants in POS using any of their barcodes, as well as the SKU.

Existing barcodes don't change and nothing needs migrating.

Why the first barcode matters

Shopify is clear on this point. The first barcode on a variant is still the one used wherever a single barcode is expected. Sales channels keep using it.

That's what keeps the change safe. Your printed labels, your channel feeds and the third party apps you rely on all keep reading the same value they read yesterday.

It also means the order of barcodes is now a decision. If you add a second code, check the one in first position is the one your channels should receive. Getting that wrong won't break the store, but it could send the wrong identifier into a feed. Clear identifiers also help products surface through Shopify Agentic Storefronts in ChatGPT, Copilot and Shop.

What it means for your ERP integration

This is where we'd spend the most thought. Most ERP integrations we build or inherit sync a single barcode field. That still works, because Shopify keeps the first barcode in the same role.

The opportunity is in the extra codes. Many ERPs hold several identifiers for an item, such as a supplier code and your own private-label code. Until now, only one could travel to Shopify. Now they all could.

Before you change anything, answer three questions.

1. Which system owns barcodes? Usually the ERP, in which case codes shouldn't be edited by hand in Shopify.
2. Which barcode is the primary? Agree which one goes first, and make sure the sync always puts it there.
3. Which extra codes are worth syncing? Only the ones someone actually scans or searches for.

Field ownership is a core part of any sync, and our guide to what a Shopify ERP integration involves covers how we set it. Changing an integration to write extra barcodes is a scoped piece of work, and it needs testing before it touches the live catalogue.

Who should act on this?

Most stores don't need to do anything. If you sell your own products with one code each, carry on as you are.

It's worth a look if any of these sound familiar.

• You sell branded products from several manufacturers, each with their own barcode, alongside your own labels.
• Your warehouse or shop team scans codes that aren't the one in Shopify.
• You keep a spreadsheet mapping one code to another.
• You sell on a marketplace that needs an identifier different from your main barcode.
• You run POS, and staff search for products by a code the variant doesn't hold.

Trade businesses tend to tick several of these. Is your catalogue overdue a clean-up anyway? Our guide to getting trade product data ready before a Shopify build sets out the order we'd work in.

A sensible way to roll it out

We'd start small rather than bulk-loading every code you've ever held.

1. Export a sample of variants and check the barcodes already there.
2. Agree which code stays in first position for each product type.
3. Pick the extra codes with a clear use, such as warehouse scanning or POS search.
4. Test the Variant Barcodes CSV column on a handful of products.
5. Check your channel feeds and apps still receive the expected barcode.
6. Update the ERP sync, or the import process, so new products follow the same rules.
7. Retire the spreadsheet once the codes live in Shopify.

The last step is the payoff. One place for every identifier is easier to trust than three.

Where parallel helps

We build and look after ERP integrations for Business Central, Odoo, NetSuite, SAP and Sage, and changes like this are part of that work. We'll map which codes should travel, update the sync and test it before it touches your live catalogue. See how we approach apps and integrations.

If you're not sure how your barcodes flow today, book a call and we'll trace it with you.