How can I remove duplicate GTIN

Hi @troyw2015

It took some time add the feature, and we truly thank everyone for being patient while we updated it.

About your question, I’m happy to clarify things for you! The GTIN in the ‘Google for WooCommerce’ tab should indeed be updated when duplicating products, as Google uses this information. If it’s showing as greyed out, you may need to update the product itself then allow to sync. To remove or change the GTIN for duplicated products, try this:

1. Go to ‘Products’ and edit the duplicated product.
2. Click on the ‘Inventory’ tab under product data.
3. Update the GTIN field with the new number.
4. Save changes.

Note that Google for WooCommerce Extension is designed to sync product data, including the GTIN from the Inventory tab, to Google Merchant Center. This ensures that the product information like availability, pricing, and identifiers like GTIN is up-to-date across Google services. So, keeping the GTIN accurate in the Inventory tab is important for correct data syncing to Google.

Hope this helps and let us know if you have more questions.

@troyw2015 Notice we do have a GTIN Migration tool in place also.

https://ibb.co/7XFp1ym

We do hide GTIN field Inside Google for WooCommerce extension only for new installs old installations can still see the old value, but for new editions they should do in Product Inventory. In case GTIN is set in Product Inventory (a new feature of WooCommerce introduced in August 2024) it will have precedence over the old GTIN in the extension. In case is not migrated we will still try to read the old GTIN for backwards compatibility. But we recommend doing the migration.

Can someone please clarify what is being explained above? So does it sync the new GTIN if I add it to the Inventory or ummmm, what ever it is that mppellicer? just said???

Hi @troyw2015 ,

Thanks for reaching out!

The explanation above covers the GTIN migration process in the Google for WooCommerce extension and how it integrates with newer WooCommerce versions and product inventory settings.

Here’s the gist: If you’re adding a new product in WooCommerce (after August 2024), you’ll need to enter the GTIN in the Product Inventory section—that’s now the primary location for it. If you’re using an older setup, the GTIN field in the Google for WooCommerce extension might still appear, but it’s best to use the migration tool to update your settings.

To answer your question:

Does it sync the new GTIN if I add it to the Inventory?

Yes! Adding the GTIN in the Product Inventory section ensures it syncs correctly.

Let me know if there’s anything else I can help with!

Thanks Jonayed,

Where I am still confused is while I understand that adding the GTIN to the new plugin syncs to Google, what happens when the GTIN in the old ‘Google for Woocommerce’ Tab displays a different GTIN?

Also, what is this ‘Migration Tool’ you keep mentioning?

Again, my issue stems from my client duplicating products to create variations of similar products (such as colour). When they duplicate the product, they can change the GTIN in the Inventory, but not the old ‘Google for Woocommerce’ tab, which retains the old GTIN from the original product.

So my questions are;

A. Is this a problem for any Google services that utilise this data (such as Google Merchant Centre)

B. Is the old Google for Woocommerce GTIN field completely redundant and no longer accessed by Google Services?

C. If there is a problem with having a different GTIN in the Google for Woocommerce GTIN field, how do I remove it?

Thanks

Hi @troyw2015 ,

I understand there’s still some confusion about the migration tool and the old method of entering GTINs in the Google for WooCommerce tab. Let me help clarify:

Also, what is this ‘Migration Tool’ you keep mentioning?

The migration copies all GTINs from the old Google for WooCommerce tab into the new Product Inventory GTIN field. If you’ve already added GTINs in the Inventory tab, these won’t be overwritten. The old GTINs in the Google for WooCommerce tab won’t be removed, but the system will prioritize the new field after migration.

Is the old Google for Woocommerce GTIN field completely redundant and no longer accessed by Google Services?

If you haven’t migrated yet, Google Services will still read GTIN data from the old Google for WooCommerce tab.

If there is a problem with having a different GTIN in the Google for Woocommerce GTIN field, how do I remove it?

By running the migration, GTIN data will shift to the Product Inventory field. Once migrated, the new field will take precedence, and the old data won’t interfere anymore.

To perform the migration, go to Marketing > Google for WooCommerce. You’ll see a notice with an option to “Click here” to start the migration process, as shown in the screenshot:

I hope this clears up any confusion!