Home/News/Shopify Product Variants Now Support Up To 20 Barcodes

Platform Policy

Shopify Product Variants Now Support Up To 20 Barcodes

2026-09-08 Shopify Changelog Platform Policy
Shopify Product Variants Now Support Up To 20 Barcodes
示意图(AI 生成,非现场图片)

Shopify raised the barcode limit on a product variant from one to 20, and any of them will identify the product.

Key facts

  • Timing: Live now (Shopify Changelog, September 8, 2026)
  • Who it hits: Merchants whose SKUs carry several codes — a manufacturer UPC, your own private-label EAN, a marketplace ASIN
  • What to do: If you keep a second set of barcodes in a spreadsheet, do a one-time migration. Single-channel, single-code sellers can ignore this

What happened

Shopify described the problem plainly: the same item arrives with a manufacturer's UPC on the box, your private-label EAN on the shelf tag, and an ASIN on a marketplace listing. You had to pick one and keep the rest in a spreadsheet.

What you can do now: add, scan and remove barcodes on the variant details page or from the Shopify app on your phone; assign each barcode a type — UPC, EAN, ISBN, GTIN, or Custom for internal codes that don't follow a standard — with values checked against that standard's format so a mistyped digit is caught during entry; update barcodes across many variants at once in the bulk editor; and import or export the full set via the Variant Barcodes column in your product CSV.

What it means for independent store owners

Unglamorous, genuinely useful warehouse plumbing. The pain it removes is the scan that returns nothing: the picker scans the manufacturer code on the carton, your system holds the label you printed, nothing comes up, and someone goes to look it up by hand. With multiple barcodes, any of those codes resolves to the same variant.

Three groups benefit most: dropshippers and anyone sourcing the same product from several suppliers who each assign different codes; merchants selling on both their own store and Amazon who want the ASIN attached to the variant; and anyone on a third-party WMS or barcode picking who has been maintaining a code-mapping table outside the system. That table is itself a source of reconciliation errors, so deleting it is pure upside.

The migration path is clean: export your product CSV, move the mappings from your spreadsheet into the Variant Barcodes column with types set, and import it back. Do set the types properly rather than marking everything Custom — format validation catches transposed digits at entry, and that class of error otherwise stays invisible until a scan fails in the warehouse. If you run one channel with one code per product, this changes nothing for you.

Someone should be watching these changes for you

I run AI automation for independent stores — content, SEO/GEO, product listing, social, and keeping up with policy shifts like this one.

See how it works