I'm hoping I can get some hard-learned advice and opinions from folks that have had to grapple with the decision on whether or not to use Matrix Items. Or some advice from folks that did not but wished they had, or DID but think that in hind-sight it was not worth the hassle. We are getting our Item Master setup currently and have to decide. We have approximately 25,000 individual SKUs (Items) in our legacy platform. Mixture of Inventory, Serialized Assembly, and Kitted. About 10,000 to 15,000 of these could be grouped into 100 to 150 parent Matrix Items with approximately 100 sub items each.
A typical assembly item product for us might have a parent item with options for the following:
a. Agency (AMT or NCR)
b. Quality Grade (1,2,3,4,5)
c. Label Type (Large Label, Small Label, Rounded Label etc...) About 30 label types
d. Holder Type (White, Black, Red)
This seems like the perfect scenario for Matrix Items. Especially since we are just getting going with our Netsuite implementation. That said, some of the options are dependent on others, so we never would have all of the possible combinations. For example, IF Agency = "AMT", then only 10 of the Label Type values are possible. I mention this because after experimenting with Matrix Item creation I feel that we would always load our items via CSV because too many of the combinations are not needed or would need to have their item name/number values tweaked.
A typical sub item for a parent named 2017-WIDGETX would look like this:
2017-WIDGETX-AMT-5-LRG-BLK
Things that seem problematic.
1. We have a lot of existing Items (SKUs) which we cannot change the Item name for and they don't conform to the auto-generated Matrix Sub Item Names. For example, all of our historical SKUs that have a White Holder Type do not have the abbreviation for WHT at the end. Newer SKUs that have a Holder type = Black DO have the option abbreviation.
For example:
2017-WIDGETX-AMT-5-LRG (this sku actually is the sub item that has the WHT (White) holder type option)
2017-WIDGETX-AMT-5-LRG-BLK (this is the black holder option)
2. Due to item option dependencies, we only use about 10% of the possible combinations of options. So if a typical Matrix Item might have a possibility of 1000 sub items, we would typically only have items for 100 of them at most.
3. We have about 150-200 custom item fields in our items to support on-line listing in various e-commerce channels. Most of these custom item fields are the same for all of the subitems, but there are 5-10 custom fields that are different and need to be edited down to the sub-item level. So once the Matrix is setup, clicking the "UPDATE MATRIX" would overwrite these unique sub-item values with the generic parent item values.
Considerations:
1. We do NOT currently use SCA, but we "may" convert to it from our current website platform in a year or so.
2. We like the concept of using the Grid Order management functionality because we typically manage, replenish, and reprice the Items en-mass in groups that would correspond to the parent matrix item.
3. Every year the new year's version of many of these items come out, so for next year's new Items we could use the full item option naming conventions and standardize the item naming conventions going forward. (For example, we could have 2018-WIDGETX-AMT-5-LRG-WHT, and 2018-WIDGETX-AMT-5-LRG-BLK ). This reduces some of the item/name post-creation editing issues I mentioned previously.
If we will be loading and editing Matrix Items via CSV and not really using the UI for maintenance , what are the remaining benefits of setting them up as Matrix Items if we are essentially sending edits for every Sub Item individually anyway? Grid Order and possible SCA integration seem like the two primary benefits.
I feel like our scenario screams for using Matrix Items, and that it might be worth it to set them up from the beginning at Matrix items and deal with the little things hoping that eventually Netsuite makes improvements to things like item option dependency management, and customization of the parent to subitem field updating capabilities.
I apologize for the lengthy overview, but this seems like a crucial decision point with many ramifications, so just looking for any lessons learned from the Netsuite experts out there.
Thanks in advance for any insights, warnings, or gotchas that might apply.