GTIN-EAN field grey, cannot be edited

Hi there,

The value in the WooCommerce > Inventory Tab will take priority when the product is synced to your Google Merchant Center account. So if the correct GTIN value is set there then you don’t strictly need to update the previous value.

However if you are concerned about fixing the value then you’d need to edit the custom field _wc_gla_gtin

One way to do this is to use a code snippet plugin and then add the following snippet to enable hidden fields in the Product editor:

add_filter( 'is_protected_meta', '__return_false' );

I’d suggest to be careful with editing any of the other fields and turn off the snippet again after you’ve fixed the GTIN field.

Hello Michael, thanks for the answer…. I don’t understand sorry. If I add the GTIN in the inventory field, when i save, the field returns blank… and in the google for woocommerce tab the gtin field has the old and wrong one… and it is not editable. It has never been in this way, it was always editable,i think it is one of your last updates that created this issue.

Hello alerion2,

Thank you for your reply.

I understand you are unable to edit the GTIN-EAN field in the Google for WooCommerce tab, as it appears greyed out.

Could you share screenshots of the GTIN-EAN field in the product settings and the data from your Google Merchant Center?

This information will help me understand the issue better and assist you effectively.

Best regards.

hello zubaid,

here it is: https://ibb.co/2P0ZX2x
as you can see the field is grey and cannot be edited. I cannot show you the google merchant screen because it is a draft product, i have yet to publish it. the issue is that these products have been created by duplicating other products, and that ean is wrong and i cannot edit it… and if i put it in the inventory field and save… it doesn’t overwrite this and the ean inventory field returns blank after saving.

Hey there @alerion2 ,

The GTIN field inside Google for WooCommerce is replaced in favor of the new GTIN field inside WooCommerce core.

For editing this field please go to Product -> Inventory tab. There you will find the new field.

https://ibb.co/P4v9JSn

You mentioned that when you do so, the field returns blank. I tried in my machine with the GTIN number you have in the image ( 8032754128862 ) and it saved correctly. Just to clarify, when you mention returns blank, do you mean in WooCommerce? Can you provide us with the new number you’re trying to use ?

Thanks

• This reply was modified 3 months, 3 weeks ago by mppellicer.

Am I the only one seeing a major flaw with this “new” feature?!! My variations in a product have all different GTINS (BY LAW!) and now only 1 GTIN can be attached to all variations? Who thought of this brain fart? This is very bad.

@eajlbekkers Every variation has as well their own GTIN field.

Just go to the Variable Product – Select “Variations”. Click on the Variation and you will find the GTIN field there.

Yes this is how I have it configured, but now the GTIN is placed/migrated at the ‘stock’ part of the parent product. The GTIN on varation part is greyed out and cannot be edited anymore after the latest update.

While the GTIN,?UPC,?EAN, or?ISBN is still available on the inventory tab for variable products. This value is only used if it isn’t set per variation (similar to how the SKU fields works).

If each variation has a unique GTIN number than you can set this per variation, the field is right next to the SKU field when expanding a variation’s details.

Is this the same behaviour you are experiencing? Or is there something which is preventing this field from appearing?

Thanks for the reply. I do indeed see this new field on variation level. However when I copy a product to make a new product; the GTIN field is baked in/greyed out. What will happend if I set the GTIN in the new field. Will it overrule the old ( greyed out) field?

Also what happends if I initiate the GTIN migration? Will all the GTIN fields on the old greyed out field be placed in the new field shown in your screenshot?

The new GTIN field in WooCommerce Core will have priority over the deprecated GTIN field in Google for WooCommerce. So in case you add the GTIN in the new inventory field (we recommend to use migration for that) thats the one we will send.

With the migration all the (valid) GTIN in the deprecated Google for WooCommerce field will be copied to their respective GTIN field in the inventory tab (or respective variation) in case it is not set yet (works for Simple and Variations). The previous GTIN wouldn’t be deleted tho. We just copy the data from one field to another.

Caveats:

– If GTIN is already set in the new field. Then the migration will NOT copy the GTIN to avoid accidental overrides.
– The new GTIN field has some validation rules. If the GTIN is not validated it won’t be copied.

• This reply was modified 3 months, 2 weeks ago by mppellicer.

Thanks for clarifying! I’ve done the migration and it went well. Only issue I’ve spotted is that there is no way to map this woocommerce GTIN field in my CTX Feed, but that will sort itself out probably.

Only issue I still have with Google for Woocommerce is that only about halve my products are updated. I’ve used the manual push because no products were updated after I turned off bulk discount. When manually pushed only halve the products (normale prices) are updated. The rest still show incorrect sale prices. Now the manually push is ‘broken’. It says that merchant center isn’t configured the right way, but thats incorrect because it worked before.

Would like to know why this plugin has such sync issues. Will probably cancel the plugin if this issue persists and use only CTX feed plugin.

Hi @eajlbekkers Happy to hear the GTIN feature and migration issue is solved for you.

For the other request you mentioned, please feel free to open a new different thread with your specific topic with all the information you can so we can assist further.