If you've ever logged into your Google Merchant Center account only to see a wave of red disapproved items with the tag "Missing GTIN" or "Invalid GTIN," you aren't alone. Product identifiers are the backbones of the Google Shopping directory. Without them, Google cannot index your products accurately, group similar catalog listings together, or show your ads for high-intent transactional search queries.
In this guide, we will break down what GTINs are, why they are mandatory for modern e-commerce campaigns, and how to permanently solve missing and invalid identifier errors to secure ad eligibility and scale revenue.
What is a GTIN and why Google Shopping requires it
A Global Trade Item Number (GTIN) is a unique numerical identifier assigned to manufactured products. It is the digit string printed beneath the black-and-white barcodes found on retail products worldwide. Unlike SKU (Stock Keeping Unit) codes, which are internal to your specific store, GTINs are globally standardized by a nonprofit organization called GS1.
Google Shopping requires GTINs for several structural reasons:
- Catalog Matching: Google groups all merchants selling the same product under a single catalog entry. This enables competitive comparison cards, product rating reviews, and rich price ranges.
- Query Contextualization: Google's search algorithm understands what a product is based on aggregate catalog data linked to its GTIN. It knows the weight, dimensions, usage, and compatibility, helping to place ads in front of the right buyers.
- Ad Rank Placement: Listings with verified GTINs receive priority bidding placement in auction algorithms over items with incomplete metadata, lowering your average Cost-Per-Click (CPC).
How to find your product's GTIN (EAN/UPC/ISBN)
The type of GTIN format depends on your region and product type. The table below outlines the differences between standard identifiers:
| Identifier Name | Standard Length | Primary Region | Product Category |
|---|---|---|---|
| UPC (Universal Product Code) | 12 digits | North America | Standard retail consumer goods |
| EAN (European Article Number) | 13 digits | Europe, India, and International | Standard retail consumer goods |
| ISBN (International Standard Book Number) | 13 digits (formerly 10) | Global | Books, ebooks, and physical publications |
| ITF-14 (Shipping Container Code) | 14 digits | Global | Multipacks, boxes, and wholesale cases |
To locate your product's GTIN:
- Examine the Physical Packaging: Locate the barcode on the back or bottom of the product. The 12 or 13 digits printed directly underneath are your UPC or EAN values.
- Query the Manufacturer: If you are a reseller, ask your distributor or manufacturer for a master catalog CSV containing a column for UPC/EAN numbers.
- GS1 GEPIR Database Search: If you know the brand and manufacturer details, search the GEPIR (Global Electronic Party Information Registry) database to look up matching barcode registrations.
Fixing "Missing GTIN" and "Invalid GTIN" errors
Merchant Center flag alerts generally fall into two categories: "Missing" (meaning the attribute field is empty but Google expects a code) or "Invalid" (meaning a code is submitted but fails validation checks).
1. Fixing "Missing GTIN"
This occurs when Google identifies that a product belongs to a brand name category that typically carries barcodes, but the gtin attribute is blank. To fix this, update your product feed by writing the correct EAN or UPC code into the gtin field. If you are using Shopify, this corresponds to the "Barcode" field on the product details page.
2. Fixing "Invalid GTIN"
An invalid GTIN disapprove status is triggered when the code provided does not exist in the GS1 database or fails the check digit mathematical calculation. To resolve this:
- Remove any spaces, hyphens, or prefix characters (like "No." or "UPC-"). The feed expects purely numerical values.
- Verify the check digit (the last digit of the code). Use an online check-digit calculator to confirm the sequence is mathematically correct.
- Avoid using duplicate GTINs across different products. Google will immediately flag duplicate values and disapprove both listings.
When to use identifier_exists = no (handmade/custom/vintage)
If you manufacture custom handmade goods, sell vintage items, or market specialized white-label products without barcodes, you do not have a GTIN. For these items, submitting empty values triggers a disapproving error cycle.
To resolve this, Google uses the identifier_exists attribute:
- Set
identifier_existstofalse(ornodepending on feed type). - By declaring that no identifier exists, you notify Google that the item is a custom, unique, or vintage piece. Google will bypass the barcode requirements and allow your items to serve.
- Crucial: When
identifier_existsis set to false, you must also omit thebrandandmpn(Manufacturer Part Number) values if they do not legitimately exist.
If you are setting this up, read our dedicated Shopify Google Channel Setup Guide to automate this mapping block.
GTIN rules for product variants (color/size)
E-commerce stores often make the critical mistake of using a single barcode value for all variations of a product. This violates Google's feed structure policies.
Every single variant (size, color, material, style) must have a **unique, distinct GTIN**. For example, if you sell a shirt in 3 sizes (Small, Medium, Large) and 2 colors (Red, Blue), you have a total of 6 variants. You must submit 6 distinct products in your feed, each with its own barcode value. Using the same UPC for all 6 will lead to immediate product disapprovals.
Common GTIN mistakes that trigger disapprovals
To keep your Merchant Center dashboard clear of warnings, audit your data for these common traps:
- Submitting SKUs as GTINs: SKUs are internal identifiers. Do not map your internal SKU field to the
gtinattribute in your feed. - Using Manufacturer Part Numbers (MPN) as GTINs: The
mpnis a manufacturer alphanumeric code, while thegtinis a global barcode. They must be submitted in separate fields. - Regional Format Mismatch: Submitting a North American UPC code in a region expecting European EAN styles without verifying prefix formatting.
By cleaning up these catalog identifier fields, you ensure your product feed remains healthy and optimized. For a broader overview of resolving database issues, consult our core Google Merchant Center Feed Errors Guide.