Skip to content

Shopify Dude Answer

Shopify Variants Can Now Have Multiple Barcodes: Stop Treating barcode as the Full Identifier List

Shopify’s 2026-10 Admin API adds a barcodes connection to ProductVariant and deprecates the single barcode field. Here’s how to update product, ERP, PIM, and POS integrations safely.

Quick answer

In Shopify Admin API 2026-10, ProductVariant has a barcodes connection for up to 20 typed barcodes. The older singular ProductVariant.barcode field is deprecated and returns only the first barcode. Integrations that synchronize UPC, EAN, ISBN, GTIN, or other identifiers should stop treating the singular field as the complete barcode set.

On this page

Why this matters in real integrations

A single barcode was easy to map into an ERP or PIM column, but it encouraged a fragile assumption: one Shopify variant equals one identifier. That breaks down when the same sellable variant legitimately has multiple typed identifiers or an upstream system retains more than one barcode.

The dangerous failure mode is not an obvious API error. Old code can continue reading barcode and appear to work while silently ignoring every barcode after the first.

Practical implementation details

When adopting API version 2026-10, audit GraphQL fragments, bulk exports, ERP mappings, product feeds, warehouse integrations, and database schemas that store one Shopify barcode. Read the barcodes connection when you need the complete identifier set.

Keep the singular field only as a temporary compatibility path where a downstream system genuinely accepts one value. Document which barcode becomes canonical rather than relying indefinitely on “first item wins.”

Also separate SKU from barcode logic. A SKU is an internal merchant identifier; a barcode is a standardized or scannable product identifier. Treating them as interchangeable creates reconciliation problems.

Common misunderstanding

“The deprecated barcode field stops working in 2026-10.” No. Shopify says it returns the first entry. That compatibility behavior is why this migration can be missed: an integration may keep running while returning incomplete data.

How to test this

  1. Use a test variant with more than one barcode.
  2. Query both the deprecated singular field and the new connection.
  3. Confirm the integration persists every expected identifier and type.
  4. Run an update from the upstream system and verify secondary identifiers survive.
  5. Test exports and feeds that historically expected one barcode column.
  6. Log variants with multiple barcodes when a legacy destination accepts only one value.

Sources and further reading

Keep going

More Shopify Answers

Browse the library