6 Replies Latest reply on Jun 4, 2019 6:29 AM by Stefan Reinhardt

    Creating Kits Using PIM

    Shiva Bharamareddi New Member

      Hello all,


      Here is a use case I am trying to solve. We want to be able to associate items and products with other related items and products. The relationship could be of different types such as - Required Accessories, Optional Accessories, Replacement Parts, Similar Competitor Products etc. I tried exploring the Kits option that is available in PIM, but could not find much help anywhere. All I see in the Kits perspective is the ability to add a referenced item and the sequence. I don't see an option to add the association type such as Required Accessories, Replacement Parts etc. I also tried entering some invalid item numbers and PIM did not seem to care to see if this was a valid item. Also, obviously when doing such an association, we will be looking at building an import job to import this data. I could not see these fields in the Kits perspective as importable fields. What am I missing? Am I even headed in the right path to solve this use case?


      I have also put some thought around solving this by creating attributes for different types of associations with attribute value being a list of items. But I am not sure if that is the best practice. I first want to explore the features that are already available in PIM and use the best practices to solve this use. Thanks in advance for any thoughts you can provide around this.

        • 1. Re: Creating Kits Using PIM
          Stefan Reinhardt Guru

          Hi Shiva,


          the concept of Kits enhances the generic References capabilities. This means with Kits Product 360 allows you to group multiple single SKUs (Components) into a Kit SKU that will then be a sell-able item itself again.

          E.g. you sell a Play Station, a Controller and a Game each individually but also have an item called Play Station Bundle (Kit) that has each of the three mapped as component to it. Furthermore you could add a sequence for the components and could also define substitutes like either a red controller or a green controller.


          That the system allows to create references to IDs not (yet) in the system is on purpose. Imagine you want to import items that cross reference each other for example. Both sides the import would fail since the referenced object is missing in the system ;-)

          With the implementation however we allow to track references even if the actual object is not (yet) maintained in Product 360.


          Now to your general use case: I think you are good with just using the references entity here. We have an oob enumeration of reference types which can easily be adjusted to match the customer needs in the repository.



          1 of 1 people found this helpful
          • 2. Re: Creating Kits Using PIM
            Shiva Bharamareddi New Member

            Hi Stefan,


            Thank you so much for your answer. Your answer definitely pointed me in the right direction. The references

            feature should take care of what we are trying to accomplish.


            Have one more follow up question. We plan to be importing the referenced items from a BI system. Let us say an item had references to 5 items as accessories. In our incoming import file if we now only have 3 items as references for that item and these 3 items could be the same or completely different. How can we take care of deleting the existing reference and reloading the new references? Any idea on how to accomplish this?


            Thanks again!

            • 3. Re: Creating Kits Using PIM
              Stefan Reinhardt Guru

              Hi Shiva,


              what you are describing is a feature we are planning to ship with the next release of Product 360 as out of the box. For now a solution to this has to be done through customization.




              • 4. Re: Creating Kits Using PIM
                Shiva Bharamareddi New Member

                Thanks Stefan!

                • 5. Re: Creating Kits Using PIM
                  Mohsin Asif New Member



                  When we are creating kits, what do we exactly mean by "component type"? I get two options

                  1. Static

                  2. Variable


                  What do they mean? Thanks.



                  • 6. Re: Creating Kits Using PIM
                    Stefan Reinhardt Guru

                    Hi Mohsin,


                    this is a semantic thing we have worked into the data model. You can use it one way or the other.


                    A "static" component is a component that has no dynamic substitutes and its sequence is unique.

                    A "dynamic" component may have dynamic substitutes that use the same sequence.


                    Simple example:

                    Kit is an outfit of jacket shirt, paints and shoes.

                    If the shoes of the kit are static it can only be this one specific item (pair of shoes). If they'd be variable the Kit could have multiple possible shoes as components to chose one from.


                    Hope that makes sense.