Shopify GTIN Suggestions: Check Product Barcodes Before BFCM

Shopify’s October 29, 2026 GTIN update gives merchants another way to review product identifiers before a busy sales period. The admin can check barcode values against the GS1 registry and suggest which ones should be marked as GTINs. That is useful assistance, but accepting a suggestion still deserves a look at the product it belongs to.

For Black Friday preparation, start with a small batch of campaign products. Confirm the identifier for each exact variant, record uncertain cases, and check the destination channel after any corrections. This guide describes a proposed review process, not results from testing a merchant’s store.

Understand what the new suggestion changes

Shopify’s GTIN announcement describes autocomplete for newly entered values and suggestions for saved Custom barcodes. It also allows accepting or dismissing suggestions in the products and inventory bulk editors.

The announcement says saved barcodes do not change unless you accept a suggestion. Internal codes can remain Custom, and the suggestions do not block saving. If the registry has a product record, you can compare its vendor and product name with yours. Shopify says you do not need to rewrite your title, vendor or description to match that record.

Treat the suggestion as a reason to investigate. A familiar-looking number is not enough to establish that the blue mug in your catalog matches the blue mug in the supplier’s documentation.

Make an identifier review sheet for the exact variant

Choose a scope your team can finish: perhaps the products featured in one gift collection. Include their variants rather than reviewing only the parent product names.

Record	What to capture
Shopify product and variant	Product URL, color, size or capacity
Current barcode value and type	Copy the existing record before editing
Evidence	Packaging photo or supplier/manufacturer reference
Review decision	Verified match, internal code, or unresolved
Follow-up owner	Person who can answer supplier or feed questions

For example, imagine a supplier sells a blue 350 ml mug, a coral 350 ml mug and a boxed pair. Put those on separate review rows. Ask the supplier which identifier belongs to each offer rather than copying one packaging number across the whole family. This is a hypothetical catalog example; the correct values must come from the products’ real records.

Keep the evidence alongside the decision. If a second person reviews the batch later, “supplier sheet, blue 350 ml, checked November 1” is more useful than “number looked valid.” Do not insert example barcode digits from a tutorial into a live product.

Separate a genuine GTIN from a useful internal code

Google’s GTIN specification says to submit a GTIN only when you know it is correct. Products with different colors or sizes need the identifier assigned to that variant. Some products have no assigned GTIN; making one up is not the solution.

An internal stockroom label can still be useful for your own operations. Before changing its type, establish whether it is a recognized product identifier or a code your team created for scanning and organization. Preserve that distinction in your review sheet.

Use three outcomes:

• Verified match: evidence identifies the same product and variant. Review the suggestion and accept the appropriate type if it agrees.
• Internal code: keep its operational purpose clear. Do not present it as a manufacturer-assigned GTIN just to complete a field.
• Unresolved: leave the case with a named owner and investigate before submitting uncertain identifiers to a channel.

If the registry comparison differs from your catalog, check the source material before changing anything. A vendor naming difference can require a different investigation from a genuinely wrong variant number. Avoid treating every mismatch as an instruction to rename your storefront products.

Check channel data after the catalog review

A correct admin record is one checkpoint. For products you distribute through Google, inspect the corresponding item in Merchant Center and confirm the variant, identifier and landing destination agree. Google notes that missing or incorrect identifiers can limit visibility; a corrected field is not a promise of approval, rankings or sales.

Record when you checked each system and which issue, if any, it still reports. Do not repeatedly change a verified identifier simply because another interface has not yet reflected the update. Investigate the channel’s processing state and the actual submitted item.

Keep this separate from inventory accuracy. A barcode review establishes identity, while a count checks physical quantities. Use our pre-BFCM stock-count checklist for that work. If the right variant appears unavailable in one system, follow the product availability mismatch guide.

Accept a reviewed batch, then return to merchandising

Before accepting suggestions in bulk, separate verified rows from unresolved ones and confirm that your selected products match the intended batch. Keep a record of the prior values and types, the accepted changes and the reviewer. Stop and investigate if the selected set is broader than expected.

Afterward, review the campaign collection as a shopper: the intended variants, clear descriptions, accurate availability and working destinations should all support the offer. Barcode cleanup belongs alongside those checks, rather than replacing them.

If maintaining collection order and handling sold-out products are the ongoing jobs, review RankCollections. Its Shopify App Store listing describes collection sorting and sold-out handling. Evaluate those features for merchandising; GTIN verification remains a separate catalog responsibility.

Merchant takeaway: accept a barcode suggestion because it matches documented product identity. Keep internal codes and unresolved cases distinct, and verify the same variant in the channel that will show it to customers.