The core functionality (of items, products). It's flexible to adjust to most retail product groups. Our catalogue has a lot of different niche attributes, and we somehow made all of these fit into the product model structure of InRiver.
The 'fluff'. Some areas seem to ambitious (like some of the merchandising functionality), whilst the core functionality should have gotten more product spend. This is not, however to say that there wasn't enough product spend in the core product. I just think that the additional functionality sometimes 'blurs' the user experience, giving some unnecessary noise.
I recommend being very clear on your requirements and vision for the product from the get go. The more input you can give from the very start, and the more you have prepared by means of knowing your product data model at heart before starting to implement, the more your project is likely to be a success.
The system is nothing but an optimisation of your current level of organisation and rigidity around your data management. If used to enhance this, InRiver can be a powerful tool to enhance the way your colleagues and customers interact with your products.
We solved the business problem of getting quality data onto our site in a standardised format.