Shopify's standardized product taxonomy categories metafields issues

Store Feedback
1

Hello,

I’m trying to arrange the transition to the new meta fields in the categories for the client, but there are a whole series of problems, and I’m interested in if anyone here has solutions for those problems.

  1. I don’t see the possibility of changing the meta field names (all changes are disabled), although it’s only a visual name change, so I don’t see the point of why name changes are disabled. To be clear, an example is “Color”, where the name cannot be changed to (say) “Shoe Color”.
  2. I don’t see an option to add an option value, because the developers didn’t include all possible option values. For example, for footwear, in the “Flats” category, there is no “Loafers” option value, and a new value cannot be added. Metafields made in this way become completely useless with this policy and practice.
  3. The developers have created a separate style metafield for each footwear category, instead of having just one “Style” for all footwear categories. So now it has the meta field “Sneaker Style”, “Slipper Style”, “Boot Style”, … This idea is utterly pointless for at least two reasons:
    1. When you go to the “All Shoes” collection, on the side in the Filtration section, there are items:
      “Sneaker Style”
      “Slipper Style”
      “Boots Style”
      “…”
      which in itself seems tragicomic and completely unusable.
    2. Such senseless multiplication of metafields creates a problem with filtration because the “Search and Filter” application limits the number of metafields in filtration. which prompts users to exclude other attributes for filtering searches.

Does anyone have any ideas how to solve these problems?

1 Like
2

Hi @wpCloudSolution ,

I understand your frustrations with the new metafields in Shopify, and these challenges can indeed complicate things. Here are some potential solutions and workarounds for the issues you’ve mentioned:

  1. Changing Metafield Names:
    Unfortunately, Shopify has limitations on changing the names of existing metafields. One workaround is to create new metafields with the desired names and then migrate your data over to these new metafields. This way, you can maintain the names you prefer without being constrained by the original naming conventions.

  2. Adding Option Values:
    If you’re unable to add new option values directly, consider using tags or creating custom product types that can accommodate all relevant categories. This way, you can still differentiate between different styles (like “Loafers”) without being limited by the metafield structure.

  3. Consolidating Style Metafields:
    Creating separate metafields for each category can indeed lead to confusion. I recommend consolidating these into a single “Style” metafield that can apply to all footwear categories. You might need to work with a developer or use a Shopify app to help manage and unify these metafields more effectively. This can simplify filtering and improve the overall user experience.

  4. Filtering Issues:
    For the filtration problem, consider leveraging the “Search and Filter” app settings to optimize how metafields are displayed. You might want to prioritize the most relevant attributes or combine similar attributes to reduce clutter. Additionally, ensure that your metafields are set up correctly in terms of visibility for the filters you wish to use.

  5. Feedback to Shopify:
    Since these issues stem from platform limitations, providing feedback to Shopify can be helpful. They often consider user insights when planning future updates, so sharing your experiences may lead to improvements in metafield management.

I hope these suggestions help address the challenges you’re facing. If you have further questions or need more specific guidance, feel free to ask!

3

Hello,

I may need to be clearer.

  • Changing Metafield Names:

First, I am not referring to the frontend, but primarily to the backend display (although this would normally change the frontend display as well).

Second, the point here is that there are fields to display the metafield name and a field for the base value of the metafield, but there is also a “handle” (slug, or whatever). I understand that for predefined values ​​the field for the basic value (used for indexing) and “handle” cannot be changed, but I do not know that the name of the display field cannot be changed, because it is only for display anyway.

Anyway, this is not a particularly significant problem, because the name of the metafield display can be changed in the frontend, and for the display in the backend, it seems we have to get used to using what it is.

In the end, this was not a question for help, but a statement for the Feedback developers, that what they are doing (disabling the change of the display name of the field) does not have its real and functional meaning.

  • Adding Option Values:

The point here is that I understand that this field is for indexing meta field values, and it’s fine that these are “locked” field values, but it’s a complete bummer that many meta fields don’t have an “Other” option when creating new values.

Again, this was not a question for help, but a statement for the Feedback developers, that what they are doing (not adding to all metafields the base value option “Other”) does not have its true and functional meaning.

  • Consolidating Style Metafields:

I don’t understand this remark at all, because I also wrote exactly how it doesn’t make sense that they put separate metafields for Style per shoe type, instead of having only one metafield for Style for all types of shoes.

An example of Loafers. I don’t understand why they have Loafers as a Style for Flats and Loafers with Heels for Heels. Not only is it logical that Loafers are on heels if Shoes on Heels are selected, but it is also technically impossible to show flat Loafers under Shoes on Heels.

  • Filtering Issues:

I don’t even understand the purpose of this remark. Namely, this section of the forum is for objections to Shopify developers and that’s exactly what I did. Namely, it is illogical that some developers within Shopify (responsible for metafields) develop metafields, without AT ALL taking into account the limitations of their fellow programmers in Shopify who develop the Filter application.

So I’m not asking for help here, I’m pointing out the STUPIDITY and DISORGANIZATION within the Shopify programming itself, where one department doesn’t consult another department at all regarding limitations.

  • Feedback to Shopify:

I don’t understand again. So isn’t this the right place for Feedback to Shopify Developers?