BugWP logo BugWP
Back to Community
Home / Community / Plugin → Google for woocommerce

Resolving GTIN Issues in Google for WooCommerce: A Complete Troubleshooting Guide

45 threads Sep 22, 2025 Plugin → Google for woocommerce

Content

Understanding GTIN Problems in Google for WooCommerce

Many WooCommerce store owners encounter GTIN-related issues when using the Google for WooCommerce plugin. These problems often manifest as product disapprovals, missing identifiers, or synchronization errors in Google Merchant Center. Based on community reports and solutions, this guide covers the most common GTIN challenges and how to resolve them.

Common GTIN Issues and Their Solutions

1. GTIN Field Location Changes

Problem: Users can't find the GTIN field in the expected location.

Solution: The GTIN field has been moved from the 'Google for WooCommerce' tab to the standard WooCommerce Inventory tab. Enter your GTIN values there, and the plugin will automatically sync them to Google Merchant Center.

2. GTIN Not Syncing Properly

Problem: GTIN values entered in WooCommerce aren't being carried over to Google Merchant Center.

Solution: Ensure you've properly configured attribute mapping:

  • Go to Marketing > Google Listings & Ads > Attributes
  • Create an attribute rule for GTIN
  • Select "Use value from existing product field"
  • Choose the appropriate field containing your GTIN data

3. Variable Products Not Picking Up GTIN

Problem: GTIN works for simple products but not variable products.

Solution: This often occurs when using third-party SEO plugins. Ensure you've properly configured GTIN settings for both parent and variation products in your SEO plugin's settings.

4. Products Without GTINs Getting Flagged

Problem: Products that shouldn't have GTINs (custom products, digital goods) are being flagged for missing identifiers.

Solution: For products without manufacturer-assigned GTINs:

  • Leave the GTIN field completely blank
  • Set MPN to use your product SKU
  • Set Brand to your domain name (without http/www)
  • These can be configured globally through attribute mapping

5. Duplicate or Grayed Out GTIN Fields

Problem: The GTIN field in the Google for WooCommerce tab appears grayed out or shows old values.

Solution: The plugin now prioritizes the GTIN value from the Inventory tab. The grayed-out field in the Google tab is historical data and doesn't affect synchronization. If you need to remove old values, you may need to edit the _wc_gla_gtin custom field directly.

6. Bulk Management Challenges

Problem: Difficulty managing GTIN values for large product catalogs.

Solution: Use WooCommerce's built-in CSV import/export functionality. Note that the GTIN field is now part of the standard inventory data rather than a separate meta field.

7. Mapping to Custom GTIN Fields

Problem: Wanting to use existing custom fields for GTIN data instead of the default fields.

Solution: While the plugin doesn't directly map to arbitrary custom fields, you can use the woocommerce_gla_product_attribute_values filter for custom mapping, or consider migrating your existing GTIN data to the standard Inventory field.

When GTIN Isn't Required

Remember that not all products require GTINs. According to Google's policies, these product types typically don't need GTINs:

  • Custom-made products
  • Digital products (though ISBN is required for books)
  • Products without manufacturer-assigned identifiers
  • Vintage or collectible items

For these products, focus on providing strong MPN and Brand information instead.

Final Recommendations

Always ensure your GTIN values meet Google's formatting requirements. Different product types require different GTIN lengths (12-digit UPC, 13-digit EAN, etc.). Test with a small batch of products before applying changes to your entire catalog, and allow 24-48 hours for changes to fully propagate through Google's systems.

If problems persist, consider checking Google Merchant Center directly for more detailed error messages, as sometimes the issue may be with Google's interpretation of your data rather than the synchronization itself.

Related Support Threads Support