← Reading listDISTINGUISH AN UNVERIFIED GTIN FROM A PRODUCT THAT HAS NONE
Text

Merchant Center catalog operations workshop / 5 MIN READ

Distinguish an unverified GTIN from a product that has none

Create an identifier evidence queue that prevents guessed GTINs and unsupported absence claims.

Published by SNS Media Tech

AI-assisted research and analysis for the SNS Creative Fieldbook

Sources checked 2026-11-07

A missing identifier in a spreadsheet does not prove that the product lacks an assigned identifier. Treat unknown, verified and genuinely unassigned as different evidence states.

What you will leave with: Create an identifier evidence queue that prevents guessed GTINs and unsupported absence claims.

Use this when

  • A supplier file lacks identifiers or produces identifier-related warnings.
  • A team proposes generating barcodes merely to fill required-looking fields.

Not authority to issue identifiers, certify GS1 registration or assume identical requirements across categories and programs.

Record uncertainty before selecting a feed value

Google says not to guess or invent a GTIN and notes that some products have no assigned GTIN. Missing or incorrect identifiers can limit visibility. Requirements must be checked against the actual category and destination rather than inferred from a competitor's listing.

Create separate internal states for verified assigned identifier, awaiting evidence, and confirmed absence. These are workflow states, not values to upload into the GTIN field. For every uncertain record, retain the precise product configuration and the question that needs answering. A blank supplier cell could mean omission, incomplete onboarding or a genuinely identifier-free product. Each interpretation leads to a different next action.

Sources for this sectionGoogle Merchant Center: GTIN →

Verify the identifier against the exact sold unit

Ask the responsible supplier or manufacturer for evidence tied to the product, pack and variant actually sold. Compare the source with the physical packaging or approved product master where available. A neighboring model's code is not a useful substitute, even when the product description is almost identical.

Treat identifiers as text throughout export preparation. Check whether spreadsheet conversion removed leading zeros, introduced scientific notation or changed a value during a copy. A format check can detect damage but cannot establish that a mathematically valid code belongs to the item. Record both the format result and the identity match. Preserve the original evidence so a later operator can distinguish a supplier correction from an accidental local edit.

Route genuine absence through the applicable rules

If investigation establishes that no relevant identifier was assigned, consult the current product-data and identifier-existence guidance for that product class. Do not set an absence flag simply because the team has not completed its research. Also do not suppress other accurate identifying attributes merely to make the row look uniformly empty.

Document who established the absence, the evidence reviewed and when to revisit the conclusion. A supplier may later assign identifiers or change packaging. Keep uncertain items in an exception queue with an owner and next review date. Business pressure to launch should change the escalation priority, not the truth of the exported data. Any temporary assortment decision should be explicit and reversible.

Test the complete identifier pipeline

Select records with leading zeros, similar variants and different pack sizes. Compare the source evidence, stored master value, generated file and processed Merchant Center value. This reveals where a correct identifier changes during transport. Ensure the quality report counts unresolved identity questions separately from simple formatting defects.

When a supplier correction arrives, update the maintained source and regenerate the affected data rather than repairing only the most visible output. Track the resolved item and its evidence without promising a particular visibility outcome. Identifier accuracy is a catalog integrity goal; approval, matching and campaign performance still depend on other requirements. Review recurring supplier problems so the next delivery includes the evidence the team actually needs.

Make the reasoning concrete.

A fictional tool merchant receives a file for two drill kits. One GTIN field is blank; the other contains a code for the bare tool rather than the kit. A launch deadline is approaching.

Fill the gaps creatively

Opening: Copy a nearby code and mark the remaining item as lacking identifiers.

Hypothesis: The file has fewer empty cells.

Risk: Both records make unsupported identity claims.

Resolve the evidence states

Opening: Request kit-specific manufacturer evidence and quarantine uncertain mappings from the approved export.

Hypothesis: The released data reflects what is actually verified.

Risk: Some items may wait while evidence is obtained.

The owner separates missing evidence from genuine absence and checks kit configuration before accepting either code. No fictional identifier is created to satisfy a spreadsheet check.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

  1. Unit

    Which variant and pack does this identifier need to describe?

  2. Evidence

    What manufacturer or packaging record supports the value?

  3. State

    Is the identifier verified, unknown or confirmed unassigned?

  4. Transport

    Does the exact text survive every export step?

  5. Owner

    Who resolves the remaining uncertainty and by when?

Watch for the wrong conclusion.

  • Treating a blank cell as proof of no assigned identifier.
  • Borrowing a GTIN from a similar item.
  • Using a checksum as proof of product identity.

Your next action

Trace one disputed GTIN from manufacturer evidence through the processed product record.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.

  • Google Merchant Center: GTIN →Primary platform documentation · Supports: Supports not guessing GTINs, the existence of products without assigned GTINs, and possible limited visibility from missing or incorrect identifiers. Evidence states and verification workflow are original editorial analysis.