Shopify POS / Improvement

Now supports scan & search
with multiple barcodes

Any barcode linked to a variant now resolves to the right product, whether you scan it or search for it. Even when codes differ by supplier, channel, or packaging, staff no longer have to hunt for the item by hand.

On this page
  1. In 30 seconds: what changed
  2. How it works: from scan to variant match
  3. Supported barcode types and scope
  4. Before vs. this update
  5. 3 steps to get started
  6. 5 points for developers
  7. 3 practical use cases
  8. One-line summary for your pitch

1In 30 seconds: what changed

Shopify POS can now identify the correct variant using any barcode linked to that product variant.
Even when the code on the physical item differs from the "primary barcode" your store normally uses, there is no need to look the product up manually.

Before: only the primary barcode worked

If the code on the item differed from the store's primary barcode, nothing matched, and staff had to search manually by product name or similar.

Now: any associated barcode works

GTIN, EAN, ASIN, SKU-based codes, and more — any code associated with that variant leads to the same product.

This covers both scanning and search . The correct variant is matched at checkout, during receiving, and in inventory work alike.

2How it works: from scan to variant match

Supplier A's label GTIN Box from another channel EAN / ASIN Different packaging SKU-based code Codes on physical items vary Scan or search in POS v11.14 and later Associated barcode matching Matches primary and additional barcodes alike Shows the right variant Works the same at checkout, receiving, and stocktakes
Prerequisite : Additional barcodes must first be linked to the variant in the Shopify Admin. Codes that aren't linked won't resolve to a variant.

3Supported barcode types and where they apply

Identifiers given as examples in the changelog

GTIN
International product identification number
EAN
European product code
ASIN
ASIN
Marketplace identifier
SKU
SKU-based code
A code derived from the SKU

Where this helps (as stated in the changelog)

Covered

Checkout

Even if the code scanned at checkout differs from the primary barcode, the product still comes up.

Covered

Receiving

Shipments labeled differently by each supplier can be scanned and matched as-is.

Covered

Inventory

For stocktakes and inventory adjustments, any code on the physical item leads to the same variant.

The maximum number of additional barcodes per variant, the supported countries and plans, and the impact on online store search are not stated.

4Before vs. this update

ItemBeforePOS v11.14 and later
Codes usable for matching Mainly the primary barcode Every linked barcode
When the code doesn't match Staff look up the product manually The correct variant comes up right away
Supported actions Scan / search Both scan and search
Setup to enable it — Automatic Available in v11.14
Prerequisites — Required Registering additional barcodes in the Admin

53 steps to get started

1

Update POS to v11.14 or later

This update becomes available automatically in POS v11.14.

2

Link additional barcodes in the Admin

In the Shopify admin, associate additional barcodes with the target variants.

3

Scan and search in store to verify

During checkout, receiving, and inventory work, confirm that any of the codes brings up the same product.

65 points for technical teams

1. It becomes "1 variant : N barcodes"

The variant-to-barcode relationship, which was effectively one-to-one until now, becomes one-to-many. If you have your own matching logic keyed on barcodes, you need to rework it on the assumption that multiple matches are possible.

Admin

2. Data registration is a prerequisite

The POS side only handles lookup; registering additional barcodes is work done in the Shopify Admin. Nothing changes for staff on the floor until the data is in place.Treating the rollout as a data migration projectis the right way to think about it.

v11.14

3. Behavior differs by version

It is enabled automatically in POS v11.14. If device versions aren't consistent across multiple stores, you'll end up with a mix of stores where a product resolves and stores where it doesn't, even for the same product. Get a handle on device versions before rolling out.

API ?

4. No mention of how to register via API

The post only says to "associate them in the Shopify Admin," and says nothing about field names in the Admin API / GraphQL or any bulk registration method = not documented. If you want to load them in bulk, you'll need to confirm separately.

5. Duplicate code design needs care

How things resolve when the same code is associated with multiple variants is not documentedin the post. Operationally, the safe approach is to make "one code maps to exactly one variant" a rule and add a duplicate check before registering. Do your testing in a sandbox.

73 practical use cases

Supplier A Supplier B Supplier C
USE CASE 1

Speeding up receiving inspection for stores that source the same product from multiple suppliers

Problem
Even for the same product, each supplier applies a different barcode, so scanning at receiving doesn't resolve and staff end up searching by product name instead.
Approach
Register each supplier's code on the relevant variant in the Shopify Admin → on POS v11.14 and later, scanning any of the labels lands on the same variant.
Impact
Less manual searching during receiving, which improves inspection throughput and registration accuracy.
Technical notes
Registration happens in Admin. You'll need a process to consolidate the code lists already held in your supplier master data down to the variant level before loading them in.
USE CASE 2

Shorter checkout lines: eliminating "products that won't scan"

Problem
Old packaging and packaging circulating in parallel carry different codes, so the scan fails at checkout and the line stalls.
Approach
Associate codes from past packaging and other channels with the variant too, so any code scans through at the register.
Impact
Less manual searching at checkout, which cuts transaction time and mis-entries (accidentally picking the wrong variant).
Technical notes
Confirm each store is on POS v11.14 or later before rolling this out. Mixed versions mean the experience won't be consistent from store to store.
USE CASE 3

Standardizing omnichannel inventory counts on a single-scan workflow

Problem
Because codes have been managed separately per sales channel, every stocktake requires a channel-by-channel conversion table.
Approach
Register the per-channel codes together on the same variant, so that during inventory work, scanning any code on the physical item updates the same inventory record.
Impact
Conversion tables no longer need maintaining, and the stocktake procedure can be unified across every store.
Technical notes
Before consolidating, identify whether the same code is duplicated across different variants. The changelog doesn't describe the behavior on duplicates, so guarantee uniqueness on the registration side.

8A one-line summary you can use in a pitch

"Shopify POS now resolves the correct product from any barcode tied to a variant (GTIN / EAN / ASIN / SKU-based) .
It's available automatically on v11.14, so all that's left is the data work of registering the extra barcodes in Admin — do that, and 'the scan won't go through' disappears from checkout, receiving, and stocktakes."