Skip to content

GTIN Google Shopping: how to find, validate and fix product identifiers

A practical guide to avoid common Merchant Center identifier issues without inventing data or breaking your feed.

J

Julia Villegas

· 10 min read · 72 views
GTIN Google Shopping products with barcodes organized into a clean feed

GTIN Google Shopping is one of the first things to check when Merchant Center flags products with warnings, limited visibility or disapprovals. If you sell barcoded goods, books, variants, multipacks or private-label products, knowing which identifier to send helps Google understand your catalog and avoids avoidable feed errors.

GTIN Google Shopping: what it is and why it matters

A GTIN is a Global Trade Item Number: a product identifier used to recognize a specific item in the market. In Google Merchant Center, it belongs to the group of unique product identifiers, alongside brand and mpn. Google’s GTIN attribute documentation says that when a product has an assigned GTIN, you should submit a valid one.

Think of a GTIN as a way to identify an exact commercial product, not just a broad description. It does not mean “white running shoe” or “wireless headphones”. It points to a specific item, often with a specific model, size, color, packaging or edition.

That is why GTINs matter most for mass-produced goods: electronics, toys, cosmetics, books, branded fashion, homeware, accessories and packaged products. They help Google match the item you sell with the product Google already understands.

Google also explains in its product data specification that well-formatted product data is the foundation for Shopping ads and free listings. Incorrect, missing or inaccurate data can lead to disapprovals, limited eligibility, incorrect display or products not appearing on Google.

A correct GTIN does not guarantee approval or better performance by itself. Merchant Center still evaluates policies, landing pages, images, price, availability and many other attributes. But if the GTIN exists and you send the right value, you give Google a cleaner signal about what you sell.

The GTIN types you may see in a product feed

Your supplier, ecommerce platform or ERP may not use the word “GTIN”. In many product files, the relevant column is called EAN, UPC, barcode, ISBN or another local name. For Google, these are all part of the same family of product identifiers.

Identifier type Common use Verified format
UPC or GTIN-12 Mainly North America 12 digits
EAN or GTIN-13 Mainly outside North America Usually 13 digits, sometimes 8 or 14
JAN Japan 8 or 13 digits
ISBN Books ISBN-13 recommended, usually starting with 978 or 979
ITF-14 Multipacks or cases 14 digits

For international ecommerce teams, this creates a practical mapping problem. A US supplier may send a upc column. A European distributor may send ean. A bookstore may send isbn13. Your store may call the same value barcode. The target attribute for Google Shopping is still gtin, as long as the value is the official identifier assigned to that product.

The important distinction is this: your SKU is not a GTIN. A SKU identifies a product inside your own business. It may be perfect for picking, stock control, internal reporting or order management, but it should not be submitted as gtin unless it is genuinely the official product identifier.

When to submit GTIN, brand and MPN

The simple rule is: if the product has unique product identifiers available, submit them. For mass-produced products with a GTIN, Google recommends sending gtin, brand and mpn when available.

Here is a hypothetical example. You sell a branded coffee machine. The box has an EAN printed below the barcode, the manufacturer publishes an MPN in the technical documentation and the brand is clear on the packaging. Your feed should include:

  • gtin: the official EAN, UPC or other GTIN for that coffee machine.
  • brand: the real product brand.
  • mpn: the manufacturer part number, if you have it.

Now imagine you sell handmade ceramic mugs made by your own studio. There is no official barcode and no external manufacturer part number. In that case, do not invent a GTIN and do not put your internal SKU into mpn just to fill the field. If a brand applies, you can send it, but identifiers that do not exist should not be fabricated.

Google gives examples of products that may not have GTINs: private-label products, replacement parts, OEM parts, custom or handmade products, books published before 1970, vintage or antique goods and preorder products.

The decision is not whether it would be convenient to have a GTIN. The decision is whether the product has one officially assigned. If it exists, use it. If it does not exist, do not make one up.

How to find the GTIN for a product

Before editing your feed, look for the identifier in the most reliable source available. Google recommends checking the code next to the barcode on the product, the packaging or the book cover. If you cannot find it, contact the manufacturer. Google also recommends checking the legitimacy of any third-party source used to look up GTINs, as explained in its Find a GTIN help page.

A practical workflow looks like this:

  1. Check the physical product or packaging. Look for the barcode and the digits printed below it.
  2. Review the manufacturer’s product documentation. Many manufacturers publish EAN, UPC, ISBN or MPN values in spec sheets.
  3. Ask your supplier for a clean export. If you buy from distributors, request EAN/UPC/GTIN and MPN columns.
  4. Separate official identifiers from internal references. If a code only exists in your warehouse, it is probably not a GTIN.
  5. Validate the source before using the value. Do not copy identifiers from similar products or unreliable lookup sites.

Variants are where many feed mistakes start. A black T-shirt in size S can have a different GTIN from the same T-shirt in size M. A product in a different color, pack size or edition may also need its own identifier. Copying one GTIN across all variants may create conflicts in Merchant Center or cause the wrong information to display.

If you are still setting up the structure of your Google feed, it is worth reviewing AdMotion’s guide on how to create a feed for Google Shopping before you clean identifiers at scale.

Common GTIN mistakes in Google Shopping feeds

Many GTIN problems are not caused by missing data. They come from data that looks complete but is actually wrong. These are the mistakes ecommerce and performance teams see most often:

  • Using the SKU as the GTIN. A SKU is internal to your store; a GTIN identifies the product in the wider market.
  • Copying the GTIN from a similar product. Similar products can have different identifiers, especially across variants.
  • Filling GTIN for products without an official identifier. Do not invent a value to make the column look complete.
  • Sending the same GTIN for different variants. Some cases are valid, but many variants have their own GTIN.
  • Mixing manufacturer-created and seller-created packs. Bundles and multipacks depend on who created the package.
  • Including extra characters. Spaces, prefixes, hyphens or text can stop the value being interpreted correctly.
  • Leaving conflicts between the feed and the website. Google can flag inconsistencies between your submitted data and landing page information.

If Merchant Center shows warnings or errors, avoid fixing them blindly from the diagnostics screen alone. First identify the root cause: format, missing value, duplicate value, wrong source, variant mismatch or website conflict. For a broader troubleshooting approach, use the guide to feed errors and how to fix them.

Bundles and multipacks: where identifiers get confusing

Bundles and multipacks need special attention because the correct identifier depends on who created the package.

If the manufacturer created the bundle or multipack, submit the GTIN, MPN and brand of that package. For example, if a brand officially sells a three-pack of filters with its own barcode, that barcode identifies the manufacturer’s pack.

If your store created the bundle, the logic changes. For seller-created bundles, Google distinguishes how identifiers should be handled based on the main product in the bundle. For seller-created multipacks, the identifiers relate to the individual products that make up the pack.

Example: your store creates a “camera + memory card + case” kit from items that are normally sold separately. You should not invent a GTIN for the kit. You also should not use the case identifier if the camera is the main product. But if the manufacturer sells an official “camera + case” kit with its own barcode, that identifier belongs to the manufacturer-created package.

The safest operational habit is to document your pack logic. Mark which products are bundles, which are multipacks, who creates them and where the identifier comes from. This avoids one-off manual decisions every time the catalog is exported.

How to fix GTIN issues in your product feed

When GTIN problems appear, work from the source feed outward. Do not manually patch hundreds of products in Merchant Center if the wrong value comes from your ecommerce platform, ERP or supplier file.

  1. Export a product sample. Include id, title, SKU, GTIN, brand, MPN, category, URL, variant attributes and pack information.
  2. Group products by identifier status. Separate mass-produced items, private-label products, handmade products, variants, bundles and multipacks.
  3. Find suspicious formats. Look for letters, prefixes, spaces, hyphens, unusual lengths or repeated values across unrelated products.
  4. Compare against a trusted source. Check packaging, manufacturer data or supplier files before changing identifiers.
  5. Clean formatting problems. If the GTIN is right but includes spaces or extra characters, normalize the field.
  6. Do not fill blanks with internal data. If there is no official identifier, leave the GTIN empty rather than using a SKU.
  7. Review variants and packs separately. These groups often need more careful logic than standard products.
  8. Regenerate the feed and review Merchant Center. Watch whether warnings change and whether new conflicts appear.

For repeated transformations, rules are safer than spreadsheet edits. You might trim spaces from a barcode field, map ean to gtin, clear gtin when it matches the SKU, or create a review set for private-label products. AdMotion’s guide to feed rules explains how this type of cleanup can be applied consistently without editing product by product.

How to manage GTIN cleanup with AdMotion

AdMotion can help you organize this workflow without rebuilding your Google feed manually every time the catalog changes. A typical setup for GTIN Google Shopping cleanup would look like this:

  1. Connect your store or product file. The Feed Manager can connect Shopify, BigCommerce, Tiendanube or any product file or feed.
  2. Map your catalog fields. Identify which column contains EAN, UPC, ISBN, barcode or another official identifier, then map it to the field you will send as gtin.
  3. Create cleanup rules. Use rules to clean and segment the catalog. Rules can also be written in natural language and reviewed in the editor before applying them.
  4. Create product sets for review. For example: products with GTINs from suppliers, products without GTINs because they are handmade, variants to check, bundles and multipacks.
  5. Build the Google feed. With Export Channels, AdMotion provides feeds for Google Shopping and other channels.
  6. Review the channel specification. The analyzer checks each feed against the channel specification and shows errors, warnings and information.
  7. Copy the feed URL to the channel. The feed is published through a URL generated at download time, ready to use in the relevant advertising or commerce platform.

This does not replace official GTIN verification. AdMotion does not retrieve identifiers from manufacturers, validate against external GS1 databases or guarantee Merchant Center approval. Its role is to help you structure the catalog, apply consistent rules and detect feed issues before you submit or refresh the Google feed.

If you want to inspect your own data, you can try AdMotion with your catalog and see which identifier fields arrive, which rules you need and how the Google feed would be structured.

What to do this week

  1. Audit a high-impact product sample. Start with products that receive the most spend, have the highest margin or drive the most revenue.
  2. Identify ambiguous columns. Look for fields named barcode, ean, upc, sku, ref, isbn or manufacturer_code and confirm what each one really means.
  3. Fix obvious formatting issues. Remove unnecessary spaces, prefixes and non-numeric characters where the field should contain a GTIN.
  4. Stop inventing identifiers. If a product has no official GTIN, document the reason instead of filling the field with internal data.
  5. Review variants, bundles and multipacks. Check these groups before applying global rules to the entire feed.

Clean identifiers make your product feed easier to maintain, troubleshoot and scale. Start by separating official product data from internal store data: that single habit prevents many GTIN Google Shopping problems before they reach Merchant Center.

Frequently asked questions

Is GTIN required for Google Shopping?

You should submit a GTIN when the product has one officially assigned. Google recommends sending a valid GTIN, plus brand and MPN when available. If the product does not have assigned unique product identifiers, do not invent them or use your internal SKU as a GTIN.

Can I use my SKU as a GTIN if I cannot find the barcode?

No. A SKU is an internal identifier used by your store or operations system, while a GTIN identifies the product in the wider market. Check packaging, manufacturer documentation or supplier data first. If the product has no official GTIN, it is better to leave it empty than submit an invented value.

Does a correct GTIN guarantee Merchant Center approval?

No. A valid GTIN helps Google recognize and classify the product, but approval also depends on policies, images, price, availability, landing page data and other feed attributes. Treat GTIN cleanup as one part of product data quality, not as a guarantee of approval or performance.

Sources

  1. Product data specification — Google Merchant Center Help
  2. GTIN [gtin] — Google Merchant Center Help
  3. Find a GTIN — Google Merchant Center Help
  4. Export Channels — Feeds for Meta, Google, TikTok and more — AdMotion
Share:
J

Written by

Julia Villegas

Performance Marketing

Julia Villegas works in performance marketing at AdMotion.

Related posts