using metafields via API / rithum

[rob-it]

Hello,

we been using rithum's api to enrich our shopify store...
we have 50 metafields by default per product avaible, we can
describe, namespace, key, value and type

but what i dont know, and it makes no sense
1. how does shopify sort / the fields after product & Variant metafields 

- because i see most of them inside the variant section...

2. does it even bother if the productmetafield is a variantmetafield ?

because this is my problem, the metafields appear as variant, even if they arent different from the rest of the whole parent group?

3. should we really just submit maybe just the meta's via the parent ? if they are all same ?

4. and for childs, we submit all values ? 

regards

[PaulNewton]

Hi @rob-it  Of course it matters, all of this depends on how the metafields are actually used.

But these are things you need to clearly define for yourself for the businesses needs.

If using storefront filtering down to the variant level leave the relevant metafields on the variants.

If using the metafields only for staff to be able to search for product info regardless of variant data then sure put em on the metafields.

etc etc etc

Really the only way to know is to step through your ENTIRE business process to find the business logic requirements.

Make some test products & variants and document the process of with product-metafields or with variant-metafields.

Not knowing this information about a business is a sign of bad information architecture and can cause serious growing pains or outright maintenance issues in the future.

If you need IA consulting or technical discovery then contact me by my email for services
Contact info in forum signature.
ALWAYS please provide context, examples: store url, theme name, post url(s) , or any further detail in ALL correspondence.

Good Luck.