Uncategorized

Shopify POS Multiple Barcodes: How to Use GTIN, EAN, ASIN and Supplier Codes on One Variant

As of September 2026, Shopify POS v11.14 can identify the same product variant using any barcode associated with that variant. That means a store no longer has to choose one physical code and force every supplier, package or sales channel to use it. A variant can be found by scanning or searching an associated GTIN, EAN, ASIN, SKU-based code or another barcode that has first been linked to the variant in Shopify Admin.

The feature is most useful when the product itself is the same but the code printed on it changes between suppliers, packaging runs or channels. It does not make different products interchangeable, and it does not remove the need for a clean SKU and variant structure.

What changed in Shopify POS v11.14?

Previously, a merchant often treated the main barcode field as the single scannable identifier for a variant. If a supplier printed a different code, staff had to search manually by product title or SKU, relabel stock, or use a separate mapping system.

With the September 1 update, Shopify POS can pull up the correct variant when staff scan or search any barcode associated with that variant. The additional codes have to be associated with the product variant in Shopify Admin first.

This is a lookup improvement. It does not merge inventory items, change stock quantities or create a new variant when a barcode is scanned.

Four cases where multiple barcodes solve a real retail problem

1. Two suppliers, one identical product

Supplier A ships a product with EAN A. Supplier B ships the exact same sellable item with another supplier-specific code. If both units truly represent the same variant, staff can scan either code and reach the same Shopify variant.

2. Packaging changed but the sellable item did not

A brand redesigns the outer box and changes or adds a code while older packaging remains on shelves. Associating both identifiers can reduce “item not found” errors during the transition.

3. Marketplace identifier vs retail barcode

A merchant may need an ASIN or channel-related identifier for operational lookup while the physical product uses GTIN/EAN. Multiple associated barcodes allow staff to search without overwriting the primary code every time.

4. Internal or SKU-based labels

A warehouse or store may apply an internal scannable code to products that arrive without a convenient retail barcode. If the internal label maps to the same variant, POS can still resolve the product.

One variant should still mean one sellable configuration

Multiple barcodes are useful only when all codes point to the same product variant. Do not use the feature to hide a bad catalog model.

Keep separate variants when any customer-facing or fulfillment-critical property differs, such as:

  • size;
  • colour;
  • pack quantity;
  • voltage or regional specification;
  • material or formulation;
  • bundle contents;
  • warranty or market-specific configuration.

If a 250 ml bottle and a 500 ml bottle share a supplier family code, they are still different variants. Associating the same scannable identifier with both would create ambiguity rather than convenience.

Primary barcode vs additional barcodes

Choose a primary identifier that makes sense for your wider catalog and integrations. Additional barcodes should expand lookup, not replace catalog governance.

A useful internal record can contain:

Field Example role
SKU merchant-controlled internal identity
Primary barcode main retail barcode
Additional barcode 1 supplier packaging code
Additional barcode 2 legacy packaging code
Additional barcode 3 marketplace or internal label

Keep the reason for each extra code somewhere your operations team understands. A long list of unexplained identifiers becomes difficult to audit months later.

Why this matters during receiving, not only checkout

The feature can reduce manual lookups when stock arrives with a barcode that is not the one staff normally see. That is especially useful for retailers who buy the same product from several distributors.

However, scanning the correct variant does not prove that the received quantity, cost or supplier reference is correct. Receiving still needs its own checks:

  • purchase or transfer quantity;
  • variant and pack size;
  • location;
  • cost data;
  • damaged or unavailable units.

Shopify also changed how inventory reporting works from September 1. If you review stock reports, read Shopify Inventory Reports: On-Hand vs Available Stock so barcode cleanup is not confused with the separate reporting definition change.

Common mistakes when adding more barcodes

Adding a code before proving product identity

Two visually similar products can have different specifications. Verify supplier part numbers and the actual product before mapping codes.

Reusing one code across different variants

A barcode should resolve unambiguously. If the same number appears on two active variants, investigate the catalog or supplier data instead of letting staff choose at checkout.

Deleting the old code too early

If old packaging is still physically in stores, removing the old identifier can recreate the original lookup problem.

Assuming every integration understands additional barcodes

POS support does not guarantee that an ERP, WMS, marketplace app or custom API integration uses the same field set. Test external systems separately.

A safe rollout for a large catalog

  1. Update Shopify POS devices to v11.14 or later.
  2. Choose a small product family with known duplicate/alternate codes.
  3. Verify that every code maps to exactly one variant.
  4. Add the barcodes in Shopify Admin.
  5. Test scanning at checkout.
  6. Test product search.
  7. Test receiving or inventory workflows used by your staff.
  8. Check any connected ERP/WMS or marketplace system.
  9. Train staff not to create a new product simply because a barcode is unfamiliar.
  10. Expand to the rest of the catalog only after the pilot is clean.

Use multiple barcodes to reduce friction, not to avoid data cleanup

The best use of the feature is controlled equivalence: several physical or channel identifiers, one real Shopify variant. If your catalog already contains duplicate variants for the same item, first decide which record is the source of truth. Otherwise multiple barcodes can make a duplicate-catalog problem harder to see.

FAQ

Which Shopify POS version supports multiple associated barcodes?

The improvement is available in Shopify POS v11.14.

Can staff scan an EAN or ASIN associated with a variant?

Yes, Shopify says associated identifiers such as GTIN, EAN, ASIN or SKU-based codes can be used to find the variant.

Do additional barcodes appear automatically?

No. They must first be associated with the product variant in Shopify Admin.

Should different sizes share the same barcode list?

No. Different sizes are different variants and should retain unambiguous identifiers.

Need hands-on help?

Let’s make your store easier to run — and easier to buy from.

Explore services