Monthly Shopify tip
Shopify now allows 20 barcodes per variant. Here's what that actually fixes
Everyone's calling this a nice UX upgrade. It's really Shopify admitting the single-barcode model never worked for retail, and it took years to fix. Here's what changed, who benefits right away, and where the gap still is.
The problem with one barcode per variant
A product variant used to hold exactly one barcode. That's fine in theory, until you're dealing with the real world: your supplier in Germany ships with their own EAN, your own warehouse label uses a different GTIN, and maybe there's an ASIN floating around from an Amazon.de listing too. Shopify could only hold one of those. Everything else got shoved into a metafield, a tag, or somebody's spreadsheet.
This has been a known gap in Shopify's data model for years, one that anyone running multi-supplier or multi-channel inventory has had to work around manually. That workaround era is now over.
What changed
A variant can now carry up to 20 barcodes, each tagged as GTIN, UPC, EAN, ISBN, ASIN, or Custom. You can add them from the variant page, the bulk editor, a CSV import, or the Shopify app on your phone, and Shopify checks the format as you go.
The real winner: point of sale
Barcodes aren't glamorous, but think about what this actually fixes on the shop floor: staff can now scan whatever barcode is physically on the box, the supplier's, the shelf label's, it doesn't matter, and the system finds the right variant regardless.
Anyone who's stood at a till re-keying a SKU because the scanner rejected a "wrong" barcode knows exactly what problem just went away.
Where the gap still is
Everything outside POS is still stuck in the old world. Sales channels, apps, anywhere that expects a single barcode, still only read the first one on the variant. Google Merchant Center included, Shopify says this outright in the release note, it's not a guess.
So if the real EAN isn't sitting in that first slot, your European Shopping feed can still throw errors or get flagged, even with 19 perfectly good codes sitting right underneath it doing nothing.
Nothing migrates automatically, and nothing breaks today. But the feature is genuinely two-tiered right now.
POS gets the full benefit immediately. Everything downstream, sales channels, feeds, most apps, is still waiting on the rest of the ecosystem to catch up.
The bottom line
Put the real EAN or GTIN first, everything else after.
Celebrate the POS win, it's a genuine one. Just don't assume it's a universal win yet. Until sales channels and feed integrations catch up, barcode order on each variant still matters.