Anders G. Nordby

Lead Software Engineer at Sopra Steria

Monthly Archives: August 2016

Considerations before an inRiver PIM Installation

One of the goals of implementing a PIM system could be create a more lively and dynamic web site. In this case, it is important to remember that the contents of your PIM system will need to be constantly updated; your site will be in a “forever beta” stage.

In the inRiver PIM system, the concept of a Product is cruicial. The Product entity contains everything that is the same for each Variant of the Product; e.g. a specific T-shirt will have some properties that vary for each variant (e.g. color and size), while other properties are fixed across variants (e.g. brand and materials). The Variant entity contains what is specific for each Variant, and contains a link to the Product. A Resource file (e.g. image or PDF) can be linked to either a Product or a Variant.

To optimize the flexibility of your inRiver PIM system, you should strive to have as many of your properties on the Product entity, and as few properties as you need on your Variant entity. For both entities, try to have as many CVLs (Controlled Value Lists) as possible, as this will reduce the risk of wrong or inaccurate input.

An important shortcoming when using the inRiver PIM together with Episerver Commerce, is that Episerver Commerce does not allow for outside systems, e.g. inRiver, to update package prizes. So creating a package consisting of several products, e.g. 1 table and 4 chairs, for a fixed package prize, is currently not supported in Episerver Commerce.