Hi @Sironi ,
The whole Install Base setup with Sold Products is focused on digital services, which are different from physical products and assets, because they are deployed in a public or private cloud.
Thus a sold product basically is a service you're selling such as router maintenance, phone subscription, document management, etc... where as an asset is a physical product located at the customer's premises.
It leads to the situation where you perfectly can have both worlds next to each other, dependent on your business. Maybe you sell an application not running in the cloud but instead on a customer's server? That would be an asset.
Though, what if you for example sell additional packages for the application running in your premises and connecting with the application at the customer's premises? That would be a service and therefore a sold product.
The sold product in its turn can be related to Configuration Items, responsible for running the service appropriately within your premises. These can be used to track incidents, problems, changes etc...
It implies you can track on a case the sold product, product and asset. But not necessarily all of these would be filled in or applicable. Assume the customer wants to log an issue regarding the previously mentioned application; this would fill in only the asset & product on the case. It's "their asset".
On the otherhand, if the customer would like to report an issue regarding the additional packages of the application; a service which is ran by your company, the sold product & product would be filled in on the case.
Last note: a sold product doesn't always have to be a SaaS product though it's quite common. It also could be for example a maintenance service, hence you can link entitlements to a sold product, not dependent on any CI. To keep it simple: a sold product represents a business service.
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
