Hi Jon,
The short answer is, it depends.
You can create your own product models and determine whether the data should be instantiated into the asset tables, the CMDB tables, or both. The big questions will be who will use data, how will the data be used, and is it best to leverage the existing processes around Asset and CMDB.
Taking your example of milk, if we are looking to track the location / quantity of milk on-hand in stockrooms, its cost, and automatically restock milk if we get low, and the contracts we have with vendors, then Asset is the way to go.
If we are looking to track the technical attributes of the milk, such as any illnesses that were caused by drinking the milk, we might also want it in the CMDB (which is related to Incident, Problem, Change, et cetera).
If we want a whole new way to look at milk, then you might consider a custom application or integrate with existing systems.
Professional Services or our Certified Implementation Partners can probably sit down with you and give you better guidance after gaining understanding of what you are looking to accomplish.
Hope this helps.
Cheers,
Joe
