A barcode suggestion is a reason to inspect a product record, not a reason to approve it without checking. Before accepting a suggested GTIN type, ask a narrower question: does the evidence connect this identifier to the exact item, variant and pack you sell?
In its October 29, 2026 announcement, Shopify described GTIN autocomplete, suggestions for saved barcodes and comparisons with the GS1 registry. These signals can inform a catalog review. They should not replace the owner’s decision about product identity.
Separate a new entry from a saved-code suggestion
Shopify describes two different paths:
- New barcode: when an entered barcode looks like a GTIN, Shopify looks it up in the GS1 registry. If it is registered, Shopify says it marks the barcode as GTIN and highlights the change.
- Saved Custom barcode: a saved code that looks like a GTIN can show a suggestion. Accepting the suggestion changes its type to GTIN; the operator can also dismiss it.
The announcement says Shopify does not change an already-saved barcode unless the suggestion is accepted. It also says these signals do not block saving, and Custom remains available for internal codes. That makes it important to record which path you are reviewing rather than treating every highlighted value as the same event.
Where the registry has a product record, Shopify describes a comparison of the vendor and product name. It explicitly says you do not need to change your title, vendor or description to match GS1. Treat a difference as something to investigate, not an instruction to rewrite otherwise-correct product copy.
Review the sellable unit, not just the matching text
Verified by GS1 provides identifier lookup. For your own review, keep the registry information alongside the evidence for the item in your catalog. A familiar product name is not a substitute for checking the variant and pack.
Use a review card with these fields:
| Record | What to retain |
|---|---|
| Catalog identity | Internal SKU, variant and pack quantity |
| Barcode state | Value, current type, and whether this is a new entry or saved suggestion |
| Item evidence | Approved product record and supplier or packaging evidence for that sellable unit |
| Registry comparison | What the lookup displays, any discrepancy and the date checked |
| Decision | Accept, dismiss or hold for more evidence, with an owner and reason |
| Follow-through | Intended change, affected destinations and verification result |
This is a proposed operating record, not a list of Shopify fields or an automated approval feature. If ownership is unclear, first establish who controls SKU identity and changes.
A hypothetical multipack review
Imagine a fictional brand selling an individual item and a multipack with similar titles. A saved Custom barcode on the multipack shows a GTIN suggestion. The reviewer has supplier evidence for the individual item, but nothing connecting the multipack to that identifier.
The useful decision is to hold acceptance for that record and ask the product-data owner to establish the association. Renaming the multipack to resemble a registry title would not supply the missing evidence. Neither would assuming that a suggestion proves the correct pack relationship.
This example uses no real barcode, lookup result or customer record. “Hold” means defer the review decision under your team’s process; it does not describe an automatic Shopify inventory or sales hold.
Give bulk acceptance a defined scope
Shopify’s announcement describes accepting or dismissing suggestions in bulk through the products and inventory bulk editors. Availability of that action is not a reason to apply one decision to every record.
Start with a small, declared sample. Include records whose identity evidence is complete and records with unresolved variant or pack questions. Use the sample to check whether your reviewers can reach and document consistent decisions. A sample does not establish that every remaining record is correct.
Before expanding the scope:
- Name the records being considered and the owner of the decision.
- Confirm that the evidence covers each sellable unit in that scope.
- Separate unresolved records from those ready for acceptance or dismissal.
- Retain the prior value and type, the decision and its reason.
- After an authorized change, verify the intended result and check affected destinations through the normal catalog workflow.
Do not treat an accepted suggestion as proof of marketplace acceptance, product authenticity or correct fulfillment configuration. Those are different questions requiring their own evidence. This review method does not set GTIN assignment rules or determine when a new identifier is required.
Make the next decision small enough to verify
Choose a bounded group of saved suggestions and complete the review card before considering bulk acceptance. Record missing evidence explicitly, with an owner and a next action. Do not turn an unknown pack association into an approval just to clear the queue.
Use the product-content acceptance checks to connect that identity decision to the wider publication review. The goal is not to make every warning disappear. It is to know why each changed record is right for the item it represents.