Support for GTIN requirements

  • Edit: I missed the call out in the documentation on this. Looks like Woo added the GTIN field fairly recently and GFW hasn’t had a chance to adapt to it yet. There is a separate GTIN field tucked away under GFW specific metadata for products which I missed. There are also instructions on how to avoid the gtin flag for custom products

    Google Merchant Center limits visibility of products which don’t include the GTIN. Woocommerce has a predefined field for GTIN but this plugin takes no notice of it. It does allow you to create a custom mapping for GTIN but then you have to ignore the WooCommerce GTIN field and either overload another field like SKU or create a custom attribute in Woo. Neither is the right way to handle this pretty significant oversight though.

    A related issue is that Google Merchant Center also allows you to specify GTIN doesn’t exist for certain types of products. Again, this plugin gives you no ability to set that attribute even if you wanted to do a custom attribute mapping.

    • This topic was modified 1 month, 1 week ago by moneals.
    • This topic was modified 1 month, 1 week ago by moneals.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Saravanan S, a11n

    (@simplysaru)

    Hey there @moneals,

    Thanks for updating your review the most recent and relevant information about GTIN support in Google For WooCommerce. We appreciate you spending the time to understand the documentation and updating your review. The GTIN support was added in WooCommerce in version 9.2 and before which, GTIN existed on it’s own and was part of Google For WooCommerce. Given there are thousands of merchants that still use the old fields, our devs are working on a way to move this data to the new field that is part of WooCommerce and then set it up as the primary GTIN field that will be synced. Given the complexity of the no of merchants and the data that is being mapped, this requires a bit of rigorous development and testing. That said, this will be streamlined soon as this is already in the works. Thanks for your patience and understanding.

    The Woo response is quite awful. If something new is introduced, it should be in the roadmap for all internally developed profit making plugins. Woo has simply let the ball roll with no plan whatsoever.

    Introduce a GTIN field – brilliant – we can move away from custom fields, but at least make it supported. It isn’t even an exportable/importable field. Awful behaviour from Woo.

    Despite moving to Woo’s official field, I have clients with thousands of products denied from Merchant Centre. It is quite horrendous.

    • This reply was modified 1 week, 1 day ago by gasurgaelach.
    Plugin Support Reynier C. (woo-hc)

    (@reynierc)

    Hi @gasurgaelach ,

    I completely understand how frustrating it must be to navigate this GTIN issue, especially with the impact it’s having on your clients and their product listings.

    We also really appreciate you for sharing this feedback and understand that we should ensure all parts of our system work together seamlessly, especially for new features like GTIN. The good news is that we’re actively working on refining this process. In the meantime, using meta:_global_unique_id as a header for GTIN in your CSV should help with the bulk updates.

    Please keep an eye on our progress here: https://github.com/woocommerce/woocommerce/issues/52049 Your experience drives us to do better, and we really appreciate your patience as we work through this.

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