Missing GTIN value in Merchant Center: fix it in your catalog
Back to Blog
SEO WooCommerce
Team Katapic
11/15/2026
10 min

Missing GTIN value in Merchant Center: fix it in your catalog

The missing GTIN flagged by Google Merchant Center almost always originates in the WooCommerce catalog. Learn the causes, how to verify the code, and how to fix it in bulk.

Missing GTIN value in Google Merchant Center: what it really means

The message appears when the feed does not contain a GTIN for a product that should have one based on its brand and category. There are three ways to resolve it: enter the actual GTIN printed by the manufacturer, provide the brand and MPN when no code exists, or set identifier_exists = no for products that genuinely have no identifier. An invented code or one copied from a similar product makes the situation worse because it replaces a visible gap with false data.

In a small WooCommerce catalog, the GTIN is rarely missing everywhere: it is usually missing in specific places. The supplier provides a price list with the barcode in a column nobody imported, variations inherit a code that belongs only to the parent product, or a spreadsheet removes leading zeros. Merchant Center does not inspect the page like a customer does: it reads the feed fields one by one, and if the identifier field is empty, it flags it even when the code appears in the description or in a photo of the packaging.

WooCommerce product list with the empty GTIN column next to the Merchant Center message
An empty GTIN field in the catalog is the most common cause of the message in Merchant Center.

When Google flags a missing GTIN and what it changes for the product

Google flags a missing GTIN when it reads the feed and does not find a completed gtin field for a branded product with a known barcode; whether the message is a warning or an error depends on the individual product.

According to Google Merchant Center documentation, the identifier helps recognize the same item across different sellers and match it to the correct listing. This is why branded products with barcodes are treated more strictly than handmade or customized items. A practical way to understand your situation is to open the product list in Merchant Center, go to the issues section, and filter for the GTIN message. Check how many products are affected and what status they have.

Warning or error: how to tell which one applies

If the product appears among active products with a warning icon, you have a warning: the product may continue to be shown, but Google has fewer elements with which to match it. If it appears among disapproved products, you have an error: the product remains excluded until you correct the data. The same message text can fall into either category, so the product status matters more than the wording in the issue title.

Why the problem affects many products at once

An unimported column or a field the feed does not read can generate hundreds of identical alerts at once. That is why it is better to look for the upstream cause before correcting products one by one: a single catalog fix can close an entire family of messages.

The most common causes of missing GTINs in WooCommerce

In WooCommerce, a GTIN is usually missing for one of these reasons: the field was never completed, the code is in the wrong place, the supplier's price list is incomplete, variations have no individual code, leading zeros were lost in a spreadsheet, or the feed does not read the field.

Recent versions of WooCommerce provide a dedicated field for GTIN, UPC, EAN, or ISBN in the product's Inventory section. In older stores, the code often ended up in a custom attribute, a theme field, or the title, and the tool that builds the feed cannot see it. Before concluding that the data does not exist, check where you actually stored it.

  • The GTIN field exists but is empty because the products were created manually without the price list available.
  • The barcode is in the title, description, or an attribute, not in the field read by the feed.
  • The supplier file contains the code column, but the import did not map it.
  • Variations such as size or color have no individual code, and the feed cannot inherit one from the parent product.
  • Leading zeros in a UPC or EAN disappeared while passing through a spreadsheet.
  • The code belongs to a multipack, while the product being sold is an individual item.
  • The product genuinely has no GTIN, but nobody declared this in the feed.
The GTIN field is completed, but Merchant Center sees it as empty

This happens when the plugin or tool that generates the feed pulls data from a different field than the one you completed. Download the generated file and look for the identifier column: if it is empty for your products, the problem is the mapping between the catalog and the feed, not the data itself.

Variations without their own code

A shirt sold in four sizes with different barcodes has four GTINs, not one. If the catalog contains only one, the feed covers at most one variation and the others remain flagged. The code must be entered in the field for each variation, not just in the parent product, and a code should never be duplicated across different variations to make the alert disappear.

Incomplete supplier data or lost zeros

A spreadsheet treats a code as a number and drops leading zeros; a twelve-digit UPC becomes eleven digits and no longer passes validation. Before importing, set the code column to text. If a code has already lost its zero, compare it with the original price list: guessing the missing digit is the fastest way to introduce false data.

Where to find the correct GTIN and how to verify it with the GS1 check digit

The correct GTIN is the number printed below the bars on the packaging or shown in the manufacturer's price list. You can verify it by counting the digits and recalculating the last one, the GS1 check digit.

  1. Take the code printed below the bars on the packaging, or the EAN or UPC from the official price list, rather than the internal SKU in your management system.
  2. Count the digits: a GTIN has eight, twelve, thirteen, or fourteen digits. Any other length indicates a copying error.
  3. Recalculate the check digit, the last digit, from the others using the example below.
  4. If the code fails the check, ask the supplier to confirm it. Do not correct it by guesswork.
  5. Enter it in the product's GTIN field as text, without spaces or hyphens.
How to calculate the check digit by hand

Hand-built example: the code 8001234567897. Take the first twelve digits, 800123456789. Starting from the right, multiply the first by 3, the second by 1, the third by 3, and so on. Add the results: 103. The check digit is the difference up to the next multiple of ten, namely 110 minus 103, which equals 7. The last digit of the code is 7, so the code is correctly formed.

A correct check digit only shows that the code is written correctly; it does not prove that it belongs to that product.

The check catches typos, transposed digits, and lost zeros. It does not catch a valid code taken from another item. That is why the source must remain the manufacturer or its price list, and a GTIN should never be taken from a random website just because it “looks” right.

Products without a GTIN: MPN, brand, and identifier_exists = no

A product that genuinely has no GTIN should be presented to Google with a brand and MPN, or with identifier_exists = no when it has neither. What you must not do is fill the field with a code that does not belong to you.

The MPN is the code the manufacturer assigns to the model. You can find it in the price list, on the label, or on the brand's website. A business that manufactures its own products is the manufacturer, so it can assign a unique, stable code to its models. According to Google documentation, identifier_exists = no is intended for products without identifiers, such as customized, handmade, or discontinued items. WooCommerce does not have a native field with this name: the plugin or tool that generates the feed sets it through a rule or custom field. Always check the generated file to confirm that the value arrived.

A craftsperson selling ceramics and managing about forty products

An illustrative example: every item is made in a workshop and has no manufacturer's barcode. In this case, use a brand, such as the workshop name, a stable internal MPN for each model, and, where the item is unique, the identifier_exists = no declaration. The GTIN should not be searched for elsewhere or simulated.

A reseller of third-party brands with a code on the packaging

Here, identifier_exists = no would be the wrong shortcut: the code exists, so it must be entered. Declaring that an identifier is absent when the product really has one creates an inconsistency that Google may detect by comparing the product with other offers for the same item.

Is a GTIN needed in a ChatGPT feed?

OpenAI's format has nine required fields: item_id, title, description, url, brand, seller_name, image_url, availability, and price with currency. GTIN and MPN are optional, and a GTIN should never be invented. Only in the Google-compatible profile, when OpenAI confirms it, is a GTIN or MPN required, except when identifier_exists = no. The names link, image_link, and identifier_exists belong to Google Merchant Center, not to the ChatGPT feed.

How to correct a WooCommerce catalog in bulk

Bulk correction uses a file: export the products, complete the GTIN column using the supplier's source, check the length and check digit, and reimport the file while updating existing products.

According to the WooCommerce developer blog, WooCommerce 11.2, in the release notes dated October 7, 2026, introduces GTIN matching in product CSV imports. If the supplier's price list already contains the code, the import can therefore match rows to existing products without relying only on the SKU. With earlier versions, matching remains based on the method you already use, and it is best to work on a sample before changing the entire catalog.

  1. In WooCommerce › Products, use the CSV export and keep an untouched copy of the original file.
  2. In the spreadsheet, set the GTIN column to text, then paste the codes from the supplier's price list.
  3. Filter rows with a length other than eight, twelve, thirteen, or fourteen digits and correct them at the source.
  4. Recalculate the check digit for the remaining codes and flag those that do not pass.
  5. For products legitimately without a code, leave the field empty and make a note of the row: the declaration is made separately, not with a fake code.
  6. Import the file using the option to update existing products, starting with a few rows.
  7. Check the generated feed and wait for Merchant Center to read it again before assessing the result.
A product page before and after correction

Illustrative example, without measured results: a page for a glazed mug.

  • Before: an uppercase title ending with an internal code; empty brand; empty GTIN; the barcode written only in the description text.
  • After: a normally formatted title; completed brand; the thirteen-digit GTIN 8001234567897 in the GTIN field, passing the check digit; the model MPN in the dedicated field.
Spreadsheet with the GTIN column checked for length and check digit before import
Check the GTIN column in the file before reimporting it into WooCommerce.
A feed does not add information that the catalog does not contain: it transmits the data as it is, including gaps.

The page text and structured data work together: if the code is in the correct field and matches what can be read on the page, Google has an additional point of comparison. What holds a product back is missing or vague information, both in the text and in the data.

Common mistakes when correcting a missing GTIN

The mistakes that bring the message back, or create a worse one, are almost always shortcuts: invented codes, lost zeros, variations sharing the same code, or declaring an identifier missing when it exists.

A GTIN copied from a similar product

What it looks like: the message disappears, but alerts about an invalid identifier or a product matched to a different item then appear. Why it happens: the code is correctly formed but belongs to another item. How to fix it: obtain the code from the manufacturer or price list, and if you cannot find it, declare its absence instead of borrowing one.

Leading zeros lost in a spreadsheet

What it looks like: the code has eleven or twelve digits instead of twelve or thirteen, and Merchant Center rejects it. Why it happens: the spreadsheet treated the code as a number. How to fix it: check the original price list and reimport with the column formatted as text.

The same GTIN on every variation

What it looks like: multiple variations appear as duplicates or only one is considered valid. Why it happens: the parent product's code was propagated to “fix” the message. How to fix it: enter each variation's own code; if some have none, declare that for those variations.

identifier_exists = no on a product that has a code

What it looks like: the product passes, but comparison with other offers for the same item does not work or an inconsistency alert appears. Why it happens: the declaration was applied to the entire catalog using one rule. How to fix it: limit the declaration to products without a code and check the feed row by row on a sample.

The code is in the text, not in the field

What it looks like: the description contains a clearly readable EAN, but the feed column is empty. Why it happens: the feed reads only the mapped field. How to fix it: move the code to the GTIN field and check the mapping in the generated file.

How Katapic flags a missing GTIN in the catalog

Katapic starts with diagnosis: it finds where the barcode is missing or invalid, suggests corrections that do not require AI, and never generates an identifier.

The free WooCommerce catalog scan reads the latest one hundred products in read-only mode without changing anything; with a free account, the diagnosis covers the entire catalog. Deterministic checks do not use AI or spend credits. Findings include invalid barcodes, missing fields, and duplicates, and the dashboard opens on “Where to start,” showing the most significant findings and how many products each affects. The barcode is validated using the GS1 check digit and flagged if it does not pass.

  • A barcode is never taken from the web: Katapic never generates an identifier.
  • A product legitimately without a code is declared as such. This is one of the free corrections, shown with a preview and count, applied only after your confirmation, and reversible for 30 days.
  • Products that differ only by size, color, or packaging are proposed as variations of one product, subject to confirmation.
  • For supplier price lists in PDF format, Katapic reads the products page by page and shows the rows before you confirm. Importing the rows is free; scanning costs one credit for every 10 products found.
  • Readiness for six channels shows which fields are missing for each product, together with the public rule behind each one. Google Shopping and ChatGPT feeds can be downloaded with only the products that pass.

To check a file before uploading it, use the free product feed validator. The missing data still needs to be corrected upstream: Katapic shows where the problem is and suggests what to do, but the manufacturer provides the correct code.

Frequently asked questions about missing GTINs in Merchant Center

How can I reduce the number of products rejected in Merchant Center?

Start with the problem affecting the most products, not with an individual item. In Merchant Center's issues list, group rejections by message and look for the upstream cause: it is often a catalog field that is incomplete or not mapped to the feed. Correct one product family at a time, update the feed, and check a sample before moving to the next one. Identifiers are a good place to start.

Is a missing GTIN value an error or a warning?

It depends on the product. If it appears among active products with a warning, it is a warning and the product may remain visible. If it appears among disapproved products, it is an error and the product remains excluded until it is corrected. The relevant factor is the status assigned by Merchant Center, not the wording of the message.

How long does Google take to reapprove a product after correction?

Google does not guarantee a specific timeframe. You see the result after Merchant Center reads the updated feed again. After correcting the catalog, regenerate the feed, wait for the next reading, and check the product status. If the message remains, open the generated file and verify that the GTIN actually reached the correct column.

Can I enter a fake GTIN or a string of zeros to make the error disappear?

No. An invented or zero-filled code does not identify any product, and Google may reject it as invalid, creating an additional problem. If the product has a code, enter the real one. If it does not, use the brand and MPN or set identifier_exists = no. A GTIN should never be fabricated just to make the feed look “clean.”

How do I set identifier_exists = no in WooCommerce?

WooCommerce does not have a native field with this name. It depends on the plugin or tool that generates the feed: usually, you use a custom field or a rule applied to products or categories. Set the value only for products without a code, then open the generated file and verify that the declaration is present on the correct rows.

Is a GTIN required in a product feed for ChatGPT?

In OpenAI's format, the required fields are nine: item_id, title, description, url, brand, seller_name, image_url, availability, and price with currency. GTIN and MPN are optional, and a GTIN should never be invented. They are needed only in the Google-compatible profile, when OpenAI confirms it, except when identifier_exists = no.

Further reading

Frequently asked questions

How can I reduce the number of products rejected in Merchant Center?
Start with the problem affecting the most products, not with an individual item. In Merchant Center's issues list, group rejections by message and look for the upstream cause: it is often a catalog field that is incomplete or not mapped to the feed. Correct one product family at a time, update the feed, and check a sample before moving to the next one. Identifiers are a good place to start.
Is a missing GTIN value an error or a warning?
It depends on the product. If it appears among active products with a warning, it is a warning and the product may remain visible. If it appears among disapproved products, it is an error and the product remains excluded until it is corrected. The relevant factor is the status assigned by Merchant Center, not the wording of the message.
How long does Google take to reapprove a product after correction?
Google does not guarantee a specific timeframe. You see the result after Merchant Center reads the updated feed again. After correcting the catalog, regenerate the feed, wait for the next reading, and check the product status. If the message remains, open the generated file and verify that the GTIN actually reached the correct column.
Can I enter a fake GTIN or a string of zeros to make the error disappear?
No. An invented or zero-filled code does not identify any product, and Google may reject it as invalid, creating an additional problem. If the product has a code, enter the real one. If it does not, use the brand and MPN or set identifier_exists = no. A GTIN should never be fabricated just to make the feed look clean.
How do I set identifier_exists = no in WooCommerce?
WooCommerce does not have a native field with this name. It depends on the plugin or tool that generates the feed: usually, you use a custom field or a rule applied to products or categories. Set the value only for products without a code, then open the generated file and verify that the declaration is present on the correct rows.
Is a GTIN required in a product feed for ChatGPT?
In OpenAI's format, the required fields are nine: item_id, title, description, url, brand, seller_name, image_url, availability, and price with currency. GTIN and MPN are optional, and a GTIN should never be invented. They are needed only in the Google-compatible profile, when OpenAI confirms it, except when identifier_exists = no.

Related articles