What you will learn in this article
- Why GTIN Google Merchant Center influences visibility and ranking in the Shopping auction, not just disapproval
- How Google Shopping feed product identifiers work: GTIN, MPN, brand and how they combine
- What concretely happens without GTIN: formal disapproval, silent penalty or nothing
- How to correctly use
identifier_existsand when setting it tofalseis legitimate - The most common errors with invalid GTINs and how to diagnose them in Merchant Center
- Where official documentation is precise and where operational experience adds crucial information
GTIN Google Merchant Center (Global Trade Item Number) and the other Google Shopping feed product identifiers are among the least understood attributes in the Shopping specification. They are not simply fields to fill in to avoid an error: they are the mechanism by which Google connects each item in the feed to its global catalogue, and this connection has direct effects on the performance of google shopping ads, visibility in the auction and disapproval rates.
The problem is that official documentation describes the formal requirements of Google Shopping feed product identifiers well, but does not clarify the concrete consequences sufficiently, both when a GTIN is missing and when a GTIN is provided but incorrect. This article analyses both situations, integrating official sources with what emerges from direct experience on real feeds.
Why GTIN Google Merchant Center matters so much
Google uses GTIN Google Merchant Center and other identifiers for two distinct purposes that official documentation does not always separate clearly.
1. Building the product listing in the Shopping Knowledge Graph
When multiple sellers offer the same product, Google aggregates them into a unified listing in the Shopping carousel. This aggregation is only possible if Google can confidently match items from different vendors, and GTIN Google Merchant Center is the unique code that makes this matching possible. Without a GTIN, your product cannot be included in the shared listing and loses the visibility that comes from multi-seller aggregation.
2. Optimising ranking in the Shopping auction
Google Shopping feed product identifiers provide Google with additional product information, product category, brand, price history, popularity, that the system uses to assess the relevance of an ad relative to search queries. A product with a valid GTIN receives contextual information that a product without identifiers cannot obtain. This translates into a competitive advantage in the auction, even at equal bid and quality score for other attributes.
What happens without product identifiers in the Google Shopping feed
The answer, depending on the type of product category and feed configuration, falls into three distinct scenarios. Understanding this distinction is fundamental: many feed managers confuse the three possible scenarios and apply the wrong solutions.
Scenario 1, Formal disapproval
A missing GTIN Google Merchant Center causes a formal disapproval only when the product belongs to a category where it is required and the manufacturer has assigned an EAN/UPC code. In practice: if you sell a well-known brand product that has an EAN barcode and do not provide it in the feed, Google disapproves the product with the message “Missing or incorrect GTIN”.
Scenario 2, Silent penalty
For products in categories where Google Shopping feed product identifiers are not formally required, or for products without a declared identifier_exists, Google does not formally disapprove but reduces the
product’s quality in its internal system. The product remains approved, but with a lower data quality score that impacts visibility in the auction with no explicit signal in Merchant Center.
Scenario 3, Invalid GTIN: the worst case
An invalid GTIN, with an incorrect checksum, wrong length or not registered in the GS1 catalogue, causes a formal disapproval with a specific message in Merchant Center. Many e-commerce businesses insert non-valid values in the
gtin field under the impression that “something is better than nothing”. The result is the opposite: an invalid GTIN Google Merchant Center causes a formal disapproval, which is worse than
just the silent penalty of an empty field.
gtin field thinking it is better than leaving it empty. Google validates GTIN values against GS1 checksum rules, a non-conforming value
always generates a formal disapproval. An empty field with identifier_exists: false is always preferable to an invalid GTIN value.
identifier_exists: how to declare products without GTIN in Merchant Center
The identifier_exists attribute is Google’s official solution for managing Google Shopping feed product identifiers when the product has no assigned GTIN. Set to false, it explicitly communicates
to Google that the product has no EAN/UPC/ISBN, and prevents a disapproval for missing GTIN in GTIN Google Merchant Center.
identifier_exists attribute to indicate that unique product identifiers (UPIs) are not available for your product. Products
that might not have unique product identifiers include: custom goods or one-of-a-kind products (custom T-shirts, art, handmade goods), products produced before GTINs were introduced (vintage products, antiques), and other special products.
Source: support.google.com/merchants/answer/6324478.
When identifier_exists: false is correct
- Handmade or bespoke products (artisan jewellery, custom furniture, art prints)
- Own-brand products (private label) without an EAN code registered in the GS1 system
- Generic non-original spare parts without a unique code
- Vintage or second-hand products with no original barcode
When identifier_exists: false is a strategic error
Using identifier_exists: false as a shortcut to avoid providing GTIN Google Merchant Center for branded products that have one is a common mistake. Google cross-references Google Shopping feed product identifiers against the GS1 catalogue: if a product appears in the catalogue with an assigned GTIN but the feed declares identifier_exists: false, the system detects the inconsistency and may disapprove the product or further reduce
its visibility.
identifier_exists: false across the entire range had produced a progressive penalty on visibility
across the entire catalogue. The correction, carried out in three phases over 6 weeks, restored impression share with an 18% increase in conversions at equal budget.
Common errors with Google Shopping feed product identifiers
1. GTIN with incorrect checksum
The GTIN has a check digit calculated mathematically from the other digits. A code transcribed with even a single typographical error almost always has the wrong checksum, and GTIN Google Merchant Center detects it as invalid before upload. Before inserting GTINs in the feed, it is good practice to run them through an EAN validation tool.
2. MPN inserted in the gtin field
The MPN (Manufacturer Part Number) is one of the Google Shopping feed product identifiers, different from GTIN, and goes in the mpn field, not in gtin. Inserting an MPN in the GTIN field almost
always produces a validation error because MPNs do not conform to the numeric format and length required.
3. Same brand + MPN combination for different products
When a product has no GTIN but has a brand and MPN, Google uses the brand + mpn combination as an alternative identifier. If two different products in the feed share the same brand and MPN, Google treats them
as duplicates. Every product must have a unique brand and MPN combination.
4. Generic or absent brand for branded products
The brand attribute is part of the unique identifier set in GTIN Google Merchant Center. Inserting generic values like “Generic” or leaving the field empty for products with a recognisable brand
reduces the quality of identifiers and can cause disapprovals.
5. Base product GTIN used for all variants
Each product variant (colour, size) has its own unique GTIN assigned by the manufacturer. Using the same GTIN for all variants, that of the base product, is a common error on clothing feeds. In feeds that use item group ids to link variants, each variant still requires its own distinct GTIN.
FAQ on GTIN Google Merchant Center and product identifiers
Is GTIN required in the Google Merchant Center feed?
identifier_exists: false. Omitting both causes a formal disapproval or silent penalty. Official source:
support.google.com/merchants/answer/6324461.What happens if I submit an invalid GTIN in the Google Merchant Center feed?
When should I use identifier_exists: false for Google Shopping feed product identifiers?
identifier_exists: false is appropriate when the product is handcrafted, bespoke, vintage or does not have an assigned EAN/UPC code. It should not be used to avoid providing GTIN Google Merchant Center for branded products that have one. Source: support.google.com/merchants/answer/6324478.What is the difference between GTIN, MPN and brand as product identifiers?
brand + mpn combination can be used as an alternative. The three attributes go in their respective feed fields and are not interchangeable. Source: support.google.com/merchants/answer/160161.Can a product without GTIN perform well in Google Shopping?
identifier_exists: false is declared correctly. The main limitation is that without GTIN Google Merchant Center the product cannot be aggregated in the shared listing with other sellers.