WooCommerce does not support custom fields for product variants

  • Resolved agg2

    (@agg2)


    6 years, 8 months ago

    I’m referring to Custom Fields which can be enabled under Screen Options on the WooCommerce edit product pages.

    This problem is critical because without the custom fields I am unable to add MPN data – needed for Google Merchant approval. I have always used custom fields to enter MPN data for single products. However, because custom fields are not segregated for product variations – there are only one set of custom fields which will apply to all product variations – this is problematic because different product variations may have different MPNs, for example. And without being able to specify unique MPNs for each product variant, you cannot get product approval on Google Merchant. Other feed plugins have solved this problem with an add-on.

    What is your solution for this?

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter agg2

    (@agg2)

    (You have admin access via the plugin setting.)

    Thread Starter agg2

    (@agg2)

    Is anyone ever going to answer this question? I prefer your plugin to exportfeed’s but if you can’t offer a solution whilst they can, then I will have no choice but to switch plugins.

    • This reply was modified 6 years, 8 months ago by agg2.

    Hi @agg2,

    My apologies for the delayed reply. I’ve been getting so many questions for help the last couple of weeks that I cannot answer everybody as fast as I would like too.

    Our plugin offers a few options for your issue:
    – when the custom field name is identical for both your single and variable products you can map it to a field that Google requires. The plugin will pick up both the values for the single and variable products;
    – there are a lot of plugin’s available that enable you to add GTIN’s (such as MPN’s) to your products for both single and variable products. Our plugin also supports most of these plugins.

    Hope this answers your question?

    All the best,
    Joris

    Thread Starter agg2

    (@agg2)

    This remains problematic for me.

    After following your lead, I installed the WC Fields Factory plugin.

    However, this plugin does not work in conjunction with your plugin because instead of submitting separate MPNs for each product variation (size for example), it’s submitting an array – or is it that Product Feed Pro is not extracting the data properly?

    Concrete example:
    I sell Micro SD cards and they are offered in different storage capacities, 16, 32, 64 and 128 Gb.

    If I look at my Google Merchant feed, what WooCommerce Product Feed Pro plugin has extracted from the custom fields data mediated by WC Fields Factory is the complete array of MPNs for every product variation:
    16Gb – “SDC10G2/64GBFR,SDC10G2/128GBFR,SDC10G2/32GBFR,SDC10G2/16GBFR”
    32Gb – “SDC10G2/64GBFR,SDC10G2/128GBFR,SDC10G2/32GBFR,SDC10G2/16GBFR”
    64Gb – “SDC10G2/64GBFR,SDC10G2/128GBFR,SDC10G2/32GBFR,SDC10G2/16GBFR”
    128Gb – “SDC10G2/64GBFR,SDC10G2/128GBFR,SDC10G2/32GBFR,SDC10G2/16GBFR”

    Instead of segregating the unique MPNs properly per product variable:
    16Gb – “SDC10G2/16GBFR”
    32Gb – “SDC10G2/32GBFR”
    64Gb – “SDC10G2/64GBFR”
    128Gb – “SDC10G2/128GBFR”

    Have I don’t something wrong? Or is your plugin not compatible with WC Fields Factory, which is the best custom fields plugin I have found that caters to product variations?

    You have opened another issue for this on the forum so I will close this one for now.

    Best,
    Joris

    Thread Starter agg2

    (@agg2)

    Ok, but please note they are not duplicates. They are two distinct problems based on two different approaches I have tried.

    Thread Starter agg2

    (@agg2)

    “when the custom field name is identical for both your single and variable products you can map it to a field that Google requires”

    What about when the field names differ? Are you saying they wouldn’t be properly mapped, in that case?

    Yes that is the case. This is because you can only map 1 attribute to a field and not two which is needed when a custom field has a different naming for single and variable products.

    All the best,
    Eva

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘WooCommerce does not support custom fields for product variants’ is closed to new replies.