GTIN to SKU

Taking advantage of the topic, I tried in every way to map the _alg_ean and alg_ean metakey, changing the underscore to advanced as I saw some instructions in other topics. In no way does the field appear as an option to map, so I thought of the solution of copying to the REF (SKU) field because I don’t need to use this code,
but the only solution I found is to generate the EAN with your plugin and go from product to product manually copying the code. If there’s anything I can do, let me know about it! Thank you again!

Hi,

At the moment it is not possible to map the EANs to SKUs but it is possible the other way around to map SKUs to EANs.

I have passed your request to our development team, they will get back to you soon.

Hi @zohaibayub85
Is there any way for the meta alg_ean to be read by the feed plugin I mentioned?

Hello!
I ended up discovering a “bug” in the feed plugin by accident. To show the metakey alg_ean I had to select another default metakey available in the list, save and after that the alg_ean appeared in the list. It’s a bug of the feed plugin and not yours. Anyway my problem is solved! Thank you!

Hi, @laserstore,

I did some research, and I have a couple of notes; maybe they will be helpful to you or to someone else:

1. I’ve installed the Product Catalog Feed by PixelYourSite plugin (free version) on my test server, and our EAN field appeared in their “Custom Fields” section right away. Then I checked the code of the plugin. They are storing meta keys in transients, which means that after their plugin goes through all the products and collects all the meta keys, it saves the results in transient with a 1-day expiration, i.e., you will see new meta keys only after the transient expires. I assume this is why you did not see our key in the list at first. Also, it looks like the feed plugin ignores keys starting with an underscore, so it needs to be changed from _alg_ean to, e.g., alg_ean (in “WooCommerce > Settings > EAN > Advanced > Meta key”).

2. There is a way to store all EANs in SKUs. All you need to do is set our “Meta key” option (in “WooCommerce > Settings > EAN > Advanced”) to _sku. I did quick testing, and it seems to be working fine. I’m not sure if this is a good idea, though.

I hope this helps. I’m marking this thread as “resolved”. Please let me know if you’ll have any questions.

Hi @algoritmika
Thank you very much for your time! Anyway, the problem was solved and I’m glad to know why. Probably the problem occurred because of the transients you mentioned, because I was testing on a site in a staging environment and the next day the field appeared, that is, the transients expired.
Thanks again for the effort to help me!

Hi, @laserstore,

Happy to help ?? Let me know if you’ll need anything else.

And if you like the plugin, please consider leaving us a rating.