Google says Some products don’t have a GTIN assigned, and so you don’t need to submit one.
But if the product does have a GTIN assigned, including this in your product data can increase the performance of the product.
And Only provide a GTIN if you’re sure it’s correct.
So what to do about a missing GTIN depends on whether your product has one. Google’s GTIN page.
“Missing GTIN” in Google Merchant Center means Google expected a GTIN for a product and didn’t get one. Google says products with a missing or incorrect GTIN may have limited visibility. If the product has a GTIN, put it in the field your store uses for barcodes (Barcode on Shopify, “GTIN, UPC, EAN, or ISBN” on WooCommerce). If it doesn’t, because it’s handmade, custom or one of a kind, you tell Google so instead. The wrong fix is inventing a GTIN: Google says never to guess or make up a value.
This post walks the decision, the bulk-edit methods on each platform, and the sync wait before you’ll see the error clear.
What “missing GTIN” actually means
GTIN is the umbrella term for Global Trade Item Number, the product-identifier family that includes UPC (12 digits, North America), EAN (13 digits, Europe and elsewhere), JAN (Japan) and ISBN (books). Google uses GTINs to understand exactly which product you sell. That drives three things:
- Matching. Google groups identical products from different sellers; the GTIN is how it knows your “Acme Wool Beanie” is the same item other retailers list.
- Visibility. Google says including a GTIN, when the product has one, can increase the product’s performance, and products with missing or incorrect GTINs may have limited visibility. Its product data specification says
Products with a GTIN but submitted without one may have limited visibility.
And its GTIN page goes further:if the product does have a GTIN assigned and you don’t submit it, then the product could be disapproved.
- Expected when one exists. Google recommends a GTIN for every product that has one assigned by the manufacturer. Products you make yourself usually don’t have one, and then you shouldn’t submit one.
Decide which path applies
Three paths, depending on your catalog:
- Path A: products HAVE GTINs but the field is empty. Branded resale, dropshipped name brands, anything with a manufacturer barcode on the box. You fill in the GTIN on each variant.
- Path B: products have no GTIN. Handmade, custom or one-of-a-kind items. Your own label products: Google says to submit your brand (your store name) and an MPN if you have one. Products with no identifiers at all: tell Google they have none.
- Path C: dropshipped or wholesale products where the supplier won’t share GTINs. An awkward middle ground with three options.
Pick the right path before bulk-editing. Mixing paths on one product (declaring “no identifiers” while also sending a GTIN, for example) is contradictory, and Google warns on products marked as having no identifier when there’s evidence one exists.
Path A: fill in the GTIN
Each variant that is a different item at the manufacturer (a red small T-shirt and a blue large T-shirt) has its own GTIN. Google’s rules say each variant has its own GTIN, so never paste one code across all of them.
Shopify. There’s no field called GTIN: Shopify uses each variant’s Barcode field, and the Google & YouTube app sends it to Merchant Center as the GTIN.
- One product: Products → open the product → click the variant → fill in Barcode → Save.
- Many products: select products in the Products list and use the bulk editor with the Barcode column, or Products → Export, fill the
Variant Barcodecolumn, then Products → Import. For very large catalogs, an import/export app such as Matrixify handles the same columns with clearer error reports.
WooCommerce. WooCommerce 9.2 and later has a built-in GTIN, UPC, EAN, or ISBN field. Google for WooCommerce syncs it to Merchant Center.
- One product: Products → edit the product → Product data → Inventory tab → GTIN, UPC, EAN, or ISBN → Update. For a variable product, open each variation: each has its own field.
- Many products: Products → Export, fill the
GTIN, UPC, EAN, or ISBNcolumn, then Products → Import with “Update existing products” ticked. - If you send products through a different feed plugin, check which field it reads GTINs from.
Any other platform. Put the GTIN in the product’s barcode or GTIN field, or wherever your Merchant Center integration or feed reads it from. Fill one product first and check it in Merchant Center before doing the rest.
Path B: products with no GTIN
When a product genuinely has no GTIN, don’t send one. Google’s identifier rules, in short:
- Brand: required for new products with a clearly associated brand. For your own label, use your store name. See missing brand.
- MPN: required when there’s no GTIN, if the manufacturer assigned one. See missing MPN.
- No identifiers at all (custom or one-of-a-kind): Google recommends setting
identifier_existstono, and leaving GTIN and MPN empty.
Where to say “no identifiers”:
- Shopify: in the Google & YouTube app, open the product’s data and check “This is a custom product”, on the product page or in the app’s bulk editor.
- WooCommerce: Google for WooCommerce doesn’t send
identifier_exists. Leave GTIN and MPN empty; if you need to sendidentifier_exists=no, use your feed plugin’s option if it has one, or a supplemental data source in Merchant Center. - Any other platform: use your integration’s “no identifier” or custom-product option if it has one, or a supplemental data source in Merchant Center.
Our identifier_exists guide covers doing this in bulk, and the MPN and brand guide covers the brand + MPN route.
Path C: dropshipped products with no GTIN
The hardest case: the GTIN exists somewhere, but your supplier won’t share it. Three options, best first:
- Ask the supplier. Send the SKU list and ask for UPCs or EANs. If they answer, go back to Path A.
- Declare no identifiers. Technically wrong, since a GTIN exists and you just don’t have it. Google says to do this only when you’re sure no identifier exists, and warns when it finds evidence of one, so treat it as a last resort.
- Leave these products out of Google. Keep selling them in your store, but don’t send them to Merchant Center. On Shopify, remove Google & YouTube from the product’s sales channels. On WooCommerce with Google for WooCommerce, set the product’s channel visibility to “Don’t sync and show”. On other platforms, exclude them in your integration or feed.
For a few high-margin products, push the supplier. For thousands of low-margin ones, leaving them out is usually the better choice.
Common mistakes
- Declaring no identifiers while still sending an MPN or GTIN. Pick one; contradictory data is worse than missing data.
- Checking too early. Changes take time to sync and be reprocessed. Checking Merchant Center 30 minutes after a bulk edit may show nothing new.
- Treating GTIN as optional for branded products. If the manufacturer assigned one, submit it.
- Pasting the same GTIN across variants. Each variant needs its own.
- Inventing GTINs to clear the error. Google validates GTINs and says never to guess or make up a value.
For other issues that look fixed but aren’t, see the less obvious Misrepresentation triggers.
How to check your fix worked
- Give it a few days. Your products have to sync and Google has to reprocess them. If products were disapproved and you request a review, Google says a review may take up to 7 business days.
- Check the product issues in Merchant Center (Products). The “missing GTIN” issues should go. If one stays, open that product: usually one variant’s field is still empty.
- Spot-check 5–10 products in Merchant Center: each should show the GTIN you set, or no identifier if you declared none.
If Merchant Center is clean but products still aren’t showing in Shopping, that’s a different problem; see products not showing in Google Shopping.
FAQ
Where is the GTIN field?
On Shopify, it’s each variant’s Barcode field; the Google & YouTube app sends it as the GTIN. On WooCommerce 9.2 and later, it’s GTIN, UPC, EAN, or ISBN on the Inventory tab (and on each variation). On other platforms, look for a barcode, GTIN, UPC or EAN field.
Is a GTIN required for every product?
No. Google recommends it for any product with a manufacturer-assigned GTIN, and products without one may have limited visibility. Handmade, custom and own-label products usually don’t have one: submit brand and MPN, or declare that the product has no identifiers.
What if my supplier won’t give me GTINs?
Ask harder, declare no identifiers as a last resort, or leave those products out of Google. Don’t invent GTINs.
How long does it take for the error to clear?
Usually a few days, once the change syncs and Google reprocesses the product. If you request a review, Google says it may take up to 7 business days.
Can I use the same GTIN across variants?
No. Google says each variant (different color or size) has its own GTIN.
What’s the difference between GTIN and MPN?
A GTIN is a global code from GS1, the standards body. An MPN is the manufacturer’s own part number. Google prefers the GTIN; brand plus MPN is the substitute when there’s no GTIN. See the MPN and brand guide.
For Google’s own rules, see Google’s product identifier requirements. For the platform fields, see Shopify’s product details help and WooCommerce’s GTIN guide.