• Resolved Andrew Comb

    (@tecazwebdev)


    Ok I’m not sure what version it appeared in, but WooCommerce now has a ‘GTIN, UPC, EAN, or ISBN’ field, which was sorely missed, as a lot of modern shops require it, such as Google shopping. I’ve tested it, and it saves the info, however I cannot for the life of me work out where it is saved, and how I could use it:

    I have other plugins for WooCommerce which already have added this as Meta: fields inside the product, which at present is how I read / write manufacturers EAN numbers into products, via bulk updates, and write it to the site, via functions, but exporting the csv, the new field just doesn’t show up?

    Is this an oversight, bug, or intentional? Surely it should be in the standard export, and not in the custom meta fields, but currently it’s nowhere I can see, without diving into mysql, which is a bit above my head!

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @tecazwebdev

    Yes, this field is indeed a new addition to WooCommerce and it’s great to hear that you’ve found it useful. The details entered in this field are saved in the database as post meta.

    You’re right! The current standard WooCommerce export doesn’t include this field. It could be a design decision. However, I’ve already created a bug report about it here: https://github.com/woocommerce/woocommerce/issues/51600

    At the time being, we can’t give you an estimate for when the team will look into or fix the issue, as bug reports are prioritized based on a few criteria. Please subscribe to the GitHub issue if you’d like to receive updates.

    Meanwhile, to include the “GTIN, UPC, EAN, or ISBN” field in your export, you would need to use a custom export solution that allows you to select which fields to include. There are many plugins available that offer this functionality.

    I wish I could help more, but hopefully, this gets you going in the right direction to get some further insight/information.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Thanks for confirming for me, that’s also how I was testing it, and could not find it in the export.

    Hopefully they will add it in later versions.

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @tecazwebdev

    Yes. However, I will mark this thread as resolved. Should you have further inquiries, kindly create a new topic here.

    Thanks!

    Hi Andrew,

    I managed to do it this way:

    • Export products from Woo
    • Add the column Meta: _global_unique_id
    • Import via product import (make sure to tick ‘Update existing products’)


    If you already have a list of products/SKUs, you can use VLOOKUP to match the GTINs. I hope this helps!

    Robbi

    • This reply was modified 2 weeks, 2 days ago by gasurgaelach.
    Plugin Support Reynier C. (woo-hc)

    (@reynierc)

    Hi @gasurgaelach ,

    That’s a smart workaround, and I appreciate your input and contribution! Your method should help others looking to manage the GTIN data for their products effectively.

    If you run into any related concerns or have further tips to share, feel free to start a new discussion.

    Thread Starter Andrew Comb

    (@tecazwebdev)

    Thanks for finding it. The issue was that it wasn’t coming out when I exported products, so I had no idea what meta field to import it. My 3rd party plugin also saves it in a meta-field, which is what I am using right now for these purposes. Fortunately I don’t need it, but it’s really not great for anyone doing IO that it doesn’t work correctly. Hopefully it can be fixed soon!

    Plugin Support Jonayed Hosen (woo-hc)

    (@jonayedhosen)

    Thank you for letting us know that the workaround is working for you! We appreciate your feedback on this issue, and I can confirm that our development team is working on a permanent fix.

    I’ll go ahead and mark this thread as resolved, but if you have any other questions or run into issues in the future, please feel free to start a new topic.

    Cheers!

    I’m with you Andrew, a feature should be a full feature, not an afterthought!

    Kindly, no canned responses from Woo.

    Plugin Support Reynier C. (woo-hc)

    (@reynierc)

    Absolutely, a feature isn’t complete unless it’s done right. We really appreciate your input and bringing this up. Just to keep everyone updated, the team working on addressing this issue.

    You can follow our progress here: https://github.com/woocommerce/woocommerce/issues/52049

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.