When you enter a GTIN-like barcode, Shopify looks it up in GS1 registry data and, if it's registered, automatically sets the type to "GTIN." Saved barcodes show suggestions, and in the bulk editor you can accept or dismiss them all at once. All of this is advisory only and never blocks saving.
Merchants had to determine on their own whether an entered barcode was a registered GTIN or an internal code, and choose the type accordingly.
If it's registered with GS1, the type is automatically set to "GTIN." Saved barcodes show suggestions, and a warning appears if they conflict with registry data. The merchant makes the final call.
When you add a new barcode that looks like a GTIN, Shopify looks it up in GS1. If it's registered, the type is automatically set to "GTIN" and highlighted so you can see what changed.
Barcodes saved with the "Custom" type that look like GTINs get a suggestion. Accept it to change the type to GTIN, or dismiss it to leave it as is.
If the barcode is registered to a different product in GS1, you can hover to compare your vendor and product name against the GS1 record.For reference only. You don't need to match your product title, vendor, or description to GS1.
In the bulk editor for products and inventory, you can accept all GTIN suggestions at once, or dismiss them all at once.
Suggestions and warnings don't prevent you from saving.
Shopify only changes a saved barcode when the merchant accepts a suggestion.
You can still choose any barcode type yourself, including "Custom" for internal codes.
| Item | Before | After this update |
|---|---|---|
| Type for new barcodes | Manual You choose it | Automatic Set to GTIN and highlighted if registered in GS1 |
| Saved as "Custom" | Unchanged | Shown as suggestion Approve to set as GTIN / can also reject |
| Mismatch with registry data | No way to notice (not mentioned in the article) | Warning shown Hover to compare vendor and product names |
| Large catalogs | One at a time | In bulk Approve all / reject all in the product and inventory bulk editors |
| Blocks saving | — | No Nothing prevents saving |
| Eligible plans, countries, and pricing | — | Not specified |
Open the product or inventory bulk editor.
Review the suggestions shown on barcodes that look like GTINs.
Approve all suggestions at once, or reject them all.
Barcodes are checked against the registry of the organization that issues GTINs, not just validated by format. The key is distinguishing a number that merely looks like a GTIN from one that is actually registered.
Newly entered barcodes are automatically set as GTINs, but saved barcodes don't change unless you approve them. Existing data won't be overwritten without your action.
Even if your data differs from GS1's product or vendor name, you don't need to update your product data. Still, the warnings can help you spot duplicates or incorrect entries.
The article only covers the admin feature. It doesn't say whether suggestions appear for barcodes added via the Admin API, CSV import, or apps, or whether the barcode type is exposed through the API. Needs verification.
The article links to the help page on assigning multiple barcodes to a variant.Storing GTINs and internal "custom" codes as separate barcode typesappears to be the intended setup. Sales channels use GTINs to match listings to products, so correct barcode types directly affect the quality of channel integrations.