Hello all.
I am unclear as to what the required field of "Model" is meant for?
To be clear, my experience in product data are typically centered around working with either SKU's and/or Manufacturers Part Numbers MPN.....
I have not professionally encountered a reason to utilize a Model, or really understand where it would or should be used in product management?
Is this something that someone can provide me some example of for best practices?
It certainly does not keep me up at night, but I do agree for those that it does.
Please understand that my own experience revolves around distribution product data.
I just feel like there may be a logic to this that I have not encountered professionally, and wanted to understand what it may be applicable for.
What is strange to me is that from a data governance perspective - it is a required field, but is acceptable to have duplication.
This type of data parameter would be reflective of an item that may be part of a product series or a branding of items.
Why have a required field if you can technically create two items completely duplicated of each other where the absolute only difference would be the internal database item IDs?
Lastly, it is leveraged in the product list in the Admin, sales order, receipt, and reporting.
Technically allowing you to show two or more products that can be identical in the list and you would have to take an additional step to discover the different product, or confusing to someone that has to pack and ship an order as to which item should be pulled to send, or confusion in reporting.
Admittingly this may be a better inquiry to the developers.
Good to be here and to read this much informative stuff, Thanks a lot for providing this great article. Nice information.
Who is online
Users browsing this forum: No registered users and 13 guests
